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

[jggautier]

What steps does it take to reproduce the issue?

• When does this issue occur?
  When trying to customize a Dataverse collection so that the Producer metadata field is hidden

• Which page(s) does it occurs on?
  The Dataverse collection "General Information" page

• What happens?
  It's not possible to uncheck the checkbox that would hide the Producer fields. The check box is greyed out or inactive.

• To whom does it occur (all users, curators, superusers)?
  Curators, superusers

• What did you expect to happen?
  The checkbox can be unchecked so that it's possible to hide the Producer field when people edit datasets in that collection

Which version of Dataverse are you using?
v.6.2, v5.10.1, v5.8.3 and possibly any version after the "conditionally required" feature (#7606) was added in v5.4.

Any related open or closed issues to this bug report?
#7606

Screenshots:

Producer field's checkbox can't be unchecked, so field can't be hidden

In a Dataverse instance I spun up on AWS, where I removed the conditional requirement of the Producer's Name child field in the citation.tsv file, I can uncheck the Producer field's checkbox to hide the field

[jggautier]

We ran into this when trying to help a manager of a collection in the Harvard Dataverse Repository hide the Producer field. So we haven't been able to hide that field.

[shlake]

This too came up at UVa. We want to remove the Producer field(s) from a collection and cannot.

Maybe a simple solution will be to change the tsv field for Producer Name to not be required.

[pdurbin]

@LauraHuisintveld just reported the same bug at https://dataverse.zulipchat.com/#narrow/stream/378866-troubleshooting/topic/Can't.20hide.20metadata.20field.20'Producer'/near/452519891

Here's the pull request where we added the concept of "conditionally required":

• 7551 expanded compound datasetfield validation #7608