Alma Ex Libris: Library Services Platform Guide

Ex Libris Alma is a cloud-based library services platform (LSP) developed by Ex Libris, a Clarivate company. Built for academic, research, and national libraries, Alma consolidates print, electronic, and digital collections into a single Software-as-a-Service (SaaS) environment. Academic librarians and systems administrators use Alma to unify acquisitions, cataloging, fulfillment, and license management across institutions and consortia.

This guide explains Alma’s system architecture, its three-tier metadata zones, standard staff search workflows, and how it compares with alternatives such as OCLC WorldShare.

What It Is

Alma is a multi-tenant SaaS Library Services Platform (LSP). In library architecture, an LSP supersedes legacy Integrated Library Systems (ILS) by merging print workflows with electronic and digital collection management.

Historically, libraries operated fragmented software silos:

An Integrated Library System (ILS), such as Voyager or Aleph, managed physical books, serial check-ins, and circulation desks.
An Electronic Resource Management (ERM) system, paired with an OpenURL link resolver like SFX, managed electronic journal licenses and publisher portfolios.
Standalone repositories managed locally digitized photos, audio, and manuscripts.

Alma unifies these operations into a single web-based application covering fund allocation, vendor ordering, cataloging, discovery indexing, and interlibrary fulfillment.

Alma differs fundamentally from patron discovery and research information tools:

Alma vs. Primo: Alma is the back-end staff platform where inventory, purchase orders, and licenses live. Ex Libris Primo (or Primo VE) is the public-facing discovery layer that students and researchers use to search the catalog. Primo queries Alma in real time to display item availability and access links.
Alma vs. Esploro: While Alma manages library collections, Esploro (Ex Libris) is a Research Information Management (RIM/CRIS) platform that tracks faculty publications, research datasets, grants, and open-access compliance.

Who Runs It and What It Covers

Alma was developed by Ex Libris, founded in 1980, acquired by ProQuest in 2015, and integrated into Clarivate in December 2021. Development began in 2007 in partnership with research libraries to lower total cost of ownership and unify disparate systems. Today, Alma is deployed across thousands of higher-education and research institutions globally.

Alma covers three resource formats across their lifecycle:

Physical Collections: Print monographs, serial volumes, archival boxes, shelf locations, call numbers, barcodes, and automated materials handling (AMH) sorter integration.
Electronic Collections: E-books, electronic journals, aggregator packages, database access points, licenses, renewal dates, and automated vendor EDI invoicing.
Digital Collections: Digitized university archives, manuscripts, image galleries, and audio/video files with digital rights and streaming profiles.

To balance institutional control with shared efficiency, Alma organizes metadata across three collaborative zones:

Institution Zone (IZ): The private institutional database containing local inventory, physical item records, local classification notes, order lines, and user patron accounts.
Community Zone (CZ): A global, centrally maintained knowledge base shared across all Alma subscribers. Ex Libris and publisher partners supply standardized bibliographic records and electronic portfolio packages. When a library subscribes to a package, staff activate it in the Community Zone with one click, inheriting coverage dates and linking targets without manual title-by-title cataloging.
Network Zone (NZ): A consortial database for multi-campus university systems (such as the California State University system). The Network Zone enables a shared union catalog, collaborative cataloging, coordinated acquisitions, and consortial interlibrary loans.

How to Search or Use It

Alma is accessed through a browser-based staff portal authenticated via institutional Single Sign-On (SSO/SAML). User privileges are governed by role-based profiles (e.g., Cataloger, Purchasing Manager, or Fulfillment Services Operator).

To find repository records or administrative data, staff follow these standard interface steps:

Access the Persistent Search Box: Focus the persistent search bar at the top of the interface. Press the forward slash (/) keyboard shortcut from any page to jump to the search field.
Select the Search Entity Type: Open the first drop-down menu to specify the target domain. Choose repository entities (such as All titles, Physical titles, Electronic portfolios, or Digital titles) or operational data (including Order lines, Invoices, Vendors, Funds, or Users).
Select the Search Field Index: Open the second drop-down menu to select an indexing field. The default is Keywords (or All), but it can be scoped to Title, Author, Subject, ISBN, ISSN, MMS ID (Alma’s internal Metadata Management System identifier), or Call number.
Choose the Search Scope Tab: Select the search zone tab: Institution for local holdings, Community for vendor knowledge-base packages, or Network for consortial holdings.
Enter Query Syntax: Type the search string. Multiple terms are implicitly combined with Boolean AND. Surround terms in double quotation marks (e.g., "machine learning") for exact phrase searching (Contains Phrase). Use a trailing asterisk (*) for wildcard truncation.
Execute Search and Apply Facets: Click the magnifying glass icon or press Enter. On the repository search results page, refine results using left-hand faceted filters (Resource Type, Library, Availability, Language), view holdings in the Sliding Panel, or select Edit Record to open the item in the Metadata Editor (MDE).

