CVocConf development: Implement code, test code, docs, release note - standard dev issue. Includes adapting existing UI code to use the new configuration mechanism (which is hopefully mostly/all changes in the back-end, not JSF)
Open
Nobody has claimed this yet.
Feature: API
Feature: Controlled Vocabulary
Size: 80
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview
- Update the CVocConf configuration mechanism
- Development: Implement code, test code, docs, release note - standard dev issue. Includes adapting existing UI code to use the new configuration mechanism
- Note: this should be mostly/all changes in the back-end, not JSF
- 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 reviewing the related issue #11278 and locating the existing CVocConf configuration mechanism and its backend consumers. Identify the existing UI integrations that must be adapted, then cover the requested implementation, tests, documentation, and release note; done means the new mechanism is used consistently across those areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100