| 2 | ILSDC + Patron Data | Understand with the chairs of those groups how to liaise / coordinate work | 20 | Team | Catherine (UCSB) has been part of the Alma cleanup UCSB migration stuff, and part of SILS Phase 3 and now chairing ILSDC. Co-chairing internal training work. Marti (UCSB) really swamped and have a lot of concerns about dedicating time to SILS. ILS Data Cleanup (ILSDC): Work is here on Google drive folder, including a spreadsheet of prioritized and triaged work. First deliverable is what will need to be done by all the campuses prior to migration. CB: what we need - we have documentation from ExL on the various system needs. What’s being harmonized and where - do we need to do anything pre-migration to deal with that, or will it be done after migration? How will we know that? What’s the starting point? Do see this group as an operational group, not decision-making. Local campuses are making decisions - we are an advisory group for that.
Carlo: I think a challenge both groups face is that since the campuses are coming from disparate ILSs and have used the various fields (whether it’s MARC or patron) differently so part is decision making, part is coordination, and harmonize where they can. Just initial thoughts Carlo: The good news is most of the non-Almas are in vanguard
. We’re going to learn a lot sooner rather than later P-to-E: Every campus has to identify their databases or identify their data somehow, knowing how to identify what is electronic and what is physical has to be done.
Patron Data: This got spun off from ILSDC because of specific data needs. How to get that work started: can they take the work of the ILSDC as a sample starting place? Lot of this data is coming from a third party - it’s an integration issue. What data are you getting from outside the ILS is crucial too.
Strategic Approach: Get as much metadata cleanup done now as you can. Take advantage of Ex Libris help Defer metadata cleanup until Alma is in because it has much better tools for this
Caitlin: this
has evolved to be a determination that is made campus by campus
Principles: Make some default decisions like “we’re only going to do the minimum now” or Prioritize the prevention data loss now Prioritize things that will “break consortially” now Prioritize those things that would end user experience
Useful Links: | What we really need from ICs is the timeline - when do you need cleanup done or mapping done or whatever. Especially what is needed for vanguard - what tasks do we want to focus on there. | |