CVocConf analysis and design: decide which parts of the current schema apply per script and per field, address any overlaps (e.g. a script might by default allow free-text entries, with that setting overridable per field)
Open
Nobody has claimed this yet.
Feature: API
Feature: Controlled Vocabulary
Size: 10
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview
- Update the CVocConf configuration mechanism:
- Decide which parts of the current schema apply per script and per field, address any overlaps (e.g. a script might by default allow free-text entries, with that setting overridable per field)
- See also: https://github.com/IQSS/dataverse/issues/11278
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 reading the current CVocConf schema and the related issue #11278. Determine which settings belong at script and field scope and how overlapping defaults and overrides should be resolved; done means the configuration design and schema changes are explicitly decided.
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