2025-05-14 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: @Jennifer Eustis @Christie Thomas @Lisa English @Katie Rahman @Mary Aycock @Robert Pleshar @Sara Colglazier @Vivian Gould @Whitney Christopher @Yael Hod Timothy Mendenhall, Tess Amram, Kimberly Wilijanen
Notetaker:
Links:
Agenda:
Topic | Who | Meeting Notes | Related Jira | Decisions/Actions |
Announcements | ALL | WOLFcon 2025: Call for proposals ends May 16th this Friday. Are you interested in testing the Linked Data App in Sunflower bugfest? Join us in #folio-linked-data-app-uat. |
|
|
SIG Conversion | Jennifer | Jennifer has reached out to the PC to present the new SIG. We have a new space in the wiki: https://folio-org.atlassian.net/wiki/spaces/DISIG . MM SIG felt that we needed to move our documents to our own space and provide a page with a link to that in MM SIG wiki area. Christie brought up the need to work better with other SIG to make DI better. Asks that more people way in on ways to get others involved. The Data Import Working Group is becoming a SIG and Metadata Management has been notified. Next steps are to notify and present to the Product Council. Meeting is May 29th from 10am - 11am. Jennifer has created a new Wiki space for DI SIG. There will be a link from Metadata Management space to the new DI space. Will discuss how DI SIG can interact better with other SIGs as a part of early conversations of the SIG conversion.
|
|
|
Order import demonstration and discussion | Christie | Should we create a WOLFCon proposal or dedicate a Lab session to demonstrate and discuss?
|
|
|
Ryan |
|
|
| |
Ryan |
|
|
| |
Ryan | Field mapping profile: limit the list of linkable action profiles based on FOLIO record type. |
|
| |
Christie | Field mapping profile: limit the list of linkable action profiles based on FOLIO record type. When creating an action profile all of the field mapping types come up instead of the type related to the specific field. Limiting the option to only display field mappings for orders when linking a field mapping profile and an order record type would improve user experience. Added a note to the issue in JIRA. |
|
| |
Christie | Do not process incoming record if it is a duplicate in the file Waiting for confirmation from SMEs. |
|
| |
Christie | Disallow usage of Update MARC Bib next to Update Instance actions |
|
|
Upcoming meetings/agenda topics: --
Chat: