-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend metadata keywords with Voc4Cat vocabularies #8
Comments
Dataverse 6.3 brings improved "External Vocabulary Services" functionality. In the examples, connecting to SKOSMOS (a web based SKOS browser and publishing tool) is demonstrated. So, after the planned update to 6.3 (#9, #26) and if TS4NFDI sets up SKOSMOS as announced, we should be able to integrate voc4cat via the skosmos-API as in the examples in https://github.com/gdcc/dataverse-external-vocab-support/ |
We have to contact TS4NFDI about some incubator project for SKOSMOS service - https://base4nfdi.de/projects/ts4nfdi (contact point - RB). |
I contacted them (@rombaum) in NFDI chat last week and they are interested (for Q1-2025). |
Roman informed me today that their widgets can already use Skosmos-APIs for autocomplete [1] or to retrieve hierarchies [2]. So we could already explore now, if using the TS4NFDI widgets is a viable option to integrate SKOS-vocabularies in dataverse or if the route linked in the first message is the way to go. [1] https://ts4nfdi.github.io/terminology-service-suite/comp/latest/?path=/story/react_autocompletewidget--use-api-gateway-with-skosmos |
FYI. Repository "bonndata" is using own SCOS server for external metadata - for field "subject". Connection to ORCID for author was little bit customized compare to basic Dataverse scripts. Updates of vocabularies and updates of Dataverse do not bring problems, so using is good. Versions of ontology look like also referenced. |
Try to use "flexible metadata" to integrate Voc4Cat vocabularies into "citation" metadata. Use SKOS, DCAT.
See here: https://guides.dataverse.org/en/latest/admin/metadatacustomization.html#using-external-vocabulary-services
The text was updated successfully, but these errors were encountered: