Don Richards (Mar 13 2026 at 14:53): Don Richards (Mar 13 2026 at 14:53):Quick question about metadata fields and the hide setting.
I marked a metadata field as hidden, expecting that it would no longer appear in the Create/Edit Dataset form in the UI. However, when I try to create a new dataset, the field still shows up in the form.
My understanding was that setting a field to hidden should remove it from the dataset metadata UI entirely, but that doesn't seem to be happening.
Am I misunderstanding how the hide property works for metadata fields? Or is there another step required (for example updating dataset forms, reloading metadata blocks, or clearing some configuration)?
For context, I'm testing this while creating a new dataset and expected the field to be completely hidden from the form.
Any guidance would be appreciated, thanks!
Philip Durbin 🚀 (Mar 13 2026 at 14:56):Hmm, it is possible you're hitting this bug? Setting a field to 'hidden' is not working #11992
Philip Durbin 🚀 (Mar 13 2026 at 14:58):No release note snippet for it in #12017... hmm, I should probably add this to the 6.10 release notes (#12208) anyway. (That's where #11992 was fixed, in #12017.)
Don Richards (Mar 13 2026 at 15:00):I don't think so.
- Add a dataset. I expected these fields not to be visible when creating a new one, but I still see them. Also, if you revisit the 'General info' page, the boxes are checked again, indicating the changes have not been saved.
For us the "the boxes are checked again" isn't accurate.
Philip Durbin 🚀 (Mar 13 2026 at 15:01):Woof. Do you want to try it on https://beta.dataverse.org, which is running the latest in the develop branch? In case it got fixed in 6.10, which is due out soon? See #community > Release 6.10 Timeline
Philip Durbin 🚀 (Mar 13 2026 at 15:10):Anyway, I updated the upcoming 6.10 release notes to mention the bug fix we added for #11992.
Don Richards (Mar 13 2026 at 15:13):Sure, but it doesn't look like I have the ability with my login to modify the fields.
Philip Durbin 🚀 (Mar 13 2026 at 15:14):No? Can you create your own collection (dataverse)?
Don Richards (Mar 13 2026 at 15:16):
It doesn't appear to allow me that access from the look of it.
Don Richards (Mar 13 2026 at 15:17):https://beta.dataverse.org/dataverse/testingfields/
Philip Durbin 🚀 (Mar 13 2026 at 15:18):What if you uncheck that box called "Use metadata fields from Root"?
Don Richards (Mar 13 2026 at 17:19):Everything but Citations becomes available.
Philip Durbin 🚀 (Mar 13 2026 at 17:24):Ok, good. Now, if you click "[+] View fields" you should be able to mark fields as hidden. Does that work?
Don Richards (Mar 13 2026 at 17:30):OK, easy instructions to replicate the issue and a workaround.
From the new Dataverse > Edit > General Information
Metadata Fields > Citation Metadata (Required) > [+] View fields + set as hidden, required, or optional > Uncheck Subtitle > Done > Save Changes
From the new Dataverse > Add Data... > New Dataset
Citation Metadata > Subtitle is still viewable
The work around:
The "Required" is the trigger.
From the new Dataverse > Edit > General Information
Metadata Fields > Citation Metadata (Required) > [+] View fields + set as hidden, required, or optional > Check it back select "Required" > Done > Save Changes
Then try it again
From the new Dataverse > Edit > General Information
Metadata Fields > Citation Metadata (Required) > [+] View fields + set as hidden, required, or optional > Uncheck Subtitle > Done > Save Changes
Broken Configuration:
Working Configuration:
If it's required when you set it to "hidden" it actually hides the field, otherwise if it's set to "Optional" it optionally hides it.
Philip Durbin 🚀 (Mar 13 2026 at 17:37):My head is swimming a bit. Do you want to create an issue about this?
Don Richards (Mar 13 2026 at 17:37):No, I just realized it's an actual bug.
Philip Durbin 🚀 (Mar 13 2026 at 17:38):If it's a bug, we should probably have an issue, right? :smile:
Don Richards (Mar 13 2026 at 17:39):Working on the Github ticket now
Philip Durbin 🚀 (Mar 13 2026 at 17:39):Awesome, thanks!
Philip Durbin 🚀 (Mar 13 2026 at 17:41):I wonder if this bug exists in the new UI: https://beta.dataverse.org/spa :thinking:
Maybe I'll ask you to test there next, if you're willing! :sweat_smile:
Don Richards (Mar 13 2026 at 17:48):https://github.com/IQSS/dataverse/issues/12216
Don Richards (Mar 13 2026 at 17:49):Sure I'm willing to test whenever
Don Richards (Mar 13 2026 at 17:49):I did my testing in the beta site.
Philip Durbin 🚀 (Mar 13 2026 at 17:53):The issue looks great. Thanks! I did make a small edit to indicate which commit the beta server is on (this changes every time we merge a pull request into the "develop" branch).
Philip Durbin 🚀 (Mar 13 2026 at 17:54):Right, so the beta server has the old JSF UI, which you tested, and the new React UI, which is found at /spa.
Philip Durbin 🚀 (Mar 13 2026 at 17:54):Fingers crossed but I'm hoping the new UI works the way we want it to! :sweat_smile:
Last updated: Apr 03 2026 at 06:08 UTC