2021-08-26 Metadata Management Meeting notes

Short meeting today.
2021-08-26 Product Council Meeting notes

No new updates

• Custom mapping profiles - determine priorities of supported properties: https://docs.google.com/spreadsheets/d/1XvHmToGQwhzmMNlQ5-l1QTEDyUtDpdn_/edit#gid=1869895650
• Default mapping profile - review remaining properties: https://docs.google.com/spreadsheets/d/11lGBiPoetHuC3u-onVVLN4Mj5KtVHqJaQe4RqCxgGzo/edit#gid=2007644603 (Instance to MARC 2021 tab)
• Exporting MFHD:
  1. 1. UXPROD-1396 Generating a simple MFHD from Inventory holdings record
     2. UXPROD-142 Export Inventory Holdings to MFHD records (with SRS MFHDs)

Distinction between Custom mapping profiles and Default mapping to help group assess the spreadsheets accurately. The two processes are very distinct from each other:

• mapping-preferences - spreadsheet that defines custom mapping profiles in data export. - These come into play when the user defines custom profiles in Settings/Data Export. A custom mapping. The fields seen when the user clicks on "Transform" is driven by the Custom mapping spreadsheet.
  
  
• recommended mapping - spreadsheet covers the properties that are part of the default mapping profile. Common use case for default mapping profile: Select records in Inventory > Actions - export Instances (MARC). The MARC record appears in the Data Export app directly from that action. The resulting default record has a 999 field with UUIDs from Source Storage, another from Inventory Storage

Question via chat : "Why wouldn’t all fields be available to be included in a custom export profile?"

Answer from Magda: Implementation was done field by field. Coding is required. 

Question via chat: "For someone fairly new to this, can you explain why we wouldn't want to export an entire record? Especially if it is a MARC record?"

Answer: Some information is not necessarily in the MARC that we do want to export. Suppress from discovery, for example.

Magda is going to talk to the development team about the possibility of having every field available for export, including the Inventory only information.

Ann-Marie, "Should add the Statistical codes and Nature of item to the list at the top of this spreadsheet"

Jennifer Eustis wondered if all administrative metadata could go into a 999 field and distinguished by indicators. Magda said this is something being done with OAI-PMH

Recommended MARC mapping to Inventory Instances (used in default mapping profile)

This spreadsheet is only for MARC generated "on the fly". At this point  you can have either SRS record or a record generated on the fly. Several members agreed that having MARC from the SRS along with some of the Inventory elements would be useful. 

Bob, via chat: "In Sierra all the non standard MARC are defined system wide for output mappings."

More admin data: Record updated_by, created_by  - returns the UUID for the user, but would be better if there is a name Need to check if this is compliant with GDPR

Identifiers - do you need to map the ASIN, BNB, CODEN, DOI, Handle, Local identifiers. Laura would put these in an 024. The identifier value could go into 024$a and the identifier type could go into an 024 $2. The first indicator should be a 7, the second indicator could be blank.

"There's also one new standard identifier type that was added for the Instance: Cancelled system control number"

VZG

Stanford

Missouri State University

Index Data