GBIF Testing Work Plan Google doc¶

9/24/18: {Rob} - I did a quick test of the member node instance at https://ws.gbif-uat.org:7000/mn/ and only see a few minor problems - mostly to do with format identifiers.

9/25/18 {Federico} - fixed some issues in our DataOne implementation, we also exported an old GBIF snapshot using the ORE resource map format (similar to eBird)

per Rob - The main things I saw seem relatively minor:

1. formatIDs • for the resource map should be "http://www.openarchives.org/ore/terms" • for the metadata object should be "eml://ecoinformatics.org/eml-2.1.1" • (for the data object is OK as "application/zip")
2. resource maps (OREs) need to use identifiers that match the GUIDs used in list objects. Reciprocal relationships also need to be defined.

Below is the basic template that should work for you:
(For more information please see https://releases.dataone.org/online/api-documentation-v2.0.1/design/DataPackage.html#generating-resource-maps)

rdf:RDF

rdfs1:labelResourceMap/rdfs1:label
rdfs1:isDefinedByhttp://www.openarchives.org/ore/terms//rdfs1:isDefinedBy
/rdf:Description




dcterms:identifier${ORE_GUID}/dcterms:identifier
dcterms:created24-07-2017/dcterms:created
dc:formatapplication/rdf+xml/dc:format
dcterms:modified24-07-2017/dcterms:modified
/rdf:Description

rdfs1:isDefinedByhttp://www.openarchives.org/ore/terms//rdfs1:isDefinedBy
rdfs1:labelAggregation/rdfs1:label
/rdf:Description




/rdf:Description

dcterms:identifier${METADATA_GUID}/dcterms:identifier


/rdf:Description

dcterms:identifier${DATA_GUID}/dcterms:identifier


/rdf:Description
/rdf:RDF

9/25/18 - {Marcos} - applied the 2 changes

1/28/19: Marcos confirm: I did that change to include the originMemberNode field in the SystemMetadata.