Analysis, design, scoping: Propose a specific set of tables and API calls to get/set scripts and fields, along with any overall listScripts/listFieldsAPI calls/changes to existing API calls (e.g. to the metadatablock api?) the SPA might need (could be a separate subtask/separate scope if needed)
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
- Propose a specific set of tables and API calls to get/set scripts and fields, along with any overall listScripts/listFieldsAPI calls/changes to existing API calls (e.g. to the metadatablock api?) the SPA might need (could be a separate subtask/separate scope if needed)
- With corresponding SPA analysis task
- 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 with the CVocConf configuration mechanism and the related issue #11278. Define the proposed tables, script and field APIs, any listScripts/listFields or metadata block API changes, and the related SPA analysis scope; the work is done when this concrete design is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend-api-design, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100