Alma 2026 Release Notes
- Last updated
- Save as PDF
Release:
Main Features
Prevent Requests for Blocked Loans
Idea Exchange
CERV Enhancement (ID#36426) URM-195332Alma can now be configured to block item requests when a patron is not eligible to loan the item based on its loan terms of use and any existing blocks on the patron. This ensures that patrons cannot place requests for materials that cannot be loaned to them under the library’s defined policies.
The configuration is controlled by the block_request_if_not_loanable parameter (Configuration > Fulfillment > General > Other Settings).

For more information, see Configuring Fulfillment Jobs, Creating a Request from the Institution and How to Set Up Blocks to Prevent Loaning, Renewing and Hold Requests for Patrons.
Update of User Data for Fulfillment Network in Real Time
Idea Exchange URM-322736When the source institution of a user changes user details, all of its linked accounts now receive this update in real time. This update will help ensure that linked account information is consistent and accurate across all institutions.
For more information, see Linking Users in Collaborative Networks.
RFID Support in Shipping Items Page
It is now possible to read the RFID tag when shipping an item for resource sharing.

When selecting Ship item physically, the sliding panel remains open, and the user should manually close it after receiving a success message.
For more information, see RFID Support.
Updated Customization Options for Document‑Delivery Login
The login page (when authentication is done with an LDAP server or by the Ex Libris Identity Service) and the document download page for digitally supplied documents now support configurable labels and color settings, enabling a more tailored patron experience. You can access the configuration page at Configuration > Fulfillment > Document Delivery Login Screen.

For more information, see Configuration of Digital Shipping.
Additional Information Field for Borrowing and Lending Requests
A new Additional Information dropdown field was added to the Request Attributes section. The information is added to borrowing requests and can be viewed and edited in lending requests.

This field only appears if values were added to the new Patron Additional Information table (Configuration > Fulfillment > Patron Additional Information).
For more information, see Managing Borrowing Requests, Managing Lending Requests and Basic Resource Sharing Configurations.
Specific Edition Information Available on Lending Requests
If a specific edition is selected on the borrowing request, whether added by staff manually creating the request or by the patron/library user, this information will now be visible in the Request Attributes section on borrowing requests and in the Request Attributes and Request Form sections in borrowing and lending requests. This provides users with more information to inform their workflow.


For more information, see Managing Borrowing Requests and Managing Lending Requests.
OCR for Received Documents
New functionality will determine if a digitally supplied PDF file already has Optical Character Recognition (OCR) applied. If not, OCR will automatically be applied when the lender ships requests from the lending workflow actions, before they are delivered to the borrowing partner.
For Alma as the lender for ISO partners, PDFs supplied by Alma lenders will also have the OCR automatically applied via the lending shipping actions.
For more information, see Managing Lending Requests and Digitization Processing.
Sharing Limits Across the Network
Libraries participating in a fulfillment network can now apply their local patron limits, such as maximum loans, requests, cash balance, or overdue thresholds, across the entire consortium. When a patron reaches a defined limit at any institution in the network, a library may choose to block the patron’s activity locally. This supports consistent policy enforcement and improved fairness by helping maintain equitable access to shared resources across the consortium, and it supports stronger network governance.

This feature affects all blocks in the Patron Limits list (Configuration > Fulfillment > Patron Configurations > Patron Limits) and the patron's Loan Limits that are defined per User Group (Configuration > Fulfillment > Loan Limits). The library can decide to block its own patrons and/or guest patrons, using the ful_network_limits_block_source and ful_network_limits_block_target customer parameters (Configuration > Fulfillment > General > Other Settings).
These limit‑based blocks do not appear in the user’s Blocks tab. Instead, librarians see them as pop-ups or messages during the workflow. The messages describe the problem and the originating institution.
-
This feature impacts networks that use linked accounts or that share users in the Network Zone.
-
It will be available on the Production and Sandbox environments in the release update, planned for 10 May.
For more information, see Configuring User Blocks and Configuring Fulfillment Jobs.
Partner‑Level Configuration for ignore_lender_due_date
Idea Exchange URM-72484It is now possible to override the ignore_lender_due_date parameter at the individual partner level. This enhancement allows institutions to specify which lenders’ due dates should be disregarded when calculating a patron’s loan due date, while still honoring due dates from other partners as needed. This enables more precise policy alignment. Libraries can tailor due‑date handling to align agreements or expectations with specific lending partners.
For more information, see Configuring Fulfillment Jobs and Resource Sharing Partners.
Streamlined Document Delivery Upload and Notification
This new workflow enhancement enables staff on the borrower side to upload a digital file for fulfilling a patron’s document delivery request, update receive parameters such as costs, and simultaneously notify the lending library — all in a single action. This enables staff to complete fulfillment and lender notification in a single streamlined step, reducing processing time and manual effort.

For more information, see Managing Borrowing Requests and Peer to Peer Resource Sharing.
Improved Navigation for Hold Blocks Information
The display of block information during hold, booking, and digitization request creation has been redesigned to streamline the workflow and reduce interruptions. Previously, block details appeared in a pop‑up after entering the Requester in the request form. Now, this information will only pop up after selecting the Calculate Blocks button in the request form, allowing staff to review block status only when needed.

If the pop_override_hold parameter (Configuration > Fulfillment > General > Other Settings) is set to false (true by default), the Calculate Blocks button will not appear.
For more information, see Other Settings.
Automatic Due‑Date Adjustment for Early Patron Expiry
Idea Exchange
CERV Enhancement (ID#6737) URM-97328Alma can now automatically update a patron's loan due dates when a patron's expiry date is moved to be earlier. If a loan’s due date extends beyond the new patron expiry date, the system can now adjust it to ensure the loan does not exceed the patron’s active account period. This is controlled by the Update Loans for Shortened User Expiry job (Configuration > Fulfillment > General > Fulfillment Jobs Configuration).
Due dates that were intentionally set beyond the patron’s expiry date using the extend_due_date_beyond_user_expiry parameter will not be changed. For institutions that enabled this customer parameter, loans whose loan date is before the new feature release will be excluded from this job.
Claim returned and lost loans are also excluded from the Update Loans for Shortened User Expiry job. Note that this job triggers the Loan Status Notice letter.
This enhancement prevents loans from remaining active past a patron’s eligibility and helps maintain accurate, policy‑aligned loan records.

For more information, see Configuring Fulfillment Jobs and Scheduled Jobs.
Configure Resource Sharing Library as Temporarily Inactive
Idea Exchange URM-222487Fulfillment Services Managers and Fulfillment Administrators can now temporarily close a library for lending by adding an Inactive date range (Fulfillment > Resource Sharing > Temporary Inactive Date Ranges). This gives libraries greater flexibility and reduces the administrative workload associated with managing temporary closures. Note that Fulfillment Operators can also enable this feature by opening a ticket with the Support team.
.png?revision=2)
Pickup Location Field Removed for Digital Resource Sharing Requests and Blank Request Forms
CERV Enhancement (ID#8562) URM-316507The Pickup Location field on Resource Sharing Digital Request Forms and Blank Request Forms is now hidden when Institutions create a digital request. This helps reduce confusion since the Pickup Location field is relevant to the Physical Request forms.

Pickup Location field removed
This is controlled by the rs_default_pickup_location_when_hide and rs_hide_pickup_location_for_digital parameters. For more information, see Other Settings.
Linking from Borrowing Request to Locate Process Log
It is now possible to link from the borrowing request to the job information for the last locate job that ran for the request. This makes it easier to understand how the locate process determined which partners to leave on the rota and which to remove.


For more information, see Managing Borrowing Requests and Locating Items for Resource Sharing.
Storage Location ID Can Now Be Managed as a Closed List
A new option is now available to manage the Storage Location ID field as a controlled list on the physical item. Enabling this feature also provides a configuration option for maintaining the entries. This enhancement is particularly beneficial for libraries that work with remote storage facilities and maintain a large number of Storage Location ID entries on their physical items in Alma.

- Contact Support to enable this feature.
- This capability is available for up to 100,000 storage IDs.
- The <More...> indicator is for informational purposes only and will be updated in a later release when the Item page moves to the NG layout.
For more information, see Storage Location ID.
Update MARC21 Bibliographic Resource Types
Idea Exchange URM-319073 URM-319489This update enhances the Alma MARC21-Based Resource Type classification to improve the accuracy, coverage, and usability of bibliographic resources. Alma determines the resource type automatically based on metadata fields, enabling more precise filtering and reporting. The enhancement introduces additional resource types that were previously unavailable, enriching the classification system.
To apply the new and improved resource types to existing records, the bibliographic data must be re-indexed. The next scheduled re-indexing will take place at the end of June 2026.
Enhanced Sorting by Full Publication Date
Previously, sorting by Publication Date was limited to the year component only. With this update, when full date metadata is available, sorting is now performed using the complete date, including year, month, and day. This aligns with existing indexing and sorting logic and enables accurate chronological ordering. As a result, institutions managing daily or frequently published content benefit from improved discoverability and a more consistent and precise sorting experience.
For more information, see Sorting Search Results.Expose Linked Headings in Simple Record View
Idea Exchange URM-238773
Configurable Pop-up Assistance
Idea Exchange URM-122158Catalogers can now customize their workflow by toggling the pop-up assistance on or off for selected subfields, giving catalogers more flexibility and control, reducing frustration and improving efficiency.

For more information, see Configuring Other Settings.
Linked Open Data (LOD) BIBFRAME Editor Enhancements
Form Editor Actions
The following actions are now available in the LOD BIBFRAME editor:
- View Work (for class instance only)
- Duplicate
- Create Instance (for class work only)
- View Instance (for class work only)
Enhancements to the Linked Open Data Editor Form and Templates
When editing a BIBFRAME record, section-level and field-level actions for adding, duplicating, and deleting sections are now available.

When hovering over the Add Section/Field or Duplicate Section/Field icons, a horizontal line appears, indicating where the section/field will be added.


It is still possible to scroll to the end of the sections and use the Add Section/Add Field buttons to the end of the sections.
Additionally, BIBFRAME records and template sections can now be reordered using the Reorder button. The new order is then applied when creating and editing records and templates.

Linked Open Data Editor Form — Manual Input Now Available for Lookup
When using the lookup service, a Manual input of data, label and/or URI icon is now available for catalogers to manually add labels and/or URIs.

For more information, see How the Lookup Service Appears in the Editor.
Relations for BIBFRAME from the Linked Open Data Editor
The out-of-the-box templates now include a relations section that is valid with the ontology and supported within Alma's relations job.

For more information, see BIBFRAME Support and Creating a BIBFRAME Records and Templates.
BIBFRAME and BFLC Ontology Update
Alma has updated the metadata standard for BIBFRAME and the BFLC extension to support version 3.0, maintaining the standard to support valid BIBFRAME creation within Alma.

Additionally, a Restore action is now available on the Linked Data Active Profile views to restore the out-of-the-box default value for any changes applied to an ontology.

For more information, see Customizing Field Labels and Descriptions.
Supporting Sets for BIBFRAME Works
Librarians can now create sets for BIBFRAME works, for both logical and itemized sets. Using work sets in different workflows will expand over time, based on need and use cases. Currently, sets can be created within a work search and edited and managed from the Manage Sets menu.

The bulk actions in the work search were replaced to align with the general Alma bulk action standard.

For more information, see Set Content Types and Work Search.
Enhanced Handling of Library and Location in the Physical Holdings Search
The holdings search was updated so that it is now possible to:
- Facet by location without first faceting by library — the library name is displayed in brackets to distinguish between similar locations in different libraries.

- See the library and location information according to the Repository search results configuration — in the record view, facets and export to Excel.

This update may impact the content of the exported holdings file.
- Configure a separate display for the table view of the search results to enable libraries to select a more condensed view for the table, maximizing the value of the table format.
Library/Location Display Configurations
Table View - Library/Location Columns
For more information, see Customizing How Library and Location Appear.
New View Options for BIBFRAME Records
Alma now supports easy navigation between different BIBFRAME record views, so each user can find the view that best suits them.
To enhance interoperability of BIBFRAME, the BIBFRAME work record now includes the Turtle (.ttl) view mode option.

Additionally, we have introduced a new condensed display for BIBFRAME records in a table view, enabling as much metadata as possible within a section and using the familiar display known to catalogers from MARC formats.

For more information, see Work Search.
Improved Language Support in AI Metadata Assistant, Using Optical Character Recognition
URM-322839The AI Metadata Assistant enables catalogers to easily extract metadata from images and files to streamline the cataloging process. The text is extracted from images by the AI LLM model used in the assistant, as part of the metadata generation process. However, for some languages, scripts, and resource types, lower LLM optical character recognition accuracy may result in lower metadata quality. It is now possible to apply a dedicated OCR tool to improve results for those resources — the LLM then generates metadata based on the text extracted by the OCR tool, rather than directly from the image, leading to improved support for more languages and resource types. Catalogers can select their preferred text extraction method for the specific resource being cataloged:
- AI Metadata Assistant — text processed by the LLM as part of the metadata generation (as today).
- Azure Document Intelligence — an advanced, AI-based OCR service with extensive language support.
- Tesseract — a seasoned, robust OCR tool for extracting text from images and files.

This is especially beneficial for libraries cataloging resources in languages and scripts with lower LLM OCR capabilities (e.g., non-Latin scripts).
For more information, see Enriching a Brief Record.Enrich Bibliographic Records in Bulk Using a Streamlined Copy — Cataloging Process and AI Title Matching
URM-325022A new job, Enrich Bibliographic Records, enables the library to enrich a set of up to 1000 records, streamlining the search for matching records in its existing search profiles and copy-cataloging partners, filtering and assessing the results, and providing copy-cataloging recommendations to the cataloger.
As a first step, the Enrich Bibliographic Records job supports searching in Alma copy-cataloging partners to avoid overwhelming external resources with a large volume of search queries they’re not prepared to handle. Support for external copy-cataloging partners will be added in the future, based on the community's needs and subject to their ability and agreement to handle a large volume of search queries.
This is especially useful for libraries enriching their bibliographic records from copy-cataloging partners, making the process easier, faster, and more efficient.
For more information, see Working with the Enrich Bibliographic Records Job.
Alma AI Assistant for Acquisitions Funds and Ledgers: Now Supports Actions! (and additional improvements)
URM-322774The Alma AI Assistant for Acquisitions Funds and Ledgers was introduced in the February 2026 release in preview mode (beta). After an additional phase of feedback and improvements, it is now available for general availability and can be enabled in Configuration Menu > Acquisitions > AI Features > AI Features Management.
The Alma AI Assistant enhances the user experience by enabling users to interact with Alma through a chat-based interface. Instead of navigating multiple screens and workflows, staff users can ask questions naturally and receive clear, relevant responses directly within Alma.
Supported Actions
It is now possible to perform actions directly from the Assistant chat interface.
Supported actions include:
- Allocate money to a specific fund
- Transfer money from fund to fund
The activate/deactivate a specific fund action will be available in a future release.
Similar to the assistant's follow-up questions, it might also suggest actions to take, depending on the conversation's context. For example:

You can use the assistant suggestions for actions, or alternatively start a conversation with your desired action, for example, "I want to..."
Before taking action, the assistant checks that all necessary information has been supplied and requests confirmation.
The action is performed using the Alma APIs (which the assistant uses as a tool). Similarly to cloud apps, which utilize APIs, the user who is kept as the modifier is the connected user.
Additional Improvements
- The Alma Assistant now identifies funds regardless of the case. For example, questions on fund "data" are answered even when the fund name in Alma database is DATA.
- Questions on fund transactions are answered with information on the transaction's related PO line or invoice. Until now, the ID was returned, which is not useful. Now, the response includes the PO line number or invoice number with the line number. Staff users can use the information and continue their work in Alma.
- The assistant now supports special characters in fund names, e.g. "Art & History fund".
For more information on enabling the feature, how it works, and our planned enhancements, refer to the Alma AI Assistant – Acquisitions Funds and Ledgers documentation. Also see Artificial Intelligence in Alma.
New Setting for Community-Linked Electronic Services to Keep Portfolios Active When Removed from the Community
Idea Exchange URM-320621Services of collections activated from the Community Zone now include a new configuration option that controls whether portfolios deleted from the Community Zone and localized in the institution are deactivated or kept active. The new setting (Automatically deactivate portfolios removed from service?) is relevant when the service is configured as non–auto-delete (meaning portfolios are localized rather than deleted when removed from the Community Zone). The setting determines how localized portfolios behave after they are removed from the Community, giving customers more granular control over Community Zone linked resources.
-
Deactivate — This is the default. It preserves the current behavior. Portfolios are unlinked from the Community Zone and set to Not Available in the institution.
-
Keep all active — Portfolios are unlinked from the Community Zone but remain Available in the institution.
-
Keep perpetual access portfolios active — Portfolios are unlinked from the Community Zone and handled based on their access type:
-
Portfolios with perpetual or current and perpetual access remain available.
-
Portfolios with current access are deactivated.
If the portfolio does not have an access type defined, the collection’s access type will be used.
-
For existing electronic services defined as non–auto-delete, the existing behavior will remain, and they will, by default, be defined to automatically deactivate.
The new setting can be updated manually in the service editor or in bulk using the Change Electronic Collection Information job, E-Collection Quick Update cloud app or via the API.
As before, linked portfolios that were deleted from the Community Zone will be reported on the Community Zone Updates Task List, but with a new dedicated report type for portfolios that were kept active in the institution.
The new setting will be available for reporting in Analytics, allowing users to create reports based on resource configurations. For more information, view the data dictionary for the e-inventory subject area (see E-Inventory).
For more information on this feature, see Activating Electronic Resources from the Community Zone and Managing Electronic Resources.
Electronic Resources Incident Reporting: Updated Company Name and More
The company name for reporting incidents related to collections/portfolios was updated to Clarivate, in order to align with the Clarivate brand.

The following fields were also added to the Additional info section to include all information that might be needed to fix the issue.
- Indication if the collection is an autoholding and if the autoholding profile is defined
- Provider collection ID and name
- DBID
- Portfolio ID (local Portfolio ID i.e., IZ id and global Portfolio ID i.e., CZ id)

The Additional info now consistently displays the relevant information, even when updating the CRM category.
For more information, see Configuring CRM Contacts.
Rialto Market Search Now Available to All Alma Users
May 2026 Resource Management NGS-14456
To strengthen integration between Rialto and Alma and better support collection development activities, a streamlined Rialto experience is now available to everyone with Alma access. Activation of Rialto Search happens automatically; no opt-in is required.
Rialto Search provides a lightweight marketplace discovery experience. All Alma users can now access the Collection Development > Market section to:
- Perform basic and advanced searches in the Rialto marketplace for title availability and pricing
- View real-time calls for holdings, course materials, and books available through Rapido resource sharing
- Explore curated lists featuring high-quality titles across a range of subjects
- Export marketplace results for further review and analysis
Market searches perform real-time calls to Alma for local and network holdings to provide accurate visibility into owned access. If enabled at the institution level, you can initiate a Rapido borrowing request and see course-related information for items associated with Leganto lists directly in search results.
From the search results, users can email marketplace offers to other Alma users within their institution. They can also create purchase requests for selected items, if they have the appropriate Alma role.
This update expands access to Rialto capabilities across a broader user base, enabling more staff to participate in resource discovery and selection workflows. For more information, see Rialto Search.
This feature is not available in Sandboxes prior to the May release.
Advanced Tools Added to the Collection Development Menu
To ensure all tools relevant to collection development are available in one central location, selected advanced tools are now also accessible from the Collection Development menu. These tools remain available in their original location (Resources > Advanced Tools) and function identically from both menus.
The following tools have been added to Collection Development > Advanced Tools:
- Overlap and Collection Analysis — Comparison of collections and title lists to identify overlapping and unique content, which enables data-driven decisions for purchases, renewals, and cancellations.
- Duplicate Title Analysis — Identification and grouping of potential duplicate bibliographic records, which supports metadata cleanup and reduces overall redundancy.
- Merge Records and Combine Inventory — Consolidation of duplicate records into a single preferred record, which leads to cleaner and more accurate catalogs.
To access and use these tools, a user must have the Collection Development Manager role plus the specific operational role required for each tool:
- Overlap and Collection Analysis — Purchasing Operator, Purchasing Manager, Repository Manager, or Electronic Inventory Operator
- Duplicate Title Analysis — Repository Manager
- Merge Records and Combine Inventory — Catalog Administrator, Catalog Manager, or General System Administrator
This update improves visibility of key collection development tools, helping users discover and use functionalities that may have previously been overlooked. For details, see Advanced Tools.
Support for Barcodes When Creating Projects from a File
Previously, creating collection development projects from a file required the uploaded file to include a column with item IDs. With this update, you can now also create projects from a file that contains a column of barcodes.
Once a file with barcodes is uploaded, the rest of the project creation process works exactly as it does when using a file that contains item IDs.
This enhancement makes project creation more intuitive by enabling staff to use barcodes—the identifiers they most likely work with daily—rather than system-generated item IDs, reducing extra steps and making file creation more intuitive.
Deeper Insight into External Holdings
May 2026 Resource Management URM-322033
To support deeper cross-institution analysis, Rialto now offers expanded bibliographic details in the Compare To section when inspecting individual recommendations in projects with external comparisons.
While the Compare To section itself remains unchanged in the main view, the sliding panel under View full list and additional information now displays expanded metadata for matching holdings. Newly added fields include:
- Library
- Publication Place
- Edition
- Material Type
- Language
- OCLC
These additional data points provide deeper insight into external holdings, enabling more informed retention and deselection decisions when comparing your collection to other institutions.
Country-Based Selection in the Compare To Section
May 2026 Resource Management URM-320716
The Compare To section for retention and deselection projects that include comparisons with external institutions has been enhanced to provide a more structured, country-based selection experience.
When creating a new project or editing an existing one, users can now browse comparison institutions using a country tree view. First, select a country to display all available institutions within it. You can then choose specific institutions individually, or select the checkbox next to the country name to automatically include all institutions within that nation.

This enhancement simplifies the process of selecting comparison institutions and makes it easier to locate relevant libraries without having to navigate a long alphabetical list.
Enhanced Sorting for Collection Development Recommendations
May 2026 Resource Management URM-306163
Rialto now provides more flexible sorting options when viewing recommendations in retention and deselection projects. In addition to sorting by Title and Publication Date, you can now also arrange recommendations by:
- Library / Location
- Call Number
You can also apply a secondary sort to further refine the results' order. The secondary sort uses the same set of fields—Title, Publication Date, Library / Location, and Call Number—and enables additional ordering when multiple recommendations share the same primary sort value.

These enhancements make it easier to review, compare, and organize recommendations, especially when working with large result sets that include many items from the same library or publication period.
New Fields in Change Electronic Portfolio Information Job for Expanded Batch Updates
Idea Exchange URM-39199New fields were added to the Change Electronic Portfolio Information job to support expanded batch updates:
-
Set coverage statement to be applied — A new dropdown (Only local, Global and local, Global or local, Only global) that updates the Which coverage statement will be applied? value in the Portfolio Editor. Note that this does not update standalone portfolios.
-
Set access type – A new dropdown (Current, Perpetual, Current and perpetual, Empty) with condition options (If field empty, If field not empty, Unconditionally – default). It updates the portfolio Access Type field.
-
Remove URL/parser override — A new option that clears all URL/parser override fields in the portfolio Linking tab (Parser parameters override, Dynamic URL override, Static URL override).
-
Electronic Material Type — A new empty option – The existing dropdown now includes an empty value that clears the field, aligning with the Portfolio Editor UI. Note that if the portfolio is linked to the Community Zone (CZ), and the linked portfolio in the CZ has an Electronic Material Type, then when selecting an empty value, the job will overwrite this field with the value in the CZ. For example, if the value in the CZ is Journal, and you select the empty value, then after saving, the field in the local portfolio is updated to Journal.

For more information, see Manual Jobs.
Easier Organization for Description Templates
Idea Exchange URM-198843The description templates configuration page (Configuration > Resources > Description Templates) has been enhanced to allow easier rule reordering via drag-and-drop.

For more information, see Configuring Item Description Templates.
Upcoming Electronic Collections
Providers can now send Ex Libris information about collections that do not yet have title lists, provided the collection name is already available.
In these cases, a new “placeholder” collection containing the collection name, provider collection ID, provider name, and expected due date will be created in the CZ, with no option to activate it. The expected due date indicates when the title list is expected to be delivered to Ex Libris, with an additional one-month buffer.
The upcoming collection feature will support better advanced planning for e-resource management by making it possible to see which collections are awaiting title lists and by increasing the overall transparency of the Community Zone.
Once a collection is populated with a title list, activation will be available, as well as other functionality such as acquisition and CDI descriptive fields. Once the collection is populated, we will notify the community in the standard Content Knowledge Base Release Notes, where we announce new collections.
In the Community Zone tab, an upcoming collection will appear with a pre-release indication and a pre-release note, with information from the provider on the planned release of the title list.

We will gradually roll out this development with Adam Matthew. As additional providers include an indication of upcoming collections with a release date, we will be able to extend this solution to other providers as well, as long as they support fully automated metadata delivery.
For more information, see Activating Electronic Resources from the Community Zone.
Prioritizing Online Services in Discovery Based on Current Year Access
CERV Enhancement (ID#36385) URM-248251The Additional Settings section on the Online Services Order configuration page (Configuration Menu > Fulfillment > Discovery Interface Display Logic > Online Services Order) now includes a new configuration option: Prefer services with current year access. This enables institutions to prioritize services with coverage dates within the current calendar year. By default this setting is turned off. When enabled, Alma pushes the current year access resources (according to the portfolio's coverage and embargo definitions in the current year) to the top of the list. This takes priority over all the other criteria.

For Consortia, Network Zone services with current access are prioritized together with Institution Zone services with current access.
For more information, see ViewIt.
Suppress Bibliographic Records Localized When Ordering Electronic Collections from Community Zone
The suppress_bib_upon_cz_ordering parameter was added to Configuration > Resources > Other Settings. When set to true, any newly localized bibliographic record created as part of Community Zone collection ordering is automatically suppressed in the Institution Zone. Bibliographic records that already exist in the Institution Zone, such as when re‑ordering a collection that was previously activated, are not suppressed. The default for this parameter is false.
- Suppression is applied only when a new bibliographic record is localized during the ordering workflow.
- This functionality applies only to ordering electronic collections from the Community Zone. The behavior for ordering portfolios from the Community Zone remains unchanged.
For more information, see Configuring Other Settings (Resource Management) and Activating Electronic Resources.
4th and 5th Reporting Codes Supported in Invoice Lines API and Export Payment
The 4th and 5th reporting codes can now be retrieved and updated by the invoice lines API. Additionally, these codes will now be part of the Export Invoices For Payment job (which can be configured in Configuration Menu > General > Integration Profiles > Editing a Finance profile > Actions).
For more information, see Invoices and Invoice Payment in the Developer Network.
Invoice Creation from PDF/Image by AI (Early Access)
URM-324280A new early access capability is now available: creating an Alma invoice directly from a PDF or image file upload.
Watch a quick demo here: Create invoice from PDF - DEMO
This feature is offered as part of an early access program to gather feedback from a broad range of real-world use cases.
Powered by AI, the process combines OCR (Optical Character Recognition) to extract data from the file with Gen-AI, which transforms this information into a structured invoice, helping streamline and accelerate invoice creation.
Like other AI-based capabilities, this feature is opt-in and must be enabled by an administrator via the AI Features Management configuration page.
Once enabled, a new option will appear under Acquisitions > Create Invoice > From File.

The feature supports PDF uploads of up to 20 pages. Generated invoices are placed in review and clearly marked as AI-created.
Institutions interested in early access are invited to contact: Zohar.Shemesh@Clarivate.com
Legal Deposit Acquisition Methods in PO Lines
The Legal Deposit workflow in Alma includes two letters that are sent:
- Legal Deposit Order Letter
- Legal Deposit Receipt Letter
Until now, when selecting the Legal Deposit Acquisition Method in the PO line, both letters were sent. When selecting Legal Deposit - Without Letter, neither of these two letters were sent. Now, two Acquisition methods were added for cases in which only one of the letters should be sent for the PO line:
- Legal Deposit - Order Letter — Only the order letter is sent
- Legal Deposit - Receipt Letter — Only the receipt letter is sent
For example, when the item has already arrived at the library, upon creating the PO line, the Legal Deposit - Receipt Letter acquisition method can be selected, as there is no need to ask the provider to supply the item.

The Legal Deposit claim is not affected by the Acquisition method selected and will be sent per the Claiming workflow.
For more information, see Manually Creating a PO Line, Configuring Acquisition Methods and Creating Legal Deposit PO Lines.
Hide Configuration links from 'Old' Menu (Partner Account Allowances, Partner Sectors, Partner Organization Type)
URM-325188After adding the Partner Account Allowances, Partner Sectors and Partner Organization Type configurations to the Consortia Central Configuration dashboard in the February release, they have now been removed from the 'old' Alma and Primo VE configuration menus of the Network Zone. Network Zone administrators, while operating at the Network Zone institution, now access those configurations directly through the Central Configuration Dashboard.
The removed configurations from the Alma and Primo VE configuration menus at Network Zone Level are:
-
Partner Account Allowances
-
Partner Sectors
-
Partner Organization Type
For more information on related configurations, see Consortia Central Configuration Dashboard.
Feature Rollout Preferences Page is Available in Consortia Central Configuration Dashboard for Management Purposes
URM-324985It is now possible for Network Zone operators to manage the Feature Rollout Preferences page via the Consortia Central Configuration Dashboard. This improves efficiency and supports central offices in their efforts to manage information across the Network Zone.
This feature is relevant only for consortia operating with a Network Zone setup.
For more information, see Sections and Configuration Options.
AI Features Management Page Now Available in Consortia Central Configuration Dashboard for Management Purposes
URM-322798It is now possible for Network Zone operators to manage the AI Features Management page via the Consortia Central Configuration Dashboard. This new page centralizes all AI features, and replaces, in their respective locations, the AI Usage Profile configurations available in the Consortia Central Configuration under the Acquisitions, Resources and General sections today. This improves efficiency and supports central offices in their efforts to manage information across the Network Zone.
This feature is relevant only for consortia operating with a Network Zone setup.
For more information, see Sections and Configuration Options.
Protection of Shared Rules in a Consortia
URM-317060 URM-319404It is now possible for Network Zone operators and Institution Zone operators to protect their shared rules (Normalization, Merge, Authority Headings, Brief Level and Indication) from being edited or deleted by other Institution Zone users, when the Protection of Shared Rules feature is enabled (Configuration > Resources > General > Other Settings > enable_shared_rules_protection set to True).
Shared rules can now be marked as Protected and will remain fully visible and executable by Institution Zone users, but cannot be modified or removed. Only Network Zone users with appropriate permissions or the Member institution Zone users who created these shared rules can edit or unprotect them. This ensures that only the Network Zone and the creator at the Institution Zone can make changes, thus preventing accidental changes or deletions of shared rules that impact multiple member institutions.

This feature is relevant only for consortia operating with a Network Zone setup.
For more information, see Working with Rules.
Enhancements in New UX for Table-View Navigation in Lists
The table view was redesigned for improved accessibility and usability. Opening the details pane is now done only through the Title field or the view icon in the Actions column - the entire row is no longer clickable. This enables the user to easily copy text from the table cells without opening the right panel.
![]()
This behavior applies to all pages that use a table view.
Now, when the right panel is open in split view, the table displays two columns and the Actions column with the view icon/s. Showing two columns instead of one when the right-panel is open, makes more information easily visible, and switching to the desired row much easier.

In addition, navigation using the Up/Down arrow keys was added.
When the focus is on the title in split view, and the user navigates using the Up/Down arrow keys, the focus on the title is kept, and the right panel is auto-refreshed to display the details of the current record in focus. When focused on any field other than the title and navigating with the Up/Down arrow keys, the focus moves to the next/previous item in the table, but the right panel does not refresh.
This provides users with more precise control when opening records in table view, avoiding unintended row clicks and using clear entry points via the Title or the view icon, which reduces unintended right-panel openings when navigating the table.
For more information, see New Layout.
Rebranding of Ex Libris/Clarivate Logos
The Ex Libris/Clarivate logos were rebranded, and the new logos now appear throughout, for example, in the Alma UX, Customer Support Portal, Developer Network, Current Status page, etc.
Your institution's logo will not be replaced.
.png?revision=1)
French Support for "Fuzzy Search" in Alma Menu Search Bar
We have expanded the functionality of the Alma search menu to include "smart" search capabilities in French (FR). Historically, this feature has supported English, Hebrew and German. However, beginning in May 2026, it has also been extended to the French interface. The search functionality offers suggestions for synonyms, interchangeable terms, and even assists with simple spelling errors. This enhances user navigation, simplifying the process of locating items within the Alma search menu.

For more information, see Alma User Interface.
Support for Create Itemized Set and Add to Itemized Set Actions When Using Select All
For the lists that support the Select All option and for users with roles that support creating sets, the Select All functionality was enhanced to support two additional bulk actions: Create Itemized Set and Add to Itemized Set. In addition, when users select all results, only supported actions are displayed. The actions run in the background, and users receive completion notifications through the Real-Time Notifications panel (see Real-Time Notifications).

For more information, see Managing Search Queries and Sets.
Search by Set ID in Manage Sets
A new 'Set ID' search option was added to the Manage Sets screen. The search by ID is an exact match search and requires the full ID number. This gives users an additional search option to support their search workflows, allowing them to find sets directly by ID. Accessibility operations remain unchanged, so users relying on keyboards and screen readers can continue using the Search option as before.

For more information, see Managing Search Queries and Sets.
Centralized AI Features Management Page
URM-321395A new institution-level configuration page, AI Features Management, was introduced in Alma. This page consolidates the enablement and configuration of all AI-based features (that will be added to this page gradually, starting with the AI Metadata Assistant, AI Insights, AI Knowledge Assistant, Alma AI Assistant and AI Title Matching). This page includes feature descriptions, enable/disable toggles, and role-based visibility of the relevant AI features. This centralized page streamlines the management and configuration (when available) of AI features, enhances clarity and control, and enables institutions to turn AI capabilities on or off according to their institutional preferences.
Users with the General System Administrator role can access the page at Configuration > General > AI Features > AI Features Management. Users with admin roles for their area can access the page via their specific area in the menu. For example, a Repository Administrator can access the Metadata Assistant from the Resources menu, which leads to the AI Features Management page. Each feature on the page is visible only to its specific role/s. For example, an Acquisitions Administrator will see Alma AI Assistant on this page.
_Centralized_AI_Features_Management_Page.png?revision=1)
Relevant users can use the toggle to enable/disable a specific feature. The user can select one, many, or all features in the list by selecting the relevant checkbox(es) and then selecting the Turn off/Turn on buttons that appear.
-
If you turn a feature on or off, the change applies to the entire institution.
-
Users that already activated a feature will still have it enabled, and no action is needed as a result of the page move.
For more information, see AI Features Management.
Number of Lending Requests Added to Consortial Analytics Filters
New Subject Area and Data Visualization Dashboard for Collection Development Workflows Added to Analytics
Additionally, the new out-of-the-box Collection Development Workflow Projects & Recommendations Data Visualization dashboard is now available in Analytics > Access Analytics > Catalog > Shared Folders > Alma > Rialto Collection Development > Data Visualization.
It provides an overview of all collection development workflow projects and their associated recommendations. It includes metrics such as the total number of projects, project distribution by status and workflow type, and a detailed recommendations report with item and bibliographic information. This dashboard helps staff monitor project progress, analyze recommendations, and export data for retention and deselection workflows.

New Resource Sharing Request Fields Available in Borrowing and Lending Requests Subject Areas
For more information, see Borrowing Requests (Resource Sharing) and Lending Requests (Resource Sharing).
Country-Based Selection in the Compare To Section
The Compare To section for retention and deselection projects that include comparisons with external institutions has been enhanced to provide a more structured, country-based selection experience.
When creating a new project or editing an existing one, users can now browse comparison institutions using a country tree view. First, select a country to display all available institutions within it. You can then choose specific institutions individually, or select the checkbox next to the country name to automatically include all institutions within that nation.

This enhancement simplifies the process of selecting comparison institutions and makes it easier to locate relevant libraries without having to navigate a long alphabetical list.
Deeper Insight into External Holdings
To support deeper cross-institution analysis, Rialto now offers expanded bibliographic details in the Compare To section when inspecting individual recommendations in projects with external comparisons.
While the Compare To section itself remains unchanged in the main view, the sliding panel under View full list and additional information now displays expanded metadata for matching holdings. Newly added fields include:
- Library
- Publication Place
- Edition
- Material Type
- Language
- OCLC
These additional data points provide deeper insight into external holdings, enabling more informed retention and deselection decisions when comparing your collection to other institutions.
Enhanced Sorting for Collection Development Recommendations
Rialto now provides more flexible sorting options when viewing recommendations in retention and deselection projects. In addition to sorting by Title and Publication Date, you can now also arrange recommendations by:
- Library/Location
- Call Number
You can also apply a secondary sort to further refine the results' order. The secondary sort uses the same set of fields—Title, Publication Date, Library / Location, and Call Number—and enables additional ordering when multiple recommendations share the same primary sort value.

These enhancements make it easier to review, compare, and organize recommendations, especially when working with large result sets that include many items from the same library or publication period.
Predictable Title Updates in Analytics
Title updates are now assigned specific run dates, ensuring libraries know when their data is refreshed. In addition, member institutions in a consortium are updated as a group, providing synchronized data across the network. A new out-of-the-box report is also available in Analytics > Access Analytics > Catalog > Shared Folders > Alma > Titles > Reports > Analytics Titles Subject Area Update. You can use this report to display a widget in your Alma home page:
- Copy the report to your institution folder.
- Create an Analytics Object in Alma pointing to this Report.
- Define it as a Widget.
With this update, libraries can rely on consistent update timing, allowing better planning for internal reporting schedules.
For more information, see Out-of-the-Box Reports and Title Details.
New Partner Fields Available in Borrowing and Lending Requests Subject Areas
New fields are available in Borrowing Requests (Analytics > Create Analysis > Access Analytics > Create > Analysis > Borrowing Requests (Resource Sharing) > Partner) and Lending Requests (Analytics > Create Analysis > Access Analytics > Create > Analysis > Lending Requests (Resource Sharing) > Partner) Subject Areas. They can be used for recording additional information on resource-sharing partner records. Libraries can report on partner information to evaluate their resource-sharing service, including fill rates, volume, charges, and request types, in relation to partner parameters. The new fields are:
- Account Allowances
- Alternate Account Number
- Organization Type
- Sector
- Send Communication Allowed
For more information, see Borrowing Requests (Resource Sharing) and Lending Requests (Resource Sharing)
New Partners Fields in Resource Sharing Partner Record
Additional fields were added to the Resource Sharing Partner record (Fulfillment > Resource Sharing > Partners) to enable further customization. The following fields were added:
- Alternate Account Number — Free text field that, in addition to an alternate symbol, enables additional information to be stored on the partner record.
- Account Allowances — Populated by customizable drop down options. Multiple selections can be made to designate additional partner information.
- Sector — Populated by customizable drop down options to enable additional information to be stored on the partner record.
- Send Communications Allowed — The value is checked/unchecked. Some libraries may want to note if marketing materials can be delivered to partners or not.
- Organization Type — Populated by customizable drop down options to enable additional information to be stored on the partner record.

For more information, see Resource Sharing Partners.
Temporarily Deactivate Lending for Different Formats
Lenders now have the ability to selectively deactivate specific lending services rather than deactivate all services. Previously, lenders could only deactivate all lending operations at once. Now they can decide whether to deactivate Everything, temporarily deactivate Physical lending while keeping digital services active, or temporarily deactivate Digital from Physical lending while continuing physical shipping or electronic lending.
This provides lenders with more flexibility to handle temporary disruptions without having to fully stop their lending services.

For more information, see Configuring Parameters of a Resource Sharing Library.
Details in Alma Metadata History
Idea Exchange URM-317895Alma now tracks the metadata changes made in the Resource Information section. They are recorded and viewable in the History tab of the request.

For more information, see Managing Borrowing Requests.
Location Level Best Copy for Fulfilling a Request
For more information, see Pickup at Shelf and Configuring Libraries.
Add Notes in Deliver Digital Documents Page
Idea Exchange URM-167540It is now possible to add notes to partner and internal notes when using Deliver Digital Documents to fulfill a document delivery request.
This enhances communication with borrowers and facilitates the recording of internal information when providing a document delivery service.

The two note fields were also added to the Download Electronic Resource page.

For more information, see Managing Lending Requests.
Ship Lending Requests Without Barcode
It is now possible to ship items when fulfilling resource sharing lending requests, even when they do not have a barcode. In this case, the ship and check-in actions are used by selecting the items from pickup lists. This impacts the Ship Items page and the Scan-In Items page.
The Item ID of shipped items can be added to the displayed information about a lending request's items. When shipping an item without a barcode, this will be the only unique identifier that can be displayed.

For more information, see Peer to Peer Resource Sharing and Scanning Items.
Override Hold Policies
Idea Exchange URM-317447When placing a hold, booking, or digitization request in Alma, the operator is shown any blocks that may affect the request. Operators with the new Override Patron Hold Blocks privilege can override these blocks. If you would like this functionality enabled, please contact the Alma Support team and request that the relevant privilege be activated for your institution.
This provides transparency around blocked requests and enables authorized overrides.


The privilege will appear for all roles that have the Override Block Request privilege. For existing customers, the privilege will be disabled. For new customers, the privilege will be enabled by default for the Circulation Desk Manager and Fulfillment Services Manager roles.
For more information, see Managing Patron Services at a Circulation Desk and Privileges for Roles in Alma.
View Mode for Courses in Course Reserves
A new privilege was added to the Course Reserves Viewer role, enabling users to view the list of courses in view mode (and not only reading lists and citations).
This impacts Alma users who should not be able to edit courses, reading lists and citations, but should be able to view all of them.
If you would like this functionality enabled, please contact the Alma Support team and request that the relevant privilege be activated for your institution.
For more information, see Managing User Roles, Privileges for Roles in Alma and Roles and Registration Configuration.
Automatic Waiver of Overdue Fines for Re-loaned Items
Idea Exchange URM-90892When an item currently on loan is checked out to a new patron, Alma may automatically check in the previous loan, depending on the configuration (Configuration > Fulfillment > Physical Fulfillment > Block Preferences) for the Item is currently on loan by another patron action. This automatic check-in can result in overdue fines for the prior borrower. Institutions can now configure Alma to automatically waive these fines or allow circulation staff performing the check-out to decide whether the fines should be waived.

For more information, see Configuring Loans and Patron Charges Configuration.
Automatic Selection of Library Digitization Department
Alma now intelligently selects the most suitable library-level digitization department for newly created Patron Digitization Requests and Ship Digitally requests. This enhancement applies in scenarios where the system automatically assigns a digitization department, including:
- Requests submitted via Primo
- Requests automatically generated from incoming resource sharing transactions
In both cases, Alma prioritizes digitization departments that are also configured as circulation desks and are responsible for reshelving the requested items.
For more information, see Configuring Fulfillment Jobs and Creating a Request from the Institution.
Differentiated User Groups in Fulfillment Networks Based on Source Institution
Idea Exchange URM-93337
The external user groups are configured in Alma from Configuration > User Management > External User Group.
For more information, see Linking Users in Collaborative Networks and Configuring External User Groups.
Pop-Up Notification for Hold Shelf Items
CERV Enhancement (ID#247150) URM-247150Libraries can now enable a pop-up alert at the circulation desk, upon logging into the Manage Patron Services page, to notify operators when a patron has an associated system note, such as a note about items waiting on a hold shelf. The notification contains the same information as that in the System notes.
This feature helps ensure that staff are promptly informed and reduces the risk of missing important hold messages during interactions with patrons. The pop-up can be enabled using the popup_message_system_notes parameter in Configuration > Fulfillment > Other Settings.
.png?revision=1)
Selecting OK in the pop-up dismisses the message and leaves the user in the Manage Patron Services page.
For more information, see Configuring Fulfillment Jobs and Managing Patron Services.
Prioritizing Locations for Fulfilling Digitization Requests

For more information, see Configuring Physical Locations, Creating a Request from the Institution and Managing Lending Requests.
New Linked Open Data (LOD) Editor for BIBFRAME Records, Now Available in Alma
This is a new world of Linked Open Data cataloging, streamlined and embedded into Alma and Alma workflows, enabling institutions to embrace BIBFRAME within their familiar workflows while maintaining MARC records alongside them within the same environment.
The new LOD editor is now available to all institutions that want to catalog and edit BIBFRAME records directly within Alma. With the new editor, catalogers can create and edit BIBFRAME works and instances in a seamless, navigation-friendly experience, including quick editing from within the search results and a draft management page for those who wish to work in a separate workflow.
The new editor is guided by the BIBFRAME and BFLC ontologies, enabling users to create entities based on the structure and relationships between properties and classes as defined by the Library of Congress. With the new lookup service, catalogers can query directly external authoritative sources such as the Library of Congress's linked data service (id.loc.gov) and Wikidata. The new editor also provides out-of-the-box templates for works and instances, based on the structures defined by the BIBFRAME interoperability group (BIG) and enables users to create and manage their own templates, with additional functionalities of private and public templates.

Configuration for Enabling BIBFRAME
For users with Cataloging Configuration or Catalog Admin roles, it is now possible to enable (default disabled) support for BIBFRAME works and instances with Alma by using a configuration page rather than needing to open a ticket with the support team.
This setup enables the Works search, the BIBFRAME editor link, and templates links within the Resources menu and the metadata configuration for these formats.

For more information, see Enabling BIBFRAME in Your Institution.
New Merge Option for SBN Authority Contribution and Alignment
Previously, merge rules were not available for SBN authority alignment or as part of SBN contributions. It is now possible to apply merge logic during both SBN authority alignment and Bibliographic/Authority contributions. Customers can select and apply merge rules in these processes to improve data consistency, reduce duplication, and enhance automation within SBN workflows.
For more information, see Integrating the SBN Italian Union Catalogue.
New Search Indexes for Physical Items
New search indexes were added to physical items:
- Physical item: Has Order = yes/no: allows searching for items with/without orders. The index accounts for both orders at the item and the holdings level, similar to the Order link in the items search results.
- Physical item: Received = yes/no: allows searching for items that were received or not received, similar to the receiving filter in the items list. Items are considered received if they have a receiving date of today or earlier.
These new search options make it easier to find items; for example, items with orders that have not yet been received.
For more information, see Physical Items Search Indexes.
Enhanced MARC Bibliographic Index Infrastructure
Idea Exchange URM-253352To enable a seamless setup for institution-specific bibliographic search indexes, customers now have the ability to define custom indexes for their institution based on Bibliographic data. This new infrastructure provides the flexibility for each customer to create their own search indexes tailored to their Bibliographic data.
This feature can only be tested in your sandbox environment after the data is cloned on February 8th.
For more information, see Configuring Search.
Sorting Option for Alma SRU External Search Resources
We have introduced a new sorting capability for Alma SRU-based external search resources only. Users can sort results in the Metadata Editor by Rank, Title (default), Creator, and Publication Date.

For more information, see Configuring External Search Resources.
New Controlled Vocabulary List for Language Codes
A new, merged controlled vocabulary list has been created by combining language codes from the MARC21 standard and the ISO 639-3 list. This enhanced list includes an expanded range of languages, addressing gaps that previously existed when cataloging the MARC 041 $a field.
The list is available only in English. When searching by the language list in subfield 041 $a, using the Language facet, or using the pop‑up assistant in the Metadata Editor for subfield 041 $a, all values are displayed in English.
For more information, see Combined Language List.
Introducing the Alma AI Assistant for Acquisitions Funds and Ledgers – Preview Mode (Beta)
Artificial Intelligence To improve day-to-day efficiency, the Alma AI Assistant enhances the user experience when interacting with Alma through a chat-based interface. Instead of navigating multiple screens and workflows, staff users can ask questions naturally and receive clear, relevant responses directly within Alma.
The first focus area for the Alma AI Assistant is Acquisitions - Funds and Ledgers. Staff users with the Fund/Ledger Manager role (from the institution level) can ask questions about their institution’s funds and ledgers and receive immediate, natural-language responses.
Since the Alma AI Assistant was first announced on the Alma roadmap, it has generated significant interest across the community. As part of the November 2025 release, we conducted an Early Access Program with 15 participating institutions. Their hands-on usage and feedback have been invaluable in shaping the next steps of this initiative.
Given the exploratory and evolving nature of this feature, we want to broaden the feedback loop even further. Therefore, as part of the February 2026 release, we are introducing Alma AI Assistant in Preview Mode (beta) across all Alma environments. Administrators can choose to activate the feature at their discretion.
Preview Mode (beta) - What to Expect
The Preview Mode (beta) is an early iteration designed to give libraries the opportunity to explore the feature, understand its potential, and actively contribute feedback that will guide future development. Additional enhancements, including the ability to perform actions as part of the Alma AI Assistant flow are planned for upcoming releases.
Libraries are encouraged to try the Alma AI Assistant in their Sandbox or Production environments to gain an initial sense of its capabilities and limitations.
Feedback is critical for this phase. You can share your input directly within the Alma AI Assistant using the thumbs up/thumbs down
options on each response, or by contacting us directly at tamar.fuches@clarivate.com.
For more information on enabling the feature, how it works, and our planned enhancements, refer to the Alma AI Assistant – Acquisitions Funds and Ledgers documentation. Also see Artificial Intelligence in Alma.
New Collection Development Manager Role
Rialto now has a dedicated Collection Development Manager role. This role centralizes collection development workflows, replacing the previous model in which multiple roles could use these workflows.
Users assigned the Collection Development Manager role are now the only ones who can:
- Access the Workflows menu under Collection Development
- Create, edit, and delete collection development projects
- Generate and manage recommendations for retention and deselection projects
Repository Administrator and Rialto Administrator roles continue to have access to collection development configuration settings, but they no longer have direct access to the workflows themselves. Collection Development Managers do not have access to configuration settings.
This change clarifies responsibilities and reduces confusion about which users can view, configure, and run collection development workflows.
On Production (not Sandbox), users who created collection development workflow projects prior to the February release will be automatically assigned the Collection Development Manager role to maintain access to existing workflows.
Export Comparison Reports for Collection Development Projects
Rialto now enables Collection Development Managers to export comprehensive comparison reports for retention and deselection projects. Reports can be generated using the Export Extended Report option in the three-dot menu next to a project name.

The export produces an Excel file containing detailed information on all active recommendations from the project, along with comparable data for all matching titles from the selected comparison institutions.

Once a report is generated, a notification appears in the top-right corner of the interface to let the user know it is ready. The report can then be downloaded using the Download Extended Report option in the same three-dot menu. This action is only visible after an extended report has been created. All generated reports can also be viewed or downloaded from the History tab in Admin > Manage Jobs and Sets > Monitor Jobs.

This feature delivers a rich, consolidated view of project recommendations, bringing all relevant data together to support confident retention and deselection decisions. For details, see Creating and Downloading an Extended Report.
Link Resolver Improvement for Video Records in Network Environments
Collaborative Networks URM-248355We have enhanced the link resolver’s search mechanism for video records in network environments. It now accurately identifies video records and distinguishes them from book records, reducing false matches and preventing book links from appearing when patrons search for videos.
For more information, see Alma Link Resolver Workflow.
Complete Record of All Changes in History for Electronic Resources
Idea Exchange
CERV Enhancement (ID#36487) URM-319130The e-resources History tab now records changes made by the CZ synchronization, as well as local changes made by system jobs or operators. This applies to electronic collections, electronic services and electronic portfolios.
Updates from the Community Zone will appear with "operator" = "system", as do other system job changes.
This development also includes the recording of changes to the general notes and the additional PO lines, which were not previously saved in the history.
For more information, see Managing Electronic Resources.
Autoholdings for Oxford University Press
Idea Exchange URM-252900Libraries can now automate the management of licensed OUP content by using autoholdings.
Once the integration is set up, Alma automatically retrieves a standardized KBART file containing monographs and serial holdings information from the provider’s platform and updates the corresponding collections. This integration removes the need for manual updates, reducing staff workload, saving significant time and enhancing accuracy.
For more information, see Upload Electronic Holdings from Oxford University Press.
Holdings Retention by MARC Fields
Institutions can now define holdings with specific metadata as "committed to retain", thus protecting them from deletion, even if the holdings do not have items. Retention blocks manual and batch deletion.
Definition rules are defined on the Holdings Records Retention definition page at Configuration > Resources > Collection Retention > Holdings Records Retention Definition.


The retention indication on the holdings level is also available in analytics in the following fields:
- Holdings Committed to Retain (Physical Items SA)
- Has Holdings Committed to Retain (Titles SA)
- Has P-Inventory Committed to Retain (Titles SA — indicates whether the title has any items/holdings that are committed to retain)
Retention from holdings is not passed on to the items, i.e., items do not inherit the holdings' retention status. To protect items from deletion, you must define the item itself as committed to be retained in the item editor.
Retention indication is applied during indexing. The new logic applies only to newly created or updated holding records. To ensure the logic is also applied to existing records, contact support to request indexing.
For more information, see Working with Holdings Records, Physical Items and Titles.
Support for German XRechnung Standard when Creating Invoice from XML
Users can now create invoices in Alma from XML file, of the German e-invoice standard XRechnung.
.png?revision=1)
For more information, see Creating Invoices.
Additional Options for EDI Configuration
Two additional fields were added to the input job parameters at Vendor > EDI Information > Input Job Parameters.
- Default VAT — Appears when Use VAT Code is set to true. The VAT default will be used (and set for the invoice) when there is no value in the input file for VAT code, or when there is a value which does not match the VAT Codes table. Note that Default VAT only applies to the invoice level. Even if the VAT In Invoice Line Level field is set to true, the default VAT is ignored.
- Internal copy — When true, the created invoice for this vendor will have the Internal copy field checked (meaning it will not be sent to ERP).
The new fields will not impact the current setup and will have null/false values by default.
.png?revision=1)
Both these fields apply to invoice creation from EDI, XML and Excel.
For more information, see Electronic Data Interchange (EDI).
More "Interested In" Letter Fields can be Customized
Idea Exchange URM-208307The Interested In letter is sent in different scenarios (upon receipt of the item, upon activation of the resource and upon cancellation of the PO line). Previously, the subject and other message labels were the same in all these cases. Now, the labels can be customized for each of the following use cases, enabling users to write a different subject line and message body depending on the trigger event.
The three main use cases that now have unique customization fields are:
- Receiving
- subject_received
- letter_name_received
- details_received
- details_item_arrival_time
- Activation
- subject_activated
- letter_name_activated
- details_activated
- Cancellation
- subject_cancelled
- letter_name_cancelled
- details_cancelled
These fields can be customized from the Labels table when editing the letter (Configuration > General > Letters Configuration > Interested In Letter > Labels).

For more information, see Configuring Alma Letters.
PO Line Cancellation: Enable Deletion of Related Inventory Even if Linked to CZ
Idea Exchange URM-319332Until now, when cancelling PO line, the portfolio would only be deleted if it was a standalone local portfolio and inactive. A new customer parameter (delete_linked_portfolio_upon_pol_cancellation) was added. When set to true, inactive portfolios that are linked to Community Zone or that are part of an electronic collection will now also be deleted, in addition to the local portfolio.
The parameter is set to false by default. It can be accessed from Configuration > Acquisitions > Other settings.
For more information, see Closing, Cancelling, Reopening and Relinking PO Lines.
Rialto Status in PO Line General Information
When a PO line was created as part of the Rialto workflow, the Rialto status is now shown in the PO line General Information section.

For more information, see Manually Creating a PO Line.
Option to Place Requests on Title and Item Level from PO Line
Idea Exchange URM-207490Users can now place requests from the PO line on the title and item level:
Title level — Using the Request Title action..png?revision=1)
Item level — In the Ordered Items and in the Items in Claim sections, using the Request Item action.
.png?revision=1)
The actions are displayed for physical PO lines. Users will see the available request types according to their user privilege, just as if the request were placed from a list of items or a repository search.
For more information, see Manually Creating a PO Line.
Link to Holdings Record from PO Line Right Pane
The PO line title in the right pane now links to the institution record in a sliding panel.

Link to sliding panel
Additionally, the Location column in the following tables will now link to the Holdings record:
- Ordered Items
- Holdings for Ordered Items
- Items in Claim
.png?revision=1)
For more information, see Manually Creating a PO Line.
New API for Creation of Allocation and Transfer Fund Transactions
Users can now use POST in the fund transactions API as follows:
POST /almaws/v1/acq/funds/{fund_id}/transactions
The supported transactions that can be created are:
- Allocation
- Transfer
For more information, see the Developer Network.
Additional COUNTER Report Attributes for SUSHI R5/R5.1. Harvesting
Idea Exchange URM-253611Users can now select additional attributes for SUSHI harvesting COUNTER R5/R5.1 reports: DR, IR, PR and TR. This enables the Access type and other attributes to be included in the harvested reports, enhancing the functionality for title (and other) reports.
For the institution-level defaults, the attributes can be selected from Configuration > Acquisitions > COUNTER R5 Additional Attributes for SUSHI Harvesting.

Attributes can also be selected for the SUSHI account level.

The report level options are:
- Default — Take the values set in COUNTER R5 Additional Attributes for SUSHI Harvesting
- Explicit yes — Send this attribute, no matter what settings are in COUNTER R5 Additional Attributes for SUSHI Harvesting
- Explicit no — Don't send this attribute, no matter what settings are in COUNTER R5 Additional Attributes for SUSHI Harvesting
For more information, see Managing COUNTER - Compliant Usage Data.
Relative Date Search Operators for Order Lines Search
When searching order lines, users can search by relative dates. This is available for:
- Creation date
- Is Within the Last (days)
- Is Older Than (days)
- Sent date
- Is Within the Last (days)
- Is Older Than (days)
- Renewal date
- Is Within the Last (days)
- Is Older Than (days)
- Is Within the Next (days)

