Feature Request: API or admin functionality to remove or deactivate specific controlled vocabulary
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Request an API endpoint or admin functionality to remove or deactivate specific controlled vocabulary values from a custom metadata field in Dataverse, especially when duplicates or incorrect entries exist.
What kind of user is the feature intended for?
API User, Curator, Superuser, Sysadmin
What inspired the request?
We accidentally created duplicate entries in a controlled vocabulary list for a custom metadata field (AffiliatedDept). We attempted to re-upload the TSV file without the incorrect value, the outdated entry persisted in the system. This highlighted the lack of a straightforward method to remove or deactivate individual vocabulary items via API or admin interface.
What existing behavior do you want changed?
Currently, once a controlled vocabulary value is added to a metadata field, there is no convenient method to remove or deactivate it through the API or admin tools. Even re-uploading the TSV file without the incorrect value does not eliminate it from the system.
Any brand new behavior do you want to add to Dataverse?
Deletion of a specific controlled vocabulary value. Optionally, deactivation or hiding of values without full deletion
Any open or closed issues related to this feature request?
This request is based on a community discussion thread titled “We are struggling in the issue of removing incorrect value of controlledVocabulary” on the Dataverse Community Google Group. But seems that there are no other ralated open/closed issues.
Are you thinking about creating a pull request for this feature?
Sorry. we have no resources to so it.
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
No files, tests, or entry points are named in the issue. Start by locating the existing controlled-vocabulary API and admin functionality, then determine how individual values are persisted and referenced. Done should provide a documented way to delete or deactivate one selected value without affecting the rest of the vocabulary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100