DataverseFieldTypeInputLevels : better support for new Conditionally Required
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
In #7606 we added support for Conditionally Required metadata fields with minimal support to handle Dataverse level input levels (when you can make something required that isn't required by the installation).
We should review this and allow users to make Optional fields Conditionally Required, but this will require a larger design effort. (for example maybe we have 3 radio buttons, but then we'd also need extra logic, since once you make one subfield Required, the other subfields cannot be Conditionally Required.
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
Start by reviewing the support added in issue #7606 and the current DataverseFieldTypeInputLevels handling. Trace how Optional and Conditionally Required metadata fields are represented, then document a consistent design for radio-button choices and subfield constraints. Done means the design is agreed and the resulting behavior is specified clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100