2024-11-13 Data Import Subgroup meeting
- Ryan Taylor
- Christie Thomas
- Jennifer Eustis
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: Ryan Taylor Autumn Faulkner, Jennifer Eustis, Raegan Wiechert, Tess Amran, Whitney Christopher, Sara Colglazier, Yael Hod, Lynne Fors, Kim Wiljanen
Notetaker: Christie Thomas
Links:
- Data Import Topic Tracker
- Data Import Roadmap
- Poppy import planning dashboard
- Poppy timeline
- Quesnelia import planning dashboard
- Quesnelia timeline
- Folijet Current Development Board
- Folijet (Data import) Bug Dashboard
Agenda:
| Topic | Who | Meeting Notes | Related Jira | Decisions and Actions |
|---|---|---|---|---|
Announcements: | Ramsons buffets has started. New bug reported by Autumn Faulkner. MSU tried a job profile to remove the $f from an 050, and the remove command deleted the contents of the $f but not the subfield delimiter code. Autumn is testing this between Poppy and Quesnelia to see if this is new behavior Prioritization request from Product Council. (Announcement from Jennifer Eustis) Discussions taking place in MM SIG meetings. | |||
| New Documentation: OCLC 035 Normalization for Instances | Ryan | OCLC 035 Normalization for Instances New documentation available on the wiki. Functionality is being introduced in Ramsons. Q: Will there be a script to clean up existing duplicates? Not for Ramsons, but could see if the team could put something together in the future. Q: Specific to data import and single record import, or will it impact records when saved in QuickMarc? Just for data import and single record import. Ryan will check on behavior when saving a record in QuickMarc. Q: Why are we keeping the $z in the 035s for OCLC records? From the production team's perspective, we did not want to make the call for an individual institution since institutions may have different local practices for the 035$z and 019 fields. | UXPROD-4081 - Getting issue details... STATUS | |
Documentation Discussion: Identify gaps/needs | Ryan/All | Spreadsheet for tracking documentation needs: Continue to fill in details. It is useful to include what information is on the wiki and what does not as a place to start when adding new documentation. Process in place to get documentation stood up on docs.folio.org. This effort is being led by Alissa Hafele. If at any point you are working something and it is not clear how it should work, add it to the list and Ryan will make sure that we get some coverage for it. Jennifer Eustis has been adding pages for data import related tickets for each release. Data Import Detailed Release Notes & Functionality | ||
Review Topics Tracker | All | Data Import Implementers Topic Tracker
Jennifer split out the topic tracker issues to put the closed issues on a separate table. The table at the top of the page includes the open issues. Will likely be looking at Trillium or Umbrellaleaf for 914 / 4935. General agreement that it would be useful to have start / stop dates and times on the log page itself - above the summary at the top. General agreement that it would be useful to have more information about the reason for no action when the reason is not an error. It was also pointed out that No record is a simply vague message that requires improved messaging. Maybe do some brainstorming about the best approach to error / log messaging for the future. Ryan would like to do an error audit at some point and make sure that the errors are legible and help with troubleshooting. Hyperlink the summary information to bring up a report of all of the errors / no action. This would not require looking up individual titles. Would also help with troubleshooting and identifying trends. Another log oddity that has been observed where no action was reported out with an error message, but the records were updated. | ||
| Notes from previous meetings... |
Upcoming meetings/agenda topics: --
Chat: