/
2023-10-25 Data Import Subgroup meeting

2023-10-25 Data Import Subgroup meeting

Oct 25, 2023

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: @Ann-Marie Breaux (Deactivated) , @Ryan Taylor , @Christie Thomas , @Corrie Hutchinson (Unlicensed) , @Jeanette Kalchik , @Jennifer Eustis , @Lynne Fors , @Raegan Wiechert , @Taylor Smith @Kim Wiljanen , @Yael Hod 

Links:

Agenda: 

  • Check in on Poppy Bugfest

  • Discuss UXPROD-4080: Review and fix MARC Updates for specific fields

    • Please bring specific examples of scenarios where you would like fields to behave differently in MARC Updates.

    • What does this option mean

      • Import a MARC record - keep the existing and just add this field from the incoming record

        • Example 1: only add the OCLC 035 to the existing record; ignore the rest of the incoming record

        • Example 2: match on OCLC number, add new 856 from the incoming record; ignore the rest of the incoming record

      • 2 kinds of updates

        • Overlay everything

        • Only update specific fields

      • In previous system, these were called merges

    • What is the simplest functionality that we could provide (most reliable and most easily understood, least development effort)

    • For repeatable fields

      • Delete existing and add this one

      • Add this one, don't touch the existing ones

      • Find a specific one and remove, then add this once the other is removed (might have to be a separate sequential process) (as a way of changing a particular field)

    • Would anyone ever be trying to update non-repeatable fields with this functionality?

      • Info from field protections page:

        • Non-repeatable: LDR, 001, 002, 003, 004, 005, 008, 009, 010, 018, 036, 038, 040, 042, 044, 045, 066, 073, all 1xx fields, 240, 243, 245, 254, 256, 263, 306, 357, 378, 384, 507, 514, 663, 664, 665, 666, 675, 682, 788, 841, 842, 844, 882, and 999 with indicators = ff

          • Note that the fields 001  and 999 ff are restricted for FOLIO use and automatically protected by the system

          • The following non-repeatable control fields are disallowed from field protection: LDR, 002, 003, 004, 005, 009

        • Repeatable: all other MARC fields

        • Control fields:

          • The following control fields are disallowed from Field protection: LDR, 002, 003, 004, 005, 009

          • The following control fields are allowed for Field protection, but no indicators or subfields are permitted: 006 (R), 007 (R), 008 (NR)

    • How does this mesh with bulk edit functionality? Talk with Magda - are there patterns there that we could use

    • What are data import scenarios vs bulk edit scenarios

      • Adds - more often import with new data

      • Changes - possible import, possible bulk edit

      • Varying data - more often import 

      • Constant data - possible import, probably easier with bulk edit (e.g. change http to https)

    • Can we borrow patterns from Inventory repeatable field actions, or the Modify actions?

    • Clarify Modifications functionality (maybe add an info icon?)

      • At the start of a job profile, acts on an incoming record

      • At the end of a job profile, acts on that incoming record that has now been saved

      • Not appropriate to have a Modify action in a job profile without another action (Create or Update)

 

Upcoming meetings/agenda topics:

 

Chat

Lynne Fors  to  Everyone 1:07 PM
I'll be honest, I haven't started yet. Planning for tomorrow

wiljanen  to  Everyone 1:27 PM
I'll have to catch up later

Jennifer Eustis  to  Everyone 1:32 PM
+1 Christie. This is really a merge where you add fields from the incoming marc to the existing srs marc

Jennifer Eustis  to  Everyone 1:45 PM
find and remove might work
like find (OCoLC)

Jennifer Eustis  to  Everyone 1:59 PM
I have to get to my next meeting. See you next week.

Christie Thomas (she/her)  to  Everyone 2:01 PM
That is right.
I had forgotten that.