For technical cataloging, staff open the Metadata Editor via Resources > Cataloging > Open Metadata Editor. The editor supports MARC21, UNIMARC, KORMARC, Dublin Core, MODS, and BIBFRAME, with normalization rules on save. Alma integrates externally via OAI-PMH for repository harvesting, SIP2 and NCIP for circulation hardware, and electronic holdings feeds that configure full-text access in Google Scholar Library Links.

Strengths and Limits

Deploying Alma provides substantial operational benefits alongside management considerations:

Strengths

Unified Operations: Single interface managing physical, electronic, and digital workflows, eliminating duplicate entry across separate systems.
Community Zone Efficiency: Shared vendor-maintained package metadata saves thousands of hours of local cataloging labor.
Multi-Tenant Cloud SaaS: Centralized monthly updates delivered via regional data centers eliminate local server maintenance and OS patching.
Consortial Scalability: Network Zones provide shared union catalogs and automated borrowing across multi-campus networks.
Embedded Analytics: Alma Analytics provides data-driven reporting on fund expenditure, circulation, and automated COUNTER usage harvesting.

Limits

Administrative Complexity: Extensive configuration menus, custom rule tables, and granular role permissions require dedicated systems administrators.
Community Zone Maintenance: Vendor-updated Community Zone packages can occasionally introduce metadata errors or portfolio mismatches that require local oversight.
Commercial Cost: Enterprise SaaS subscription pricing can be prohibitive for smaller libraries.
Multi-Tenant Standardization: Libraries cannot modify underlying database structures directly and must work within Ex Libris APIs and UI configurations.

Alternatives

Libraries evaluate several enterprise alternatives when choosing a modern management system:

Platform	Provider / Architecture	Metadata Model	Target Institutions	Key Trade-Off
Ex Libris Alma	Clarivate (Commercial Multi-Tenant SaaS)	Three-Tier Zones (Institution, Community, Network)	Medium-to-large academic research libraries and large consortia	Comprehensive functionality and analytics; high commercial licensing cost and administrative complexity.
OCLC WorldShare Management Services (WMS)	OCLC (Non-profit Multi-Tenant Cloud)	WorldCat-Centric Global Shared Union Catalog	Academic, research, and specialized institutions of all sizes	Seamless integration with OCLC WorldShare and WorldCat interlibrary loan; less granular local workflow customization.
FOLIO	Open Source (Community / EBSCO Hosting)	Modular Microservices (Local or Shared Tenants)	Academic institutions seeking open-source autonomy and vendor flexibility	No commercial license fees and complete architectural freedom; requires self-hosting expertise or third-party hosting contracts.
SirsiDynix Symphony	SirsiDynix (Commercial Hosted / ILS)	Relational Database with Cloud API Extensions (BLUEcloud)	Public libraries, consortia, and mid-sized academic institutions	Robust physical circulation and item management; electronic resource management relies on add-on modules rather than unified LSP design.

FAQ

What is the difference between Ex Libris Alma and Primo?

Alma is the back-end staff management system used by librarians for acquisitions, cataloging, license tracking, and circulation policies. Primo is the public-facing discovery interface used by patrons to search the collection, view real-time availability, and access electronic full text. Primo retrieves availability and holdings from Alma via live APIs.

What is the difference between the Institution Zone and Community Zone in Alma?

The Institution Zone (IZ) contains an institution’s private local inventory, physical item barcodes, circulation rules, and patron records. The Community Zone (CZ) is a global shared knowledge base populated by Clarivate and contributing libraries with standardized bibliographic records and electronic portfolio packages.

Which cataloging and metadata standards does Alma support?

Alma supports MARC21, UNIMARC, KORMARC, Dublin Core, MODS, and BIBFRAME in its Metadata Editor. It offers real-time cataloging rule validation, normalization processes on save, and automated authority linking.

Can Alma integrate with non-library campus systems?

Yes. Alma provides REST APIs and supports industry standards including SIP2 and NCIP for circulation hardware, OAI-PMH for repository synchronization, and automated data pipelines for campus Student Information Systems (SIS) and enterprise finance/ERP systems.