2022-03-31 Meeting notes

Updates/announcements (Please add in advance)

0

UCI - Acquisitions at UCI is proposing to test the GOBI API loading records directly into the NZ. Information: The SILS Acquisitions team is working on a revision to the Vendor Bib Record decision. Since the brief bibs created by the GOBI API include OCLC numbers, we think that campuses using the API can choose to share them immediately with the NZ. If they do that, then the incoming record might be: 

• matched with an NZ record if one already exists and linked to the IZ with an IZ POL, OR

• imported into the NZ as a brief bib, linked to the IZ with an IZ POL, and overlaid within a day by the complete record from OCLC if someone has already edited it via the WorldShare Daily Update job, OR

• imported into the NZ as a brief bib, linked to the IZ with an IZ POL, and overlaid eventually when GOBI completes the cataloging in OCLC (but still probably faster than if we wait for records to be delivered and imported)

In addition to having more complete records for titles on order, we could also ditch the separate step of running the Link to Network job. Import profiles will still be needed to add any local extensions to the bib and update inventory information

UCLA (Hermine)

• I’m going to be outsourcing some scores to a cataloging vendor, and I’m considering having the vendor work directly in Alma like our local catalogers do. Since these already have order records in the NZ (migrated), I know there’s going to be plenty of unlinking, changing the OCLC number, and linking back up, plus we have oversize locations. etc. Is there any way to consider making this a file load instead?

• ELUNA membership for individual campuses--I know the campuses that were already on Alma pre-SILS are members; have any of the new-to-Alma members joined? It’s only $280/year so it seems like a no-brainer to get the extra NERS input.

UCSD:

• We’re also trying to set up our Gobi purchases to work with the API so are probably in the same boat as UCI

• Have decided against doing the reclamation unless something compelling comes up

• Working on a procedure for our serial analytics, will share when it’s done.

UCI:

API testing can only take place in the production environment.

The incoming complete record is using POL as the match point.

UCI and UCR both observe the brief records have OCLC numbers.

Thing to watch out for: if the OCLC number of the complete record is different from that of the brief record.

Adam asks if we should make a decision on what to do with 019. Liz suggests that we remove the 019 with normalization rule at the point of import.

UCR has been doing the GOBI API. If there is any issue, please let Yoko know.

Send any question related to the GOBI API to Sarah.

Liz will confirm if it is okay for each campus to purchase the individual membership.

Consent agenda item: Batch CZ deletions

Final decision page

If no objections, this will start in production

The decision will be published as is.

Free OCLC reclamation

10 mins

Final decision page

Should we track campus decisions around participation?

UCSC sent in a web form and got information back, including this:

1. For every holding or record we've added to WorldCat, we will send you back your own record with the OCLC Control Number inserted as the first 035 field. Please tell us if you would rather receive OCLC MARC records instead

Regarding CDL’s proposal of using 1 OCLC symbol, Shi shared that our setup is rather unique. Also, if we go forward with the proposal, it is irreversible. More discussion will take place within CDL folks.

The decision will be published as is. Each campus can make the decision individually.

We should keep track of campuses that choose to go forward with the project and reasons of campuses who choose not to do it in a shared documentation. The documentation will be posted on the Confluence.

Work Plan and Ops Team Handoff

Review priorities in Handoff document

25 mins

Hermine suggests we officially announce the implementation of the WorldCat updates and have a public documentation to describe the process of WorldCat updates, impacts, and what to do if there is an issue.

Adam suggests that we should consider beginning including other formats beyond monographs.

No analytics report for records being updated via the process at the moment. Folks can just search 908.

904 will be automatically added when NZ bib are merged.

Possible timeline: end of April.

Updated normalization/merge rules:

• Turnaround time: two weeks for proposal consideration. Changes will be implemented in a quarterly base unless critical

• Continue tracking change history in the rules and on a decision page

• Broader communication when updates are being made so campuses can take action accordingly

We will share our observation on the result at the next meeting.

Look at the workplan between now and the next meeting

Bound-withs

Check some assumptions around harmonization, find out what questions campuses have

15 mins

Folks agree not to standardize

Guidelines and pros/cons are made available and campuses are allowed to make the decision themselves

A live session to answer any questions will be made available

Timeline: May-early summer

Parking Lot

Capture important topics for future discussion

/60