2026-05-13 Data Import SIG Meeting

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: @Christie Thomas @Jennifer Eustis @Robert Pleshar @Whitney Christopher @Lynne Fors @Yael Hod @Katie Rahman
Notetaker: Jennifer Eustis

Links:

Agenda:

	Item	Notes
Announcements
	Trillium bugfest - Slack channel #folio-bug-fest / Bug Fest R1 2026 Trillium - Non-ECS - Eureka New topic: Set for delete: Should users be able to match on deleted records in Data Import? - To be discussed at June 3rd meeting?	Bugfest is going well. Some people are testing. One person is testing https://folio-org.atlassian.net/browse/UXPROD-4704 which is a new feature. Please test this to make sure it works to your expectations. The next topic will be “Set for delete” on being able to match or not to deleted records. Whitney will be there for the discussion.
	EBSCO Users Group	New Features: Match criterion has been removed so that only “exact” matches can be created. Stop import when user stops job. Work was done with ECS where you can see everything in a library EDS: Features to optimize EDS - this will look at all subscriptions to see if these are the correct ones. EBSCO is redesigning their resource hub
	May 20, 2026: Updates on new functionality and bugs: Update instance, holdings, and item in reverse order (Line 6 in New Topics spreadsheet.) https://folio-org.atlassian.net/browse/MODDATAIMP-1290 / https://folio-org.atlassian.net/browse/MODINVSTOR-1363	@Ryan Taylor Would it be possible to get updates on these tickets (and for 1363 how redundancy works and any documentation)?
	New Bug: https://folio-org.atlassian.net/browse/MODINV-1373	When instance updated to source when SRS creation fails.
Housekeeping
	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{}{}	See Jira ticket for comments

Discussion
Open questions?
Roadmap Discussion (At same time of a new release)
MVP Discussion (at the same time of a new release)

Upcoming meetings/agenda topics: --

Chat: