| 1 | Updates (please add in advance) | | 10 mins | | Liz: 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.
| | | |