Bug #2964
Incorrect Metacat ORE SystemMetadata
100%
Description
When Metacat generates SystemMetadata for a generated ORE document it attempts to mirror the revision history of the {EML} datapackage it is describing.
This works fine for non-DOI identified packages, but the identifiers in the obsoletes/obsoletedBy fields for DOI-identified packages have the incorrect identifiers. They include the resourceMap_ prefix before the DOI prefix which is not how the actual resourceMap objects are identified.
The correct resourceMap identifier is in the form:
"resourceMap_{localDocid}"
whereas the obsoletes/obsoletedBy are in the form:
"resourceMap_{doi_prefix}/{localDocid}
For example:
https://mn-stage-ucsb-1.dataone.org/knb/d1/mn/v1/meta/resourceMap_bowdish.217.1
reports to be obsoleted by:
resourceMap_doi:10.5072/FK2/KNB/bowdish.217.2
when it should be:
resourceMap_bowdish.217.2
so that we can get to the next version:
https://mn-stage-ucsb-1.dataone.org/knb/d1/mn/v1/meta/resourceMap_bowdish.217.2
which also has an incorrect obsoletes element:
resourceMap_doi:10.5072/FK2/KNB/bowdish.217.1
This can be manually fixed in the Metacat DB if anyone does generate the invalid SystemMetadata, but an updated Metacat version should be made available with this fix before we begin generating ORE maps in production.
History
#1 Updated by Ben Leinfelder over 12 years ago
- Category set to Metacat
- Status changed from New to Closed
Released a Metacat 2.0.1 with this fixed. Also incorporates as better URI scheme for ORE "aggregations" so that within a given resource map, the aggregation URI incorporates the map it is contained in rather than being a generic [nonunique] filler URI