2024-1-17 Data Import Subgroup meeting

Recordings are posted Here (2022+) and Here (pre-2022) Slack channel for Q&A, discussion between meetings

Requirements details Here Additional discussion topics in Subgroup parking lot

Attendees:

Notetaker: Jennifer Eustis, Corrie Hutchinson, Christie Thomas

Links:

Agenda:

- Quesnelia Status Update
  - Quick update on how Quesnelia is moving along so far.
- UXPROD-2742: MARC-MARC matching enhancements: Narrowing multiple matches & Bug work
  - Discuss use case scenario provided by Jennifer Eustis.
    - The 5 Colleges consortium has a shared instance. We often shared bibliographic records. To keep track of these records, we use what we are calling a container code in the MARC field 035 9\$a. This code has the prefix of one of the schools in the consortium (if the eResource is for 1+ then we use 5c or FC as the prefix) followed by some designation and a unique number. For example, UMass' Springer container code is (UMSPR)document_identifier. For our JSTOR open access, we use FCJSTOROA followed by the linking text. Sometimes we purchase packages that aren't exactly the same coverage. Typically in that case, we add our own container codes for the shared resource. For example a bib record might have (UMSPR)uniqueID and (ACSPING)uniqueID and so on. We need to be able to match on the existing 035 9\$a as an exact match where the existing marc srs can potentially have more than more 035 9\$a and our match might be the 1st, 2nd or 3rd in the order of those 035 9\$a's in the existing record. The issue is to be able to match to a repeating field. This applies to a marc to marc match as well as a marc to instance system control number match.

Upcoming meetings/agenda topics:

Chat: