--
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/b0ef6d57-e95f-4314-b4da-dd114b062c99%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/b0ef6d57-e95f-4314-b4da-dd114b062c99%40googlegroups.com.
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/b0ef6d57-e95f-4314-b4da-dd114b062c99%40googlegroups.com.
--Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
--
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/1c3597ee-6c0c-4226-b8b1-f8cc386eed9e%40googlegroups.com.
DarwinCore Version without groups:
https://docs.google.com/spreadsheets/d/1P2y8Kz9pDJlZhPiZiT5EoJAeZGvUOPR1gZh8T3gIMw0/edit?usp=sharing
DarwinCore Version with groups (parent):
https://docs.google.com/spreadsheets/d/1p_myNEdbV-afBaF7D-I__-3CyybY8oiR3zP2VsyrKqU/edit?usp=sharing
Kamil,
Nice to see a block associated with an external vocabulary with an RDF mapping!
FWIW, the metadata block you’ve created can be more directly tied to the Darwin Core RDF terms with a couple minor changes. Your block made me realize that the info on how to do that isn’t in the docs yet, so I just created a pull request (see https://github.com/IQSS/dataverse/pull/6548 ). The benefit to be had is that info from this block will be correctly serialized in JSON-LD in the OAI_ORE metadata export and the archival zipped Bags that Dataverse can create. The OAI_ORE file can be parsed by RDF/JSON-LD aware programs to pull out the Darwin Core info.
There are two options for a change.
· Since it looks like DWC prefixes all terms with http://rs.tdwg.org/dwc/terms/, you could set that as the blockURI and remove the ‘dwc’ from your term names (Dataverse appends the property name to the blockURI to create the term.) Using this option, if you also renamed the block to dwc, the JSON export would look like:
{
“dwc:type”:”<type value>”,
“@context”:{
“dwc”:”http://rs.tdwg.org/dwc/terms/”
}
i.e. the block name is used as the prefix, so the export would look similar to your current term naming with the dwc prefix.
· Alternately, you can define the termURI for each term, e.g. http://rs.tdwg.org/dwc/terms/type for ‘dwcType’. This would allow you to keep the term names as they are, but you’d have to define the termURI for each property in the block. (In JSON-LD, this results in
{
“dwcType”:”<dwcType value>”,
“@context”: {
“dwcType”: “http://rs.tdwg.org/dwc/terms/type”,
…
}
}
with additional entries for each term in the @context – so similar but a bit more verbose.)
These are definitely optional changes, particularly given the discussion about further changes to Dataverse’s metadata handling, but they might be useful in a new block.
Cheers,
-- Jim
--
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/08e73bef-6870-46a3-8149-bce405b6b7ff%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
Kamil,
I think you’re right, and that ought to be reported as an issue (metadatablocks must have unique terms (independent of any semantic web links) – it looks like that is documented in http://guides.dataverse.org/en/latest/admin/metadatacustomization.html but it seems like something that could/should be fixed in a metadata redesign). As you say, the second option is probably the best way to go then.
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/08e73bef-6870-46a3-8149-bce405b6b7ff%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/d2436d07-8b93-4f92-84ae-3c1e8ea70505%40googlegroups.com.