2021-07-28 Data Import Subgroup meeting
Recordings are posted Here
Slack channel for Q&A, discussion between meetings
Additional discussion topics in Subgroup parking lot
Attendees: @Ann-Marie Breaux (Deactivated) @leeda.adkins@duke.edu @Robert Scheier
Agenda topics: NOTE: This meeting is only relevant to libraries that plan to store MARC Holdings records in SRS
Review plans for MARC Holdings in SRS and linked to Inventory Holdings (Spitfire work in Kiwi and Lotus): Here
What fields of the Inventory Holdings would be editable if Holdings Source = MARC?
Recommend that these Inventory Holdings fields are editable if Source = MARC
Suppress from discovery
maybe Former Holdings ID (currently from 035$a of MFHD)
Statistical code
Temp location
Number of items
ILL policy
Digitization policy
Retention policy
Receiving history would be maintained in the Receiving app and only appears on the Inventory Holdings record, so doesn't need to be mapped
What if library creates Inventory instance, holdings, item at point of order, and then the holdings needs to be updated and tied to a MARC holdings?
At point of receipt, there is no MARC Bib or Holdings in SRS
Instance would need to change from source = FOLIO to source = MARC: this can already happen
Holdings would need to change from source = FOLIO to source = MARC; the holdings data is coming in on a MARC Bib, not a MARC Holdings
Could a draft MARC holdings be created from the Inventory holdings (and then clean up manually via QM if necessary)?
If loading approval plan records and creating holdings, could the MARC bib 9xx data be used to create a MARC Holdings?
Could the POL and/or Vendor Ref Number be used to match to the Instance, Holdings, and Item for updating them?
See additional comments and questions on the Spitfire spike linked above
Review the default mappings for Inventory Instance records from MARC Holdings records: the Folijet Inventory Holdings from MFHD tab Here
Review the quickMARC subgroup homework Here
Added a couple comments in the doc
To do's
Most important part is 1) making sure this is clearly documented, and 2) preferably, consistent, and 3) preferably, that implicit actions are acknowledged somehow in the import profile (A-M confirm with devs and document)