2025-05-07 Data Import Subgroup Meeting Notes

2025-05-07 Data Import Subgroup Meeting Notes

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: @Whitney Christopher @Jennifer Eustis @Katie Rahman @kimberly wiljanen, @Raegan Wiechert , @Robert Pleshar , @tess amram, @Ryan Taylor @cathy tuohy @Lynne Fors @Yael Hod
Notetaker: 

Links:

Agenda: 

Topic

Who

Meeting Notes

Related Jira

Decisions/Actions

Announcements

ALL

 

 

 

Prioritization Poll

ALL

Results of Jira Prioritization Poll
Results of Jira Prioritization Poll

 

Create single log entry for a batch import jobs that are split rather than a log entry for each sub-batch of 1000 records
Jobs run immediately after canceled jobs take excess time (https://folio-org.atlassian.net/browse/MODSOURMAN-970)
Allow update of the Instance and the SRS record in a single data import job (https://folio-org.atlassian.net/browse/MODDATAIMP-1199)
Allow for MARC field protection at the import profile level (https://folio-org.atlassian.net/browse/UXPROD-2934)
Reporting: Have the ability to download a list of errors from an import (https://folio-org.atlassian.net/browse/UIDATIMP-914)
Update Instance Administrative Data Only (https://folio-org.atlassian.net/browse/UIDATIMP-1724)

 

Thanks to Lynne’s poll, there were a total of 8 responses. The votes corresponding to the order above are: 6,5,2,2,2,1.

Jennifer put this on the PC Communities Priorities board.

In future, we want to rely on votes. The one with the highest votes is https://folio-org.atlassian.net/browse/UXPROD-2829 . However, because it is a draft, it doesn’t appear in any of our dashboards. Could the status be changed to open? then it would appear in our open list of issues?

For this and to track issues, there is now the Data Import Releases Dashboard.

 

Related Jira discussed in meeting that could open up the data file types used in Data Import to support work in other areas: https://folio-org.atlassian.net/browse/UXPROD-5253  

DI a SIG or working group discussion

 

Conversations have occurred in MM SIG, Acqusitions SIG, and App Interaction SIG.

The consensus in these groups is that DI should become a SIG. DI is much more than Inventory and bibliographic data. Some in Acq SIG mentioned that they didn’t come because they felt the focus was too much on bib records.

Of note for this group. People have requested:

  • More asynchronous and synchronous sharing (see below)

  • More equitable time spent on acquisitions and bib functions

  • More collaboration between other SIGs

 

We are now a SIG!

Looking for a group of notetakers.

  • Whitney and Yael

Ask from community on asynchronous input

MM SIG/various

In MM SIG on 4/24/2025, several people mentioned that they couldn’t attend DI meetings. There is no meeting time. People would like to see more asynchronous ways to provide input and be proactive on how DI evolves.

Ideas:

  • Rotating days and times of Data Import Lab so more can participate.

  • Integrate lab more tightly with the SIG.

  • Post lab day/time at the top of each meeting agenda

 

 

https://folio-org.atlassian.net/browse/UIDATIMP-1329 https://folio-org.atlassian.net/browse/UIDATIMP-1328

Old Request for use case

Field mapping profile: limit the list of linkable action profiles based on FOLIO record type.

 

 

https://folio-org.atlassian.net/browse/MODSOURMAN-1013

All

Do not process incoming record if it is a duplicate in the file

Waiting for confirmation from SMEs.

 

 

https://folio-org.atlassian.net/browse/MODDICONV-394

 

Disallow usage of Update MARC Bib next to Update Instance actions

 

 

Upcoming meetings/agenda topics: --

 

Chat: