Data Import UI Changes for SRS MARC Holdings records

DRAFT - Still to be updated

• Ann-Marie Breaux (Deactivated) create draft page
• Ann-Marie Breaux (Deactivated)and Khalilah Gambrell review together
• Then review with Data Import subgroup (and quickMARC?)
• Determine which team and which release for the dev work

Developer research spike details 

Goal is to deliver basic work in Lotus, if possible; otherwise Morning Glory

Problem(s):

• Existing Data Import UI and logic mainly focuses on updating MARC Bibliographic records during Data Import. Review all UI screens and logic to determine what adjustments are needed for handling MARC Holdings records via Data Import

UI Screens to review

• Settings
  • Job profiles: no changes
  • Match profiles
    • Incoming records: turn on MARC Holdings
    • Existing records: turn on MARC Holdings
    • Headers in the matching section already work properly
  • Action profiles
    • Decide if Create and/or Update need to be enabled
    • Enable FOLIO record type: MARC Holdings
    • If MARC Holdings is enabled, what happens with MARC Modifications (or just update, like authority?)
  • Field mapping profiles
    • Incoming record type: enable MARC Holdings
    • FOLIO record type: enable MARC Holdings
    • TBD: Field mapping for MARC: Modify and Updates, or just Updates?
    • If updates, Allow any overrides to field protections? Allow update of individual fields only?
  • File extensions
    • Any additional default file extensions needed? No
  • MARC field protection
    • Any adds/edits to the text? Maybe - TBD
    • Add a note that MARC Authorities follow these field protections, but a library cannot override the field protections in individual job profiles
  • Data Import landing page: no change needed
  • Data import view all page: no change needed
  • Log detail: Holdings shows as SRS MARC and Holdings Created or Updated; hotlink to the Inventory holdings works
  • Log JSON: all fine, except add Holdings HRID in the header parentheses (where title is for MARC Bibs, Instances, Holdings, Items, Invoices)

• Still need to confirm whether any additional UI changes needed for
  • Inventory
  • quickMARC: check that multiple subfields without spaces do not cause save errors

Use Cases & Requirements:

Links 

SME Questions:

Basic workflow

What Backend stories are needed?

What UI stories are needed?

Developer Questions: