Alma 2025 Release Notes
- Subscribe by RSS
- Share page by email
- Last updated
- Apr 20, 2025
- Save as PDF

Upcoming Issues to Note
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 Purchase Requests (Analytics) subject area was updated:
Upcoming Issues to Note
AI Metadata Assistant Update
In November 2024, we launched the Preview Mode of the AI Metadata Assistant for all Alma libraries. This initial testing phase enabled libraries to experience metadata enrichment and provide valuable feedback. We appreciate the many libraries and librarians who contributed their insights to help us improve the assistant!
Phase I: Full Availability
Phase I of the AI Metadata Assistant is now fully available, featuring:
- Improved Metadata - Enhanced metadata generation based on community feedback. We will continue to refine this by monitoring catalogers' feedback and collaborating with the community.
- PDF Support - Upload a PDF file of up to four pages containing a resource description (for example, publisher's description). If a larger file is uploaded, only the first four pages are processed.
- Streamlined Workflow:
- Select a template for creating new records. The AI-generated draft expands from this template, adding fields not generated by the AI. The system remembers the cataloger's selection for future use.
- Upload up to four images of the resource, supporting cases where more than two images are needed (for example, books with a long table of contents).
- New Configuration Options
- Normalization Process: Create a process to correct AI-generated metadata by removing, replacing, or adding metadata fields and subfields.
- Merge Method: Select a merge method for enhancing records with the AI Metadata Assistant.
- Version Tracking - For records created or enriched using the AI Metadata Assistant after the February release, it is possible to identify the version created with the assistant when viewing record versions.
For more information about the AI Metadata Assistant, see the recording of the Alma 2025 Roadmap Webinar Series: The AI Metadata Assistant in the Metadata Editor.
We continue to work with our community to further improve the AI Metadata capabilities in Alma. Stay tuned for future enhancements!
Elevating Your Experience with Our Service Excellence Program
We are committed to enhancing your experience through our Service Excellence Program, driven by your valuable feedback and support needs.
Key initiatives for the upcoming year include:
- Improved visibility into cases requiring development support.
- Estimated timelines for issue resolutions.
- Consistent updates: Regular status updates on cases at set intervals.
To achieve these goals, we are launching the Defect Backlog Resolution Project for Alma and PrimoVE in collaboration with the ELUNA and IGELU Steering Committees. Resolved issues will be documented in the release notes.
We will keep you informed of our progress and appreciate your ongoing feedback. We look forward to continually enhancing your experience.
Upcoming Issues to Note
Elevating Your Experience with Our Service Excellence Program
We are committed to enhancing your experience through our Service Excellence Program, driven by your valuable feedback and support needs.
Key initiatives for the upcoming year include:
- Improved visibility into cases requiring development support.
- Estimated timelines for issue resolutions.
- Consistent updates: Regular status updates on cases at set intervals.
To achieve these goals, we are launching the Defect Backlog Resolution Project for Alma and PrimoVE in collaboration with the ELUNA and IGELU Steering Committees. Resolved issues will be documented in the release notes.
We will keep you informed of our progress and appreciate your ongoing feedback. We look forward to continually enhancing your experience.
Main Features
Upcoming UX Enhancements in the May 2025 Release
Alma introduces major UX improvements in the May 2025 Alma Release, bringing enhanced workflows, improved readability, and a smoother transition to the new UI experiences.
Manage Patron Services and Return Items New UX
The new, next-generation Alma UX design is available for the Manage Patron Services and Return Items pages. In this release, the new UX is automatically set as the default for all users, with no option to opt-out.
For a general overview of the new Manage Patron Services and Return Items pages, see Managing Patron Services at a Circulation Desk - New Layout.
Title Searches New UX – Enhancements & August Sunset
The classic title search UX will be sunset as part of the August 2025 - we encourage you to work with the new search and become accustomed to it.
The May release introduces several improvements to the new Title Searches UX, addressing feedback and fixing known issues:
View Work Action for BIBFRAME Instances in All Titles Search
A new action in the All Titles search for BIBFRAME instance records enables users to navigate to the details page of the linked work within a sliding panel, improving navigation and display of the BIBFRAME work.
For more information, see Performing Record Actions on the Repository Search Results Page.
Enhanced Saved Facets in Title and Holdings Searches
You can now save multiple facet combinations and quickly apply them to your searches, similar to the functionality on the Manage Sets page. Saved facets appear in the Saved drop-down list, where you can also set a default that is automatically applied to searches.
Users who previously saved facets in title searches before this update will find them in the drop-down list, labeled Pre-saved.
For more information, see Saving Multiple Combinations of Facets.
Adding Cataloger Notes in the Titles and Holdings Searches
In title and holdings searches, catalogers can now view, add, edit, and delete notes directly without opening the Metadata Editor. Notes are only accessible for viewing or editing when available to the user in the Metadata Editor: if the cataloger has permission in the Metadata Editor and the record is not locked. Additionally, notes can only be managed within the search scope where the record is maintained (institution, network, or community). This enhancement enables catalogers to quickly add notes to bibliographic or holdings records.
For more information, see Searching in Alma > Notes Section.
Navigation Links Added to the Title Searches Export
The new title search UX includes single-click links to additional related entities, such as Related Records, Courses, Licenses, and Reminders, along with a link to the new Notes section for catalogers. These fields are now included in search exports to Excel, just like existing navigation links for Orders and Requests. This enhancement enables users to quickly identify records with related entities in their exported files at a glance.
For more information, see Export to Excel.
AI Indication for Community Zone Enriched Records
In the new title searches UX, the AI indication () is now displayed for Community Zone records enriched by the Community Zone AI generator.
For more information, see:
Enhanced Electronic Portfolio Availability Information in Title Searches
The expanded electronic tab and the electronic portfolio section now include a calculated availability indication, taking into account both the portfolio and service status and reflecting the availability of the portfolio to patrons.
This availability, as well as the availability set in the portfolio, are also added to the Excel created when exporting the electronic portfolio section.
For more information, see Searching in Alma > Electronic Portfolios.
New Title Search Experience Features Now Available When Adding Titles to Collections
The features of the New Title Search Experience are now available when adding titles to collections (Resources > Manage Collections > Edit a Collection > Titles List > Add Title):
Among other characteristics of the next-generation interface, it displays as a sliding panel, with a multi-select facets pane and title details pane.
For an overview of the next-generation interface, see Introduction to the New Title Search Experience.
Enhanced Search Query Design with Improved UI and Accessibility

We have introduced a new search query design with an updated UI to ensure a more consistent and efficient search process, improving the visibility and usability of search options across different workflows. The new design includes a refreshed search query display and a magnifying glass icon for quick access to update the query via the Advanced Search.
The redesigned search query and new icon make it easier for users to understand the search query and locate and utilize Advanced Search functionalities. The enhanced UI elements and structured design improve navigation, benefiting all users, including those using assistive technologies.
For more information, see Searching in Alma.
Enhanced Text Appearance for Improved Readability
The text appearance in the record view and sections of the new UI across Alma was updated. Labels now have bold font, and values appear as regular text rather than bold. This change enhances various pages, including Purchase Order Lines, Resource Sharing, Manage Patron Services and Title Searches, to create a clearer and more intuitive interface.
This update improves readability by making it easier to distinguish between labels and their corresponding values. It was driven by user feedback, discussed, and approved by the UX focus group. It enhances the overall user experience, ensuring a more user-friendly, readable, and visually appealing system.
Closed Library Management TOU for Resource Sharing Request

It is now possible to configure system behavior for managing a lending request's due date if the calculated date falls on a closed date. This enables the library to ensure that the lending requests' due date is not calculated to fall on dates when the library is closed.
For more information, see Managing Lending Requests.
Supporting Linked Open Data and VIAF for Local Authorities
Institutions that use local authorities (in Institution Zone or Network Zone) or copy Community Zone authorities to work with them locally can define global ID's to be extracted from the authority records and mapped to VIAF (Virtual International Authority File). Institutions with local name authorities that are part of VIAF are able to view info cards, contributor pages and use the URI enrichment configuration.
For more information, see Configuring Linked Open Data for Local Authorities.
Alma AI Metadata Assistant Developments
AI Metadata Assistant: Request Specific Metadata
Administrator Control: Manage Requested Metadata from AI Assistant
Searching for Titles with AI Generated Metadata
Two new search indexes have been added to title searches:
-
Processed with Alma AI tools – Searches for records created or enriched using Alma's AI Metadata Assistant.
-
Enriched with AI metadata by CZ – Searches for Community Zone records that have been enriched with AI-generated metadata.
These indexes help libraries quickly identify records cataloged with AI-generated metadata.
The new indexes require re-indexing and will be fully operational for new, updated, and re-indexed records only. Full functionality will be available after the semi-annual indexing process is completed. In sandbox environments, they will become fully operational after the next refresh or re-indexing.
For more information, see Search Index to MARC 21 Bibliographic Tag Mapping.
Upload Resource Descriptions in PDF and Word Document Formats in AI Metadata Assistant
Catalogers can now upload a PDF or Word document (up to 4 pages) containing a resource description, in addition to JPEG and PNG images. For larger files, only the first 4 pages will be used to generate metadata.
This feature is particularly useful for libraries that receive descriptive files and metadata from vendors, allowing them to generate or enrich records more efficiently.
For more information, see Working with the AI Metadata Assistant > Creating a New Record.
Delete Portfolios Directly from the Metadata Editor

It is now possible to delete portfolios directly from the Metadata Editor inventory section.
For more information, see Navigating the Metadata Editor page > View Inventory.
For more information on network-specific configurations for record deletion, see Restrict Deletion of Network Zone Bibliographic Records with Related Records and/or Local Extensions.
Enhanced Title Navigation in the Physical Holdings Search
In the physical holdings search, viewing title information now opens the full title details instead of just the bibliographic record. This enables users to access the bibliographic record, its inventory, and related entities, as well as perform actions on the title and inventory based on their privileges. The Record View page remains accessible from the title details via the "View Record" action. This enhancement is especially useful for users who need to navigate seamlessly between holdings and titles while performing actions on both.
For more information, see Performing Record Actions on the Repository Search Results Page.
Physical Holdings Search Labels Management for Physical Inventory Operators
Since the repository search is available to all system users, managing repository search labels is restricted by a privilege, which is granted by default to administrators and managers. Previously, a single privilege controlled label management for both the physical holdings search and the new title searches. Now, separate privileges exist for bibliographic and physical holdings search labels, and physical inventory operators are able to manage physical holdings search labels by default, without affecting title search labels.
This update is particularly beneficial for physical inventory operators, who primarily use the physical holdings search and need to efficiently manage physical inventory. Libraries that wish to modify which roles can add and manage labels for title searches or the physical holdings search can contact Ex Libris support for assistance.
For more information, see Repository Search Labels.
XSL Normalization Process for Metadata Records
XSL normalization of metadata records is now supported, enabling both manual and batch processing. Institutions can use XSL to manipulate metadata across all MARC-supported formats, enabling advanced data normalization through complex logic.
Key updates:
-
The new enable_xsl_normalization_rules parameter is set to false by default for all customers, except for DC/MODS customers who have already defined XSL normalization rules, for whom it is set to true.
-
A new privilege, Normalization Rules Enabled, has been added to all cataloger roles. Institutions can control which users can create normalization rules (DROOLS or XSL) and disable this privilege for selected roles if needed.
Customers who enable XSL normalization rules acknowledge that XSL is a programming language used to manipulate data and accept the associated risks.
For more information, see:
- Privileges for Roles in Alma
- Configuring Other Settings (Resource Management)
- Blog post: Alma XSL Normalization Rule Examples
Persistent Sorting Routine for Physical Items List

When users select a sort method different from the default, their choice will now be saved. The selected sorting will persist the next time they view a physical items list, providing a more consistent experience.
For more information, see Configuring Physical Item Sort Routines.
Flexibility in the Definition of Community Zone Updates Behaviour for New and Deleted Portfolios

Alma now enables a more precise configuration of how updates from the Community Zone affect collections. For collections activated from the Community Zone, two distinct settings are now available to manage new and deleted portfolios:
- Activate new portfolios associated with the service automatically: Before the current release, this setting controlled both the automatic activation of new portfolios and the automatic removal of portfolios deleted from the Community Zone. Now, this setting controls only whether new portfolios added to the Community Zone are automatically activated.
- Automatically delete portfolios removed from the service: This new setting determines how to handle portfolios deleted from the Community Zone. If set to "Yes," the portfolio will be deleted from the Institution Zone, as well as the Community Zone; if set to "No," the portfolio will be unlinked and deactivated.
For existing activated services, the newly added auto-delete setting will automatically inherit the value of the auto-active setting, ensuring that current behavior remains unchanged. (i.e. an existing service that had 'Activate new portfolios associated with the service automatically' set to 'Yes' will now have 'Automatically delete portfolios removed from the service' set to 'Yes' as well, and vice versa. Each of the settings can be modified at any time using the Service Editor, the Change E-Collection Information job, the API, or the E-Collection Quick Update application.
As always, all Community Zone updates are recorded in the Community Zone Updates Task List.
For more information, see:
- Working with the Community Zone Updates Task List
- Activating an Electronic Collection Using the Activation Wizard
Adding Titles from Network Zone to Institution Zone Collections

You can now add titles from the Network Zone to Collections in your Institution Zone. There are two ways that you can do this:
- When adding a title from the Network Zone from the Collection Resource Editor (Resources > Manage Collections > Edit a Collection > Title List > Add Title). Select the titles you want to add and select Select.
Collection Search in Network Zone
- From the search results list when searching for titles in the Network Zone. A new Add to Collection option is now available:
Add to Collection
Select this option and then select a collection to which you want to add the title.
With either method, the Network Zone title is linked to the Institution Zone in order to be added to the collection.
Improvements to Ordering from Network Zone

Improvements were implemented to the process for ordering titles from the Network Zone (NZ):
-
When ordering in Primo from the Network Zone (NZ), the purchase requests created in the Institution Zone (IZ) are now linked to the bibliographic record in the Network. Alma first checks for a local MMS ID linked to the bibliographic record in the Network. If such a record exists, Alma uses it for the purchase request. If it doesn't exist, Alma creates one and uses it.
-
When importing with profiles of type New Order that are defined as Use Network Zone, it is now possible to match against the NZ records and create a linked record in the IZ, for which the order will be linked. To implement this, the Use NZ Record option should be used for "Upon match" in the Match Actions section:
Existing profiles with the following definitions need to be edited so that the correct Upon match option will be saved:
-
Use Network Zone = Yes
-
In the Match Profile tab, Use Existing Record is selected as a value for the Upon Match field.
For more information, see Managing Import Profiles and Working with Purchase Requests.
General Electronic Services in the Consortia Central Configuration Dashboard

It is now possible for the Network Zone operator from the Central Configuration Dashboard to manage General Electronic Services configurations at the institution level.
This feature improves cooperation by enabling centralized management of General Electronic Services configurations (General Electronic Services, General Electronic Services Order, General Electronic Services Bib Fields Enrichment) at the Network Zone level.
This new feature is only relevant to Consortia with a Network Zone setup.
For more information, see Discovery Interface Display Logic in Dashboard Sections and Configurations.
Network Zone Distribution Notifications to Institution Zone Administrators

Configuration updates distributed from the Consortia Central Configuration Dashboard at the Network level now trigger an email to the relevant administrator at the Member level.
This feature improves communication and enhances collaboration across the network.
This is only relevant to Consortia institutions with a Network Zone setup.
For more information, see Consortia Central Configuration Dashboard.
Redirect Old Menu Links to New Central Configuration Dashboard

Network Zone operators can now access the New Central Configuration Dashboard directly from the Alma Configuration search when no results are found. A link appears, enabling quick access to the Dashboard to find the configuration.
This enhancement improves access to configurations at the Network Zone level.
This feature is only applicable to consortia with a Network Zone setup.
For more information, see Accessing the Consortia Central Configuration Dashboard.
Request Release of a Configuration Managed by the Network

Institution Zone administrators (at the Member level) can now request to release configurations managed by their Collaborative Network’s Central Office, allowing them to customize these configurations locally. This enhancement increases flexibility by allowing Institution Zone administrators to regain control over customizing configurations initially managed by the Central Office.
This feature applies only to consortia with a Network Zone setup.
For more information, see Request Release of a Configuration Managed by the Network.
Removal of Gender Information
As part of our GDPR compliance efforts and in order to improve the protection of private information on the Alma database, all gender information will be removed from the user records in Alma in the upcoming August release. Since gender is not essential for product functionality, retaining it poses unnecessary compliance risks according to GDPR requirements that personal data be collected and processed only when there is a clear legal basis and business need.
The deletion will not be reversible. From that point on, it will no longer be possible to input or retrieve gender information to the user record using any of the standard interfaces that concurrently update this record.
Digital Adoption Policy Update
As announced in the November 2023 release, Ex Libris began deploying Pendo, a new digital adoption tool, across Alma and other Library Open Platform back-office suite components.
Pendo is a digital adoption tool that allows customers to benefit from functionalities such as online guides and "what's new” notifications. It is also used by SAAS (Software as a Service) software companies to identify usage trends and behavioural analytics to help improve the user experience.
After further review and due to the extensive measures we are taking to anonymize the usage data and ensure full compliance with our privacy polices, in which no personal data is collected (see Privacy center | Clarivate), we will activate Digital Adoption for institutions subject to GDPR, that were inactive up until now.
There will be no other changes for all other institutions. We will continue to comply with their country and institutional policies.
For more information, visit Configuring Digital Adoption.
Search for Dates Within Specific Range of Days

Date-related search indexes in the Users advanced search, such as Purge Date, Last Activity Date, Expiration Date, etc., now include the following options to search within a moving range of days:
-
Is Within the Last (days)
-
Is Older Than (days)
-
Is Within the Next (days)
This enables customers to create dynamic "moving-window" sets (for example a logical set of users that expired in the last 30 days).
For more information, see Searching in Alma.
Security Improvements for Multi-Factor Authentication (MFA)
It was already possible to configure Alma to recommend (or enforce) an additional identification method (MFA). In addition to the regular username and password screen, users receive an email with a link that they need to select in order to log in.
The MFA security has now been enhanced as follows:
-
The email link's expiry is now 10 minutes (previously it was 60 minutes).
-
The link is usable only in the same browser where the login flow started from.
Configurable Session Timeout

All Ex Libris platform products now include a configurable session timeout feature in response to community feedback from the Idea Exchange. Institutions can now set a default session timeout duration ranging from 15 to 150 minutes (default remains 60 minutes) from the new "Session Timeout" configuration page (Configuration > General > General Configuration > Session Timeout). This page is accessible to General System Administrators.
In addition, institutions can choose whether to allow individual users to override this default setting by selecting the Allow users to override the default session timeout checkbox. The user-level options also range from 15 to 150 minutes.
This functionality enhances flexibility while maintaining compatibility with security standards and infrastructure capabilities.
For more information, see Session Timeout Configuration.
Login Hint for OpenID Connect
Institutions using OpenID Connect can now configure a login hint for single sign-on. This streamlines the user login experience by reducing the number of steps required for authentication. This option is disabled by default, and can be configured at Configuration > General > Integration Profiles > Add profile > Integration Type = OpenID Connect.
For more information, see OpenID Connect.
Apply Login Restrictions to All Users
Alma users' login can be restricted by IP Range. To override these restrictions for a particular user, it is possible to select Disable all login restrictions when editing the user. Until now, users with the General System Administrator role were not restricted by the IP Range restriction.
Now, clicking on the new Apply restrictions for all users checkbox in the Login Restriction Configuration page (Alma Configuration > General > Security > Login Restriction Configuration) limits users with the General System Administrator role. This provides enhanced security through more precise user access management.
In addition, selecting the Apply restrictions for all users checkbox cancels the user-level override.
The previous configuration is not removed and will return once the checkbox is unchecked.
For more information, see Security.
Upgrade Alma Cloud App SDK for Node and Angular
Cloud App developers can now upgrade the Alma Cloud App SDK to support the latest versions of Node and Angular. This enhances the security of the Cloud App.
This upgrade is not mandatory. You may continue maintaining Cloud Apps developed before 2025 without upgrading.
For more information, including instructions for upgrading your Cloud Apps, see Upgrade of the SDK to v2.0.
Support Basic Authentication in NCIP P2P
Alma now supports basic authentication when NCIP P2P messages are received. This improves security by enabling the user to protect the NCIP communication with an authentication header.
For more information, see Resource Sharing Partners.
New Bibliographic Records Distribution by LC and Dewey Classifications Canvas
The New Bibliographic Records Distribution by LC and Dewey Classifications canvas is now available. It was combined with the existing Bibliographic Records Distribution by Language and Publication Year canvas under the new Bibliographic Records Distribution workbook. The new canvas shows the most prominent Library of Congress (LC) and Dewey classifications in the catalog, highlighting the distribution of different areas of knowledge across the collection. You can filter and analyze the data to evaluate how well your holdings support various fields of study and research interests to aid in strategic planning for a well-balanced and impactful collection.
Additional Holdings Local Parameters Now Available
You can now define up to 30 Holdings Local Parameter fields (Physical Items > Holdings Details), an increase from the previous limit of 10.
For more information, see Holdings Details.
Additional Page Range Fields for Book Extracts, Part 1


The requested pages are added to the Alma Citation details Note/Leganto full details Library services section.
The option to request up to 10 page ranges will be added to the citation metadata per type form, add item form, the notes on the citation brief and full display in a future release.
For more information, see Submitting Digitization/Copyright Clearance Requests to the Library.
Alma New UX Developments
New Manage Patron Services UX - Opt Out

If you’re experiencing an issue preventing you from working in the new UX, please open a support case and add “Circulation new UX opt-out” or “Search new UX opt-out” to the case title so that it will be communicated to the Alma product team.
Sound Alerts in New Manage Patron Services UX


Updates to the Holdings Search User Experience
-
Search results table view
-
Search configuration - both at the institution level and the personal user level
-
Performing more actions directly from the search results, including:
-
Running jobs on selected holdings
-
Adding and updating itemized holdings sets
-
A new items section enabling users to perform actions on items directly from the holdings search. Users who want to retain access to the old items list section can enable it through the configuration settings.
-
A smart link for items provides configurable, one-click access to the items section, the holdings' items list, or an items search by holdings ID.
-
Suppressing the holdings record.
-
-
An enhanced details pane, including the Quick-access component and renaming of the sections for a more intuitive user experience.
-
Exclude facets
-
Search labels
-
Viewing cataloger notes for the holdings record
New Titles Search UX - Opt Out

Viewing Cataloger Notes in the Title Searches
Repository Search Labels

Enhanced Names and Subjects Navigation Options in the Title Search
February 2025 Metadata ManagementURM-230138
This feature requires re-indexing and will therefore be fully operational in sandbox environments for new, updated and re-indexed records only, or following the sandbox refresh or re-indexing.
The linked open data & navigation sections of the new search UX, based on the bibliographic headings of the record, enable for easy access and navigation, both to external Linked Open Data resources such as Wikidata, and to internal searches of the linked authority/bib headings information in the library's catalog.
It is now also possible to navigate to a broader catalog search, searching the normalized value from the bibliographic record in the "Names" and "Subjects" title search indexes.
As part of this enhancement, the "Contributors" section was renamed to "Names" section, following feedback from the community - to make its content and use more intuitive.
This new search option is most helpful when a search by a bibliographic heading information may be too limiting, such as bibliographic headings that aren't linked to authorities, or consortia members where a bibliographic heading information is maintained in the network and will not retrieve local results.
For more information, see Enhanced Navigation and Linked Open Data Sections.
Searching and Faceting Bibliographic Records with Purchase Order Lines
February 2025 Metadata ManagementURM-229291
When working in the new titles search, it is now possible to search for bibliographic records with or without purchase orders and use the "Has orders" facet to filter search results. Setting the facet "Has orders=Yes" retrieves only bibliographic records with a Purchase Order Line (POL) linked to them.
-
Relinking a POL to another bibliographic record impacts which records are retrieved.
-
For a consortia that places orders in the network institution, it will be possible to search in the network scope for network records that have an order, and a new “Network Orders” icon (
) was added in the network scope to reflect this.
For more information, see: Searching in Alma.
Enhanced Navigation Options from Title Search Results
February 2025 Metadata ManagementURM-233008
In the new Title Search UX, single-click links are added for more related entities, including courses, licenses, reminders and related records, alongside the existing orders and requests links.
Users can customize their view and hide these links if they are not needed in their workflow by using the configuration cogwheel ().
Additionally, the display of these links in the details pane now match the layout of the orders and requests links, ensuring a more intuitive and consistent user experience.
This enhancement enables users to quickly identify and access related entities like courses, licenses, reminders and related records directly from the search results.
For more information, see Using Navigation Links.
Advanced Physical Title Search by Permanent Call Number
February 2025 Metadata ManagementURM-236962
Previously, performing an advanced search for physical titles using a permanent call number required specifying the call number type. Now, it’s possible to search by permanent call number without specifying the type, except when searching by a call number range.
This enhancement is especially useful for libraries that want to combine permanent call number searches with other search conditions.
For more information, see Searching in Alma > Searching for an Exact Phrase.
Choose Which Citation Tags to Copy on Rollover (Bulk Rollover Only)

When the On rollover copy citation tags checkbox is checked, and Select tags is selected from the Course Loader Actions (Configuration > Leganto > LTI > Integration Profiles), tags to include can be selected from the dropdown list. When the job runs, only the selected tags are copied to the duplicated list.
For more information, see Configuring Course Loading.
Access Digitized Content Without Authentication
February 2025 Fulfillment and Resource Sharing URM-XXXXXX
Libraries can now include a link in the Document Delivery Notification Letter email that does not require authentication. This enables patrons to access digital requests that are not subject to copyright restrictions, without first authenticating.
When the parameter rs_no_authentication_document_delivery (Configuration > Fulfillment > General > Other Settings) is set to true (default false), and the label without_authentication (Configuration > General > Letters > Letters Configuration > Document Delivery Notification Letter) is enabled, the Without authentication link is included in the Document Delivery Notification Letter and does not require user authentication when opening the link.

Option to Share Operator Name Across the Fulfillment Network

Institutions in a Fulfillment Network can now opt-in to share the name of their operators who have put items of another institution in transit. This improves transparency, and enables owning institutions more clarity on who at their partner institution is the last person to have handled items they own.
This option is turned off by default.
The operator name displays in the following locations:
-
Resource Request Monitoring
-
General tab of the Physical Item Editor (right hand information pane)
-
History tab of the Physical Item Editor (for Item changes and Fulfillment activities)
-
Loan history (Loan Audit Trail)
For more information, see Configuring Other Settings.
Marking In-process Items as Missing
CERV Enhancement (ID#8918)
Users who want to change the status of items not in place to 'missing', no longer need to do so from the linked request. They can now do this directly from the items list. This enables simpler management of missing items that were previously in a library process, such as in transit from one library to another, technical migration, etc.
For more information, see Working with Items.
Prioritization of Off-site Storage Location
When fulfilling requests, Alma uses items in remote storage locations as either the first or last priority, depending on whether "Prefer Over Other Locations" was selected. It is now possible to turn off this behavior so that remote storage items will be considered like any other item for prioritization purposes. This enables libraries to improve request fulfillment logistics and supply time when their remote storage facilities are neither automatic storage nor remote off-site storage.
Libraries that currently have this parameter checked will be migrated to have the 'Prefer over other locations' value selected. Libraries that currently have this parameter unchecked will be migrated to have the 'Set as last option' value selected. Libraries that want to use the new functionality need to select the "Do not prefer over other locations" option.
See Configuring Remote Storage Facilities for more information.
Saving Selected Request Type
The request type selected on the patron request form in Alma is now saved as a preference, and is automatically selected as the default choice the next time the request form is opened. This enables skipping the step of selecting the request type when creating a patron request in Alma.
For more information, see Creating a Request from the Institution and Managing Patron Services.
Completion of Alma Integration with NACSIS-ILL
The integration of Alma with the NACSIS-ILL system to streamline NACSIS-ILL workflows with Alma Resource Sharing has been completed. All relevant borrowing and lending workflows are now fully integrated, ensuring that all necessary functionality for NACSIS-ILL operators using Alma is available. This includes creating and synchronizing NACSIS borrowing/lending requests, reflecting NACSIS status and related information on Alma requests, full support for NACSIS shipping costs, and actions based on request status, among other features.
For more information, see Integration with NACSIS-ILL.
Permanent Linked Data Enrichment Configuration for MARC Records
(Updated January 30, 2025) This feature will be released as part of the release update on February 9, 2025.
Permanent Linked Data enrichment can now be configured in addition to on-the-fly enrichment. Users can enable permanent enrichment of their MARC records through the linked data configuration. When this feature is activated for an authority in the enrichment configuration, the URI will be permanently added to the record in the designated subfield.
Impact: Institutions can now permanently embed the URI of the linked authority into their records, ensuring that this information is saved as part of the record rather than being applied temporarily.
The availability of this feature in your environment is subject to the completion of the semi-annual indexing in your Alma instance.
For more information, see Linked Data Enrichment Configuration.
Work Search Capability for BIBFRAME
To enhance user accessibility to linked instances and related works, a dedicated "Work Search" functionality is implemented. This feature allows users to search for works directly, in addition to the current capability of searching instances across all titles. Currently, users can only view work details through instances; the new feature enables direct access to works.
The implementation involves creating a "Work Search" section that replicates existing search indexes for works and, if necessary, introduces new indexes to support comprehensive search capabilities.
This functionality will be available only if BIBFRAME support is enabled. For more information, see BIBFRAME support.
For more information, see Searching in Alma > Work Search.
New Link BIB Headings Rules to Enhance Control Over Automated Linking to Authority Records

Authority control rules enable libraries to determine scenarios in which Alma automatically links bibliographic headings to authority records. When active, Alma evaluates these rules from the top and applies the first rule that meets all input parameters. To enhance control over automated linking, the following new input parameters for Link BIB Headings Rules have been added: "Subfield codes = not identical" and "Diacritics = not identical".
These enhancements enables libraries to better control automatic linking to authority records, improving the quality of authority control in their catalog.
For more information, see Linking Bibliographic Headings Rules.
Enhancements to Browse Bibliographic Headings
Previously, Browse Bib Headings displayed a single result per display value, grouping together all bibliographic headings with the same value, regardless of their linked authority records. This approach sometimes caused confusion, especially in cases where similar authority records had different source codes or when bibliographic headings varied in subfields not included in the display value. As a result, the authority record shown in the right pane might not always correspond to all grouped headings.
Now, headings are displayed more precisely to reflect the catalog's structure. When similar values are linked to multiple authority records, Browse Bib Headings displays a separate line for each authority record, accurately showing the connection between headings and their respective authority records. Bibliographic headings that are not linked to any authority record are displayed on a separate line.
As part of this enhancement, we’ve also introduced the following improvements:
- Source Code Display: When browsing (blank) source codes, the source code is now displayed in brackets, enabling librarians to easily identify the desired headings.
- Estimated Heading Count: Due to performance limitations, the exact number of bibliographic headings cannot always be displayed. Instead, we show the minimum identified number, accompanied by a plus (+) sign to indicate the actual count may be higher.
- "Open in Repository Search" Enhancement:
- When browsing (blank) source codes, repository searches will also exclude source codes, ensuring all relevant results are shown.
- The "Heading Information" advanced repository search index now aligns with Browse Bib Headings. For Browse Type = "TITLE", the "Family" drop-down has been removed, ensuring title-based searches return comprehensive results.
These enhancements make Browse Bib Headings a more effective tool for librarians, enabling them to assess their catalog more accurately, identify relationships between bibliographic headings and authority records with greater clarity, and seamlessly transition between browsing and repository searches.
FTP Configuration Supports Maximum Number of Files
The FTP configuration now supports a Max. Number of Files setting, which was previously non-functional. This feature enables users to limit the number of files processed by a job, specifically within Import Profiles. This allows better control over file imports, enabling them to set a maximum number of files to be handled during each import process. This enhancement provides greater flexibility and control over file management workflows.
For more information, see Creating/Editing an Import Profile: General Profile Information.
Automatic Upload Electronic Holdings from Sage

Sage journals and books are now supported by the Automatic Upload of Electronic Holdings feature. With this feature enabled, libraries can seamlessly update their Sage holdings. The system automatically retrieves a standardized KBART file containing holdings information from the provider’s platform and updates the corresponding collections. This integration removes the need for manual updates, reducing staff workload, saving time, and enhancing accuracy and efficiency.
For more information, see Upload Electronic Holdings from Sage.
Overlap Collection Analysis Now Takes Into Account Embargo Periods
Overlap collection analysis now takes into account embargo periods when coverage comparison is enabled ("Include date coverage in the comparison"). You can also select to calculate the embargo based on a reference year, which can assist in evaluating your future inventory.
This enhancement provides a clearer and more accurate view of the coverage overlap between titles in the compared collections.
For more information, see Working with Overlap and Collection Analysis.
Support for COUNTER R5.1 Reports
Alma now supports loading of COUNTER R5.1 reports, both manually and by SUSHI harvesting. By adhering to the updated standard, Alma ensures that usage statistics are collected consistently across various electronic resources, enabling librarians to effectively assess resource utilization and justify expenditures.
COUNTER R5.1 reports’ usage will be added to the current R5 folder in Analytics, and will be comparable with usage data in R5. This is aligned with the COUNTER guidelines (see "Are Release 5.1 reports comparable to Release 5 reports?" in the FAQs).
Harvesting COUNTER R5.1 Reports
To harvest reports in R5.1, an account of R5_1 type is needed. For background on the considerations that led to this decision, see the knowledge article.
For new publishers, add a new SUSHI account of type R5_1, and fill the relevant fields.
For existing publishers transitioning from R5 to R5.1, create a R5.1 SUSHI account based on their current R5 account, using the new Create R5.1 account. This will create a R5.1 account with the same details as the R5 account, except for the name (SUSHI Account), Vendor URL and Override URL, which you will need to enter manually.
Note that the newly created R5.1 account will start harvesting from the last R5 harvesting onwards (using the scheduled job or the Harvest Now action) to avoid data duplication.
For more details on the recommended workflow when transitioning to R5.1, see Managing COUNTER-Compliant Usage Data.
Viewing Reports in Analytics
The reports will be added to the current R5 folder in Analytics, and the data is comparable. There are some specific changes in R5.1 that may impact the Analytics reports. For details, see Usage Data (COUNTER).
Enhanced "PO Line - Claiming" Scheduled Job Report


The job report now includes a list of vendors to which claim letters were successfully sent, as well as a list of send failures. The lists include the related PO line numbers.
For more information, see Processing Claims.
Changes in Bibliographic Records Reflected Automatically in PO Lines

Alma can now automatically update linked PO lines when changes are made to bibliographic records. This improves order accuracy and eliminates the need for manual updates.
The new configuration is disabled by default. To enable it, go to Configuration Menu > Acquisitions > Other Settings and update the po_line_description_update_upon_bib_change parameter to true.
For more details see Other Settings.
Change PO Lines Types for Different Inventory and Continuity


The Update PO Lines Information - Advanced job now changes the PO line type, even when the inventory type and/or continuity are different. This can help with alignment for statistical purposes and provide a 'simple' error-fixing method in the daily work.
When selecting to change the PO line type, three additional fields will appear:
-
Handling existing inventory - The available options are: Detach from PO line/Delete.
-
Detach inventory when it can't be deleted - Appears when Delete is selected for "Handle existing inventory".
-
Assign inventory manually - Change the PO line type without automatically creating inventory.
For more details, see Manual Jobs.
Changes to Display of PO Lines
The following changes were made to the PO line display:
-
The following PO line section names were changed to align with the new Alma UI:
-
PO Line Summary was changed to Summary.
-
PO Lines Information was changed to General Information.
-
The recent selection list was added to the following PO line fields:
-
Acquisition method
-
Material type
-
Access provider
-
Vendor reference number type
-
Currency
Quick Access Links in PO Lines
Users working on PO lines can now more efficiently search the relevant fields to update by using the Quick Access module.
The Quick Access feature appears when the PO lines list operates in split view and in full page view (as opposed to list view). This module enables searching for sections, fields, and actions within the form. Users can initiate the module by using the keyboard shortcut (period '.') or by selecting the Quick Access link below the section links in the side menu area.
This provides users with a more streamlined and intuitive way of interacting with the form-focused search module.
For more information, see Quick Access Module.
Pagination in PO Line Related Inventory
Pagination was added to the following PO Line sections:
-
Ordered Items
-
Ordered Portfolios
-
Ordered Collections
By default, the pagination appears when there are more than 20 rows in the list.
In the slider, you can change the number of rows required to make the pagination appear.
Alma saves the slider value after logging out or refreshing the page.
Holdings and Representations do not have pagination as they usually don't have many items in the list.
For more information, see Manually Creating a PO Line.
Opening Hours Configuration in the Consortia Central Configuration Dashboard
February 2025 Collaborative Networks
It is now possible for the Network Zone operator from the Central Configuration Dashboard to manage standard opening hours (Calendar Management, Summary information, Contact information and IP addresses information) at the institution level and/or Library level (when appropriate).
It is also possible to distribute the calendar information from the Central Configuration Dashboard to its institution members using one of the existing distribution mode (Proposed/Imposed/Hybrid) of the Central Configuration Dashboard from Network Zone level to Institution Zone level (Members level) while keeping the current behavior:
-
Libraries inherit events and exceptions from the institution.
-
Libraries inherit institution opening hours.
This feature improves efficiency by enabling centralized management of Opening hours (e.g. Summary information, Contact information, Calendar information and IP addresses information) at the Network Zone level, as well as offering the possibility to distribute the Calendar information to its members for better cooperation.
This new feature is only relevant to Consortia with a Network Zone setup.
For more information, see Sections and Configurations Options.
Hide Configuration Links for Code and Mapping Tables in the Alma Configuration Menu at Network Zone Level

Six months after the General Availability (GA) of the new Consortia Central Configuration Dashboard, all Code and Mapping table configurations have 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 through the Central Configuration Dashboard directly.
The removed configurations from the Alma and Primo VE configuration menus at Network Zone Level are only:
- Code Tables
- Mapping Tables
For more information on related configurations, see Consortia Central Configuration Dashboard.
Accessibility Conformance Report (ACR/VPAT) Update
As part of our ongoing commitment to accessibility, an independent audit of Alma was conducted by Deque, a leading accessibility consulting firm, in 2023. Based on the audit findings, the Alma team has made significant accessibility improvements throughout late 2023 and during 2024.
We are pleased to announce the publication of the updated Accessibility Conformance Report (ACR), which provides a comprehensive overview of Alma’s compliance with WCAG 2.1 AA standards as of February 2025.
For the updated report, see Alma Accessibility Conformance Report.
For more information, see the Alma Accessibility Statement.
Thumbnails Include Images from Syndetics
The infrastructure functionality for retrieving the thumbnail images for records was enhanced. It now includes Syndetics as an external source of records cover images, in addition to the existing external source of Google Book Cover. This increases the number of records that will have thumbnail images.
For more information, see Customizing the Thumbnail Display.
Auto Completion in Statistical Category Search
When searching in Users > Statistical category in the advanced search with more than 1000 statistical categories, an auto-complete option appears, starting with the first 3 characters. This provides enhanced searching functionality for institutions with high amounts of user Statistical Categories data.
For more information, see Searching in Alma.
Multiple Saved Facets
On the Manage Sets page, multiple combinations of facets can now be saved under different names. This makes it easier to manage different sets of facets and access them as needed.
The saved facets are available in the Saved drop-down list.
Users who previously saved facets on the Manage Sets page before this change was implemented, will see those facets in the drop-down list with the name Pre-saved.
For more information, see New Layout.
Manage Sets - Export Current View
When exporting sets, there is now an option to export the current view rather than all sets.
For more information see New Layout.
Enhanced Information for Results of Bulk Actions in Sets
After running bulk actions for sets, information displays at the top of the page showing the results, including the number of successes and failures and a link to the results.
For more information, see Manage Sets and Queries.
Labels on Manage Sets Page
The Manage Sets page now supports labels, providing an improved sets management and maintenance experience. Users see the labels as badges in the list of sets.
The labels are also added to the Manage Sets facets.
For more information, see Managing Labels in Alma.
Improved UX for Updating Sets
When adding or updating sets where the content type uses the new UI, the set header and search information is now displayed in separate rows to make it easier for the user to differentiate between them.
When editing the search query, the advanced search appears as a pop up, separate from the persistent advanced search. This makes it clearer to the user that the search is in the context of sets.
The advanced search pop up also appears when adding members to an itemized set. In addition, when adding members to an itemized set, you no longer have to exit to the Manage Sets page and search for the new set. Instead, you can now immediately view the new set content by selecting the View Members button.
For more information, see Managing Search Queries and Sets.
New DV Dashboard Now Available: Bibliographic Records Distribution by Language and Publication Place
The new Bibliographic Records Distribution by Language and Publication Place dashboard is now available under the Alma > Titles > Data Visualization folder. This Diversity, Equity, and Inclusion (DEI) dashboard represents the variety of languages in which the library’s titles are available, highlighting the linguistic diversity of the collection. It also maps out the countries where these titles were published, offering a global perspective on the library’s resources. Users can filter and explore data to see how well the collection represents different cultures and regions. The dashboard includes all active titles in the library.
Resolved Known Issues for the New Manage Patron Service UI
A number of known issues in the new Manage Patron Service UI were resolved. For more information see Managing Patron Services.
New Physical Books Titles Network View Dashboard Now Available
The new out-of-the-box Physical Books Titles Network View data visualization dashboard is now available under the Alma > Consortia > Data Visualization folder. It is designed to provide the main office of a Network Zone with an overview of its single copies of physical items across the network to facilitate retention and deselection processes.
It displays information about the physical books in your consortia and contains the following tabs:
- Overview – an overview of physical book titles, which presents useful information regarding unique titles in your consortia
- Unique Titles Details – information on physical book titles that are held by only one institution in the network, which can be useful when preparing retention plans
- Limited Titles Details – information on physical book titles that are held by up to 3 institutions in the network, which can be useful when preparing retention plans
- Multiple Titles Details – information on physical book titles that are held by more than 3 institutions in the network, which can be useful for deselection processes
Additional Enhancements
- May 2025 Fulfillment and Resource Sharing URM-221991
When an intended lender cancels a request, the request is no longer considered completed. Instead, the request is now sent to the next lender on the list, and the History indicates that the previous lender rejected the request. This indication in the History includes a note that: "The lender shipped the request but then scanned it back to the library. Therefore, the lender was removed from the rota of this request." - May 2025 Metadata Management URM-235048
GND Profile Updates:- 043 is now repeatable
- Several values were added to the CV list of 670 $a
- One value of the CV list of 885 $b was altered
- May 2025 User Experience, Accessibility & Infrastructure URM-241119
On the Monitor Jobs page, for MD Import, there is no longer a limit for downloading records from the report. Previously, the export had a limit of 5,000 records. - May 2025 Analytics and Insights URM-233255
The Has Perpetual Electronic Access field (Titles > Title Details) was enhanced to include the access type of the portfolios on the title and not only the access type of the collections of the title. Knowing that permanent electronic versions are available enables libraries to optimize space and costs by removing print materials.- If the access type on the portfolio is different than the one on the collection, the one on the portfolio is indicated. For example, if the access type on the portfolio is Current and the value on the collection is Perpetual, the Has Perpetual Electronic Access field indicates no.
- If the access type on the portfolio is Current and Perpetual, the Has Perpetual Electronic Access field indicates no.
- This enhancement takes effect from your institution's next ETL.
For more information, see Title Details.
- May 2025 Analytics and Insights URM-243471
The Alma Users - Logins Per Day (Past 365 Days) out-of-the-box report is now available. It displays a table of the successful logins to Alma from your institution per day for the past year. This detailed staff login report demonstrates the Alma usage. - May 2025 Analytics and Insights URM-227752
Improved the logic for extracting the Analytics Source field from the rfr_id parameter in the Open URL. Note that this applies to data from this point onwards and not retroactively.
- April 2025 User Experience, Accessibility & Infrastructure URM-118440
The handling of character direction in the UX was enhanced for better display in left-to-right languages. - April 2025 Analytics and Insights
Idea Exchange URM-229344
The Invoice-General Note field was added to Funds Expenditure > Invoice Line. It displays the general note on the invoice line. Creating reports with this field will enhance acquisition workflows by enabling libraries to easily extract and analyze unique invoice data and improve financial tracking. For more information, see Invoice Line. - April 2025 Analytics and Insights URM-240244
The Language Description field was added to the Bibliographic Details dimension for all subject areas for which it appears. This field displays the language name of the title, based on the Language Code field on the record. For more information, see Bibliographic Details. - April 2025 Fulfillment and Resource Sharing URM-238062
Leganto provides more flexibility for matching citations to library inventory using the Resource Locate process. The Resource Locate process runs automatically as items are added to lists, manually on demand, or in bulk using a job. It is now possible to specify that a combination of the title, author, and year fields be used to identify matching resources in the library collection. The library can now configure, for example, that Leganto checks for a match using first ISBN/ISSN, and if a match is not found, check for a match using title, author, and year. The title, author, and year must match the repository record for the citation to link to the bibliographic record.To configure, enable the parameter Title_Author_Year in the Locate Citation by Fields table (Configuration > Fulfillment > Courses > Locate Citation by Fields). When the parameter resource_locate_mode (Configuration > Fulfillment > General > Other Settings) is set to OR, Leganto checks against all enabled fields in the order configured in the table.
Title_Author_Year parameterFor more information, see Match by Fields. - April 2025 Fulfillment and Resource Sharing URM-239843
When resource_locate_mode (Configuration > Fulfillment > General > Other Settings) is set to OR, the priority can now be set for the enabled Match by Fields by using the drag icon and dragging and dropping to order the fields.Drag fields
- March 2025 Analytics and Insights
Idea Exchange URM-229373
The Portfolio General Note field was added to E-Inventory > Portfolio and E-Inventory > Portfolio Details for Consortia Members > Portfolio. It lists all the General Notes of the portfolio, concatenated with the newest note first. Multiple values are separated by semicolons. For more information, see E-Inventory. - March 2025 Analytics and Insights
Idea Exchange URM-140921
The Summary Holdings Non-Public Note and Summary Holdings Public Note fields were added to Physical Items > Holdings Details. These fields display the non-public notes and public notes on the holdings found in MARC fields 866 subfield x and 866 subfield z, respectively. Multiple values are separated by semicolons. For more information, see Holdings Details.
- February 2025 Fulfillment and Resource Sharing URM-232431
The Citation System Tags field was added to the Citations folder in the following subject areas. This field displays all tags not mapped to a tag type, including tags added from the integration with the UK Digital Content Store and possibly tags added from the Leganto Questions feature.- Leganto Student Usage
- Course Reserves
- Leganto Instructor Usage Events
- Purchase Requests
- February 2025 Fulfillment and Resource Sharing URM-192949 SF: 06737730
The Year facet is now displayed in a logical order.Year facet - February 2025 Fulfillment and Resource Sharing URM-233734
Alma resource sharing is now aligned with the NACSIS ILL termination points. - February 2025 Metadata Management URM-231183
Physical Description Extent From 300$$a Available in Search Results:
When working in the new titles search UX, record customization allows adding information from MARC 21 300$$a to the displayed metadata in the search results.This feature requires re-indexing and will therefore be fully operational in sandbox environments for new, updated and re-indexed records only, or following the sandbox refresh or re-indexing.
- February 2025 User Experience, Accessibility & Infrastructure URM-231857
Various fixes and enhancements were done to improve accessibility and to comply with the standards.
- January 2025 Analytics and Insights URM-229360
The PO Approval Date and Time field was added to the following locations. It displays the date and time that the PO was approved.- E-Inventory > Portfolio PO Line
- E-Inventory > Electronic Collection PO Line
- E-Inventory > Cost Usage > Cost Usage POL
- Funds Expenditure > PO Line
- Physical Items > PO Line
- Purchase Requests > PO Line
- January 2025 Analytics and Insights URM-227062
The Event Library Unit dimension was added to the System Events subject area. It contains fields about the library in which the event occurred. Previously, it was only possible to report on the institution in which the event occurred. For more information, see Event Library Unit. - January 2025 Analytics and Insights URM-225324
The following enhancements were implemented for fields in Analytics Usage Tracking > Query Details:- The Query Type Group field was renamed to Query Type and its possible values were enhanced to include the following:
- Classic Report
- Classic Dashboard
- Data Visualization Workbook
- SOAP API Calls
- None (includes support queries such as report prompts and dashboard prompts)
Reports including the original field are not affected, unless the field was saved as a filter with one of the original values. In this case, the filter needs to be updated.
- For the Object Type field, if the analysis is not linked to an object, the value is now No object assigned instead of None.
- For the Dashboard / Workbook Path field, the values where updated to be consistent and now all begin with shared/.
- The Query Type Group field was renamed to Query Type and its possible values were enhanced to include the following:
Resolved Issues
- May 2025 Acquisitions SF: 07907294 URM-243871
Public Templates did not appear when using Amazon Order It. This was fixed. - May 2025 Acquisitions SF: 06860959 URM-237306
Icons for ordered electronic resources in PO Lines did not show the source of the resource when the PO Line was an additional one to this resource. This was fixed. - May 2025 Acquisitions SF: 07168566 URM-234985
Purged Users were displayed in Analytics. This was fixed by removing the entry of an inactive/non existing user from the PO Line interested users list. This may require a refresh of the PO Line in Alma after loading. - May 2025 Acquisitions SF: 07497136 URM-243236
There were issues with searching the ISBN, ISSN, and UPC product identifiers. This was fixed and the “Requester ID” search field is now an “Identifier” in the Receiving Department Items and Requests search filters. - May 2025 Acquisitions SF: 07193282 07728482 URM-233082
An incorrect alert was received that the item or ordered resource already exists. This was fixed. - May 2025 Acquisitions SF: 07106590 URM-226147
The 035 field was removed from new bibliographic records for Purchase Requests. This was fixed. - May 2025 Acquisitions SF: 07904101 URM-243364
An error message stating that "An error occurred while fetching items" was displayed when a POL created via API had active Interested users. This was fixed. - May 2025 Acquisitions SF: 07792295 07812205 07754608 URM-241164
The "Change currency" option to "Re-send order to vendor" had no effect. This was fixed and now the letter is only sent to vendors if the "Resent to vendor" checkbox was selected. - May 2025 Acquisitions SF: 07754218 URM-237093
Orders were sometimes created with a different vendor than the one for the purchase request. This was fixed. - May 2025 Acquisitions SF: 07876872 URM-241042
When creating an invoice from a PO, the create date incorrectly appeared in the search options. This was fixed. - May 2025 Acquisitions SF: 07157387 URM-237214
A fund could not be added to an invoice line, even though there were sufficient funds. - May 2025 Acquisitions SF: 07254760 URM-237185
Invoice lines of one-time orders had the From date and To date fields populated. This was fixed. - May 2025 Acquisitions SF: 07203911 URM-230597
Lithuanian characters in the vendor code were displayed incorrectly for PO line searches. This was fixed. - May 2025 Acquisitions SF: 07904098 URM-243175
The receive row action did not take into account the "keep in department" user preference, and the date picker did not provide a date in the past. This was fixed. - May 2025 Acquisitions SF: 07769447 URM-241128
The claim e-mail address was not used for manual claim communication with the vendor. This was fixed. - May 2025 Acquisitions SF: 07873909 URM-242665
An error message was displayed when accessing the Communications tab for a vendor, because the related PO Line was deleted. This was fixed. - May 2025 Acquisitions SF: 07832609 07786800 07099751 07872799 06874959 07845674 07695780 07786450 URM-206587
Various issues occurred when importing invoices. These were fixed. - May 2025 Acquisitions SF: 07913941 URM-243525
In some cases, users could not add multiple SUSHI connections for the same vendor with different platforms in Counter release 5.1. This was fixed. - May 2025 Analytics and Insights SF: 07877534 URM-243560
Statistical Categories were still displayed in Borrowing Requests > Requester even after being removed from user record. This was fixed. - May 2025 Analytics and Insights SF: 07889127 07858597 URM-242474
Network Zone folders were not displayed when creating analytics objects for Primo VE. This was fixed. - May 2025 Analytics and Insights SF: 07904582 07272318 07872873 URM-240590
The Num of Loans (Not In House) field (Physical Items > Loan Measures Post-Migration) did not display any values even though loans were not marked as In-House. - May 2025 Analytics and Insights SF: 07822565 URM-240147
Deleting a folder, file, or other object from the Community folder did not work properly. This was fixed. - May 2025 Analytics and Insights SF: 07892147 07842641 07805688 07898373 07883995 07752648 07852301 07873008 07903923 URM-237985
There was a discrepancy in the fulfillment data between Alma and Analytics. This was fixed. - May 2025 API SF: 07857395 URM-241680
Running jobs from Cloud Apps was limited to admin users. This was fixed. - May 2025 API SF: 07178261 URM-236988
For the Retrieve PO lines API, the results were not sorted correctly in some cases. This was fixed. - May 2025 Digital Resource Management SF: 07915379 URM-242957
The Digital Import job from CSV created the MARC 500 field even if the field did not exist in the CSV. This was fixed. - May 2025 Digital Resource Management SF: 07864485 URM-242789
The handle identifier subfield prefix cannot be changed or removed. This was fixed. - May 2025 Electronic Resource Management SF: 07841077 07845286 URM-241401
An error message appears after changing the Additional descriptive information in the Electronic Collection activation and clicking the "Next" button when the new Titles search is enabled. This was fixed. - May 2025 Electronic Resource Management SF: 07208866 URM-237760
Local extensions were deleted from the contributing institution after the contribution process to the Community Zone ran. This was fixed. - May 2025 Electronic Resource Management SF: 07260657 URM-232278
E-Resource Activation Task List was not able to be filtered by PO Line Owner when the resource was added to the PO Line after the Activation task was created. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07896989 URM-244032
In Manage patron services, the focus of the cursor did not go back to the barcode scanner after opening the user details. This was fixed in Full User Details, Quick User Management, and Manage Notes. - May 2025 Fulfillment and Resource Sharing SF: 07913347 URM-243433
Payment methods when paying a fine were not displayed in alphabetical order. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07812893 URM-242828
When paying a fine in the new UI, the amount was displayed with a period instead of a comma. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07807778 07917723 07897994 07875401 URM-242825
System notes did not include a hold shelf item if the request existed at another circulation desk within the same library. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07775894 07891515 URM-242204
When scanning in a lending resource sharing item through the new Return Items UI, an unnecessary "The item is not on loan" alert appeared. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07793661 URM-238259
When scanning a barcode on the loans or returns page, an error sometimes appeared stating that the "item barcode field is empty". This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07974612 07779259 URM-236383
In the new circulation desk UI, in a specific case, the "Place in queue X" text was truncated on small screens, hiding the number. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07941836 07901991 07777408 07827114 URM-235615
An error appeared when waiving some fines from the row actions menu. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07205575 URM-234797
In Primo -> GetIt, the Related holdings' relation type was incorrectly displayed for network members as a label code. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 06780628 URM-196532
In the Courses list, the Course Terms were not translated in non-English UIs. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07907403 URM-242699
An unexpected error occurred while registering a user in the Manage Patron Services page. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07795984 URM-241059
In some cases, the Retrieve Library Opening Hours API failed to return a response when the date range included a change to DST. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07876920 URM-243731
When loaning multiple items via RFID in the new Manage Patron Services UI, “Loan Items” was displayed but did not mention to which barcode the message refers. This was fixed. Now, the relevant barcode appears in the pop-up title. - May 2025 Fulfillment and Resource Sharing SF: 07872864 07907592 07911604 07926038 07950319 URM-242634
In some cases, the Loan Receipt Letter was sent to the wrong patron after loaning items in the New Circulation Desk UI. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07885993 07972776 07861448 07811899 07861490 07903205 07929866 URM-241701
A pop-up message for items in a temporary location did not appear when scanning in/returning items that were in a temporary location. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07833615 URM-238519
The alert for an adjusted loan due date gave the incorrect reason. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07792205 URM-238090
An unnecessary loan block pop-up appeared when creating a new item from the Manage Patron Services loan page. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07242912 URM-232364
The option to renew all loans via Primo VE was blocked when a user was in the Expiration Alert Period. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07778847 URM-238055
A booking request was not assigned to the library and circulation desk that belonged to the selected Pickup Location. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07273626 URM-237655
When a patron added a new personal delivery address in Primo's item request form for the first time, the new address was not added to the resource request slip XML. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07063824 URM-232871
When items were received in the acquisitions department with the "Keep in Department" checkbox selected, only one of the items was correctly processed to the hold shelf when scanned in the fulfillment department. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07889721 URM-230540
The Requests list In Manage Patron Services displayed requests without a workflow step with a value of "Not Started". This was fixed, and these requests now display the workflow step as "Undefined". - May 2025 Fulfillment and Resource Sharing SF: 07758164 URM-238620
In the Ful Requests Report Letter XML, the start_time and end_time fields only contained the date, not the time. This was fixed, and now there are two elements for the time: booking_start_time and booking_end_time. - May 2025 Fulfillment and Resource Sharing SF: 07132284 URM-240224
Sending files between PSB and Production via resource sharing requests was not working. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07698904 URM-239531
An incorrect request date appeared on the On Hold Shelf letter and Ful Cancel Request letters when related to borrowing requests. This was fixed and these letters now have a new XML field that can be used (notification_data/outgoing). - May 2025 Fulfillment and Resource Sharing SF: 06869407 URM-236359
Sometimes, the exported file from the borrowing/lending task list was not identical to the view. That was fixed - May 2025 Fulfillment and Resource Sharing SF: 07486101 URM-234407
The resource "Edition" field was not displayed in the Lending Requests in Alma. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07221630 URM-232972
Institutions that kept the rejected borrowing requests active could not receive the reactivate general message from the lender. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 06947029 URM-214218
In some cases, the Due Date was set back for a lending request without a warning. This was fixed and a warning now pops up when the librarian tries to set back a due date. - May 2025 Fulfillment and Resource Sharing SF: 07812488 06583220 URM-189875
In some cases, the partners' search took a long time. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07722241 07907277 URM-244039
In Alma mobile, the call number and other data were not displayed properly because the list was loaded incorrectly. This was fixed - May 2025 Fulfillment and Resource Sharing SF: 07793366 URM-242903
In Alma mobile, the print slip was printed twice. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 06990341 URM-238744
In Alma mobile, canceling a request did not send an email notification, both on Android and iOS. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07256543 URM-235229
In Alma mobile, the pick from shelf filters were not sticky. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07770997 07722674 07733454 URM-233826
In Alma mobile, the login authentication for SAML on Android was inconsistent. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07088679 URM-235513
In some cases, an unnecessary file was placed in the institution’s SMS subdirectory as part of the “Loans - Due Date Correction after Calendar Change” job. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07207614 URM-226320
In some cases, the "Create physical work orders" job failed to communicate part of the remote storage request. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07812037 URM-238992
There was an error when a deposit was deleted in the "Approve Deposits" page. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07817225 URM-241969
Previously, the external search did not appear in the task list. This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 07804916 URM-241951
Previously, Rapido was unable to send requests to ISO SHAREit . SHAREit now has a designated profile type and configuration. - May 2025 Fulfillment and Resource Sharing SF: 07772490 URM-241206
Previously, the cancellation message was not sent when the request status was "Locate failed." This was fixed. - May 2025 Fulfillment and Resource Sharing SF: 06811967 URM-200938
Previously, adding an NZ record to a reading list generated a Locate Failed error. This was fixed. - May 2025 Metadata Management SF: 07819071 URM-241219
The report of the Change Holdings Information job showed an incorrect number of processed records. This was fixed. - May 2025 Metadata Management SF: 07875134 URM-243625
The suppress indication in the "held by" drawer in the Network scope was displayed incorrectly. This was fixed. - May 2025 Metadata Management SF: 07168518 07823211 URM-224481
Call numbers with diacritics were sorted at the end of the Browse Shelf Listing. This was fixed. A new "call_number_diacritics_sort" customer parameter was added (in the Resources > Other settings menu), to enable correct sorting of call numbers with diacritics in Browse Shelf Listing. The default value is "false". Note that the best practice for searching call numbers with diacritics in the Browse Shelf Listing is to search untill the letter with diacritics. For example, search for "2000/Wü" and not "2000/Wür". - May 2025 Metadata Management SF: 07895989 07894168 07931338 URM-243725
Selecting the institution in the Held By drawer/section caused an error when the record title included the special character #. This was fixed. - May 2025 Metadata Management SF: 07906028 07870907 URM-243259
When using the advanced search in the new UI to search for dates, for example, MMS Creation Date or Modification Date, it was not possible to type in the dates manually. This was fixed. - May 2025 Metadata Management SF: 07906269 URM-243255
In the new titles search, the ‘Display in Discovery’ action did not appear for records from the Network in a combined search. This was fixed. - May 2025 Metadata Management SF: 07897905 URM-243230
In the new titles search, when opening the list of holdings page in the sliding panel and then performing the "Associate POL" action, the sliding panel closed. This was fixed. - May 2025 Metadata Management SF: 07938052 URM-242929
In the new titles search, the Items list sliding panel closed when placing a request or work order. This was fixed. - May 2025 Metadata Management SF: 07906259 07915101 07905171 07952315 URM-242877
In the new search UI, serial items availability in temporary holding locations appeared incorrectly. This was fixed. - May 2025 Metadata Management SF: 07857738 URM-242776
In the new UI, when performing an Electronic Titles search, standalone portfolios with an interface name were also displayed as a collection name. This was fixed. - May 2025 Metadata Management SF: 07863572 URM-242744
In the new UI for titles, the “Remove” option for sets was missing from the "Actions Customization" menu. This was fixed. - May 2025 Metadata Management SF: 07913613 07866793 07844514 URM-242022
For the new titles search in table view, the items' availability was displayed in the physical availability column instead of "Null". This was fixed. - May 2025 Metadata Management SF: 07895147 URM-241901
There were wrong counters in the drawers and portfolio sections for some Community Zone records. This was fixed. - May 2025 Metadata Management SF: 07854114 07878982 URM-241359
In the new titles search, there were issues when switching between Institution, Network, and Community Zones. This was fixed and the scope toggle is now disabled in record full view. - May 2025 Metadata Management URM-241208
The General Electronic Service in Get It was built with information from a related record instead of the main bibliographic record. General electronic services are built using data from the context object. When there are related bibliographic records, the context object was sometimes created with the related record's information. As a result, the general electronic service had the related records information - for example, ISBN. This was fixed, and now General Electronic Services in Get It use the main record's data and not the related record's data. Note that as this is a sensitive area, the fix will be gradually deployed to the various Alma instances, to assure safe deployment. - May 2025 Metadata Management SF: 07831603 URM-242122
When viewing the import profiles list and selecting on one of the profile IDs, the profile was displayed in editing mode regardless of the user privileges. This was fixed and now, by selecting the profile ID, the profile is displayed in view mode for all users. - May 2025 Metadata Management SF: 07832256 URM-241129
In CNMARC, when LDR position 09 was #, the resource type was incorrectly set to "Book {Undefined}" instead of "Book {Rare - Physical}". This was fixed. - May 2025 Physical Resource Management SF: 07826182 URM-241476
In some cases, the physical item creation date was incorrect due to time zone shifts. This was fixed. - May 2025 Physical Resource Management SF: 07266078 URM-239214
In some cases (usually for customers in the Asia/Shanghai time zone), the physical item field "Due Back Date" (return date from temporary location) was indexed with an incorrect date, displayed with an incorrect date in the item history tab, and saved incorrectly to Analytics (field RETURN_FROM_TMP_LOC of the INVENTORY_ITEM table). This was fixed. To enable the fix, set the customer parameter "temp_adjust_item_dates_to_local_time_zone" to "true". If needed, run a full inventory indexing and physical item flattening. - May 2025 Physical Resource Management SF: 07752316 URM-237157
In some cases (usually for customers in the Asia/Shanghai time zone), the physical item "Inventory Date" field was indexed with an incorrect date and as a result, the item could not be retrieved by searching the correct date. This was fixed. To enable the fix, set the customer parameter "temp_adjust_item_dates_to_local_time_zone" to "true". - May 2025 Physical Resource Management SF: 07634242 URM-236162
When moving an item (which is the last item in a holdings record) to a new location, an inaccurate warning message is displayed. The message was amended as follows: This item, which is the last remaining item in this location, will be moved to another holdings record. If there is an existing holdings record with the destination location, the item will be moved to it, and the current holdings record will be deleted. Otherwise, the item will remain in the current holdings record, but its library/location will be changed to the destination. - May 2025 Physical Resource Management SF: 07228334 URM-233109
Holdings records data in Analytics: The "Public Note" (852 subfield z) and "Non Public Note" (852 subfield x) fields display only the value of the first occurrence of the subfield. This was fixed. Now all repeatable subfields are included in the field, separated by semicolons. - May 2025 Physical Resource Management SF: 07783198 URM-200508
Item deletion events were incorrectly registered in Analytics as item creation events. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07900035 URM-242888
In the new UI for managing patron services, user notes were sorted by modification date instead of creation date. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07817299 07820676 URM-243252
In the new UI for managing patron services, the payment option was available despite the “Circulation Desk Operator - Limited” role being defined for the circulation desk. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07869497 URM-241529
In the new circulation desk UI, after clicking the "Pay" button, the focus did not return to the barcode scanner. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07790110 07780751 07984248 07944849 07758408 07894205 07911263 07820676 07936840 URM-236049
In the new circulation desk UI, a payment option was available although no payment method was defined for the circulation desk. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07034991 07715707 URM-222073
In some cases, the Patron Welcome letter was sent upon updating a user even though no new patron role was created. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07813694 URM-240154
Search Indexes in Alma displayed an error in some cases. This was fixed - May 2025 User Experience, Accessibility & Infrastructure SF: 07756260 URM-235298
There was an issue with moving columns in various areas of the Alma UI. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07888059 URM-215406
The status of the DARA recommendations could not be toggled in the second page and onwards. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07864358 URM-241339
The receiving page had two buttons (Cancel and Receive), which were not translated. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07874789 URM-241336
Warnings in the Purchase Order list were not translated in some cases. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07744871 URM-234206
Exporting bib records jobs was slow in some cases. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07886888 07742840 07931806 URM-243744
In some cases, the SIS synchronize job logged an incorrect history change in user roles. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07892849 URM-242771
The "Chat with Support" and "Cloud App Operator" roles were displayed as numbers and could not be added by administrators. This was fixed. - May 2025 User Experience, Accessibility & Infrastructure SF: 07735711 07902932 URM-241706
In some cases, the patron could view the user contact card. This was fixed.
- April 2025 Acquisitions SF: 07741482 URM-234817
An error occurred when updating the fund for some orders via API. This was fixed. - April 2025 Acquisitions SF: 07714880 07497297 URM-233149
The Service Unit was not saved after adding it to the "Receiving Operator Limited" role. This was fixed. - April 2025 Acquisitions SF: 07925872 07234517 07847037 07894080 07806542 07748998 07844867 07801984 07761230 07910805 07894453 07218906 07844324 URM-232741
An error appeared if one of the recent selections of associated PO lines was deleted. This was fixed. - April 2025 Acquisitions SF: 07185417 URM-239566
Reject Purchase Requests - The approval message was updated: "You are about to reject Purchase Requests. This will attempt to delete the related bibliographic record, depending on inventory existence. Note that Purchase Requests with status Approved will not be rejected. Are you sure you want to continue?" - April 2025 Acquisitions SF: 07257272 URM-232037
For users with deferred PO lines, order line searches sometimes gave an error message. This was fixed. - April 2025 Acquisitions SF: 07118540 URM-222555
Some improvements were made in the loading of purchase requests pages. - April 2025 Acquisitions SF: 07846577 URM-240504
An error was displayed when trying to load Fund ledger lists in some specific cases. This was fixed. - April 2025 Acquisitions SF: 07213263 06411931 07876422 07181748 07862787 URM-175588
In some cases, the same EDI order was sent twice to the vendor. This was fixed. - April 2025 Acquisitions SF: 07260855 URM-232371
A SUSHI file was successfully harvested in Alma even though the updates were incorrect. This was fixed. - April 2025 Acquisitions SF: 07118557 URM-130745
Alma performed slowly in the Usage Data tab on the Vendor page. This was fixed. - April 2025 Analytics and Insights SF: 07866603 URM-240438
An analytics object could not be created for a dashboard. This was fixed. - April 2025 Digital Resource Management SF: 07848448 URM-239273
Users could not login to access a digital file from the Digital Viewer. This was fixed. - April 2025 Digital Resource Management SF: 07753403 URM-238053
The Controlled Digital Lending configuration for long-term loans displayed an option to allow downloading. This was an error as downloading is not allowed for long-term CDL. The option was changed to display "No" and be read-only. - April 2025 Digital Resource Management SF: 07761097 URM-237170
Digital representations could not be added to Network Zone records. This was fixed. - April 2025 Digital Resource Management SF: 07032933 URM-229642
The Digital Viewer did not display digital files on Apple mobile devices. This was fixed. - April 2025 Digital Resource Management SF: 06760851 URM-224532
PDF files loaded slowly or not at all in the Alma Viewer. This was fixed. - April 2025 Electronic Resource Management SF: 07811193 URM-239834
The Excel report file in Wiley upload electronic holdings job did not display a warning message in certain scenarios where the identifiers were identical in the journals integration. This was fixed. - April 2025 Electronic Resource Management SF: 07772530 URM-239188
Activation data was not updated after the ProQuest upload electronic holdings job if a PO line was attached. This was fixed and the activation date is now updated. - April 2025 Electronic Resource Management SF: 07193965 07187267 URM-232556
Purchase model values for portfolios in the Ebook Central (Ebook Central Perpetual, DDA and Subscription Titles) e-collection did not always display correctly in Analytics. This was fixed. - April 2025 Electronic Resource Management SF: 07175801 URM-227888
For some cached bib records, the Originating System ID was empty. This was fixed and the missing originating system ID was added. - April 2025 Fulfillment and Resource Sharing SF: 07805538 URM-239217
When updating the expiry date in Manage Patron Services, the Notify patron checkbox did not appear in languages other than English. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07948483 07921077 07763405 URM-237665
In the Requests Customization new UI, the Call Number label was replaced with the Item Call Number label. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07787590 07821446 URM-237526
Fine types were not displayed alphabetically when adding a fine in the new UI. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07102747 07067096 URM-226888
Upon re-logging in, the link to the "Terms of Use and Policies" form added to the Configuration Quick Links Menu was replaced with "Shipping Terms of Use." This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07761632 07808330 07887847 07863085 07759142 URM-235245
In the new UX pages in Alma, the date picker incorrectly appeared in English for certain non-English environments, and the weeks did not start from Monday. This was fixed, and the calendar is now localized according to the user's application language. - April 2025 Fulfillment and Resource Sharing SF: 07798382 URM-240404
The SMS version of the "Hold Shelf Expiry Date Update Letter" could not be edited. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 06658866 URM-197288
In the General Electronic Services settings, the URL could not be saved with the "rft.lccn" code in lowercase, which caused the link to malfunction. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07887717 07862839 07812191 07889724 07808186 07775393 07889690 07896475 07772558 07798490 URM-238073
On the loan and returns pages in the new UI, the call number did not appear if there was an item call number. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07751439 URM-234566
The new Manage Patron Service Loans Sorting by Title did not take the Icelandic alphabet into account. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07739723 07240189 URM-234812
Library-Level digitization requests could not be created via API. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07210678 07201141 URM-232361
In some cases, requests that were supposed to create a recall on the loans did not do so. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07257198 07200642 URM-231080
In some cases, the link to the Request Queue page when coming from Resource Request Monitoring led to an empty list. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07014768 URM-223110
Library-Level digitization requests could not be created via API. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 06909407 URM-217884
The Convert to Resource Sharing option appeared without checking the scope of the role. This was fixed. Now, it appears only if the scope of the role is a resource sharing library attached to the requester patron. - April 2025 Fulfillment and Resource Sharing SF: 06717456 URM-199045
The Requests search did not work after being routed from the Requests link from a Title search result. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 06760999 URM-198100
When an item was scanned to be in transit, the expected arrival time calculated according to the Transit Time rule was set to the end of the calculated day. This was fixed. Now, the expected arrival time is set to be the exact calculated time. - April 2025 Fulfillment and Resource Sharing SF: 06749576 URM-208833
When scanning in an item for a lending request, the print slip was not printed, although the Item was "Shipped physically". This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 06807126 URM-207419
In some cases, a timeout caused error messages for borrowing resource sharing. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07867797 URM-241267
In some cases, the "Enrich from Global Index" action did not work as expected. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07862823 07880930 URM-240625
Previously, the "Active Students" column in the Analytics List report did not reflect the "Active Students" column in the Alma Analytics Leganto Student Usage report. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07794498 URM-240130
The field "Citation Number of Loans" was inaccurate. This was fixed. - April 2025 Fulfillment and Resource Sharing SF: 07758658 07771318 URM-235193
The values of "Number of loans" column did not match the citation's (item) usage. This was fixed. - April 2025 Metadata Management SF: 07753168 URM-239230
The message text in the History tab of the physical item editor was incorrectly displayed. It was now updated from "There have been Holdings changes in the past 6 months" to "There have been Holdings changes". - April 2025 Metadata Management SF: 07715198 URM-237603
Change Physical Item information job: in the job parameters form, it was possible to set the "item temporary indication" to "Yes" without selecting a temporary location. This was fixed. In such a case, an error message is displayed and the job cannot be submitted. - April 2025 Metadata Management SF: 07871264 URM-241808
The "Repository Label Management" privilege was missing for the "Discovery Administrator", "View Management", "General System Administrator" and "Printout Queue Manager" roles. This was fixed. - April 2025 Metadata Management SF: 07858060 07893109 07890489 URM-243108
In the New Titles search, the Held By information was not passed on to the resource-sharing request in the new UI, resulting in AFN members being skipped. This was fixed. - April 2025 Metadata Management SF: 07921472 07840125 URM-240184
In the New titles search, the availability in the holdings section did not break the line when no spaces existed in the text. This was fixed. - April 2025 Metadata Management SF: 07811819 07878940 07944854 URM-239797
The ISBN "is empty/is not empty" search index was not working properly in the New Titles Advanced Search. This was fixed. - April 2025 Metadata Management SF: 07821545 URM-239705
In the Items List for the New Titles Search, running a job for a second time caused Alma to freeze. This was fixed. - April 2025 Metadata Management SF: 07844104 URM-240499
The link resolver did not retrieve related record services when the genre was missing from the URL, affecting OpenURL calls from Alma and PrimoVE side view records. This issue was fixed, and related services now display correctly. - April 2025 Metadata Management SF: 07689613 URM-234957
When opening a Community Zone record in the Metadata Editor there are two options for viewing related data: "View Versions" and "View Versions of Original Record". The Restore Metadata functionality was not working for "View Versions of Original Record". This was fixed. We removed the Restore Metadata button in the "View Versions of Original Record" for linked CZ records. There is no logic to support metadata restoration for linked CZ records in "View Versions of Original Record." The "View Versions" option continues to work as before, with both View and Restore Metadata buttons available. - April 2025 Metadata Management SF: 07905424 URM-242579
When external records are imported into the CZ, they are created in the "primary" CZ instance, and not copied to the "read-only" CZ instance until later. When clicking "Edit" or "Push to MDE" from the Community tab of the search results, data about the records was being retrieved from the "read-only" CZ instance, which means that certain data (such as GND cataloging level) was not found for records imported "today" (typically, in the last 6 hours or so). This led to the display of incorrect messages about the user's cataloger level, and the records being opened in the MD Editor as "read-only". This was fixed. - April 2025 Metadata Management SF: 06949700 URM-216758
After importing authorities using profile of type initial_authority, the authorities could not be found while browsing authorities and using F3. This is fixed. - April 2025 Metadata Management SF: 06965242 URM-210246
Duplicate Title Analysis job: when running the job from a Network Zone institution, the "Held By" column is now populated in the job's report also when the Network Zone record is linked to a Community Zone record and there are member records linked to the same Community Zone record (thus are considered "Held By"). This was fixed. - April 2025 Metadata Management SF: 07814221 URM-241080
AUTH linked data URIs cannot handle different types of originating system IDs. This was fixed. - April 2025 Metadata Management SF: 07712541 URM-234831
Cloud App Update: NACSIS-CAT: The Cloud App was using an incorrect separator. This was fixed. The separator between the PHYSP and PHYSI subfields in NACSIS-CAT was changed from a semicolon to a colon in the Monographs tab of the NACSIS catalog. - April 2025 Metadata Management SF: 06771617 URM-197526
Cloud App NACSIS-CAT: In the VOLG section, XISBNs from other VOLs were incorrectly mixed together, causing all XISBNs to be displayed in each VLOG action instead of displaying only the relevant XISBN for each VLOG. This issue has been fixed, and now only the appropriate XISBN is displayed for each VLOG. - April 2025 User Experience, Accessibility & Infrastructure SF: 07025876 URM-221021
In a specific case, no user was found when searching on the Manage Patron Services page for a user with a dot at the end. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07246550 07056789 07064160 URM-233787
After marking a loan as found, the Advanced Search for users with the "Fine/Fee total sum" field did not work properly. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07835334 URM-239989
In some cases in the Manage Selected menu, the list of items opened on a blank page. This was fixed - April 2025 User Experience, Accessibility & Infrastructure SF: 07816028 URM-239076
The Back to Top button arrow was not centered and was missing part of the pointer. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07799524 URM-237424
The Task Widget listed Alma and Esploro tasks in the Alma UI. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07202851 07827870 URM-234571
The Vendor Account facet in the vendor record displays numeric Alma System ID. This was corrected. Now, the vendor account description is displayed in the facet. - April 2025 User Experience, Accessibility & Infrastructure SF: 07865473 URM-241275
In some cases, jobs ran very slowly. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07923190 URM-243854
User > Identifiers tab: An unexpected error was displayed when the last remaining identifier was deleted. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07865701 URM-240172
The reset-password procedure did not work in some cases. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07821720 URM-238632
In a specific case, there was an error when trying to delete/edit addresses and phone numbers for the admin user. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07686067 07892831 URM-237973
The read-only User Administrator role did not behave as expected and could edit configuration tables. This was fixed. - April 2025 User Experience, Accessibility & Infrastructure SF: 07704359 URM-237302
The user history for the password change displayed the wrong update date in the old value column. This was fixed and the old value for the password change is now left empty. - April 2025 User Experience, Accessibility & Infrastructure SF: 07818809 07852051 URM-239502
When receiving subjects from the cataloger assistant they are validated to match LCSH subject headings. In institutions where LCSH was not the priority, the validation was done improperly resulting in no subjects being returned. This was fixed to accommodate all priorities
- March 2025 Acquisitions SF: 07762278 URM-235495
An error message occurred when updating Vendor Contact information. This was fixed. - March 2025 Acquisitions SF: 07172090 URM-225229
In some cases, invoices were very slow to load/view. This was fixed and the performance of the page was improved. - March 2025 Acquisitions SF: 07741740 URM-233943
There was an error when saving PO lines to a recent entity which caused the job to get stuck. This was fixed. Note that after the fix, the job will not get stuck but it will create bibs without titles, PO lines without titles, etc. - March 2025 Acquisitions SF: 07796244 07691088 URM-237087
Encumbered from (fund code) searches in Alma did not return the expected results. This was fixed. - March 2025 Acquisitions SF: 07170477 URM-231350
When trying to create a PO Line in Order It! and the selected Owner (Library) did not have the Default location for acquisition, an error prevented the PO Line from being created. This was fixed. - March 2025 Acquisitions SF: 07875173 07855595 07880178 URM-240545
In some cases EDI invoices could not be loaded. This was fixed. - March 2025 Analytics and Insights SF: 07794393 URM-239265
An LC classification code was not displayed in Alma Analytics and Insights. This was fixed. - March 2025 Analytics and Insights SF: 07782551 07790010 URM-238712
Several LC classification codes were not displayed in Alma Analytics and Insights. This was fixed. - March 2025 Analytics and Insights SF: 07743259 URM-235583
The Temporary Physical Location In Use field displayed values other than Yes and No. This was fixed. - March 2025 API SF: 07782296 URM-237978
APIs did not support the Delete Electronic Collection Job. This was fixed. - March 2025 Electronic Resource Management SF: 07794565 URM-238821
Contribute portfolio in Miscellaneous collection failed to display differences before the contribution. This was fixed. - March 2025 Electronic Resource Management SF: 07249694 URM-238298
Run a Job > Publishing Jobs > Remove Manual Scheduling option removes the title from the Alma collection, but is still displayed in Primo collection. This was fixed. - March 2025 Fulfillment and Resource Sharing and Resource Sharing SF: 07762005 URM-235001
The system note was not updated when the patron role was added or renewed in the new UI. This was fixed. - March 2025 Fulfillment and Resource Sharing and Resource Sharing SF: 07120561 07766601 URM-220910
Auto completion in the Users search did not work correctly where the primary ID included a slash (‘/‘) sign. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07820651 URM-241418
When loaning and returning a RS item and then returning it again at the RS library, an error occurred. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07846533 07847828 URM-239823
In some cases, the Transaction Amount did not match the amount waived in waive all in the new UI. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07596717 URM-235766
The renew_status field was not populated for the Ful Overdue And Lost Loan Notification Letter. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 06948485 URM-230096
The How to GetIt only GES cannot be added to the General Electronic Services Order page. This was fixed, and now this service is not filtered for PrimoVE customers. - March 2025 Fulfillment and Resource Sharing SF: 07209876 URM-229606
When marking a requested journal issue as missing, the confirmation message incorrectly stated that all issues would become missing. This was fixed and the confirmation message for the Mark as Missing action in the Pick from Shelf task list was changed to: ‘Note that the request may be canceled. If multiple items are attached to the holdings and match the request, they will all become ‘missing‘. Do you want to proceed?‘ - March 2025 Fulfillment and Resource Sharing SF: 06789849 07272615 URM-207668
While printing letters for users from another institution, the letters did not use their preferred names. This issue has been fixed, and from now on, the letters will use the preferred names for users both inside and outside the institution. - March 2025 Fulfillment and Resource Sharing SF: 06665256 URM-194847
In some cases, the Check-in action via the self-check machine responded with incorrect permanent location (AQ) and sort bin (CL) fields. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07883021 07854869 URM-240418
When the RFID system is active in Alma and the user attempts to scan a barcode in the regular way (without using the RFID), if the item doesn‘t exist in the RFID system (the item is not on the reader), the UI would get stuck in loading mode. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07816806 07765416 07883979 07796092 URM-237817
When doing Check In/Out on Alma new UI using D-Tech RFID Readers as a barcode scanner, the barcodes did not display and the action was not implemented. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07248779 URM-232752
Previously, for loans done via SIP2, no user card symbol was displayed in Item History > Fulfillment and Resource Sharing Activities > in the Borrower Id column. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07036317 URM-229165
Previously, when an item with a Personal Delivery Request was scanned, it was loaned to the patron and a Loan receipt letter was sent. The letter did not include the personal delivery address. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07221190 07495031 URM-227258
An error occurred when attempting to return an item with the process type Lost and Paid, that was on loan to a user who had been deleted from the system. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 06631568 URM-189316
When a loan was marked as recalled, and the recall was removed so the original due date was reinstated, the Automatic Renewal did not renew the loan. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07136756 URM-232420
If two circulation desks with reading rooms and hold shelves were defined, the booking request was sometimes routed to the incorrect hold shelf. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07259863 URM-232762
In some cases, the skip location option was not available for Booking requests. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07681838 07803951 URM-232477
The Back to back booking policy did not prevent overlapping booking requests for the same user. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07688144 URM-235566
The Distribute job did not copy the externalProfileAlma field. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07100344 URM-229781
Prior to the fix, the user could create a borrowing request without a preferred pickup location. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07082943 URM-229709
When creating a digitization request for a physical lending request, after scanning in the barcode and attaching files, the request‘s status was changed to Shipped digitally but the Sent date was not registered in the request‘s history. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07729341 07802994 URM-233700
The KERIS Update Item Arrival Status API does not always accept ‘received‘ messages made for borrowing requests from the KERIS WILL LOAN and KERIS WILL EDDS resource sharing partners. When Alma received a response indicating that the KERIS system did not accept the ‘received‘ response, it presented an error message, even though the borrowing request was successfully received in Alma. This was fixed. - March 2025 Fulfillment and Resource Sharing SF: 07820651 URM-241418
In some cases an error occurred when returning a resource sharing item to the resource sharing library. This was fixed. - March 2025 Metadata Management SF: 07750480 URM-237597
Repository search: Complex searches involving ranges, e.g. (call No 1 >= X AND call No 1 <= Y) OR (call No 2 >= W AND call No 2 <= Z), did not retrieve any results in some cases. This was fixed. - March 2025 Metadata Management SF: 07789783 URM-237844
Logical sets had inconsistent behavior between Run Query and Set Query. This was fixed and the functionality is now similar to the content button. - March 2025 Metadata Management SF: 07699442 URM-232958
In some scenarios of contribution to the network, the member‘s bibliographic headings were not linked correctly. This was fixed. - March 2025 Metadata Management SF: 07168518 07823211 URM-224481
Updated: February 23, 2025 - The Browse Shelf Listing for call numbers that contained special characters (such as umlaut) were not sorted properly. This was fixed. A new customer parameter was added: call_number_diacritics_sort - (under Resources > Other settings menu), to enable correct sorting of call numbers with diacritics in Browse Shelf Listing. The default value is ‘false‘.
Note: To activate the call_number_diacritics_sort customer parameter, contact Ex Libris support. - March 2025 Metadata Management SF: 07850581 URM-239914
In some cases, the display of the holding and items drawers and sections for title searches was broken. This was fixed. - March 2025 Metadata Management SF: 07798609 07868698 07862077 07848473 URM-239004
In the new titles search, course information was missing for users without the COURSE RESERVES privilege. This was fixed. - March 2025 Metadata Management SF: 07798573 URM-238876
In the new titles search, when searching in the Network Zone tab, if the expand selection option was Held by, the held by drawers were not opened. This was fixed. - March 2025 Metadata Management SF: 07763428 URM-238607
In some cases for the new Titles search, the linked data info card did not appear in the summary section of Network Zone titles. This was fixed. - March 2025 Metadata Management SF: 07066606 URM-226589
When a record had a suppressed holding without items, the Display Logic Rules considered it as having a General Hold/Digitization request, which led to mistakenly hiding other services. This was fixed. - March 2025 Metadata Management SF: 07844104 07841742 URM-240343
New titles search: When clicking View It, the call is missing genre=journal for journal records and related records are not retrieved. This was fixed. - March 2025 Metadata Management SF: 07810312 07806125 URM-239167
Electronic title View It with multiple services configured with HAN proxy failed to get services. This was fixed. - March 2025 Metadata Management SF: 07238767 URM-231506
An internal error in the Link a set of records to the Network Zone job failed the job without a clear error message. This has been resolved. The error is now correctly handled and prevented from occurring. - March 2025 Metadata Management SF: 07205245 URM-227566
In the Metadata Editor, a Page Unresponsive error occurred when cataloging a field linked to a Controlled Vocabulary with many values. This issue has been resolved, and now results are retrieved immediately, displaying no more than the first 100 entries, which are updated dynamically as characters are typed. - March 2025 Metadata Management SF: 07155394 URM-223197
Customers have reported experiencing slowness when saving local extensions in Community Zone records, especially when the local server and the Community Zone instance are geographically distant. This delay is primarily due to network traffic factors. This was fixed by improving performance in such cases by eliminating a redundant API call when only local extensions are modified, not the core Community Zone fields. - March 2025 Metadata Management SF: 06985409 06507616 URM-212024
Identifying Brief Level job was not updating Community Zone cache records. This is fixed. - March 2025 Metadata Management SF: 07809803 URM-237992
Preferred Term Correction Job was duplicating $$0 subfield. This is fixed. The system now checks for the existence of a 0 subfield with the same content before adding a new one, preventing duplicates. - March 2025 Metadata Management SF: 07017153 URM-218116
MD Import: When selecting Unlink record from Community Zone and create a local record, subfield 9 of local fields is deleted. This was fixed by adding a new customer parameter: import_unlink_cz_remove_subfield_9_from_local_fields with default ‘true‘, under the Resources > Other settings. When the customer parameter is set to ‘false‘ subfield 9 of local fields is not deleted. - March 2025 Metadata Management SF: 07795880 URM-238988
When importing a NACSIS record to Alma, the title parsing did not stop looking for a remainder of title after the statement of responsibility was found. This was fixed. - March 2025 Metadata Management SF: 07079442 URM-237998
SBN Bibliographic alignment: In some cases, merge records were not handled although both preferred and non-preferred records exist in Alma. This was fixed. - March 2025 Metadata Management SF: 07712541 URM-234831
Cloud App Update: NACSIS-CAT: The separator between the PHYSP and PHYSI subfields in NACSIS-CAT has been changed from a semicolon to a colon in the Monographs tab of the NACSIS catalog. - March 2025 Metadata Management SF: 07692777 URM-233372
When importing a NACSIS bibliographic record to Alma, a ‘parallel title‘ included in the NACSIS title field was not parsed correctly, and not copied to field MARC 246. This was fixed. - March 2025 Metadata Management SF: 07498375 URM-232241
When $v (sequence number) was updated in the bibliographic record (4XX fields) but no other change was made to the linked authorites, the contribution to SBN did not recognize that there was a change to be processed. This was fixed. - March 2025 Metadata Management SF: 07238094 06973666 URM-213847
When contributing a uniform title record authority record to SBN, the linked authority records in the 7XX fields did not include the relator code data from subfield 4. This was fixed. - March 2025 Metadata Management SF: 06829642 06829646 URM-207236
In the NACSIS-CAT Cloud application, the Creating Institution field in the Names tab previously did not display as a hyperlink. The same issue was also observed in the Uniform Titles tab. The issue has now been resolved, and the ‘Creating Institution‘ field correctly appears as a clickable link in both tabs. - March 2025 Metadata Management SF: 06771617 URM-197526
Cloud App NACSIS-CAT: In the VOLG section, XISBNs from other VOLs were incorrectly mixed together, causing all XISBNs to be displayed in each VLOG action instead of showing only the relevant XISBN for each VLOG. This issue has been fixed, and now only the appropriate XISBN is displayed for each VLOG. - March 2025 Physical Resource Management SF: 07740034 07790453 URM-236252
The Export Bibliographical records job completed with errors but the file of failed records was empty. This was fixed. - March 2025 Physical Resource Management SF: 07486796 URM-233634
Physical Material Type Descriptions table could not be sorted properly. This was fixed. - March 2025 Physical Resource Management SF: 07716525 07241203 URM-233131
In the Item Creator by Excel cloud app, there were two issues:
1. Creating more than one item in an empty holding was creating only one and failing on all other items.
2. All information on holding (all temp info) was not added to the item.
These two bugs are fixed. - March 2025 Physical Resource Management SF: 07686507 URM-232031
Quick Cataloging > Title > Select from a list displays an ‘Oops‘ error when the citation type is not properly defined. This has been fixed, by assigning a default value (‘book‘) to the citation type. - March 2025 Physical Resource Management SF: 07863614 07066222 07215351 07894029 URM-218619
There are cases where an item on loan is edited by user A, and while the editor is open, user B returns the item, or vice versa. In such cases, user A overrides the action of user B when the item is saved. This has been fixed by displaying a message when the item is saved, enabling the editing user (user A) to decide whether to cancel the changes done in the editor (but keep the process type change done by user B), or save the changes and update the item with the process type changes done by user B. - March 2025 User Experience, Accessibility & Infrastructure SF: 07794293 URM-237074
Using items filter shows more options and makes items disappear. This was fixed. - March 2025 User Experience, Accessibility & Infrastructure SF: 07729741 06898133 URM-233860
Primo VE: Request Pickup Location sort order is incorrect. This was fixed by changing the compaction of the categories. - March 2025 User Experience, Accessibility & Infrastructure SF: 07127113 URM-228525
Primo VE: Prevent Premium/Sandbox from being indexed by Google. This was resolved. - March 2025 User Experience, Accessibility & Infrastructure SF: 07775020 07816002 URM-238683
Alma supports accepting encrypted files in FTP-based integrations, but the public key did not have an expiration date. This was fixed, and now, if desired for additional security, it is possible to configure an expiration time in General > Other Settings > pgp_key_expiry_days. For example, to expire after a year, configure 365. If left blank, it does not expire. - March 2025 User Experience, Accessibility & Infrastructure SF: 07047180 07184569 URM-217001
After opening an Analytics and Insights page via SAML, it was not possible to access the Alma home page and users were directed back to the Analytics and Insights pages. This was fixed. - March 2025 User Experience, Accessibility & Infrastructure SF: 07870973 07859604 07872825 URM-241035
Letters with accents were not displayed in the Portuguese (Brazil and Portugal) interface. This was fixed. - March 2025 User Experience, Accessibility & Infrastructure SF: 07764940 URM-236209
In the Identifiers tab in User Details, when using pagination, not all identifiers were displayed. This was fixed. - March 2025 User Experience, Accessibility & Infrastructure SF: 07718106 URM-234177
When the Automatic Role Assignment rule was toggled, the date changed but the ‘updated by‘ field remained with the original creator‘s name. This was fixed. - March 2025 User Experience, Accessibility & Infrastructure SF: 07121828 URM-226889
In specific cases, the search feature in Alma for users with a Block Type of Loan differed from Analytics and Insights reports. This was fixed. - March 2025 User Experience, Accessibility & Infrastructure SF: 06926395 URM-221065
An error occurred when saving changes in the Contact People tab of the vendor record. This happened when trying to delete the last phone or email from the list and then selecting the Save button. This was fixed. - March 2025 API SF: 06525349 URM-181801
Updated: February 23, 2025 - API update call for Holdings record was not updating the 'Last Updated By' field on the Physical Item Editor page. This was fixed.
- February 2025 Acquisitions SF: 07208090 07760353 URM-229203
The "min_expected_arrival_date" and "max_expected_arrival_date" parameters were not working in the po-lines web service. This was fixed. - February 2025 Acquisitions SF: 07167317 URM-229112
In some situations, users could not search by title or date when creating an invoice from a PO. This was fixed. - February 2025 Acquisitions SF: 06659147 06678786 06395876 07709657 URM-189306
Sending claims did not work for some orders. This was fixed. - February 2025 Analytics and Insights SF: 07699916 URM-235837
The Generate Recommendations based on Analytics reports job did not work. This was fixed. - February 2025 Digital Resource Management SF: 07168769 URM-228694
The Add Digital Representation workflow did not perform DC metadata validation when creating a new digital bibliographic record. This was fixed. - February 2025 Electronic Resource Management SF: 07725840 07006742 URM-214693
Upload electronic holdings - Elsevier job frequently fails after running for hours. This was fixed by implementing ListSafeInOperator to retrieve pids when dealing with a large number of records. - February 2025 Fulfillment and Resource Sharing SF: 07216367 URM-230904
Circulation desk operators deleted by API still appeared in the operator list. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07806579 URM-238813
Return Items gave an incorrect due date for borrowing requests in the new UI. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07790780 07781800 URM-237733
There was an issue with the time display in the new UI for patron services. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07145915 URM-237070
In the copyright declarations configuration there was an option to change the organization unit. This is not needed and therefore it was removed. - February 2025 Fulfillment and Resource Sharing SF: 07763233 07780434 URM-236946
Only users with Circulation desk manager roles could access user information with a link from the manage patron services page in the new UI. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07703545 07493830 URM-233139
The Query to Patron Letter incorrectly displayed the "Type_6_header" under the To/From label. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07795695 07777404 07786448 07756541 URM-234654
The tab titles in the browser were incorrect in the new UI for Manage Patron Services. This was fixed and the updated tab titles are as follows:- Loans Tab - "Patron Services- Loans"
- Returns Tab - "Patron Services- Returns"
- Requests Tab - "Patron Services- Requests"
- Fees Tab - "Patron Services- Fines and Fees"
- Return Items - "Man age Return Items"
- February 2025 Fulfillment and Resource Sharing SF: 07495850 URM-236279
Importing a calendar Excel file for an institution with a time zone over 12+ caused the date to shift by one day. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07772704 07801289 07739599 07761618 07791750 07785974 URM-235791
In the new UI for Manage Patron Services, searching for external users generated a general error. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07805148 07801050 07801614 07813094 07803925 07801951 07806377 07797669 URM-234769
Loan/Return receipts were not printed in the new UI when using quick print. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 06729615 07033226 URM-196165
Operators were unable to create multiple requests on a title for the same patron even though the "Override Block Request" privilege was enabled. This was fixed. It is now possible to create multiple requests for the same patron by adding a different note for each request. - February 2025 Fulfillment and Resource Sharing SF: 07693594 URM-236179
There were issues with the display in the partner list with more than 1000 partners. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07246283 URM-233829
There were issues using address3 in the xsl form of the letter. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07112073 URM-231314
There were issues with the date format for newspapers in some cases. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07175788 URM-230449
When performing the "renew" action on a borrowing request, an internal note did not appear in the request's note. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07227870 URM-230446
The "issue" and "volume" metadata fields on borrowing requests were both inserted in the "volume" field on the lender side. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 06982787 URM-218659
There were issues with the Fulfillment Unit rule for resource sharing requests from Primo VE. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07700292 URM-234331
The "Default item policy" field was mandatory for NCIP partners. This was fixed to be not mandatory. - February 2025 Fulfillment and Resource Sharing SF: 07779010 07207592 URM-236305
In some cases, the manual download label was not translated correctly when downloading a file from the document delivery. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07185462 URM-225164
When adding a conditional label when editing a request, the request remained in the Created Lending Request set rather than moving to the Conditional set. This was fixed. - February 2025 Fulfillment and Resource Sharing SF: 07732397 07491957 URM-174745
Previously, when Enable Display of License Information (Configuration > Fulfillment > Discovery Interface Display Logic > Other Settings) was enabled, the Terms and Internal description were not displayed for Network Zone resources. This was fixed. - February 2025 Metadata Management SF: 07691727 URM-231581
ID based linking overrides IDs in subfield $1. This was fixed by adding subfield 1 to the list of subfields to be preserved when executing the Preferred Term Correction job, or by using F3 functionality in the MD Editor, for the specified data fields. - February 2025 Metadata Management SF: 07792256 URM-237857
General Publishing > Republish by Date Range - a discrepancy of explanations between UI and Online Help. This was fixed. The info message was updated to indicate that this option republishes the records that were processed within the selected date range, not only the records that were actually published. - February 2025 Metadata Management SF: 07713611 07016467 07713586 07745610 URM-233092
INN-Reach V.3 - The hourly item publishing job gets stuck processing only one item until the profile and sets are recreated. This happened after rejecting a lending request from Alma (which runs publishing for one item). This was fixed, so the scheduled publishing job is not affected. - February 2025 Metadata Management SF: 07090953 URM-228603
General Publishing - when the 'File name' is configured with a dot character, the published filename is created with “-new” in the wrong place. This was fixed. - February 2025 Metadata Management SF: 06989139 URM-221730
Publishing to Primo, Classification Enrichment - When MARC field 084 (Other Classification Number) has any subfield in addition to subfields $$a and $$2, the field's content is published, but no enrichment is done. This was fixed so the record is enriched with preferred and non-preferred terms. - February 2025 Metadata Management SF: 07801622 URM-239046
New Search - the results for grouped searches were inconsistent. This was fixed. - February 2025 Metadata Management SF: 07823747 07812083 URM-238841
There were issues with ranking in the new Titles Search. This was fixed. - February 2025 Metadata Management SF: 07834411 URM-238572
The new Titles Search caused issues with the testing of Primo VE normalization rules. This was fixed. - February 2025 Metadata Management SF: 07808041 URM-238508
In the new Title Search, the order of the MARC title fields on the bibliographic record section was inconsistent. This was fixed. - February 2025 Metadata Management SF: 07713217 URM-234316
Attach to an electronic collection button was not working. This was fixed. The cause of this issue was incorrect redirection when editing a portfolio from the Metadata Editor. Previously, editing redirected to the Electronic Portfolio Editor's Coverage tab, which caused issues with back URLs and led to errors. This was updated so that editing now redirects to the General Information tab of the Electronic Portfolio Editor. - February 2025 Metadata Management SF: 07238176 URM-230216
Release all records for user - does not release records. This was fixed. Now when releasing records for another user they actually get released. - February 2025 Metadata Management SF: 07228739 07154434 URM-229404
Metadata Editor: Holding record warnings displayed without any message or information on field 854. This was fixed by adding checks for fields 854 and 855 hidden fields. - February 2025 Metadata Management SF: 07205245 URM-227566
In the Metadata Editor, a 'Page Unresponsive' error occurred when cataloging a field linked to a Controlled Vocabulary with many values. This issue has been resolved, and now results are retrieved immediately, displaying no more than the first 100 entries, which are updated dynamically as characters are typed. - February 2025 Metadata Management SF: 07135223 URM-224710
Adding Undefined Subfields showed that validation did not work for all fields. The problem occurred for certain fields and only in the networkzone. This was fixed by changing the process so that Ex Libris validates all fields regardless if we are in an institution or network zone. - February 2025 Metadata Management SF: 07046299 07052527 URM-218114
When a normalization rule contains a comment (a hash sign followed by a text), the comments preceding the rule are sometimes deleted after saving. This was fixed. - February 2025 Metadata Management SF: 06680341 URM-197246
When adding a portfolio in the Metadata Editor's split view, it does not populate the right bibliographic information for the selected record. This is now fixed, so that only in the case where the left pane is the holdings record and the right pane is InventoryNavigationPresenter, is information taken from the left pane; otherwise, it is taken from the pane that is the focus. - February 2025 Metadata Management SF: 06765635 URM-195218
When the 'font_for_special_characters' customer parameter was enabled, the controlled vocabulary drop-down list in the Metadata Editor remained in the old font. This was fixed. - February 2025 Metadata Management SF: 07208631 URM-228749
An issue occurred when more than one authority names was defined. When more then one was defined, an error message appeared without any information. This was because when trying to add a prefix to vocabularies, the ID was null. This was fixed by changing the way we get the registry ID. - February 2025 Metadata Management SF: 06378761 URM-178951
When adding a local extension to a field, the extension now appears in the indication rule form. Previously, it was missing because the system fetched institution-configured fields first, followed by the general profile fields, causing the institution-configured fields to be overridden. The issue was resolved by adjusting the order in which fields are fetched. - February 2025 Metadata Management SF: 07821435 URM-237932
When there were headings not linked to any fields in the records, the PTC job failed with the flip linking active. This is fixed, and from now the PTC no longer fails. - February 2025 Metadata Management SF: 07698202 URM-232511
In a record, when a subfield to preserve ended with a dot, the Preferred Term Correction job duplicated it. This is fixed. - February 2025 Metadata Management SF: 06807651 URM-205021
The preferred term correction job did not correct headings where the only difference between the preferred and non-preferred terms was in the diacritics. This was fixed, and the headings are now correct. - February 2025 Metadata Management SF: 07226077 URM-228182
Registry Type Label in Field Configuration: Translation is complex as the registry is fetched by ID and shared across untranslated profiles in other areas (e.g., Config > Menu > Resources > Metadata Configuration). Further discussion and planning are needed to address this. - February 2025 Metadata Management SF: 06780819 06780800 URM-206278
Translation Fix for "Mandatory" Label in MARC21 Profiles: The "Mandatory" label was not translated in MARC21 profiles under metadata configuration. The following areas were fixed:- Fields List: Description and filter group columns.
- Field Configuration: Mandatory label, subfields description, field type label, and 1st and 2nd indicators.
- Registry Type Label in Field Configuration: Translation is complex as the registry is fetched by ID and shared across untranslated profiles in other areas (e.g., Config > Menu > Resources > Metadata Configuration). Further discussion and planning are needed to address this.
- Normalization and Validation Tabs: These tabs are not translated because they include user-defined data, which is currently unsupported for translation. Some default processes visible to customers are also untranslated. Translating these tabs would require further prioritization and a new story.
Further fixes depend on customer needs and discussions with the product owner.
- February 2025 Metadata Management SF: 07718661 URM-233823
The UNIMARC Bibliographic 7XX4-OTB vocabulary was not available in Italian, and five new codes were missing. This issue was resolved by adding the missing codes and ensuring the vocabulary is now fully available in Italian. - February 2025 Metadata Management SF: 07776494 URM-235950
Update From Central Catalog job - Merge fails when one of the records is a ghost record. This was fixed. - February 2025 Metadata Management SF: 07178339 URM-226026
When crosswalking NACSIS bibliographic records to MARC, the NACSIS PTBNO= field could contain multiple subseries, and each subseries could have an associated a subseries volume. This is now handled correctly. - February 2025 Metadata Management SF: 06971678 URM-212804
Alma did not add Romanized transliterations of NACSIS CJK reading values when importing NACSIS records with "variant title" fields (NACSIS field) or "formatted notes" fields (NACSIS field ). This was fixed. - February 2025 Physical Resource Management SF: 07634242 URM-236162
Item editor: When moving an item (which is the last item in a holdings record) to a new location, a warning message is displayed, stating that the holdings record will be deleted. However, if the holdings record is the only one in the bibliographic record, the holdings record is not deleted; only its library/location data is changed according to the destination. This was fixed and the warning message now includes this information. - February 2025 Physical Resource Management SF: 07212536 URM-231294
Item statuses appeared in English even if a non-English UI was being used. This was fixed and now the item statuses are translated. - February 2025 Physical Resource Management SF: 07195791 URM-225702
Slowness, lagging, and system crashing occurred when trying to retrieve a line from the "Statistical Note 1" field in the Item Editor. This was fixed by changing the statistical fields component. - February 2025 Physical Resource Management SF: 06939827 URM-211582
Physical Item Editor > History Tab: Library and location changes should be tracked in the "Holdings changes" section, as these modifications are made at the holdings level. Historically, permanent library and location changes were listed under the "Item changes" section before introducing the "Holdings changes" section. This approach sometimes caused inaccuracies, as location changes were not described at the correct level. This was fixed and to address this, location change entries were removed from the "Item changes" section and can be reviewed in the "Holdings changes" section as they used to be. However, permanent library changes remain in the "Item changes" section, and were improved. This is necessary to support cases where an item is moved between holdings records, a process that cannot be tracked in the "Holdings changes" section. - February 2025 Physical Resource Management SF: 06298133 06297781 URM-171172
Physical Item Editor > History Tab: Library and location changes are now tracked in the "Holdings changes" section, as they occur at the holdings level. Previously, such changes appeared in the "Item changes" section, leading to inaccuracies. This was fixed and now location change entries have been removed from "Item changes" and can be reviewed in "Holdings changes." However, permanent library changes remain in "Item changes" to support cases of item moves between holdings records, which cannot be tracked in "Holdings changes." - February 2025 Physical Resource Management SF: 07242991 URM-228793
The physical item condition was not translated in the physical items list. This was fixed and now the condition is translated. - February 2025 Electronic Resource Management SF: 07812085 URM-239264
Updated - February 9, 2025 - Some portfolios in the 'Elsevier ScienceDirect Journals' e-collection were unlinked from the Community and made unavailable in error. This data was fixed. - February 2025 User Experience, Accessibility & Infrastructure SF: 07084065 07083861 URM-237533
Updated - February 23, 2025 When internal users logged into Primo VE, no 'Successful login - Primo' event was generated in the Alma database. This was fixed. This also fixes an issue of a false-positive for primo login events. - February 2025 User Experience, Accessibility & Infrastructure SF: 06937296 07039267 URM-212677
In some cases, user history lines were added by the system with no actual change. This was fixed. In some cases, as a result of the resolution, a one-time creation of an unnecessary history entry may occur. - February 2025 User Experience, Accessibility & Infrastructure SF: 07718181 URM-235199
In a record where multiple headings had the same normalized or sub-normalized value, saving after selecting an authority using F3 sometimes broke the link. This was fixed. - February 2025 User Experience, Accessibility & Infrastructure SF: 07491939 URM-233188
An error occurred in some cases for saved searches after switching the UI language. This was fixed. - February 2025 User Experience, Accessibility & Infrastructure SF: 07755751 URM-234642
Help for this page in Alma did not link to the correct Portuguese page. This was fixed. - February 2025 User Experience, Accessibility & Infrastructure SF: 07062904 URM-233499
The Alma Configuration button disappeared or was hidden on iPad/Tablet devices. This was fixed. - February 2025 User Experience, Accessibility & Infrastructure SF: 07777353 07724641 URM-233598
When viewing a user role without saving it, it no longer appeared in the filtered roles list and only reappeared if the user record was saved. This was fixed.
- January 2025 Acquisitions SF: 07710086 URM-234944
PO Lines would sometimes return errors when adding funds due to an invalid fund in the Recently Used list. This was fixed. - January 2025 Acquisitions SF: 07147595 (Added - December 17, 2024)URM-223708
The issue with long holdings records, where summary holdings (866/7/8) were not created during the enhancement process using the 'MARC21 Expand Holding By 866/7/8 Task', has been resolved. The fix ensures that holdings are now enhanced as expected, with all 866/7/8 fields being generated correctly. Please note that for this fix to work, the customer parameter 'send_summary_holdings_request_to_aleph_in_chunks' must be enabled (it is set to 'false' by default). This parameter is only enabled by Ex Libris Support. - January 2025 Analytics and Insights SF: 07748750 URM-234776
The Analytics Shared with Me page did not open for a customer. This was fixed. - January 2025 Analytics and Insights SF: 07690543 URM-234523
In several cases, the Is Blocked field (Users > User Details) did not display the correct value. This was fixed. - January 2025 Analytics and Insights SF: 07023561 URM-217027
An incorrect currency symbol was displayed in the Rialto data visualization dashboards. This was fixed and the symbol was removed. - January 2025 APIs SF: 07271536 URM-230481
When sending multiple Update Open Hours API calls while the Apply Calendar Changes job (initiated from the first API update) was still running, later APIs were not processed correctly. This was fixed. In addition, the Update API response now also includes the "APPLY CALENDAR CHANGES" job ID, which can be used to verify the status of the previous job. - January 2025 APIs SF: 06732443 06767091 06814972 URM-198122
In some cases, orders that received an invoice were incorrectly marked as "waiting for an invoice". This was fixed. - January 2025 Digital Resource Management SF: 07763400 URM-235054
The "webm" extension was missing from the Extension drop-down list in the Digital File Advanced Search. It was added. - January 2025 Digital Resource Management SF: 07746273 URM-234726
The DC Import could not handle records with very long descriptions. This was fixed by truncating the records at the maximum character limit. - January 2025 Electronic Resource Management SF: 07684307 07681003 URM-234357
The Community Zone Updates Task List Extended Export produced an empty Excel file. This was fixed. The exception was handled, so the export does not fail. - January 2025 Electronic Resource Management SF: 07185047 07693390 URM-231451
Upload electronic holdings jobs (Project Muse, T&F, Ovid, Wiley) randomly failed. This was fixed and all holdings jobs execute without failure. - January 2025 Electronic Resource Management SF: 07750108 URM-234792
Collections deleted via API left orphaned sub-collections behind. This was fixed. Users can no longer delete collections with sub-collections, regardless if the sub-collection is being suppressed or not. - January 2025 Fulfillment and Resource Sharing SF: 06929261 URM-231166
When selecting “Submit Request” from the Manage Patron Services page, searching in the Network Zone scope did not work correctly. For the moment, this was fixed by disabling the search title by Network Zone scope. - January 2025 Fulfillment and Resource Sharing SF: 07241116 URM-230425
On the patron requests tab, the "Item information" section showed the "External Name" (the Primo name of the location) of a physical location. This was fixed and it now shows the internal name. - January 2025 Fulfillment and Resource Sharing SF: 06960247 URM-227696
The recalculate requests job may cancel a TRANSIT_FOR_RESHELVING request if the item that is in transit is deleted. However, the job would send a redundant notice to the operator that put the item in transit. This was fixed and the notification is no longer sent. - January 2025 Fulfillment and Resource Sharing SF: 07106533 URM-222050
The "Requests" count on the "Pick From Shelf" list was incorrect in some scenarios. This was fixed. For example, if there are 3 booking requests and 1 hold request for a title, the initial count shows 4 requests. When filtering by "Booking Requests" the count shows 3 + start/end time of the earliest booking request. When filtering by 'Patron Physical Item Request', the count shows 1. - January 2025 Fulfillment and Resource Sharing SF: 06721704 URM-201599
The Workflow Step Status facet showed the name for institution work orders and the code for library work orders. This was fixed, and now the library-level workflow step status also shows the name. - January 2025 Fulfillment and Resource Sharing SF: 07194749 URM-225401
The manual skip location did not work as expected for booking requests. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 06944947 URM-233140
In some cases, a completed pick-from-shelf request related to a lending request remained active. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 06881733 URM-230982
In some cases, when a borrowing request was completed, the related MMS and its entire hierarchy were deleted. This was fixed, and now the system runs pre-deletion validations before deleting the temporary bib record associated with a borrowing request. - January 2025 Fulfillment and Resource Sharing SF: 07123486 07216689 URM-227401
Trying to ship SLNP requests that shared the external ID with closed requests resulted in an error. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 07176920 URM-226884
Some records caused the manual locate job process to fail. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 07178516 URM-226568
For lending requests, an error occurred for the Ship item physically option. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 07704188 07139149 07716549 URM-222832
An error occurred when using the download function for a lending request. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 07050330 07042126 URM-218769
Re-adding partner records after rejecting them resulted in an error. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 06969090 07132284 URM-218623
In some cases, an institution could not open files sent from their PSB instances for digital lending requests. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 07022437 URM-215265
Sometimes, requests failed to be sent to a lender because the note sent from the borrower to the lender was too long. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 07199085 URM-234572
In some cases, the NCIP message sent to an existing borrowing request did not trigger the sending of an "On hold shelf" letter to the patron. This was fixed. - January 2025 Fulfillment and Resource Sharing SF: 06646209 07180331 URM-160884
Previously, when the View It label c.uresolver.request.ill.patron_has_duplicate_request (Configuration > Discovery > Display Configuration > Labels) was customized, the customized message was not displayed. This was fixed. - January 2025 Metadata Management SF: 07713617 URM-234529
Running an advanced search did not work correctly when "Is Empty" and "Is Not Empty" were used in the local call number fields. This was fixed. - January 2025 Metadata Management SF: 07259719 07259713 07221796 URM-230910
Running an All Titles search with Resource Type equal to “Music Component Part” did not work correctly. This was fixed. - January 2025 Metadata Management SF: 07805523 URM-237359
Exporting itemized sets to Excel sometimes failed when the new titles search UX was enabled. This was fixed. - January 2025 Metadata Management SF: 07804433 07805797 07805799 07797699 URM-237336
Electronic collections of type "Database" did not appear in the new titles search UX. This was fixed. - January 2025 Metadata Management SF: 06891329 07002225 07034433 URM-214864
In a record, selecting an authority using F3 added a duplicate subfield if this was a subfield to preserve. This was fixed. Now, if the subfield code and value are already in the field, it will no longer be added again. - January 2025 Metadata Management SF: 06850301 07027010 URM-185266
Synchronize changes from the Community Zone jobs failed frequently due to an internal error. This was fixed. - January 2025 Metadata Management SF: 06444141 06869239 06531921 07143473 URM-184524
Occasionally, import jobs that ran in a member institution and used the Network Zone repository, detected “Records duplicated in Job” incorrectly. This was fixed. - January 2025 Metadata Management SF: 07743331 URM-234739
When importing NACSIS records into Alma, the previous handling was that author names in CJK script (imported into MARC fields 100 and 700) did not have a comma between $a and $d. This was fixed. Now, per the customer's request, names will always have a comma between $a and $d, regardless of the script. - January 2025 Metadata Management SF: 07116770 URM-221255
When importing a NACSIS serial bibliographic record into Alma, the NACSIS NDLPN field was crosswalked to MARC field 024 instead of MARC field 016. This was fixed. - January 2025 Metadata Management SF: 07079201 URM-218089
Customer requested that the crosswalk of MARC field 007 to NACSIS GMD/SMD fields take into account the value in MARC field 300 subfield b (to determine, if possible, if the sound recording is analog or digital). This was added. - January 2025 User Experience, Accessibility & Infrastructure SF: 07154703 URM-226315
Previously, when the "allow_activity_on_transferred_finesfees" parameter was set to true, there were errors when waiving fines/fees in the "Transferred" status. This was fixed. - January 2025 User Experience, Accessibility & Infrastructure SF: 07145438 07015407 06567575 URM-217328
The "Update/Notify Users" job did not toggle the account type of some user accounts from "Internal" to "External". This was fixed. - January 2025 User Experience, Accessibility & Infrastructure SF: 07498158 URM-233689
The SAML metadata file contained a misleading code: "nameid-format:transient", specifically for ADFS (EntraID). This was fixed. - January 2025 User Experience, Accessibility & Infrastructure SF: 06923130 URM-204138
For widgets, the remove button still appeared even after being selected a second time. This was fixed. - January 2025 User Experience, Accessibility & Infrastructure SF: 07175611 URM-231484
The modification of a note owner placed on an account via API USERS, sometimes did not work correctly. This was fixed. - January 2025 User Experience, Accessibility & Infrastructure SF: 07086209 URM-231194
In some cases of the synchronize action, where users were loaded without a user_name, the generated user_name was not unique, which caused a failure. This was fixed. - January 2025 User Experience, Accessibility & Infrastructure SF: 07194479 URM-229262
Users could not be found when searching by Job Category. This was fixed. - January 2025 User Experience, Accessibility & Infrastructure SF: 07250614 URM-235500
For deposit forms, the mandatory Checkbox field was not working correctly when the default value was false. This was fixed.