2025-12-10 Data Import SIG 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: @Christie Thomas @Jennifer Eustis @Robert Pleshar @Sara Colglazier @Lynne Fors @Katie Rahman @Vivian Gould @Whitney Christopher @Yael Hod @Kim Wiljanen
Notetaker: @Whitney Christopher , @Autumn Faulkner , @Yael Hod , @Robert Pleshar
Links:
Agenda:
| Item | Notes |
Announcements |
|
|
Updates | Decision log for Cancelled jobs not showing up in Settings preview of jobs that used this profile Working Document for Log Messages Working document for refinement and use cases for match profile using qualifiers | The sig is endorsing the ‘Cancelled jobs’ ticket for UX work for DI. Sig should feel free to share comments or any testing they have done for the ‘match profile using qualifiers’ issue. The call for proposals for WOLFcon will come out next year in early February. |
|
|
|
Discussion (New Topic or Jira Issue) |
|
|
Qualifier match Lab Session Testing | SIG to review Report from lab session Working document for refinement and use cases | Jennifer Eustis shared out the work from last weeks DI Lab session on refinement and use cases for match profile of ‘qualifier’. Does/should alphanumerics include punctuation and special characters? Do we make the qualifiers case sensitive? We are trying to find use cases for all of the available match types (starts with, contains, ends with). No one currently has one that uses ends with. VG has a historical example (see notes). |
MARC Modifications after update | https://folio-org.atlassian.net/browse/MODDATAIMP-1237 This is still labeled as needing review from the SIG. (@Christie Thomas updated the label to sig-reviewed.) Does this solution work for us? | Does this need further discussion? Ryan is probably needed for this, but not available today. Solution developers came up with is unknown. Carry forward and ask Ryan for more information. |
Update instance, holdings, and item in reverse order. | From Request: “Right now the instance, holdings, and item must be updated in that order. It is also not possible to update an item independently and then, in the same job, match and update the instance and holdings. When updating all three records as a part of a shelf ready workflow, integrations (FOLIO app and external) require that the barcode be added to the item before the holdings record is updated. We need to be able to match and instance, holdings, and item (in that order) and then update the item, holdings, and instance or the item, instance, holdings in either of those orders. Error message from import in Poppy: | tabled due to lack of time |
Housekeeping |
|
|
Qualifier match lab session | What are next steps (new issue, reopen 386)? | continue fleshing out use cases, then test them in lab |
|
|
|
| Actions/Decisions Needed | To do Lab will work on defining and testing use cases for qualifier matching. Will request more information about the solution for https://folio-org.atlassian.net/browse/MODDATAIMP-1237 from developers and/or Ryan. |
Roadmap Discussion (At same time of a new release) |
|
|
MVP Discussion (at the same time of a new release) |
|
|
Upcoming meetings/agenda topics: --
Chat: