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
1. What fields of the Inventory Holdings would be editable if Holdings Source = MARC?
  1. Recommend that these Inventory Holdings fields are editable if Source = MARC
    1. Suppress from discovery
    2. maybe Former Holdings ID (currently from 035$a of MFHD)
    3. Statistical code
    4. Temp location
    5. Number of items
    6. ILL policy
    7. Digitization policy
    8. Retention policy
  2. Receiving history would be maintained in the Receiving app and only appears on the Inventory Holdings record, so doesn't need to be mapped
2. 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?
  1. At point of receipt, there is no MARC Bib or Holdings in SRS
  2. Instance would need to change from source = FOLIO to source = MARC: this can already happen
  3. 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
    1. Could a draft MARC holdings be created from the Inventory holdings (and then clean up manually via QM if necessary)?
    2. If loading approval plan records and creating holdings, could the MARC bib 9xx data be used to create a MARC Holdings?
  4. Could the POL and/or Vendor Ref Number be used to match to the Instance, Holdings, and Item for updating them?
3. 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
1. Added a couple comments in the doc

To do's

Confirm Rancher environment for Data Import/quickMARC testing (Khalilah and Ann-Marie) - IN PROCESS
Data Import FAQ updates (Ann-Marie) - IN PROCESS
Make videos confirming the following scenarios
- For import profiles that match on Holdings or Item IDs (and doesn't need to affect the Instance), make a video showing what happens to SRS MARC (Ann-Marie)
- For a brief MARC updating the suppress status on a group of instances. What happens with the SRS MARC (A-M)
Talk with Kimie and see if ideas for updating the UI for implicit (A-M)
If a profile has update instance (to update cat date) which has an implicit update MARC, and also an update MARC (with implicit update instance) that has field protections, will the field protections be honored by the update instance? (A-M to check with devs)
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)
1. QM edit: increments
2. Import MARC Modify: increments, we think
3. Import MARC Update: does not increment
4. Import Instance Update (implicit MARC update): increments

Browser not supported