| Table of Contents |
|---|
CMS 2024.3.5
Recording
1. 9XX reconfiguration
947, 948, and 949 combo going away
New approach will use one single 949 for all instance, holdings, & item data
Subfield codes will be different, but format will be the same
New constant data available shortly
Autumn will help you update yours as needed
Try out in Test environment before we switch to Poppy
2. Reminders & updates
Sierra order records – sometimes they’re in FOLIO, sometimes they’re not – and what to do about it
RDA Phase 1 webinars open to all
First one on March 15
Training on multiple holdings/items and boundwiths for next CMS (more Poppy changes)
CMS 2024.2.20
Recording
1. Poppy update
Updating Folio Production from Orchid to Poppy is on hold at the moment.
Implementation timeline is pushed back because of issues found by MSUL staff in testing which would severely impede our workflows.
Folio Service patch #2 is in development and promised to fix a lot of the issues identified as a problem by MSUL
MSU Dry-run instance is set to be updated around first of March. MSUL staff will resume testing at that point and we should know more regarding when implementation might happen in Folio Production.
...
CMS 2024.2.6
Notes: Autumn
Recording
1. Poppy update
Poppy installed in Test tenant; results of testing so far:
Lists app working well
Can run lists on a number of different item record fields, plus a limited number of instance record fields
Queries can be built with multiple lines; no “OR” option, though, only “AND”
Offers a preview of query results before running the entire list
Results can be exported to CSV, but limited to a select set of fields
No apparent limit on the number of lists that can be run/stored at any given time
Boundwiths/analytics
Function to add/delete linkages now available
Links are between one shared item record and the holdings records of the related instances
Viewing and editing these can be confusing! More training to come
Job profile 9XX configurations will be changing
New functionality to create multiple holdings/items for one instance using 9XX field mappings in Data Import
However, this means all values for one holdings/item pair must be in one single MARC field
We will be changing from the 947/948/949 configuration to just the 949 field
Autumn will be testing this thoroughly and helping everyone adjust their constant data accordingly
Possible issue with action profiles
Known issue with Poppy, where the “action profile” component of a job profile might be unlinked from all the job profiles it’s associated with
Catalogers don’t need to grasp all the details of the problem, but just know it could be a factor in when we ultimately move to Poppy
...
This was a brief off-cycle meeting immediately after the holiday break, only on Zoom.
Recording
1. New IMCO (Identity management) cooperative program
...