Only a partial identifier, and a prefix needs to be added
These were allays a hack, using identifiers created for other purposes to link to identifiers used by the software we are using to provide patron access. These other fields regularly have incomplete identifiers ("CIHM numbers", etc), or otherwise custom as was done for "oocihm" and "ooe" when modifying the record to match current technology enabled better interoperability.
Ideal is if we move entirely to using the "856 - Electronic Location and Access" field, which needs to be encoded in our records for other purposes anyway. This is likely what we'll need in the future, such as if we adopt and integrate FOLIO and Blacklight.
If there are multiple matches, be helpful in detecting if all the identifiers point to the same Access object and report otherwise.
Report back the slug that is referenced, which what staff would see in the existing https://access.canadiana.ca/dmd interface.
Ideally if both MARC and DC CSV files use full Slug identifiers, the added step of optionally adding a prefix can be removed from https://access.canadiana.ca/dmd
The descriptive metadata loader currently supports looking up identifiers in MARC in 3 different ways:
"marc490"
"oocihm"
"ooe"
These were allays a hack, using identifiers created for other purposes to link to identifiers used by the software we are using to provide patron access. These other fields regularly have incomplete identifiers ("CIHM numbers", etc), or otherwise custom as was done for "oocihm" and "ooe" when modifying the record to match current technology enabled better interoperability.
Ideal is if we move entirely to using the "856 - Electronic Location and Access" field, which needs to be encoded in our records for other purposes anyway. This is likely what we'll need in the future, such as if we adopt and integrate FOLIO and Blacklight.
https://www.loc.gov/marc/bibliographic/bd856.html
What our software would do: