Cannot save multiple kind of metadata block modifications at once
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
- Edit "General information" of a dataverse
- Edit metadata block with both "hide" and then "mandatory"
- Save
What happens?
The mandatory option is not saved
To whom does it occur (all users, curators, superusers)?
superusers
What did you expect to happen?
All modifications are correctly saved
Which version of Dataverse are you using?
5.3 but it was also reproduced on demo.dataverse.org
Any related open or closed issues to this bug report?
Not found
Screenshots:
In the video, you can see when I save a metadata block only the "hide" is saved but not the "mandatory".
Thanks
As always, thank you for your services in Dataverse community.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the dataverse metadata block editor by changing both “hide” and “mandatory” before saving, then trace the save entry point and persistence handling. Confirm the fix by verifying that both options remain enabled after saving and reopening the metadata block.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100