For more information, see Searching for PO Lines and Using Facets to Refine Results.
New Order Import Profile: Option to Use Call Number for Holdings Matching
The New Order Import profile looks for the holding on which the item should be created. This match is based on the library and location.
Institutions can now configure this match to also consider the call number. This can be achieved by setting the eod_match_holdings_by_call_number customer parameter
(Configuration > Acquisitions > Other Settings) to True. When the call number is different from that of an existing holding for the matched bibliographic record, a new holding is created.
If more than one matched holding is found, a new holding is created, as the system cannot determine which one to use. This is the existing behavior when multiple matches are found based on library and location.
- This new feature assumes a mapping to 852h.
- When the parameter is set to true, and the call number has an empty value, the behavior is as follows:
- When there is one existing holding in the matched bib, the item is created for this holding.
- When there is more than one existing holding in the matched bib, a new holding is created.
For more information, see Managing Import Profiles and Other Settings.
Support Services for Consortia Central Office
URM-215332 URM-226822 URM-317340It is now possible for the Network Zone operator, from the Central Configuration Dashboard, to perform a defined set of maintenance and troubleshooting tasks on behalf of its member institutions. These include support services and utilities that were previously handled only by Ex Libris support, enabling faster problem resolution and proactive system management at the consortial level.
This enhancement empowers the Central Office to support its members more effectively by performing direct maintenance and troubleshooting actions. It strengthens the Central Office’s role as a service provider, improves response times for member institutions, and reduces reliance on external support for common issues.


