...
Item | Desired Outcome | Time | Who | Notes | Decisions | Actions | |
---|---|---|---|---|---|---|---|
1 | Updates | 10 mins | Liz | Update from CDL in NZ subgroup, including order of NZ loading change. I. The systemwide Resource Management group heard the fallout from this morning's troubled meeting with ExLibris -- that was full of bad news for the way the Vanguard, and possibly even the go-live is going to turn out. "It was a very tough meeting..." ExLibris hadn't understood the complexity of our data, and they were finally beginning to, but it is now too late to revisit the order of loading or change protocols. The CDL (Calif. Digital Lib.), particularly SCP (Shared Cataloging Program) data upload has been changed. There are serious impacts on the Vanguard and in duplication that will be rife. Other workflows will be made more difficult. Now they've The CDL subgroup met with ExLibris to review options for loading SCP data and it became clear that the original loading plan would cause significant duplication that would likely have significant impacts on other groups and make it difficult to test various workflows. It was decided that SCP data will be moved to a separate IZ (Institution Zone), instead of to the NZ (Network Zone); SFX (the link server) data will be moved to the NZ. The trouble will also fan out to impact Discovery and User Experience. loaded into an unlinked IZ at the outset of the Vanguard and that SCP will use existing “Alma Tools” in order to make connections between their data and the NZ/CZ. They will have to review each collection individually. Since the order of NZ loads has already been submitted to ExLibris and since extracts are due Friday, there isn’t time now to revise NZ load order but we will take a look before go-live especially once there is a final decision on how to handle SCP data. Campus data won't link to SCP data during NZ loading. We will lose things. We'll need to talk to our stakeholders and do a lot of testing. Apparently even within ExLibris, they are not all on the same page with each other about what "Test" means. In messaging the campuses were getting, ExLibris neglected to mention that some of our early decisions and Vanguard decisions were more permanent than we thought. Possible Band-aid: Maybe we could de-dup SCP by collection? (can't do it one by one), but it's hard to find the matching point; ISBN is not reliable. Also, we should look at the merging rules, and how SCP local data will work. After go-live, we could make priorities for SCP work. https://knowledge.exlibrisgroup.com/Alma/Training/Alma_Administration_CertificationUCSD will be working with SCP on testing their original proposed method of loading/cleanup since they will be loading SFX data and sending e-resource bibs through P2E. | |||
2 | Configuration questions | Field questions/comments on configuration and harmonization for Vanguard | 50 minutes | https://uc-sils.atlassian.net/wiki/spaces/RMF/pages/521437672/Call+number+parsing Other areas for potential harmonization based on the form?
| |||
3 | OCLC updates during Vanguard | 30 mins | Vanguard-- Testing OCLC daily updates
|
...