CVOC : Multiple services for 1 term field
@qqmyers is already working on this.
Since Feb 23, 2026.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Following the last Community Call August 22, 2023 Notes it appears that it would be nice to have one issue describing a new use case of external vocabulary using the supported generic external vocabulary support mechanism of Dataverse.
Right now, the setting :CVocConf (that uses a configuration file cvoc-conf.json as value) allows to implement 1 service url for 1 field (or a group of 1 parent field and many childs fields).
For our Dataverse, we are thinking about having multiple services for the same bloc of termName/vocabularyUri fields.
For example :
- https://thesaurus.inrae.fr/thesaurus-inrae/fr/ (SKOMOS)
- https://skosmos.loterre.fr/en/ (SKOMOS)
- https://agroportal.lirmm.fr/ontologies (OntoPortal)
This feature mainly concerns the java code which will have to manage the cache and indexing needs for the multilingual search results (search result page/api and dataset metadata tab view) of each service while the javascript modifications only concern the dataset edit view.
Feedback: Each instance is working well independently using the generic external vocabulary mechanism with the good configuration of the json file.
@qqmyers @4tikhonov @qqmyers @DS-INRA
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.
Assessment
This issue has not been assessed yet.