This new feature is only relevant to Consortia with a Network Zone setup. The Network Zone operator must have the Support Services role in order to access and use these tools.
For more information, see Support Services.
New Additions to the Central Configuration Dashboard
URM-319235 URM-319507 URM-319423The following information was added to the new Central Configuration Dashboard:
- Activate Linked Open Data Formats page to expand the exposure of Linked Open Data across the network.
- Homepage Notifications for management and distribution.
- Usage Calculation mapping table in a brand new Collection Development section to offer a central management and distribution across members without the need to opt-in locally in the Data Sharing profile.
- Partner Sectors, Partner Organization Type and Partner Account Allowances code tables for central management of Resource Sharing and Rapido.
These additions enable the central office to work more efficiently, reducing time spent applying central policies.
Shared Blocks Across the Fulfillment Network for Network Zone Managed Users
Idea Exchange URM-314620Previously, in a Network where users are managed at the Network Zone level, patron blocks could only be shared from the Network Zone to the institutions where the patron had local accounts. It is now possible to share blocks from any institution with any other institution where the patron has an active account.
This enables patron blocking more easily and efficiently across the entire network where users are managed in the Network Zone.
For more information, see Configuring User Blocks and Managing Users.
Combination of Electronic Resources Activated at Network Zone and Institution Zone for Online Services Order
Idea Exchange URM-248932It is now possible for the Member Administrator to select from a combined list of electronic resources activated at Network Zone and Institution Zone levels in the Online Services Order configuration. At the Network Zone level, the operator (from the dashboard) can still update the order for these services for the Network (only local resources from the network) and for the Members (combined list of local and network resources).
This enhancement improves efficiency by allowing the combination of Network and Institution Zone electronic resources for improved services.
.png?revision=1)
This new feature is only relevant to Consortia with a Network Zone setup.
For more information, see ViewIt.
Support for Italian in Online Help
Support for Italian was added to the online help.
When working in the Italian user interface and accessing the online help, it now opens automatically in Italian.


