2023-12-14 Meeting notes

Updates/announcements (Please add in advance)

Share information

10 mins

All

Start recording!

Ryan (UCSD)

• Given that it exists on our campus CMS and has a high barrier for editing and that Google analytics shows that we get almost no external visitors, we have decided to shut down our TPOT site and move all content to our intranet.

• We are looking at stopping local cataloging of our ETDs and just rely on the ProQuest and eScholarship collections.

  • From Hermine, there is some movement to look at how ETDs are handled in the Network Zone and improving access; work will begin in January 2024

• This might be more appropriate as a future agenda item, but we would like to start using the new(ish) 856 2nd indicators and have started revising some local documentation. Are there any RM policies, rules, etc. that would need to be updated to accommodate this?

Hermine (UCLA)

• https://uc-sils.atlassian.net/wiki/spaces/ACH/pages/2288943105

  • State of the SILS town hall in January - 2-3 minute update for each OST. Anything in particular we want to include?

    • From Catherine, possibly highlight what we have harmonized on

• https://uc-sils.atlassian.net/wiki/spaces/ACH/pages/2279178241

• Kanji character fix in Primo VE = good. Our ticket is still open, because our Japanese Studies Librarian had another spreadsheet of characters that need to be mapped.

• OT is still discussing proposal for expanded NZ access

Adam (UCB)

• LCSH was updated to replace “gays” with “gay people” (see Approved Monthly List 08 LCSH 2). While many NZ records will be updated via WorldCat Updates, what steps do we want to take to identify and correct records that do no get updated? When might we want to undertake this work?

TJ (UCD)

• Published 10 BIBFRAME converted MARC records to WorldCat (example) and shared issues identified with Ex Libris to enhance the BF-to-MARC converter. Next step: publish BF as BF to WorldCat. (2023-12-13 update at UC Davis)

• Questions for the group: will it be okay to bring BF descriptions (with or without OCLC number) into Alma Sandbox NZ? If yes, is everyone comfortable with having duplicate “records” for a resource, i.e. one MARC record and the other BF description?

Catherine (UCSB)

• Loaded latest version of all records for our Ethnic & Gender Studies collections; will be sending the set to Gem to get added to WorldCat Daily Updates

Coordination will be needed when the ETD project begins

Review action items

Check in on action items

5 mins

All

https://uc-sils.atlassian.net/l/cp/sBLun4Ru

Local notes in NZ

10 mins

All

• Progress? UCSC is finished; UCSB is finished

• New report for 591-599. Next steps?

Policy on Local Bibliographic Data

15 min.

All

Time for a revision?

• An official instruction not to include local fields in the NZ record (there we can add the exception for CDL Acq 590s (), and maybe we can also mention 590s present in some e-resource packages)

• Overview of how local extensions work and when they can/should be used

• Mention of the setting that prevents 590s being added to NZ records

• Other?

  • CDL Acq records also do not include OCLC number, should add to exceptions on decision page

Yes, we should revise and add more details. Suggestion to add list of harmonization by MARC fields, as well.

Authority control

Start discussion

15 mins

All

Brain dump of background:

Next steps?

Tabled

Additional discussion

5 mins

Next meeting - cancel 12/21. Do we want to meet on 1/4?

No meeting on 1/4.

Parking Lot

/60