2026-04-22 Data Import SIG Workshop Meeting

Item

Announcements

Remember to use our https://folio-org.atlassian.net/wiki/spaces/DISIG/pages/1728741396 to sign up for taking notes or jot down a discussion item for the SIG.

Any Updates from developers @Ryan Taylor ?: Update instance, holdings, and item in reverse order (Line 6 in New Topics spreadsheet.)

No update yet, developers need more time to do a deep dive. @Ryan Taylor will bring it to them again.

Testing

Updates from Technical Council

TC spent time at this morning's technical council meeting discussing a process that could have surfaced the "bug" that we are discussing today. It was more focused on how to locate these types of changes to the UI.

TC meeting: https://folio-org.atlassian.net/wiki/x/AYBAcQ

• Disconnect/gap between business (user) requirements versus technical requirements.

• How do we understand and know how changes to technical requirements impact business (user) requirements?

• How do we surface these issues?

Discussion (Continued from 4/8): https://folio-org.atlassian.net/browse/MODDATAIMP-1290

https://folio-org.atlassian.net/browse/MODINVSTOR-1363

https://folio-org.atlassian.net/browse/MODSOURCE-962

How does the system decide that a record is redundant? @Ryan Taylor is working on how the determination is happening. Will post in Slack when more information is available.

Thorough documentation of this process is needed to move forward.

Does the determination of exact matches actually save resources when compared to overriding/updating as previous?

What are the benefits of this in terms of optimization?

What are the impacts on future performance?

Non-proliferation of records versions? Storage and version history impacts on future performance/development.

Nothing changes to the record if it is identified as an exact match, so last updated date and the user won’t be changed.

Log issues need to be addressed to reflect what is actually happening.

Need to be able to override. Potential impacts to data cleanup. Diacritics example: display to the user the same way but coded in differently (pre-coordinated vs. post-coordinated)

Develop https://folio-org.atlassian.net/browse/UXPROD-4080 Created in 2023.

Developers need SME use cases and examples.

Current Examples in this Jira as of Apr 22, 2026 :

• Example 1: Incoming MARC Bib only has Leader, 245, 856. Library only wants to update the existing 856, but not replace the rest of the existing MARC Bib

• Example 2: only add the OCLC 035 to the existing record; ignore the rest of the incoming record{*}{*}

Discussed previously: https://folio-org.atlassian.net/wiki/x/wDZH ; https://folio-org.atlassian.net/wiki/spaces/DISIG/pages/4669801

The working group did some functional testing and envisioning future enhancements in 2022/2023 https://docs.google.com/spreadsheets/d/1K6Tuo4zT1GMgStu4xccDtescI-sa1ZcL8wAnp--fwEc/edit?gid=924334300#gid=924334300

What does overlay mean? Do we need to update our terminology?

Change terminology?

• Find

• Add

• Replace

Examples during meeting:

• Authority work: find and replace all the 6xx fields

• Find and replace the OCoLC number by match on hrid/uuid

• Find the 035$a with (OCoLC) prefix and replace it with the 035 with an (OCoLC) prefix in the incoming record.

Merge functionality could be useful.

Housekeeping

Roadmap Discussion (At same time of a new release)

MVP Discussion (at the same time of a new release)