Scripts and material related to using external vocabulary services with Dataverse
https://github.com/user-attachments/assets/4a4ba8c6-1ecb-473d-92d4-70051016fecb
This example manages the Keyword child fields (Term, Term URI, Controlled Vocabulary Name, and Controlled Vocabulary URL), providing OntoPortal based software lookup while also allowing free text entries (for entities that don’t have these identifiers) and manual entry of alternate identifiers for keywords.
This example requires the changes being added to Dataverse in PR #10331 PR #10371 PR #10404 PR #10503 PR #10505 PR #10603 packaged in v6.3.
This example requires two files:
(These scripts also use jquery and select2 which are already included in Dataverse).
This examples is entirely developed around AgroPortal, a fork of Ontoportal which contains more advanced features around languages API parameters than other OntoPortal installations as I write these lines. This means depending on the installation of OntoPortal, you may need to fix some javascript that suit your available functionalities. Be fully aware that integrating this example will not be easy as adapting or debugging the provided files may require to understand the full stack of the code (From OntoPortal API, passing by Javascript code to all related features hidden in Dataverse software code).
In cvoc-ontoportal-conf.json :
"headers": {"Authorization": "apikey token=<your_apikey>"}, is used to send api key in javascript frontend request and java backend request since OntoPortal required an api key for API usage. This is not architecturally safe but it’s a start. If you want to improved the security, you can develop a proxy that will embed the api key and allow only your domain using CORS rules."js-url": "https://raw.githubusercontent.com/gdcc/dataverse-external-vocab-support/main/scripts/ontoportal.js", is a way to invoke the javascript file in the dataset page but for production use it’s recommanded to have it hosted in your own machines."retrieval-uri": "https://data.agroportal.lirmm.fr/ontologies/{encodeUrl:keywordVocabulary}/classes/{encodeUrl:keywordTermURI}?lang=en,fr", used by java backend code to store in database and SOLR keywords values in specified languages. encodeUrl: is used to encode the URL of Keyword Term and any space in Vocabulary Name case."allow-free-text": true, allows users to enter keywords not found in the OntoPortal repository."vocabs": list of ontologies requested. We recommend restricting this list to a set of previously evaluated ontologies whose scope and quality you know."uriSpace": "http" http value is a trick that allows entering Terms URL that might be out of specified vocabularties uri spaces (java backend code validate Term URL by checking if it startsWith “http”)."managed-fields": are required in frontend management and to use field naming value feature in "retrieval-uri":."retrieval-filtering" we decided to store /synonym and /prefLabel values in database and map them in keywordValue SOLR field to improved SOLR research (allowing to search related dataset with two languages and via synonyms or prefLabel) using "indexIn": feature.In ontoportal.js :
ontoportal.js is constructed around free text typing possibility; In addition, it allows users to toggle view between four basic inputs fields to one selectbox for OntoPortal search.