Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
Document status

Status
titleDRAFT

Area coveredCataloging, Import Profiles
Lead AuthorJeremy Hobbs
Co-authors

Background

Management When importing records management tags can be used to suppress bibliographic records from display in Primo and to synchronize holdings with OCLC.

...

The task force recommends that campuses not suppress bibliographic records from Primo. The Orbis Cascade Alliance has found that suppressing at the bibliographic level may have negative consequences on collection analysis and statistics and may cause confusing displays in Primo. https://www.orbiscascade.org/suppression-of-records-for-physical-inventory/In

Furthermore, in an import profile established at the network zone level, it is unclear unknown how holdings would be synchronized by Alma . It is unclear if holdings would be set whether at the CSU NZ level or at the individual campus level.

Exlibris documentation on managing records in a network zone states that “publishing publishing to OCLC is processed at the local institution level since this process is used to expose institutions' physical holdings. Each institution in a collaborative network determines how bibliographic and holdings records are published.”https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(English)/Managing_Multiple_Institutions_Using_a_Network_Zone/03_Managing_Records_in_Consortia

The task force recommends that OCLC holdings be updated through an automatic job established in each campus’ instance of Alma. For a description of setting up this job please see Exlibris documentation. http://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(English)/Integrations_with_External_Systems/030Resource_Management/110Publishing_to_OCLC#Publishing_Print_Holdings_to_OCLC

Best practice recommendations

...