2026-04-08 Data Import SIG Workshop Meeting

2026-04-08 Data Import SIG Workshop 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: @Vivian Gould
Notetaker: @Whitney Christopher , @Autumn Faulkner , @Yael Hod , @Robert Pleshar

Links:

Agenda: 

 

Item

Notes

Announcements

 

 

 

WOLFcon 2026 call for proposals ends April 15, 2026. Learn more about guidelines and submission on the conference homepage.

WolfCON will be held in person this year. As always there is a virtual option for regular sessions.

 

 

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.

 

Testing

 

 

 

Housekeeping: Update Jira issue Retest https://folio-org.atlassian.net/browse/MODDATAIMP-1199 based on testing and create new Jira issue for marc to instance match to update srs and instance.

 

 

The tests done did not work. The SIG would like to be able to do both updates in one job. JE will finish the testing and update the ticket after the meeting.

 

Update instance, holdings, and item in reverse order (Line 6 in New Topics spreadsheet.)

@Ryan Taylor will speak more with the developers about this. If more info is needed, can consult with Christie for logs or IndexData? to view logs and jobs.

 

Discussion (Continue on 4/15): https://folio-org.atlassian.net/browse/MODDATAIMP-1290

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

Recent change in Sunflower - Needs review. Was not reviewed before implementation.

in order to prevent redundant updates if the incoming record matches the existing the system does nothing. This is the intended functionality. On the DI side, our logs aren’t granular enough to reflect that. The log says updated even when there is no change. 

How is this affecting the users?

Ryan will confirm if the system is doing a full comparison of the records.

The concern is that now the logs and the reports are not reliable and its affecting our workflows.

Ryan proposed two questions. Poll is in slack:

  1. How would you feel if Data Import Logs were enhanced to say "Unchanged" when it encountered a record that was the same as one processed earlier 

  2. Would you be fine if the current behavior as explained in the issues linked in post above continues, if the updated date and user are reflected by recent jobs rather than this "Unchanged" or no update action?

 

Housekeeping

 

 

Next SIG meeting

https://folio-org.atlassian.net/wiki/spaces/DISIG/pages/1728741396

 

 

 

 

 

Actions/Decisions Needed

To do

Roadmap Discussion (At same time of a new release)

 

 

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

 

 

Upcoming meetings/agenda topics: --

 

Chat: