--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/9dbcd175-9466-4197-bcf7-e357ad5103ean%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/a83c6d83-76bb-403a-9b9e-a1f35e0fac23n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAHGG%3DWYu0pjYUgQHmfe_ELQF1UxWZrHYevFMw74BxTD5B%2BCCgQ%40mail.gmail.com.
One thing that Dataverse already does that may be of interest is that it exposes Dataset-level metadata as json-ld in the OAI_ORE metadata export file. (This doesn’t currently capture the variable-level metadata for individual files in the Dataset (see below for plans), but does have all of the manually entered metadata for the Dataset along with the list of files with their names, paths, descriptions.) Many of the terms in Dataverse’s core metadata block have already been mapped to external vocabularies (e.g. Dublin Core, Schema.org) and it is possible to create new metadata blocks that cover domain-specific vocabularies (e.g. an initial DarwinCore metadata block was presented at the recent Dataverse 2020 meeting.).
You might also be interested in the Data Curation Tool recently created by Scholar’s Portal – it’s integrated using the external tools framework Danny mentioned. It allows editing of the DDI metadata and might serve as a model/something that could be extended to match column names to external vocabularies.
Related to that - one of the reasons this metadata wasn’t originally included in the OAI_ORE export I mentioned above is because that metadata was always machine generated by Dataverse and would be re-created if the file was re-imported. Now that it can be edited, I’m looking to add it to the OAI_ORE export where it would be easy to also expose mappings of that info.
-- Jim
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAFndDShTm88yWBSr59J8FFrYn2gR3mcf1ycRNwAGJrhnOMyT1g%40mail.gmail.com.