| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
---|
1 | Housekeeping | Add any new topics to the agenda Take a temperature check / How is it going? Confirm Minutes Recorder for this meeting - Lai Arakawa Share co-chair update Affirm Vacations/Out document
| 5 min | Greg | Shared Google drive | | |
2 | Patron Data Q&A with Ex Libris | | 5 min | Greg | Ex Libris is scheduling Q&A sessions with individual SILS groups. Questions must be presented to them in writing ahead of time We could use our Questions for Up Stream document to collect questions and then discuss for prioritization and submission
| No need to schedule Q&A with Ex Libris at this time. | |
3 | Guidelines for Minutes | | 10 min | Greg | | Everyone has agreed to the Guidelines | |
4 | Tasks & Deliverables | Confirm - Single UC-wide patron record database or separate institutional patron databases? Confirm - Should we migrate expired patron records? From Governance Charge -
A list of patron data cleanup activities and assignments that need to be accomplished prior to the initial data migration. A list of patron data issues which require harmonization decisions, to be made available to the Implementation Coordinators group.
| 10 min | Greg | Ex Libris Migration Guides & Tutorials Status - Single UC-wide patron record database or separate institutional patron databases? Still awaiting decision from Fulfillment & ILL FG; due date is May 21st Decision page within the IC Confluence space have not received any feedback from the group yet
Status - Should we migrate expired patron records? Still awaiting decision from Fulfillment & ILL FG; due date is May 21st Decision page within the IC Confluence space
From Governance Charge - A list of patron data cleanup activities and assignments that need to be accomplished prior to the initial data migration. Created a “Local Campus Data Cleanup Documents” folder in Patron Data Google share. UCSD and UCI have provided documents thus far; others should as well, following structure/format of their choosing. Sites already on Alma should obviously have much less data cleanup.
UCI also provided a copy of a Patron Data report from their 2018 migration to Alma that documents decisions and actions they completed, in addition to lessons learned. UCSD will be creating a similar document; should we all for final documentation/report? other formating requirements that we may need to think about
A list of patron data issues which require harmonization decisions, to be made available to the Implementation Coordinators group. Still tabled until there is resolution on question of single versus separate patron record databases.
| | - All - 3a. Create local patron data audit and cleanup document and place anonymized “snapshot” copy in shared folder.
|
5 | Patron (User) Barcodes in Alma | | 20 min | | Some UC campuses, who are not already on Alma have multiple barcodes in some of their patron records. Proxy Cards having their own barcodes Extraction - how should we clean up to not flood the barcode field? Can you only transfer only one barcode through migration? Formatting - Can patron barcodes be alpha numeric? Through SIS, are certain fields designated for protection?
| | |
6 | Homework | | | | | | All - (ONGOING) Add questions for up stream |
7 | Parking Lot | | | | | | |
8 | | Total | x/x | | | | |