2025-10-15 Data Import SIG Meeting Notes

Announcements

ALL

JE: available recordings are up from WOLFCON
CT: Need to keep momentum going on acquisitions sig work.

Discussion Topic

Review wiki pages:

File a bug

File a new topic

ALL

CT: Continue discussion of Participation and Development Guide. VG: What do we mean by bugs? Are we including things considered features? CT: Start with operational definition of “bug”. Users are not thinking about if things are enhancements or not. If something doesn’t work the way we expect, we consider it a “bug”. YH: If the sig thinks its a bug, we should fill out the Jira and let devs figure it out. VG: bring things returned as “working as intended” to SIG to file appropriate JIRA. CT: Figuring out how to have these conversations will go a long way. We might need another pathway to flag something that isn’t a bug and make sure it gets captured.
CT: Re-creating data import profile for a bug in the same flower version of bugfest so that developers can replicate and to confirm that it is not confined to your local environment (not only in snapshot as it gets overwritten). RT: Directing to a specific job or profile in Bugfest can be SUPER helpful. YH: DI Lab is also a good resource for determining if things are bugs. VG: Slack channel is another resource. JE: test environment CT: link to exemplar bug and attachments so that we can support quality bug filings. CT: What to do when you can’t point to a job profile or re-create in a shared environment like bugfest? (for us, order imports) CT: If a known issue, verify with community in slack, confirm it is not already a JIRA. CT: We should also have a session(?) on how to locate JIRAs. CT/JE: live demo / review of steps to file JIRA. JE: we could include things like dates, files and recordings as well. Some providers ask for more information than others. RT: this sort of information would be helpful for the team (attachments, videos, etc.) JE: Visual cue is good for non-native English speakers as well. CT: Do we need to tag Ryan? RT: Fine to do so, but will get added later if not done. CT: Are we missing anything? What questions do we have? YH: Sharing on slack that you have opened a JIRA.

Standing Issue Review

MARC modifcation

MODDATAIMP-1237: MARC Modifications fail for UpdatesClosedPreview

ALL

This has been assigned to Sprint 229. What work will this entail?
RT: No decision yet on how this will be approached.

New Topic

Log UI Enhancements:

• Add date and start/stop running date and times to the summary log page

• include the date/time data (start + end) somewhere in the Data Import log individual job view

Jira Issue that needs review

MODDATAIMP-1232: Data Import Log Error Messages InconsistentClosedPreview

RT: will add log enhancements to the epic.

Discussion topic at the time of a flower release

Roadmap Discussion (At same time of a new release)

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