Resource Management

This page links to documents related to the following Resource Management workflows and processes:

  • Bibliographic record creation & maintenance, including record imports
  • Holdings record creation & maintenance
  • Item record creation & maintenance for physical resources

Documentation on this site will continue to change as we gain experience in Alma and UC Library Search, and as new features, processes, and policies are introduced. If you notice anything that needs to be updated or fixed, please let us know using the feedback form.

Contents

APriCoT functional area lead

Resource Management functional area lead: Adam Baron (adam.baron@berkeley.edu)


Information sources

UC Berkeley Resource Management Group

The Resource Management Group (RMG) is responsible for developing and maintaining policies, procedures, and workflows for cataloging in Alma, ensuring alignment systemwide and locally.

UC-wide general resources

Presentations

UC-wide Resource Management: Cataloging and Metadata Operations Subteam

Problem reporting

Requesting and updating Alma roles

Required Alma roles

To perform basic Resource Management functions, the following Alma roles are required:

  • Cataloger
  • Physical Inventory Operator or Physical Inventory Operator Limited
    • Tasks: Create and manage physical inventory for the scoped library or libraries. For Physical Inventory Operator, move inventory from one bibliographic record to another.
    • Required training: UC Berkeley RM training. Module 5
Optional Alma roles

Additional Alma roles that are commonly assigned include:

Additional Alma roles that are not commonly assigned include:

For information on requesting or updating Alma roles in production or the sandbox, see Requesting and updating Alma roles.

Training

UCB RM documentation

Alma Analytics

Alma bibliographic, holdings, and item records

Bibliographic records

Holdings records

Item records

Binding

Cataloging procedures

Cataloging statistics

FAQ

OCLC

Physical processing

Unit procedures

Bancroft Library

Collection Services

Metadata Services

Systemwide Library Facility-North (SLF-N)

Withdrawals

By abaron on 11-27-2025

Pages

Interim procedures for creating Host Bibliographic Records that continue the status quo of records that were created on migration to Alma in 2021, and are not meant to represent any final decisions regarding Berkeley’s treatment of Host Bibliographic Records. The procedures are meant to provide guidance for catalogers to create records that can be updated in batch, along with the migrated records, as any changes are implemented in their treatment.

By gosselar on

Options for removing or working around unreceived/missing issues when binding serials.

By jcripe on

This document contains the processes and use cases for deleting item records which were created recently in error. This document does not cover deletion for catalog maintenance nor what are traditionally considered as withdrawals.

By jcripe on

This Collection Services Division policy identifies which components of newly acquired resources are considered to be essential to retain, describe, and preserve. This policy also applies to the preservation of circulating collections, as well as any changes that may be made to a catalog record.

By abaron on

This document outlines the procedure for receiving an exact match monograph replacement for an item in our collection.

By jcripe on

This procedure presents the steps for marking Alma bibliographic records in the Institution Zone (IZ) so they are not linked to the Network Zone (NZ).

By abaron on

Common genre/form terms in use by the Bancroft Library.

By rbrandt on

This document provides guidance for units to submit lists of items to be withdrawn in batch by Metadata Services.

By abaron on

This document covers coding best practices for fields and subfields in holdings records.

By gosselar on

Holdings records in Alma contain data about where to locate specific items within our libraries. Every holdings record is linked to a single bibliographic record; every item record is linked to a single holdings record. Holdings records may also have attached POLs (order records). Holdings records are created and modified within the Metadata Editor (MDE).

By abaron on