Page Comparison

Updates (please add in advance)

10 mins

Before the meeting started: 

Hermine V. (UCLA) was asking Shi D. (CDL, California Digital Library) about “My institution” view. When an SCP (Shared Cataloging Program) record is available, does it show up in Primo? UCLA wants to be able to see consortial licensed materials.

Shi said only 4% of SCP records are available in Alma yet. Shi will look in Basecamp.

Liz M. said, If you own it it will be included, if the resource has been set up as a participant. You can search by putting “available for” in Alma.

Shi added that the SCP e-resource page will tell you that the pack is done. [Jean: I don’t know what a “pack” is for sure.]

~. ~. ~

Meeting proper:

Liz:

• Liz and Sarah have a standing meeting with CDL ICs every Friday

• AEFG page approved at PPC (still need to dial in norm rules) (Go-Live) Vendor bib records/overlay rules - AEFG w/ RMFG (MVP 003)

• Follow up work order meeting

Hermine:

• Preliminary results of authority control testing:

  • Overall, using reports exported from Authority Control Task list is effective for Day 1, especially the BIB heading found no matching AUT headings reports. In a 20-LCNAMES heading sample:

    • 11 headings required correction and controlling in OCLC

    • 7 headings had no corresponding NARs; no action taken

    • 2 headings were correct and controlled in OCLC but failed to link in Alma.

  • Many headings are controlled in Connexion but don’t link in Alma for various reasons. Question - Does this matter at all? Or is the only purpose of linking headings in Alma to aid in preferred term correction? If we do authority work in WorldCat and get daily updates, can we stop worrying about this, or does it have other ramifications?

    • What Alma considers an “ambiguous” match should often not be ambiguous. Example: 651 Winter Harbor (Me.) will not link even though it matches a 151--we think it’s because there is an existing 451 for Winter Harbor, Me. (a see reference to Winter Harbor (ME. : Town), and Alma normalizes them to be the same.

    • Alma is terrible at doing partial linking (e.g., linking on a 700 $a but not $t). Example record: MMS ID 9912345526206531, where none of the 700s link because of the (valid) presence of $s Vocal score at the end of each heading--since the entire string doesn’t match an authority record, Alma doesn’t link.

• Now that data migration specs are in, need to pivot to training planning.

UCB:

• If other campuses are recording their training, and are OK with it being shared, some Berkeley RMFG trainers were interested in the possibility.

• Tentatively scheduled cataloger training to begin on June 28.

RMFG import profile best practices

15 mins

Draft

What are people’s thoughts on 1 generic template "and then comments on how campuses can change/adjust?

RMFG-MVP-004 Best practices for the Metadata editor, including WorldCat search for NZ and IZ records

Draft

RMFG-MVP-005 Policy and workflow for working with the NZ Authority control task list

Draft

RMFG-MVP-013 Policies for NZ record deletion

Draft