2021-08-04 Data Import Subgroup meeting

Owned by Ann-Marie Breaux (Deactivated)
Last updated: Aug 04, 2021
3 min read

 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 Jennifer Eustis Nick Cappadona Robert Scheier Mark Arnold, Lloyd Chittenden Christie Thomas Jenn Colt

Development update: 

  • Finishing Juniper
    • Linking POLs to EDIFACT invoice lines is part of Juniper
  • Current Kiwi development
  • Current bugfixes
  • Spitfire starting work on storing MARC Holdings in SRS and mapping to Inventory Holdings 
  • Sprint demo (A-M add link): 1) PTF work on Data Import stability and performance, 2) linking POLs to imported invoice lines

Agenda topics: Matching and Updating Multiple Record Types

Use Cases

  1. Creating, then updating Instances and Holdings for Films on Demand; see outline here
    1. Missouri State - get 2 files - 1 for West Campus and 1 for Main
      1. 2 locations, e.g. West Plains Electronic and Meyer Electronic
    2. Each have their own 856, on separate MARC records
      1. Need to have MARC field protection so that the first one is not removed/deleted
      2. Maybe could put the 856 into the holdings record, and then MARC modification to remove from the MARC Bib
    3. Christie has tried option 2 for instance, holdings, item and it didn't work
      1. Instance match 035 to System control number, Holdings static match to UCHPUCX, Item static match to Status On order
    4. Jennifer E has tried Instance match on 035, then Holdings status match to location or static text in a note, and then item static match on status or note
      1. would it be possible to match on Stat code? Have not been able to get it to work yet
    5. Useful match tip: Static match Begins and then just use the first letter or number of the HRID
  2. Creating Instance, Holdings, Item for ordered material, then updating Instance, Holdings, Item with MARC Bib
  3. Should we start an area here for sharing Job profiles, Matching tips and tricks, etc?
    1. Add info about the labs there (and the zoom link) - Jenn will remake the link and add to the DI channel
    2. Add info about shared rancher for experimenting, after a few more details are worked out
  4. A-M to start the matches page in Tips and Tricks
    1. If you want to match on location, do this
    2. If you want to match on OCLC number, do this

Questions:

  • Matchpoints in the above scenarios: see MODDATAIMP-399 for order-related matching
    • Data Import will explore and see how soon we can implement, but it relies on Acq features as well (get number)
    • Yes, would be useful - if the POL is moved to a different instance, then the shelfready record would move with it 
      • Ask Dennis - can the POL-instance link be changed?
      • Further goal: How could the shelfready updates also accomplish the receiving?
  • From chat: what about deletes? How are people handling them since MARC Bibs and Instances cannot be deleted?
    • A-M add link to the Deleting user portion of the 3 August 2021 Sprint demo; could be useful for instances

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