2026-03-18 Data Import SIG Meeting

Item

Announcements

Next meeting on April 8, 2026. (Next week is no meeting for calming and the April 1, 2026 meeting is canceled for holidays and absences.)

We need notetakers! Please sign up on our 2026 Topic Calendar, now in our shortcuts if you are in our DI space.

Open

Shortcut menu includes our current topic calendar

April 8 meeting will be a workshop - continue testing.
Focus on updating items, holdings, instance

Decision log: Data Import Documentation Audit and ReorganizationPreview - Endorsed

Discussion (New Topic or Jira Issue)

Testing Results/Review

Update srs marc + instance in a single job. related Jira: MODDATAIMP-1199: Allow update of the instance and the srs record in a single data import jobOpenPreview Jira indicates that this works as expected when the match is marc to marc and the srs marc update comes before the instance update.

Testing on 2026-03-11 Data Import SIG Workshop MeetingPreview indicates that this is possible with a marc to instance match if the instance update is the first action rather than the srs marc update. The records display as expected after the updates, but the log summary is not working. The log summary displays 4 updated instance rows and 4 no action instance rows with an error for each record in the file.

Next steps:

Data import documentation reorganization will go forward as proposed by Autumn.

WolfCon - we are proposing two workshops one on bibs and authorities, the other on acquisitions workflows. JE and YH the first, CT will do the second. Looking for another co-presenter. 

Possible a panel on the proposed scope to discuss users needs. 

Ryan may do a presentation on what will be coming in future releases.

Testing Results/Review

Update items before instance and holdings. Update from Christie Thomas. Will be the focus of testing at the workshop on April 8, 2026.

CT presented the results of last week’s testing. Need to add the issues with the log to our log enhancements tracking. CT will create a bug ticket showing that the job worked but the log made no sense. 

JE - maybe the log is a symptom of something else? Is this the intentional behavior of the log? Matching on an instance and updating the MARC SRS was not intentional behavior so maybe it happens to work but the log does not display correctly.

RT will take back to the team. 

CT - if we create a bug saying this is what we want to do and the log is wrong will that be enough for the developers to understand what we want. 

RT - will keep an eye on the ticket and sort out next steps as needed with the understanding that we want this to work and the log needs to be updated.
Will add creating the ticket to next meeting’s agenda.

Autumn Faulkner

Using Bib Update Services (e.g. vendors like Backstage) in conjunction with Data Import

Workflow - monthly we gather new cataloging in the reporting app. Export list of IDs and use default instance export from the DE app. Upload a file to backstage ftp of between 3-5k records. The return the bibs are uploaded. Match on 999i and create a default MARC record. 

Backstage send us updates when LC creates a new file. Match on 010$a and update existing records and creates new ones that aren’t in our system. We are not linking bibs currently. 

CT - we looked into this and haven’t been able to do in batch. Only singular records. 

AF - had some issues with our cataloged dates since we had an issue with our migration. 

CT - do we want to have a community conversation on how large updates should be reflected and not wipe out previous information such as updated by.

AF - Backstage has our authority file so whenever LC updates the authority records they know to send us an update. Size is usually a few thousand except when we do dissertations once a year. 

KR - how did you send the initial file?

AF - did it when we were in our previous system and our Authorities librarian sent to backstage before the migration. 

We have asked Backstage to include URIs for all our headings. 

KR - we were thinking of not adding URIs now and then adding them once the linking functionality is working. 

AF - we want the URIs in place for when the linking does work so won't have to send the whole file again.  We plan on adding a “send to backstage” stat code so that we can add to older records that may have been overlaid. We don’t have a reliable way of knowing how much this is happening. Adding the stat code should solve that. We don’t think we are wiping out a ton of URIs. It will be more of an issue once we start loading our electronic resource records in the future.

Housekeeping

Next SIG meeting

April 8 Workshop: Test update items before instance and holdings. Create Jira for log errors when updating an srs and an instance record after a marc to instance match.

Actions/Decisions Needed

Roadmap Discussion (At same time of a new release)

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