2025-10-08 Data Import SIG Meeting Notes

Announcements

ALL

WolfCon feedback:

• LOC plugins are interesting

• Recordings have been posted to WolfCon YouTube channel

• https://www.youtube.com/playlist?list=PLMocoPoiGkwcUSiOjdssz_2iXrYwf7cR4

Topic Discussion: DI SIG Process

ALL

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

• Seeking input from SIG members / participants on this draft

• Document has instructions for reporting a bug, list of dashboards relevant to Data Import SIG, list of issues needing review, list of issues that have been reviewed

• Roadmaps: high-level roadmap will be more “human readable” and less dependent on Jira terminology

• Q: How do we balance reviewing old items with making space for new business / items?

• Q: How can the SIG get involved in the development process for the Data Import App?

• Q: how can SIG help manage review of existing bugs, epics, etc. in JIRA

• Discussion: could make review of old items and discussion of new items a standing part of meeting agenda; follow-up: how often should we review things like the roadmap, MVP, etc.? Might depend on release schedule and what is in a given release. Could also be tied to Bugfest – did we accomplish roadmap goals for a given flower release?

• Follow-up: can we create a method for prioritizing Jira issues? Discussion: there are multiple types of JIRAs (e.g. bug vs. feature request), and some are more complex than others. We could figure this out as we go, but also provide a way for SIG members to request that something is on the agenda or bumped up. Meeting agendas are regularly being posted a couple weeks in advance, so asynchronous discussion on Slack could help us prioritize ahead of each meeting. Idea: prioritize bugs over other types of issue. But important also not to lose sight of big-picture issues. Could have a priority discussion topic and a set amount of time to review bugs, etc.

Add to meeting agenda template: 1) review of existing Jira items; 2) review of new items. Add a regular meeting relating to roadmap (possibly tied to flower release schedule, bugfest, or another regular event). Allot set times for these reviews (of old and new Jira items) and for big-picture discussion topics to ensure a balance.

Try to post these topics and review items in advance to allow for some asynchronous discussion on Slack

https://folio-org.atlassian.net/jira/dashboards/11170

@Robert Pleshar

The bug was fixed in Quesnelia but has reappeared in Ramsoms, with somewhat different behavior. Ryan T. recently discussed this bug with dev lead. Is not working because FOLIO thinks you are updating the same entity twice within the same job. Might line up with issues encountered with other MARC update processes (e.g. adding field, modifying field, and removing field in a single import operation can cause problems). Use case: holdings and item data in MARC bib 9XX that should be removed from MARC record at end of import job. Ryan T.: the request is relating to the distinction in FOLIO between updating and modifying data.

Issue arises when there is a need to override field protections, thus an Update SRS action must happen. So the MARC SRS has to be updated (e.g. with a new 856 field), the holdings/item then need to be updated via 9XX in the incoming MARC, but then a separate action profile to remove the 9XX after holdings and/or item are updated will not work.

https://folio-org.atlassian.net/browse/MODDATAIMP-1237

@Ryan Taylor will continue working on this with the dev team. Will report back. This might end up being classed as an enhancement rather than as a bug