crkn-rcdr / cihm-metadatabus

Documentation and Docker build environment for key portions of the metadata bus.
BSD 2-Clause "Simplified" License
0 stars 1 forks source link

Hammer2: order of identifiers becomes random. #74

Closed RussellMcOrmond closed 1 year ago

RussellMcOrmond commented 1 year ago

https://github.com/crkn-rcdr/cihm-metadatabus/blob/1554bebc5c93de8506d9f17b110c4eb294c1702e/CIHM-Meta/lib/CIHM/Meta/Hammer2/Process.pm#L236-L247

The method we are using to add in the {slug} and the part of the slug after the first "." (previously thought of as the {objid}, when AIP identifiers were defined as {depositor}.{objid}) , and remove duplicates, is causing the order of identifiers to change from what is expressed in the metadata. The order becomes the order of hash keys, which might as well be considered random.

RussellMcOrmond commented 1 year ago

For reference, the metadata-bus crosswalks DC, Issueinfo and MARC to CMR.

We moved from an XML XSD to a JSON schema a few years back, and continued enhancements to the JSON. There is a ticket to convert a spreadsheet used as documentation to something on GitHub, but that hasn't been completed.

CAP/Solr only use CMR. CMR is used with the Solr schema for Search and the fields displayed for the "Document Record" in CAP.

There are spreadsheets and metadata application profile (MAP) documents that were previously maintained by Julienne that provide documentation in more "human readable" formats of the crosswalks, CMR, etc.