Page Comparison

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 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. Campus data won't link to SCP data. 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_Certification

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?

1. For subfield indicators, the double dagger is preferred by this group, rather than double dollar signs. n.b. Alma’s double dagger is not the same as OCLC’s double dagger though, watch out... But if it’s just a display issue, then maybe we can decide to leave that up to the campuses.

2. There is a difference between NZ (Network Zone) Administration, and NZ Access. How this will work is under discussion now; it will be a big policy decision. (For example, OCLC updates will be impacted.) 

OCLC updates during Vanguard

30 mins

Vanguard-- Testing OCLC daily updates

1. We would need one campus to be the one receiving the OCLC updates, set up an import file/collection in WorldShare, and process the updates for everybody. Then push those into the NZ. 

   1. SCP won’t have the bandwidth to do this.

   2. The campus that does this would get Administrative permissions.

   3. Maybe we could: leave off the electronic resource holdings, decide what formats to be dealt with, etc., and then see which Go-live operations are affected.

   4. UCLA has several people who are very much against having the OCLC updates (for example, some Special Collections people and some authority control people [especially people who work with series]). UCLA is setting up a subgroup of their local Resource Management group, that will be devoted to authority control.

2. We talked about: we could test this in the Vanguard. We could try out a small collection with no SCP, and see. THUS: which campus volunteers to do this for the Vanguard?? (Orbis Cascade has some good information on this: https://www.orbiscascade.org/alma-daily-bib-record-updates/  It was confirmed with Orbis that they do not receive duplicate updates for records held by multiple campuses, so if 10 Orbis institutions own a resource they don’t get 10 updated copies if the record changes.)