Skip to content

Conversation

@qqmyers
Copy link
Member

@qqmyers qqmyers commented Nov 20, 2025

What this PR does / why we need it: This PR makes the change suggested in #8690 to not require the producerName so that the producer field becomes optional.

Which issue(s) this PR closes:

Special notes for your reviewer: There's discussion in the issue. If we want to set producerName to not be required at the block level, this PR will do it. (Probably should include a release note w.r.t. how to set it to required at the root Dataverse level if you want for backward compatibility, and with the usual instructions for updating the block. Happy to add that when I get back.)

Suggestions on how to test this: Testing requires a fix for #11992 - e.g. PR #12017 .Once that is available/merged, you should be able to check in the UI that it is now possible to uncheck the Producer field on a given Dataverse and verify that the field no longer shows for datasets created within it.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

@qqmyers qqmyers moved this to Ready for Triage in IQSS Dataverse Project Feb 4, 2026
@qqmyers qqmyers marked this pull request as ready for review February 4, 2026 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Ready for Triage

Development

Successfully merging this pull request may close these issues.

Dataverse collection managers can't hide the Producer metadata field, and possibly any field with a child field that's conditionally required

1 participant