Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Status

IN PROGRESS

Description

Determine whether any local authority files should be loaded into the Network Zone

Decision

Owning group

Resource Management FG

Approver

PPC

Stakeholders

R = Resource Management IG
A = Resource Management IG
C = ILSDC
I = PPC, ILSDC

Decision-making process

Due date

Recommendations

Background

ExLibris documentation:

https://knowledge.exlibrisgroup.com/Alma/Training/Extended_Training/Presentations_and_Documents_-_Authorities

https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/010Alma_Migration_Considerations_for_Consortia

https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/060Working_with_Authority_Records#Adding_a_Local_Authority_Definition

From Basecamp: local authorities managed in an IZ can only be used in records that are not linked to the NZ. If local authorities are needed for any records linked to the NZ those authorities must also live in the NZ.

Alma allows multiple subject authorities to be used but only one name authority, regardless of whether they are managed in NZ or IZ. The result is that any local name authorities have to be added to the “regular” name authority file (ex. LCNAMES) and will show up in Alma authority search results with “(Local)” in parentheses but will appear in bibs as though they are regular NAF records

Outside sources:

Harvard Wiki - Known Issues in Alma Authority Control - https://wiki.harvard.edu/confluence/display/LibraryStaffDoc/Alma+Known+Issues#AlmaKnownIssues-AuthorityControl

Orbis Cascade - Authority Control Group - https://www.orbiscascade.org/authority-control-group/

From Phase 3:

“Local authority record conversion is not part of the migration scope of Alma. If you have locally created or modified authority records to load into your local institution, use the standard Alma loader tools post-migration. In a consortial setup, they likely reside in the Network Zone for sharing across members. Contact your local Ex Libris project team for consultation if this is relevant for your institution. ”So Ex Libris says local authority records go last - do we disagree for any reason?

Questions to consider

What local authorities files do campuses have?

UCLA has SARs and other authorities to test

UCSD has local non-series authorities to test

UCB has some local non-series authorities, unsure if they will be able to test them but definitely open to it

What information is in them that we want to port over?

Series treatment

Fully local records: names, subjects

What do campuses want to use local authorities for (i.e. anything that would wind up in an NZ bib or just for local reference?)

Series treatment (used at check-in and other areas)

Local authority management/creation

Can non-series authorities be added to the NAF?

Should they live in an IZ or in the NZ?

See above, authorities that are needed for NZ-linked bibs should live in an IZ

Do local decisions about certain LCSH terms have any bearing on this (Illegal Aliens, for example)?

Pros and cons for using IZ vs. NZ for campus authority records?

What do we want to test during the Vanguard stage?

How do local authorities interact with global ones

Are links between local ARs and other types of records maintained?

Who (campuses or SILS groups) needs to talk to Ex Libris and when?

UCLA and RMFG chair have both posted to Basecamp

For go-live local authorities can be enabled “at any time”

Is CDL in charge of setting them up for the NZ?

What permissions/roles are needed in Alma?

Action Log

Action/Point Person

Expected Completion Date

Notes

Status

  • No labels