For more information, see Alma User Interface.
Enhanced Performance for Searching Combo Boxes in New UX
Enhanced functionality was added to support searching combo boxes with long lists of options (above 200) in the Alma new UX, for example, in the Advanced Search. Previously, when opening a combo box list with many options, opening the list caused performance issues. Now, as you scroll down, more options are auto-loaded. The user can now scroll to view all the results, and the general performance was improved without changing the current functionality of searching the combo box.
User ID Appended to System for Manual Jobs
CERV Enhancement (ID#36485)URM-319756When running manual jobs, the user ID can now be appended to "System" in Alma entities updated by the job. For example, when the user John_Branson runs a manual job, instead of "System" appearing in the Physical Item Editor Modified-By field, Alma now displays "John_Branson (System)".
This requires the detailed_creator_and_modifier_for_job_changes parameter (Configuration > General > General Configuration > Other Settings) to be set to true (false by default). Note that enabling this parameter causes a change in the data from this point on, and this data change cannot be modified retroactively. Disabling this parameter again causes a change in the data from that point onwards, and again cannot be modified retroactively.
This feature only applies to:
- Manual jobs (non-scheduled) when the Run Now button is used

- Scheduled jobs when the Run button is used
This field is commonly used in analytics reports (for example, Modified by in the Physical Items Subject Area). Upon enabling the new customer parameter, the data will change accordingly from this point forward, and no retrospective data correction is performed. The same applies when this parameter is disabled.
For more information, see Manual Jobs and Configuring Other Settings.
New Link to Known Issues Portal from Alma Help Menu
A new link to the Known Issues Portal was added to Alma’s Help menu. This link opens the Known Issues page in a new browser tab. This update improves access to the Known Issues Platform, helping users stay informed about current issues and reducing the need to open support cases for existing known issues.

For more information, see Alma User Interface.
Support for Actions Configuration in Manage Sets List
You can now customize the display and order of the actions for the Manage Sets list.

For more information, see New Layout.
Enhanced Display and Behavior for Related Sets, Filter and Combine Badges and Set ID Label in Manage Sets List
The Related Sets description in the Related Sets section in the Manage Sets interface was updated to be more meaningful and improve clarity and consistency as follows:
- New badges were introduced to indicate the type of relationship:
- Used for combined sets
- Combined set
- Used for filtered sets
- Filtered Set
New Badges
- The Related Sets section in the Manage Sets page was enhanced to be more informative and improve clarity and consistency:
- Set IDs are now displayed at the end of each set name.
Set ID in Related Sets - The related sets display logic has been updated to better handle scenarios where sets are deleted or updated, ensuring an accurate representation of relationships.
Filtered sets whose "parent" was deleted are now indicated as such.
Deleted Parent in Related Sets - Additional relations are now included, showing related set details for actions like Create Titles Set and Itemize.
Itemized and Created Title Sets in Related Sets
- Set IDs are now displayed at the end of each set name.
- Updates/changes to sets (e.g., name change, adding members, etc.) that are part of a relation, no longer affect the display of the badges (for filter or combine operations) or the related set information in the Related Sets section.
- This change will not affect existing sets and existing sets relations and will take effect from this point onwards.
Additionally, the Manage Sets list now includes the Set ID information displayed in the first column of set information in the list, in addition to its current display in the right panel.

For more information, see Managing Search Queries and Sets.
Support for Plain Text Email
Idea Exchange URM-316414Alma now provides an option to include plain text on top of the HTML version. This provides patrons with plain-text email clients the ability to view emails from Alma.
This feature can be enabled by setting the include_plain_text_in_emails parameter to true (Configuration > General > Other Settings).
For more information, see Configuring Other Settings.
User-Controlled Default Collapse State for Success Fly-In Messages
The success fly-in messages checkbox was updated to enable users to set the default display state (collapsed or expanded) for success messages. Prior to this change, in pages with the new user interface, the default selection was for that specific message. Now, when selected, all similar message types on the same page follow the chosen default behavior. This change aligns the behavior with pages that do not have the new interface, and enables users to reduce visual clutter by collapsing success messages on the same page by default.

For more information, see Alma User Interface.
Search Users by Role and Scope
It is now possible to search for user records in the Advanced Search by role and scope, for example, to search for users with a circulation desk operator role in the scope of the Main Library. This new option enhances search options and enables the creation of user sets based on their roles and scopes.

For more information, see Searching in Alma.
Secondary Search for Titles/Holdings Search Results and PO Lines
When searching for titles, holdings or PO lines in Alma, it is now possible to perform a secondary search within the search results. This is also available when viewing logical set content, allowing for easy location of specific set members. This is especially useful for users who want to quickly or temporarily refine their search query, without having to update an advanced search with additional search criteria.

For pages with a Search Query, the secondary search is added to the search query.

After performing a secondary search, it is possible to save the refined results as a logical set.
The secondary search is also available when viewing the content of a logical set of any of these search types.
For more information, see Secondary Search.
New Encryption for User ID Encryption Field in Fulfillment Subject Area
The User ID Encryption field in the Fulfillment Subject Area in Analytics is used to obtain counts by user ID after the anonymization job is run, which deletes the Primary ID. This field is now calculated using a new encryption method.
Existing reports using a specific value as a filter may need to be reviewed and updated to ensure they continue to function as expected.
For more information, see Analytics Fulfillment Subject Area.
Flexible Definition of Local Parameters Being Sent to Analytics
Users can now decide which parts of a MARC field (indicators and subfields) are sent to Analytics through local parameters. This is possible for both bibliographic and holdings information. It provides more control over data granularity in reports, enabling a more accurate and focused analysis.
For more information, see Holding Details and Administrative Bibliographic Details.
Electronic Resource Network Data Accessible in a Single Location in Analytics
All electronic resource Network fields are now available in a single location within the Portfolio Details for Consortia Members folder in the E-Inventory Subject Area. Users can easily access all Network-related information in a single place, providing a clear and organized view.
For more information, see Analytics When Using a Network Zone and Portfolio Details for Consortia Members.
Electronic Collection Pending Deletion Reason and Alternative Collections CZ ID Fields Now Available in Analytics
Two new fields, Electronic Collection Pending Deletion Reason and Alternative Collections CZ ID, are now available in the E-Inventory Subject Area, specifically in the Electronic Collection and Portfolio Details for Consortia Members > Electronic Collection folders. Additional information about collections pending deletion in the Community is now available in analytics, making it accessible even after the Pending Deletion collection has been deleted in Alma.

For more information, see Electronic Collection and Portfolio Details for Consortia Members (Electronic Collection).
Set "No List Expected" in Bulk Using Course Bulk Update Task
Idea Exchange URM-240421The Course Bulk Update job (Admin > Run a Job > Courses > Course Bulk Update) now supports the No list expected attribute. Staff can select the No list expected checkbox in the job and choose either Add No list expected or Remove No list expected for all courses in the selected set, which enables efficient large-scale updates.

A new No list expected facet is also available on the Fulfillment > Courses page. It enables staff to filter courses based on whether the No list expected attribute is selected (Yes) or not selected (No). This enhancement improves course management by enabling institutions to quickly identify and organize courses that are intentionally not expected to have lists.

Related Records from Recommendation Summaries
January 2026 Resource Management URM-316541
Rialto now displays a Related Records link in the Summary section when viewing a retention or deselection recommendation that has associated bibliographic records. The link indicates the number of related records in parentheses.

Selecting Related Records opens a sliding panel with a list of all bibliographic records associated with the recommendation’s MMS ID.
This enhancement makes it easy to find connected records when examining recommendations and helps users understand the broader bibliographic landscape of a title.
Expanded Details in Item-Level Compare To Sections
January 2026 Resource Management URM-253024
Item-level Compare To sections for both retention and deselection recommendations now include detailed data for other institutions' resources. Users can view this data by selecting the View full list and additional information link in the Compare To sections.

Selecting View full list and additional information opens a detailed sliding panel that displays various data related to all matching holdings in comparison institutions, such as:
- MMS IDs
- Titles
- Authors
- Publication date
- Publisher name
- ISBNs
- Other system numbers

The panel presents one row per matching MMS ID per institution. For example, if a single institution holds two matching MMS IDs, the panel lists two rows—one for each match. Additionally, if multiple identifiers exist, the sliding panel displays all of them in the same field.
Some data points are hidden by default; use the panel’s configuration button to add additional columns to the sliding panel.

This update increases transparency across comparison institutions and supports more confident decision-making when assessing items for retention and deselection.
Create Collection Development Projects from a File
January 2026 Resource Management URM-314774
Rialto now enables users to create retention and deselection projects by uploading a file that contains a predefined list of items. Users can upload a tab-delimited text file or an Excel file with item IDs to serve as the project’s data source from which Rialto can generate recommendations. The uploaded file must be smaller than 10 MB and include a column named Item ID in the header row.
This capability is ideal for libraries that manage curated title lists outside of Rialto—for example, lists exported from previous projects, inventory analyses, or collaborative collection studies.
When creating a new project, a new Upload Project From File option is available on the Add New Project window (Collection Development > Workflows > Retention or Deselection). When selected, the window updates to include a field for uploading a file.

This enhancement gives libraries greater flexibility when creating collection development projects. Direct file uploads also reduce manual setup time and improve accuracy when analyzing preselected title lists. For more information, see Creating a Deselection Project from a File and Creating a Retention Project from a File.
Create Collection Development Projects from an Alma Set
January 2026 Resource Management URM-306178
In addition to creating a project from a file, users can now also create new projects directly from existing Alma physical item sets. This enhancement applies to both retention and deselection projects.
When creating a new project, a Create Project from Set option is now available on the Add New Project window (Collection Development > Workflows > Deselection or Retention). Once selected, users can choose any Alma set containing physical items from the Select Physical Items Set dropdown. When generating recommendations for a project created this way, Rialto evaluates only the items included in the selected Alma set.

This enhancement streamlines project setup and strengthens the connection between Alma’s inventory management and Rialto’s collection development workflows. For more information, see Creating a Deselection Project from a Set and Creating a Retention Project from a Set.
Define Usage Scope in Retention Projects
January 2026 Resource Management URM-254904
Rialto now enables users to include usage criteria when defining the scope of retention projects. Previously, usage filters were available only for deselection projects.
A new Suggest when total usage per title is more than field has been added to the Scope section of the retention Criteria form. This field includes two dropdowns:
- A usage count dropdown (1–10) that specifies the minimum number of uses per title.
- A timeframe dropdown (1–10 years) that defines the period during which usage is calculated.
The field is optional and is blank by default.

This enhancement helps libraries preserve high-value materials by basing retention decisions on measurable usage patterns.
Include Digitization Requests in Usage Calculations
January 2026 Resource Management URM-306180
Rialto now enables institutions to account for digitization requests when calculating item usage in retention and deselection projects.
A new configuration option, DIGITIZATION_REQUESTS, is now available in the table found in Configuration > Collection Development > Workflows > Usage Calculation. When enabled, Rialto includes digitization requests in the total usage count used for generating project recommendations.

Digitization requests represent instances where users or staff request the creation of a digital copy of a physical item.
By incorporating digitization requests into the overall usage calculation, libraries gain a more accurate understanding of how their collections are accessed and valued. This helps institutions make better-informed decisions when identifying titles for retention or deselection.
Search Within Recommendations
January 2026 Resource Management URM-313438
Users can now search within the recommendations list in both retention and deselection projects. A new search bar has been added to the View Recommendations page, next to the existing sort control. You can search by several indexed fields, including:
- Keywords
- Creator
- Edition
- MMS ID
- Publisher
- Title
- Title Local Labels

Any selected facets remain applied when running a search. If no titles match the entered keywords, the page displays a message indicating that no results were found.
This improvement makes it easier to locate specific titles among large recommendation sets.
Additional Enhancements
-
May 2026 Fulfillment and Resource Sharing URM-175629
Institutions can now customize copyright status labels in Alma, which enables libraries to align terminology with local regulations and practices.You can configure these labels in Configuration > Fulfillment > Copyright Management > Citation Copyright by updating the text in the Description column.
Citation Copyright table - Updated fair use labelInstitutions cannot add/delete entries or modify the underlying code in the Citation Copyright table; only the display text (Description) can be edited.
After updating the Description column, the custom label appears in Fulfillment > Course Reserves > Citations for all items with the corresponding copyright status. Updated labels are also reflected in facets and are available when applying bulk changes using Change Copyright Status.
Custom label for the fair use status - May 2026 Metadata & Linked Open Data URM-218454
To provide consistent Analytics reporting across MARC formats UNIMARC data was added to Analytics to align with the data already available for MARC21.For more information, see Bibliographic Details.
- May 2026 Metadata & Linked Open Data URM-252667
Updates to MARC21 Profile MARC21 bibliographic update No. 41 (December 2025), MARC21 holdings update No. 41 (December 2025), and MARC21 authorities update No. 41 (December 2025), including Bibliographic, Authorities, Classifications, and Community changes and updates to the MARC21 Holdings.For more information, see MARC21 Search Indexes.
- May 2026 Metadata & Linked Open Data URM-253419
LOD Editor — bf:hasInstance and bf:instanceOf are now consistent and reciprocal. To ensure a smooth workflow, incompatible links between BIBFRAME Works and Instances are no longer allowed. - May 2026 Metadata & Linked Open Data URM-319214
When performing a Wikidata lookup in a language other than the English default, the selected language tag is stored for that specific record field, ensuring future record updates do not revert to the default language.For more information, see Wikidata-Specific Features.
- May 2026 Metadata & Linked Open Data URM-318550
When creating a new BIBFRAME record (work or instance) from a template, the template name now appears at the beginning of the summary section to indicate to the cataloger which template was selected. The template name is visible until the record is saved to the database.
"From template" Indication - May 2026 Metadata & Linked Open Data URM-253699
Updates have been made to the GND Profile. These updates are ongoing. - May 2026 Metadata & Linked Open Data URM-318309
In the new UX titles and holdings searches, a new display field, Short Title, was added that contains only the title proper (245 $$a). This field is hidden by default, but can be added to the table or record displays by configuring the views. It is especially useful for users who want to minimize the space the title takes in the table view, and can now choose to display a Short Title column instead of the Title column.This new field was also added when exporting all fields from the search results to Excel.
Short Title Column
- April 2026 Analytics and Insights URM-324439
The field Public Note has been added to the following Subject Areas:- Fulfillment > Physical Item Details
- Lending Requests (Resource Sharing) > Physical Item Details
- Physical Items Historical Events > Physical Item Details (Current)
- Requests > Physical Item Details
- Rialto Collection Development > Physical Item Details
For more information, see Fulfillment, Lending Requests (Resource Sharing), Physical Item Historical Events, Requests and Rialto Collection Development.
- March 2026 Fulfillment and Resource Sharing
Idea Exchange URM-253833
Leganto now enables libraries to customize the labels of workflow tags, including those used for integrations with external systems such as Bolk and DCS.To customize a tag, navigate to Configuration > Fulfillment > Courses > Reading List Citation System Tags, select More actions, and then choose Customize. Libraries can then update the text shown in the Description column to better reflect local terminology or workflows.
Reading List Citation System Tags
- February 2026 Acquisitions URM-315421
In the receiving workbench, when selecting 25 or more PO lines for receiving, or when they have more than 25 items together, the receiving will now be done by a job. This is designed to enhance performance in cases of large selections. When the job has completed, a message is displayed that the job has finished, and the results of the receiving are displayed.
- January 2026 Fulfillment and Resource Sharing URM-315436
Alma now records which user uploaded a file to a citation. When a file is uploaded, the system stores either the uploader username or, if the file was added by a job, the job ID.In Alma, this information is visible in the File Upload component under the label Uploaded by. This information will be added to analytics in a future release
Information on who uploaded a file
Upcoming Issues to Note
Collection Development Consent Updates to Include Item-Level Data
In the August 2026 release, the Collection Development data‑sharing consent will be updated to include discoverable item‑level data.
This update follows a request from our Early Adopters group, who found that discoverable item‑level data can be valuable in specific scenarios when making more informed collection development decisions.
This change will not affect existing opt‑in status.
Updated Documentation for Analytics Table
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of analytics field tables with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following table within the E-Inventory Subject Area was updated:
Fulfillment Anonymization Job
Infrastructure enhancements were applied to the Fulfillment Anonymization Job to improve overall performance. As a temporary side effect, the job will appear twice in Admin > Monitor Jobs > Manage Jobs and Sets — one entry reflecting the actual processing activity, and a second entry showing 0 records processed.
This duplicate entry is expected and will be removed in an upcoming release.
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of analytics field tables with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following table within the E-Inventory subject area was updated:
Updates to OCLC Control Number Indexes
In the May 2026 release, we will be changing the following indexes.
- Other System Number (035a)
- Other System (035a) Exact
- OCLC Control Number (035a)
- Other System Number (035z)
- OCLC Control Number (035z)
- Other System Number (035a+z)
- OCLC Control Number (035a+z)
The indexing of these fields will no longer split the values. For example, searching for SCR will now return values such as 202408SCR.
Enhanced Bibliographic Index Infrastructure
Empower your institution with fully customizable bibliographic search indexes designed to deliver a smarter, more precise discovery experience. Our enhanced infrastructure lets you define indexes tailored to your institution’s unique bibliographic data—giving you greater flexibility, improved search accuracy, and a powerful foundation for more intuitive workflows. With this new capability, you can shape your search experience to match your exact needs and elevate the way your users find and access information.
For more information, see Configuring Search.
Data Dictionary E-Inventory
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of analytics field tables with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the E-Inventory subject area have been updated:
Resolved Issues
- May 2026 Acquisitions SF: 8237372 URM-319045
In some cases, addresses and email addresses were duplicated in the Contact Information tab. This was fixed. - May 2026 Acquisitions SF: 08251001 08357169 URM-321035
Previously, the Manage Items pages defaulted to the first page after closing the item editor. This was fixed. - May 2026 Acquisitions SF: 8227840 URM-322645
Previously, when selecting the Release Encumbrance checkbox, the disencumbrance data disappeared. This was fixed. - May 2026 Acquisitions SF: 8309271 URM-322714
Previously, funds disappeared after being moved. This was fixed. - May 2026 Acquisitions SF: 8332848 URM-323796
Previously, the PO Line Packaging job failed repeatedly. This was fixed. - May 2026 Acquisitions SF: 8287298 URM-323914
Previously, you were unable to create an invoice from an Excel file containing 0 percent of VAT. This was fixed. - May 2026 Acquisitions SF: 8330927 URM-324077
Previously, invoice lines created with API for invoices could only be edited/deleted with permissions at the institutional level. This was fixed. Now, invoice lines created with API for invoices can be edited/deleted with permissions at the library level. - May 2026 Acquisitions SF: 8377786 URM-326103
Previously, when searching for order lines in the Advanced Search > PO Status: Sent, no results were returned. This was fixed. - May 2026 Acquisitions SF: 8352393 URM-326192
Previously, after receiving Print POLs, a mandatory field was missing or an erroneous field was mistakenly added. This was fixed. - May 2026 Acquisitions SF: 08392075 08415406 URM-326907
Previously, the PO line Sent Date differed between Analytics and Alma. This was fixed. - May 2026 User Experience, Accessibility and Infrastructure SF: 08379533 URM-326014
Previously, the log contained a misleading error message. This was fixed. - May 2026 User Experience, Accessibility and Infrastructure SF: 07798070 08312181 08410182 URM-316502
Previously, an error could occur when editing and saving a user record after modifying the user's statistics in the same session. This was fixed so that user records are now saved correctly regardless of the order in which changes are made across the different tabs. - May 2026 User Experience, Accessibility and Infrastructure SF: 08244828 08333940 URM-322116
Previously, the SAML Integration Profiles Updated By and Status Date fields were incorrect. This was fixed. - May 2026 User Experience, Accessibility and Infrastructure SF: 8321512 URM-322984
Previously, the Patron Services sliding panel was not displayed correctly. This was fixed. - May 2026 Analytics and Insights SF: 8356340 URM-324840
Previously, the Search Analytics Objects feature did not correctly display object results based on the search terms. This was fixed. - May 2026 APIs SF: 8250999 URM-320475
Previously, the due date policy in a specific case of the Retrieve Items List API was inconsistent. This was fixed. - May 2026 Fulfillment and Resource Sharing SF: 8257740 URM-320437
Previously, when expanding the user account window to Full page display, the tabs menu under the User Details page was missing. This was fixed. - May 2026 Fulfillment and Resource Sharing SF: 8277416 URM-322814
Previously, an error was generated when scanning items for a title with multiple requests. In these cases, the scan in should be done in the ALMA web UI. An appropriate error was added to these cases. - May 2026 Fulfillment and Resource Sharing SF: 08339530 08347966 08328686 08373075 08391852 08342012 URM-323916
In some cases, the error, "Patron has duplicate request error in Primo, and the request was cancelled" was generated. This was fixed. - May 2026 Fulfillment and Resource Sharing SF: 8334976 URM-324284
Previously, an error was generated when editing the Request Pickup Configuration Rule. This was fixed. - May 2026 Fulfillment and Resource Sharing SF: 8355594 URM-325997
When navigating through reading lists using the Tab key, the JAWS screen reader incorrectly read out cover thumbnails, resulting in confusing information. This was fixed. - May 2026 Metadata Management SF: 08279289 URM-321503
In some cases, when call numbers contained special characters, the browse bibliographic heading did not return matched records. This was fixed. - May 2026 Metadata Management SF: 08217325 08217171 URM-317281
Previously, local extensions were not added to Community Zone records. This was fixed. - May 2026 Metadata Management SF: 8187017 URM-321161
Previously, the search index Physical Item > In temporary location returned inconsistent results. This was fixed. - May 2026 Metadata Management SF: 08285170 08337696 URM-321211
When the customer parameter sbn_version was set to 2.03 or 3.02, Uniform Title links in SBN bibliographic records using the element but with tipoLegame=500 were not handled correctly. This was fixed. - May 2026 Metadata Management SF: 8316595 URM-323907
In some cases, when adding a new holdings record (after adding an item or from search results), the holdings record did not appear in the list of the inventory screen in the MDE or the search results. This was fixed. - May 2026 Resource Management SF: 07977003 08355443 08428782 URM-313662
Previously, collection name translations were not displayed correctly in the UI. This was fixed. - May 2026 Resource Management SF: 8283400 URM-321279
Previously, there was a mismatch between the Number of Loans and Number of In-House Uses displayed in Alma and corresponding values in Analytics. This was fixed. - May 2026 Resource Management SF: 08335932 08371550 URM-324326
Previously, saving a Collection in the Chinese interface overwrote the English Collection name. This was fixed. - May 2026 Resource Management SF: 8341556 URM-324381
The “Link a set of records to the Network Zone” job failed when executed on bibliographic records containing local extensions where subfield $$6 was used for purposes other than linking to an 880 field, and the $$6 value length was exactly five characters. This was fixed, and the job now completes successfully when handling such records. - May 2026 Resource Management SF: 8344058 URM-325522
Previously, there was an error when trying to open the bibliographic record from a collection. This was fixed. - May 2026 Resource Management SF: 8298610 URM-325674
In some cases, when using the Extended Export option in the CZ Update Task List, part of the entries were not included in the Excel file (this happens only when the extended export is done via a job, for more than 5,000 entries). This was fixed.
- April 2026 Acquisitions SF: 07960448 URM-253925
Previously, the Keep in Department setting was ignored when receiving more than 20 items. This was fixed. - April 2026 Acquisitions SF: 08005526 URM-306104
In some cases, an error was generated when creating or saving an invoice from a PO. This was fixed. - April 2026 Acquisitions SF: 08271353 URM-322763
Previously, selecting the License Terms tab for a license generated an error. This was fixed. - April 2026 Acquisitions SF: 08351746 URM-324272
Previously, the text Test2 was displayed as the first header in the Purchasing Review Rules configuration (Configuration Menu > Acquisitions > Purchase Orders > Purchasing Review Rules) for the rule's basic details. This was fixed. - April 2026 User Experience, Accessibility and Infrastructure URM-317221
Long facet labels would wrap to the next line instead of being truncated with an ellipsis. This was fixed for pages that use the new UX, such as Borrowing Requests, Lending Requests, All Titles searches, etc. To implement the fix, the allow_ng_facets_text_wrap_display parameter (Configuration > Resources > General > Other Settings) must be set to true. - April 2026 User Experience, Accessibility and Infrastructure URM-317221
When text spacing was adjusted, some content was cut off and could not be seen. This was fixed. To implement the fix, the text_spacing_extension_correction parameter (Configuration > Resources > General > Other Settings) must be set to true. - April 2026 User Experience, Accessibility and Infrastructure SF: 08101202 08080066 URM-254026
In some cases, there were multiple Primo login events in short succession. This was fixed. - April 2026 User Experience, Accessibility and Infrastructure SF: 08191697 URM-317766
For Bib records with double-space in the Originating System ID field, the double space was not displayed in Alma, a single space was displayed instead. This was fixed, and now a double-space will be displayed. Note: We have currently fixed only the Originating System ID field and only in the header of the "Record View" page, since white space collapsing is the default browser behavior and changing it system-wide might cause undesired behavior elsewhere. - April 2026 User Experience, Accessibility and Infrastructure SF: 08265760 URM-320468
Previously, the calendar to choose a date in a Staff Mediated Deposit field did not open. This was fixed. - April 2026 Analytics and Insights SF: 08166376 URM-317013
Previously, the Analytics report did not display items with provenance codes exceeding 64 characters in Alma. This was fixed. - April 2026 Analytics and Insights SF: 08240761 URM-322012
Previously, the Data Sharing Profile form did not allow free‑text entry when Other is selected for any question that includes this option. This was fixed. - April 2026 APIs SF: 08222934 URM-322408
Previously, the REST API update for digitization requests failed when page numbers were out of range. This was fixed; the API now behaves the same as the UI. - April 2026 Fulfillment and Resource Sharing SF: 8105010 URM-316820
Previously, staff could not set a shipped item to Lost when the lending request was associated with an NCIP partner. This was fixed, and a Lost action has been added that updates the borrowing request without sending a general message, enabling staff to set the item to Lost in these cases. - April 2026 Fulfillment and Resource Sharing SF: 07982690 08015756 08380365 URM-248092
Previously, when an item on loan had a Temporary Move Request and was checked in using the Return Items at the destination library, an error occurred, and the return was not processed. This was fixed, and the loan is now successfully returned. - April 2026 Fulfillment and Resource Sharing SF: 08117060 URM-254880
Previously, the Download Electronic Resource screen for lending requests did not display any results for limited-coverage portfolios or dateless lending requests. This was fixed. - April 2026 Fulfillment and Resource Sharing SF: 08163939 URM-316135
The patron workbench Fines and Fees list displayed an Oops error for corrupted fees where the fee owner (Library ID) was not found in the organization. This was fixed. Now, Alma displays the fee with an empty owner field. - April 2026 Fulfillment and Resource Sharing SF: 08219563 URM-317155
After canceling a booking request and loaning the item to a patron, the canceled request remained listed under Expired Hold Shelf. This was fixed. - April 2026 Fulfillment and Resource Sharing SF: 07941000 URM-318770
NCIP P2P ItemShipped messages were failing validation because the MonetaryValue element was sent with decimal values, while the NCIP specification requires an integer. The shipping cost value is now normalized before being included in the message, ensuring MonetaryValue is always sent as an integer. This aligns the message with NCIP requirements and prevents validation errors during processing. - April 2026 Fulfillment and Resource Sharing SF: 08274212 URM-320667
Previously, when an item's material type was changed while a request existed, the request was canceled without notifying the user. This was fixed, and a confirmation message now appears. - April 2026 Fulfillment and Resource Sharing SF: 08272545 URM-321364
In some cases, creating patron physical item requests with long notes did not work. This was fixed. - April 2026 Fulfillment and Resource Sharing SF: 08332647 08327345 URM-323394
Previously, when the ship digitally failed, lending requests were marked as shipped digitally, even though they were not actually shipped. This was fixed. - April 2026 Fulfillment and Resource Sharing SF: 08327393 URM-323817
Previously, when accessing Manage Patron Services via the On Loan Item > Borrower path, after selecting Done, an error was displayed. This was fixed. - April 2026 Fulfillment and Resource Sharing SF: 08386785 08388316 URM-323937
In some cases, the Rapido request form was not submitting. This was fixed - April 2026 Fulfillment and Resource Sharing SF: 08294270 URM-323989
Previously, the long DOI format did not populate when performing a manual borrowing request. This was fixed. - April 2026 Fulfillment and Resource Sharing SF: 08349298 08359155 URM-324181
Previously, Alma automatically rejected all RapidILL Lending requests. This was fixed. - April 2026 Metadata Management SF: 07867766 07826965 06785838 07824983 URM-213108
Under some configurations, it was possible that during an import job, a temporary record in the institution was not deleted when the institution record was linked to a network record. This was fixed. - April 2026 Metadata Management SF: 07932016 07888787 07887460 URM-242573
Previously, when viewing imported records (Import Job > … > Imported Records), the underlying query included the condition “linked institution not equal community.” This condition caused issues when attempting to change the search type. The CZ-related condition has been removed from the query, as it is no longer relevant. As a result, the search type can now be changed successfully while preserving the existing query conditions. - April 2026 Metadata Management SF: 07854586 URM-249966
In some cases, the Metadata Editor displayed different metadata for holdings than the value in MMS_RECORD and INVENTORY_HOLDING. This was fixed. - April 2026 Metadata Management SF: 08060469 URM-254146
In some cases, the Duplicate Title Analylsis job report didn't include all of the relevant institutions in the Held By column. This was fixed. - April 2026 Metadata Management SF: 08065708 URM-254702
When reloading an authority record from the NLI system (Authority Record Contribution integration profile: NLI), the external record's version was not updated in the Alma Community Zone. This was fixed. - April 2026 Metadata Management SF: 08156977 URM-315506
Previously, transliteration for special characters was incorrect. This was fixed. - April 2026 Metadata Management SF: 08208038 08255155 08245447 URM-318534
Previously, the Advanced Search > Modification Date reverted to the previous day when selected from a previous search. This was fixed. - April 2026 Metadata Management SF: 08229577 08281457 URM-319934
In some cases, when the Additional Authorized Fields were configured, the PTC job failed. This is fixed. - April 2026 Metadata Management SF: 08307962 URM-322203
Previously, the Field Information button on the Metadata Editor fields was linked to an outdated URL. This was fixed. - April 2026 Metadata Management SF: 08281738 URM-322679
Previously, when an XSL normalization contained a comment ( ) that included the word rule in it, it could not be saved properly. After saving, the editor cuts all text before the word rule. This was fixed. - April 2026 Metadata Management SF: 08331133 URM-323390
Previously, the Update Inventory import behavior was changed to apply Normalization before matching incoming records to existing records. This change caused issues for multiple customers who require normalization to be applied after the matching phase. A new customer parameter has been introduced to control whether to apply normalization prior to or after the matching phase. - April 2026 Metadata Management SF: 08328038 URM-323927
In some cases, when a title search contained multiple bibliographic records with related records, the Holdings tab displayed related holdings of another record. Those related holdings disappear when refreshing the search results. This was fixed. - April 2026 Resource Management SF: 08158585 08013989 URM-252807
Previously, when an Electronic Activation Task list included an electronic collection with thousands of portfolios, the Unsuppress action was non-responsive, resulting in a timeout. This was fixed. - April 2026 Resource Management SF: 7928835 URM-253097
Items List: When binding items that were in process and then selecting Create and Edit, when editing the bound item and saving it, the user was returned to the items list and the bound items were mistakenly displayed in the items list as blank rows. This was fixed. - April 2026 Resource Management SF: 08179454 URM-317202
Previously, the Primo VE link resolver was retrieving CZ-related records even when the Related Records for Serials configuration was disabled. This was fixed, and CZ-related records are now only retrieved when enabled by the user configuration. - April 2026 Resource Management SF: 07939042 URM-318874
Previously, the Representation was not imported for a record found as a single match with MERGE operation in the OAI import job. This was fixed. - April 2026 Resource Management SF: 08221408 URM-319510
When a general publishing profile with Profile Details / Content / Publish the entire repository selected, and Data Enrichment / Related Records Enrichment / Add related records information selected and configured, was executed, the published records did not contain the expected related records data. This was fixed. - April 2026 Resource Management SF: 08165267 URM-320140
When creating a new portfolio via the API that was defined as active (the value of the availability tag was 11), the portfolio was activated, but the activation date remained empty. This was fixed. - April 2026 Resource Management SF: 08278680 URM-321962
When a network member institution retrieved an electronic portfolio in the Community Zone tab, a network icon was displayed to the left of the title, indicating that a Network Zone portfolio was linked to this Community Zone, even though no portfolio in the Network Zone was actually linked to the Community Zone portfolio. This was fixed, and the network icon is only displayed if there is a Network Zone portfolio directly linked to the Community Zone portfolio. - April 2026 Resource Management SF: 08303950 URM-322986
Previously, an incorrect expiry date was displayed in a Long-Term Digital Loan expiry date field in the Digital Viewer. This was fixed. - April 2026 Resource Management SF: 08322736 URM-323609
Previously, when using the Item updater by Excel, the Replacement Cost field was updated even when it was not included in the file. This was fixed. - April 2026 Resource Management SF: 08328567 URM-323660
Previously, Extended Exports from the Community Zone portfolios list downloaded an Excel file in the wrong format (appearing as corrupted). This was fixed, and the export now downloads in the correct Excel format. - April 2026 Resource Management SF: 08370008 URM-325152
Previously, the file sorting did not work according to the sub-field 08 linking number. This was fixed.
- March 2026 Acquisitions SF: 08099408 08290660 08294826 08294470 08327831 08329304 08319384 URM-254271
Previously, wildcards and special characters did not work as expected on the Receive New Material search. This was fixed. - March 2026 Acquisitions SF: 8073250 URM-306203
Previously, when creating an invoice via EDI, invoices could not be created if the over expenditure limit sum was 0.0. This was fixed. - March 2026 Acquisitions SF: 08184374 08240818 URM-319266
Previously, the Uploaded Counter report did not appear in Usage Data > Uploaded Files. This was fixed. - March 2026 Acquisitions SF: 8130899 URM-319576
Previously, users with the roles Purchasing Operator Extended and Purchasing Manager were unable to delete POs. This was fixed. Now, if the PO line owner matches the library in the role scope, the user can delete the PO. - March 2026 Acquisitions SF: 8250748 URM-319708
Previously, the service unit name was not translated on the In Process Item (Configuration > General > Work Order Types) page. This was fixed, and the service unit name is now translated. - March 2026 Acquisitions SF: 08190147 08075310 URM-320419
Previously, the Replace resource action didn't remove the linking between the NZ resource and the local IZ poline. This caused the NZ resource to appear in Analytics reports. This was fixed. - March 2026 Acquisitions SF: 8242152 URM-320576
Previously, there was an issue with a limitation on records in input files. This was fixed. The limitation was removed, and large files can be loaded. - March 2026 Acquisitions SF: 8303664 URM-321845
Previously, creating an invoice from Excel always set the invoice line to fully invoiced and released the remaining encumbrance regardless of the encumbrance setting. This was fixed, and subscription PO lines will not be fully invoiced. - March 2026 Acquisitions SF: 8317624 URM-322978
Previously, users with read-only roles were not able to view the acquisition configuration. This was fixed. - March 2026 User Experience, Accessibility and Infrastructure SF: 8173354 URM-318775
Previously, bib headings created when Deposits were created with a name in field 100 could not be deleted. This was fixed. - March 2026 User Experience, Accessibility and Infrastructure SF: 8287782 URM-322227
Previously, Discovery Import Job Counters were visible in the Alma job report UI, but were not exposed in the Get-Job-Instance API. This was fixed. - March 2026 User Experience, Accessibility and Infrastructure SF: 08283644 08321391 08292662 URM-322719
In some cases, users were receiving notifications on expired SAML certificates in a profile that no longer exists. This was fixed. - March 2026 Analytics and Insights SF: 8225498 URM-319465
Previously, when the Network Zone opened the Analytics configuration mapping table Participants in Consortial Analytics for the first time, the Updated By for every member had the login user ID, and Last Update was populated with the current date, even if the user did not change the table at all. This was fixed. - March 2026 Analytics and Insights SF: 8249188 URM-322017
Previously, the Not Relevant option was missing from the Total Undergraduate Student Body Size question in the Data Sharing Profile configuration form. This was fixed. - March 2026 Analytics and Insights SF: 8282310 URM-322440
Previously, several LC classification codes were not displayed in Analytics. This was fixed. - March 2026 APIs SF: 8091137 URM-313844
Previously, when First Label Print Position was set to any row other than Row 1, Col 1, the application reverted to Row 1, Col 1 upon restart. Additionally, while the preview displayed the correct starting position, the actual PDF output printed from position 1, 1 instead of the configured position. This was fixed, and the First Label Print Position is now retained, and the PDF output now prints the correct position. - March 2026 APIs SF: 08228003 08245501 08264202 08283722 08267822 08275555 08317676 URM-317588
Previously, when running the latest Stunnnel version v5.76, an error was generated in the Stunnel log. This was fixed. - March 2026 APIs SF: 08289255 URM-322307
Previously, in the Webhook Integration Profile, the Custom Header was not sent via the GET challenge request. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 7207614 URM-226320
In some cases, the Create physical work orders job failed to communicate part of the remote storage request. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 08141225 07892060 URM-247163
Previously, the circulation desk names were displayed in English rather than the user's selected language on the create request form. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 08115142 08262080 08300845 URM-314166
Previously, Export for Current View ignored customizations and always used the default values. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 8153470 URM-315007
When a citation with copyright information was copied or duplicated to another reading list, the copyright data was lost and became editable. This was fixed so that the copyright information is retained and remains disabled for editing, just as it is on the original citation. - March 2026 Fulfillment and Resource Sharing SF: 8148886 URM-316004
In some cases, when searching for linked users via API source_user_id, or via UI Find user in another institution the user was not found even though the linked account already existed in the target institution. This resulted in the creation of multiple duplicate users. This was fix. Now, when searching for a duplicated linked user, Alma returns the latest created user. - March 2026 Fulfillment and Resource Sharing SF: 8149652 URM-316007
In some cases, the rota template page did not display correctly. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 8166249 URM-316033
Previously, the user card was visible even when the View User Card was disabled. This was fixed, and now only users with the View User Card privilege can view user cards. - March 2026 Fulfillment and Resource Sharing SF: 08185960 08257107 08218646 08285960 08259743 08259682 08293979 URM-316175
Previously, a temporary CZ outage occurred during the first attempt to retrieve information, causing a runtime exception that resulted in duplication. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 08164867 08186496 08268070 08272106 08336416 URM-316359
Previously, overdue fines continued accruing even when the overdue_at_lost_loan/overdue_at_claim_return_loan (Configuration Menu > Fulfillment > General > Other Settings) parameter was set to true. This was fixed. Now, when the Found Item action is used to revert a lost/claim return item back to active status, any overdue fines that were generated are waived (based on the overdue_at_lost_loan/overdue_at_claim_return_loan parameter). Once the item is actually returned, the overdue fine policies are applied to the entire overdue period. - March 2026 Fulfillment and Resource Sharing SF: 8215138 URM-317673
Previously, when creating an AFN request, the borrowing request displayed the correct pickup location, but the fulfillment request on the lending side displayed a library from another consortia institution. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 8223017 URM-318449
Previously, editing a fulfillment unit whose name contained an ampersand resulted in an error. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 8239728 URM-318484
In some cases, the show file action was not working. That was fixed - March 2026 Fulfillment and Resource Sharing SF: 08231072 08287110 URM-318715
Previously, when editing a physical item request, the error failed to initialize the request was generated, and the pickup location was not listed. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 8192435 URM-319580
Previously, the ISO 18626 message sent from Alma to Tipasa included incomplete or truncated data in the volume and issue fields. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 8252331 URM-320918
Previously, when a digital borrowing request was received as Physical non-returnable and completed upon receiving, the request's additional ID was not included in the On hold shelf letter. This was fixed, and now the field in the letter XML is populated correctly. - March 2026 Fulfillment and Resource Sharing SF: 8234435 URM-321690
Previously deselecting ‘I only need a specific chapter’ did not remove chapter information from Alma borrowing request. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 8259982 URM-322192
SSI: Handle historical archiving - Previously, the job Status was Completed with Errors, even though there were no failed records. This was fixed. - March 2026 Fulfillment and Resource Sharing SF: 08317665 08316927 URM-322575
Previously, Recalculate Partner and Reset Rota actions did not re-add partners that were already in the rota. It was fixed. - March 2026 Metadata Management SF: 07648627 07777627 URM-235490
In some cases, when Record has matches was defined as an error, authority records with matches were saved, and an error was generated. This is fixed. - March 2026 Metadata Management SF: 8039172 URM-254190
When a new UNIMARC authority record containing a field 815 was contributed to SBN, the tipoAuthority (authority type) attribute for the 815 link was incorrectly set to AU (Author) instead of RE (Repertoire), causing the SBN server to reject the record. This was fixed. - March 2026 Metadata Management SF: 08249028 08258474 URM-319113
Previously, the Description search index didn't work with is/is not Empty. This was fixed but requires re-indexing. - March 2026 Metadata Management SF: 08253742 08267593 08245281 URM-321043
In some cases, the CV-List was not displayed for repeated subfields. This was fixed. - March 2026 Metadata Management SF: 8257076 URM-322591
Previously, an incorrect info card was displayed in Primo VE when no info card was displayed in Alma. This was fixed. - March 2026 Resource Management SF: 8134079 URM-314656
Previously, the Springer autoholding integration generated an incorrect local date for a portfolio in the Coverage tab. - March 2026 Resource Management SF: 8165862 URM-315558
Previously, the host record did not display all related holdings and all related items from the part records. This was fixed. - March 2026 Resource Management SF: 8187904 URM-316947
Previously, Collections were not deleted after the Delete Collection job was run. This was fixed. - March 2026 Resource Management SF: 08230180 08344487 URM-318608
Users with the role Physical Inventory Operator or Physical Inventory Operator - Limited were unable to see the Run a Job menu and run the Change Physical Items Information job. This was fixed. - March 2026 Resource Management SF: 08215120 08253170 08288925 URM-318615
Previously, when relinking a holdings record to a target bib record that had a matching holdings record, the items were moved from the source holdings record to the target matching holdings record; then, the empty source holdings record was deleted (unless it was marked as committed to retain). However, the deletion process was not completed, and the empty, partially deleted source holdings record was mistakenly attached to the target bib record. This made the source holdings record searchable and editable in the MD Editor as if it were part of the target bib record. Both of these issues were fixed. - March 2026 Resource Management SF: 8159175 URM-319166
Previously, parent records were deleted when a purchase request was rejected. This was fixed. - March 2026 Resource Management SF: 8221498 URM-319499
Previously, the Online service order configuration was not applied. This was fixed. - March 2026 Resource Management SF: 8284853 URM-321110
Previously, when the Description in the Copyrights Statements form exceeded the character limit, an error was generated. This was fixed. - March 2026 Resource Management SF: 8304754 URM-322352
Previously, when a collection was created via the API, the source and creator fields were not populated. This was fixed.
- February 2026 Acquisitions SF: 08218470 07913344 URM-243237
Previously, there was an incorrect rounding in PO Lines created from an API when applying a discount, resulting in an inconsistency between the net price and total funds amount. This was fixed. - February 2026 Acquisitions SF: 8066446 URM-254712
In some cases, the classic Primo View It frame did not have white space padding between the Access Model field name and its value. This was fixed. - February 2026 Acquisitions SF: 8032144 URM-254885
Previously, PO line Ordered Collection results were inconsistent. This was fixed. - February 2026 Acquisitions SF: 8164681 URM-316372
Previously, the Has Content blue triangle indicator was missing from the Licenses History tab. This was fixed. - February 2026 Acquisitions SF: 8179190 URM-317510
Previously, the reclaim date did not behave consistently depending on how the date was changed. This was fixed. - February 2026 Acquisitions SF: 8232300 URM-319152
Previously, the request URL construction did not include proper normalization of spaces into valid encoded characters. This was fixed. - February 2026 Acquisitions SF: 07831409 08252574 08252187 08262143 07842204 08257233 08273133 08274260 08289623 08288954 URM-319251
Previously, when the parameter po_line_description_update_upon_bib_change (Configuration Menu > Acquisitions > General > Other Settings) was enabled in a Network Zone environment, when the Network Harvesting Job executed to distribute changes to the linked records in member institutions, the member registered was not updated. This was fixed. - February 2026 Acquisitions SF: 8242222 URM-319321
In some cases, the Import job failed. This was fixed. - February 2026 Analytics and Insights
In cases of long harvesting jobs, data was missing from Analytics. This was fixed. - February 2026 Analytics and Insights SF: 8082221 URM-314858
Previously, some successfully harvested COUNTER files were not loaded into Alma Analytics, causing missing usage data. This was fixed. - February 2026 Analytics and Insights SF: 8231753 URM-319238
After the fix, when an admin revokes a user's access to a report, the associated notification is automatically removed from that user's account. - February 2026 APIs SF: 8230381 URM-319455
Previously, when searching for a letter configuration for the SystemJobLetter using the API, the wrong configuration was returned. This was fixed. - February 2026 APIs SF: 8242097 URM-320904
Previously, the SAML Certificate Expiration Email was sent despite the letter being disabled. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 6776553 URM-205111
SLNP: Previously, Alma returned an error response 510 Command not supported to the ZFL server, even though the lending request was correctly created in Alma. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8115275 URM-314820
Previously, the Creation Date on resource sharing partners copied from the Community Zone was set to the current date rather than the date the partner was created. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8186877 URM-316613
Previously, the measure Days of Request to Material Arrival was not accurate. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8152977 URM-316622
In some cases, partners originating from the Network Zone received incorrect information from the Community Zone. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8169326 URM-317095
Previously, Fill Locally workflow sometimes created a lending request to the wrong member. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8219563 URM-317155
Previously, when a loaned item was scanned, the booking request that was canceled remained in the system and was not deleted. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8257361 URM-319328
There was no translation for the External Identifier on the Scan in Items. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 08258777 08119975 URM-319700
Previously, when using {rft.normalized_issn} in the General Electronic Services (GES), the ISSN value was removed entirely, resulting in an empty parameter (issn=&) instead of returning the normalized ISSN. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8243713 URM-319882
Manage patron services: Previously, filtering loans by Loaning desk caused a display issue where the wrong number of loans was displayed. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8239481 URM-320133
In some cases, using the Exact Open Days option in the Grace Period policy caused problems when trying to return loaned items. This was fixed. - February 2026 Fulfillment and Resource Sharing SF: 8275396 URM-320305
Previously, when a lending request's overdue message failed to send, no indication was listed on the lending request's history. This was fixed. - February 2026 Metadata Management SF: 08351319 08351300 08353288 08351653 08352823 08349278 08349033 08343093 08353249 08351194 08353522 08354221 08353992 08349257 08356724 08352289 08357481 08359400 08358859 08353385 08358739 08361919
(Updated on 12 February 2026) The LoC iframe no longer works. LoC links will now open in a new tab instead of an iframe. - February 2026 Metadata Management URM-317212
(Updated on 26 January 2026) In Metadata Editor records, when text spacing was in use, some content was cut off. This was fixed and it is now improved to comply with accessibility standards. For the fix to be implemented, the text_spacing_extension_correction parameter (Configuration Menu > Resources > General > Other Settings) must be set to true (the default is false). - February 2026 Metadata Management SF: 07950333 08059340 07811933 07900249 08223318 08279617 URM-242356
In some cases, searches from the Network tab returned Community zone server is down error when it should not have. This was fixed. - February 2026 Metadata Management SF: 7998094 URM-253332
Held By Details page: Holdings suppressed on the location level were not shown as suppressed. This was fixed. - February 2026 Metadata Management SF: 8164017 URM-316029
In some very specific cases, when browsing bibliographic headings, the same heading was duplicated in the results list. This is fixed. - February 2026 Metadata Management SF: 8216305 URM-317976
In some cases, when partial linking was activated in the Network Zone and not in the Institution Zone, editing an NZ record and reselecting the linked authority using F3 sometimes duplicated the subfields. This is fixed. - February 2026 Resource Management SF: 08232956 08042063 URM-254705
In some cases, the Deleted bib records counter in the report of the Withdraw Physical Items job was incorrect. This was fixed. - February 2026 Resource Management SF: 08226846 08106801 URM-254901
Relink holdings to another bib: if a matching holdings was found in the target bib, and the source holdings had many (thousands) items, the relink action did not complete. This was fixed. - February 2026 Resource Management SF: 08164382 08104481 URM-313547
In some cases, when adding a new item in the Items List page, Alma returned to the Items List, but it was either empty or displayed fewer items. This was fixed. - February 2026 Resource Management SF: 8100394 URM-314241
Previously, the Remove titles from collection job displayed incorrect numbers. This was fixed. - February 2026 Resource Management SF: 8203517 URM-317108
Previously, the Network Zone Held by details page showed the same item twice, one in the permanent holding and once in the temporary (virtual) holding. This was fixed. When an item is in a temporary location, it is displayed in the virtual temporary holding, and does not also appear in the permanent holding entry. - February 2026 Resource Management SF: 08240163 08246656 08284579 URM-319258
Previously, due to corrupt data, an error was generated when opening the Electronic Resource Activation Task List (Resources > Manage Inventory > Manage Electronic Resource Activation). This was fixed. - February 2026 Resource Management SF: 8274343 URM-321109
In some cases, the wrong error message was generated for the Restore jobs tool in non-Network Zone environments. This was fixed. - February 2026 Resource Management SF: 8271651 URM-321157
Previously, the portfolio title was not displayed when the bib record is Dublin Core. This was fixed. - February 2026 User Experience, Accessibility and Infrastructure SF: 8173478 URM-316352
It is now possible to configure the OpenID Connect Login Link from the Help menu > Premium Sandbox. - February 2026 User Experience, Accessibility and Infrastructure SF: 8259007 URM-319655
Previously, the Print Queue showed printouts of another user when both users had the same first and last names. This was fixed. - February 2026 User Experience, Accessibility and Infrastructure SF: 8261268 URM-320112
Users created using SAML JIT were always created as account type EXTERNAL, even if the XSL specifically generated an XML with INTERNAL. This was fixed.
- January 2026 Acquisitions SF: 08171726 URM-315955
Previously, when the Solr search language was in Korean/Japanese/Chinese, searching for a purchase request with a title in Korean/Japanese/Chinese did not return results. This was fixed. - January 2026 Acquisitions SF: 08130242 08227742 08036238 08100455 08098008 URM-253923
Previously, purchase orders were not closed when purchase order lines were closed by the invoice process. This was fixed. - January 2026 Acquisitions SF: 06985469 08209793 08232790 URM-318978
Previously, the serial item/s receiving process did not update the expected receiving date on the PO line. This was fixed. - January 2026 Acquisitions SF: 08118687 URM-315921
Previously, it was possible to generate fund transfers between different fiscal periods. This was fixed. - January 2026 Acquisitions SF: 08082352 URM-314357
Previously, the Manage EDI tasks included both English and the selected UI language in the response summary (Acquisitions > Purchase Order Lines > Manage EDI Tasks). This was fixed. Now only the selected UI language is displayed. - January 2026 Fulfillment and Resource Sharing SF: 07977013 URM-318601
When changing the due date on multiple loans, the new due date was not displayed in the This Session filter. This occurred in cases where the loan ID was longer than 14 digits. This issue has been resolved, and the new due date is now displayed immediately for all loans in "This Session". - January 2026 Fulfillment and Resource Sharing SF: 08184667 URM-316616
In some cases, hiding the General Hold Request button using Display Logic Rules (DLR) when a General Electronic Service (GES) existed did not work. This was fixed. - January 2026 Fulfillment and Resource Sharing SF: 08142256 08031444 08186472 08144502 08084155 08031561 08070341 08221355 08189769 URM-253656
In some cases, the manage patron services indicated users had active requests when those requests were not active. This was fixed. - January 2026 Fulfillment and Resource Sharing SF: 07964481 URM-252320
Previously, reading room items that were loaned were not renewed when they were re-scanned. This was fixed, and now reading room items with an AT_USER status are renewed when re-scanned. - January 2026 Fulfillment and Resource Sharing SF: 07982690 08015756 URM-248092
Previously, when an item on loan had a Temporary Move Request and was checked in using the Return Items at the destination library, an error occurred, and the return was not processed. This was fixed, and the loan is now successfully returned. - January 2026 Fulfillment and Resource Sharing SF: 07911914 URM-248185
Previously, requests for serial items with identical item descriptions ignored the Pickup Location. This was fixed. - January 2026 Fulfillment and Resource Sharing SF: 06807126 URM-246886
In some cases, creating borrowing requests triggered a timeout. This was fixed. - January 2026 Fulfillment and Resource Sharing SF: 08282063 URM-320789
In some cases, Rapido tiles were not displayed for users who were not logged in. This was fixed. If customers prefer to hide these tiles for non-logged-in users, adjust the setting under from Configuration > Resource Sharing > Hide Rapido Options, and check the Hide section when user is not logged in checkbox. - January 2026 Metadata Management SF: 08212024 URM-318609
Previously, Alma always preserved the literal # character in MARC21 007 fields when storing the record in the database. This behavior is now configurable, and when the parameter is set to false, all # characters in MARC21 007 fields are replaced with spaces before being stored in the database. Contact support to change this parameter setting. - January 2026 Metadata Management SF: 08197214 URM-318602
In some cases, the record was not returned in the LC Subject search. This was fixed. - January 2026 Metadata Management SF: 08223775 URM-318277
In some cases, searches containing special characters returned incomplete results. This was fixed. - January 2026 Metadata Management SF: 08241533 URM-318888
Previously, portfolios whose collections contained special characters were not viewable in an All Title search. This was fixed. - January 2026 Metadata Management SF: 08153386 URM-316406
New titles search: In some cases, an "Oops" error was displayed when selecting the Licenses link. This was fixed. - January 2026 Metadata Management SF: 08216442 URM-318575
In some cases, scheduled manual jobs failed and were not restarted. This was fixed. - January 2026 Metadata Management SF: 08197357 URM-318025
Previously, the normalization rule was not considered when matching by the POLine/vendor reference number in the Update Inventory import profile. This was fixed. - January 2026 Metadata Management SF: 08155855 URM-314669
When an authority or bibliographic record was created in Alma, then contributed to SBN, the record's originating system id was not reset to be the SBN record id. Because the originating system id for an authority record did not match the external (SBN) system id, the authority import profile's match method "001 To ORIGINATING_SYSTEM_ID" did not match the Alma record to the SBN record, which resulted in the SBN authority alignment job creating duplicate authority records in Alma. This was fixed. - January 2026 Resource Management SF: 08170475 URM-315899
In some cases, the Open Predicted Items job took a long time to complete. This was fixed. - January 2026 Resource Management SF: 08097888 URM-315046
Previously, local extensions were deleted after adding portfolio contributions. This was fixed, and the local extensions now remain intact. - January 2026 Resource Management SF: 08075239 08071233 URM-254239
In some cases, when the Delete Electronic Collection job and the Electronic activation job accidentally ran almost in parallel, bibliographic records that had live portfolios were deleted. As a result, these portfolios turned to "orphans". To prevent this, a dependency has been added between these two jobs, so that they can no longer run in parallel. - January 2026 Resource Management SF: 08158585 08013989 URM-252807
Unsuppress record from Electronic Activation Task list: when this involved an electronic collection with thousands of portfolios, the Unsuppress action got stuck and timed out. This was fixed. - January 2026 Resource Management SF: 08033240 URM-252709
In some cases, when selecting Electronic Collection > Portfolio list > Other details > selecting a course with a linkable number, an error occurred, and the course was not displayed. This was fixed. - January 2026 Resource Management SF: 08143772 URM-318429
Previously, Controlled Vocabulary tables were not displayed when the UI's results per page was set to a value lower than the number of tables. This was fixed. - January 2026 Resource Management SF: 07977003 URM-313662
Previously, collection name translations were not displayed correctly in the UI. This was fixed. - January 2026 User Experience, Accessibility and Infrastructure SF: 08222944 URM-318528
In some cases, the text from the multi-select text boxes was missing on the Staff-mediated Deposit form (Specto > Deposit > Staff-mediated Deposit). This was fixed. - January 2026 User Experience, Accessibility and Infrastructure SF: 08168238 URM-315656
Previously, the Bulk Fine Waiving functionality from a set did not work for all users in large sets. This was fixed. - January 2026 User Experience, Accessibility and Infrastructure SF: 08203650 URM-318546
Previously, translations were missing for Draft, Submitted, and Withdraw labels on the patron Deposit form. This was fixed. - January 2026 User Experience, Accessibility and Infrastructure SF: 08243441 URM-318532
Previously, when the Staff-mediated Deposit form (Specto > Deposit > Staff-mediated Deposit) was open, the file uploader appeared inactive. This was fixed.

