Alma March 2026 Release Notes

Features

Enhanced Sorting for Collection Development Recommendations

March 2026 Resource ManagementURM-306163

Rialto now provides more flexible sorting options when viewing recommendations in retention and deselection projects. In addition to sorting by Title and Publication Date, you can now also arrange recommendations by:

  • Library/Location
  • Call Number

You can also apply a secondary sort to further refine the results' order. The secondary sort uses the same set of fields—Title,Publication Date,Library / Location, and Call Number—and enables additional ordering when multiple recommendations share the same primary sort value.

Primary and secondary Sort by fields.

Primary and secondary Sort by fields

These enhancements make it easier to review, compare, and organize recommendations, especially when working with large result sets that include many items from the same library or publication period.

Predictable Title Updates in Analytics

March 2026 Analytics and InsightsURM-319026

Title updates are now assigned specific run dates, ensuring libraries know when their data is refreshed. In addition, member institutions in a consortium are updated as a group, providing synchronized data across the network. A new out-of-the-box report is also available in Analytics > Access Analytics > Catalog > Shared Folders > Alma > Titles > Reports > Analytics Titles Subject Area Update. You can use this report to display a widget in your Alma home page:

  1. Copy the report to your institution folder.
  2. Create an Analytics Object in Alma pointing to this Report.
  3. Define it as a Widget.

With this update, libraries can rely on consistent update timing, allowing better planning for internal reporting schedules.

For more information, see Out-of-the-Box Reports and Title Details.

New Partner Fields Available in Borrowing and Lending Requests Subject Areas

March 2026 Analytics and InsightsURM-318683

New fields are available in Borrowing Requests (Analytics > Create Analysis > Access Analytics > Create > Analysis > Borrowing Requests (Resource Sharing) > Partner) and Lending Requests (Analytics > Create Analysis > Access Analytics > Create > Analysis > Lending Requests (Resource Sharing) > Partner) Subject Areas. They can be used for recording additional information on resource-sharing partner records. Libraries can report on partner information to evaluate their resource-sharing service, including fill rates, volume, charges, and request types, in relation to partner parameters. The new fields are:

  • Account Allowances
  • Alternate Account Number
  • Organization Type
  • Sector
  • Send Communication Allowed

For more information, see Borrowing Requests (Resource Sharing) and Lending Requests (Resource Sharing)

Additional Enhancements

  • March 2026 Fulfillment and Resource Sharing idea exchange Idea Exchange
    Leganto now enables libraries to customize the labels of workflow tags, including those used for integrations with external systems such as Bolk and DCS.

    To customize a tag, navigate to Configuration > Fulfillment > Courses > Reading List Citation System Tags, select More actions, and then choose Customize. Libraries can then update the text shown in the Description column to better reflect local terminology or workflows.

Upcoming Issues to Note

Collection Development Consent Updates to Include Item-Level Data

July 2026 Resource Management

In the August 2026 release, the Collection Development data‑sharing consent will be updated to include discoverable item‑level data.

This update follows a request from our Early Adopters group, who found that discoverable item‑level data can be valuable in specific scenarios when making collection development decisions.

This change will not affect existing opt‑in status.

Fulfillment Anonymization Job

Infrastructure enhancements were applied to the Fulfillment Anonymization Job to improve overall performance. As a temporary side effect, the job will appear twice in Admin > Monitor Jobs > Manage Jobs and Sets— one entry reflecting the actual processing activity, and a second entry showing 0 records processed.

This duplicate entry is expected and will be removed in an upcoming release.

Updated Documentation for Analytics Tables

As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of analytics field tables with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following table within the E-Inventory subject area was updated:

Resolved Issues

SF number Area Description
08099408 08290660 08294826 08294470 08327831 08329304 08319384 URM-254271 Acquisitions Previously, wildcards and special characters did not work as expected on the Receive New Material search. This was fixed.
8073250 URM-306203 Acquisitions Previously, when creating an invoice via EDI, invoices could not be created if the over expenditure limit sum was 0.0. This was fixed.
08184374 08240818 URM-319266 Acquisitions Previously, the Uploaded Counter report did not appear in Usage Data > Uploaded Files. This was fixed.
8130899 URM-319576 Acquisitions Previously, users with the roles Purchasing Operator Extended and Purchasing Manager were unable to delete POs. This was fixed. Now, if the PO line owner matches the library in the role scope, the user can delete the PO.
8250748 URM-319708 Acquisitions Previously, the service unit name was not translated on the In Process Item(Configuration > General > Work Order Types) page. This was fixed, and the service unit name is now translated.
08190147 08075310 URM-320419 Acquisitions Previously, the Replace resource action didn't remove the linking between the NZ resource and the local IZ poline. This caused the NZ resource to appear in Analytics reports. This was fixed.
8242152 URM-320576 Acquisitions Previously, there was an issue with a limitation on records in input files. This was fixed. The limitation was removed, and large files can be loaded.
8303664 URM-321845 Acquisitions Previously, creating an invoice from Excel always set the invoice line to fully invoiced and released the remaining encumbrance regardless of the encumbrance setting. This was fixed, and subscription PO lines will not be fully invoiced.
8317624 URM-322978 Acquisitions Previously, users with read-only roles were not able to view the acquisition configuration. This was fixed.
8173354 URM-318775 User Experience, Accessibility and Infrastructure Previously, bib headings created when Deposits were created with a name in field 100 could not be deleted. This was fixed.
8287782 URM-322227 User Experience, Accessibility and Infrastructure Previously, Discovery Import Job Counters were visible in the Alma job report UI, but were not exposed in the Get-Job-Instance API. This was fixed.
08283644 08321391 08292662 URM-322719 User Experience, Accessibility and Infrastructure In some cases, users were receiving notifications on expired SAML certificates in a profile that no longer exists. This was fixed.
8225498 URM-319465 Analytics and Insights Previously, when the Network Zone opened the Analytics configuration mapping table Participants in Consortial Analytics for the first time, the Updated By for every member had the login user ID, and Last Update was populated with the current date, even if the user did not change the table at all. This was fixed.
8249188 URM-322017 Analytics and Insights Previously, the Not Relevant option was missing from the Total Undergraduate Student Body Size question in the Data Sharing Profile configuration form. This was fixed.
8282310 URM-322440 Analytics and Insights Previously, several LC classification codes were not displayed in Analytics. This was fixed.
8091137 URM-313844 APIs Previously, when First Label Print Position was set to any row other than Row 1, Col 1, the application reverted to Row 1, Col 1 upon restart. Additionally, while the preview displayed the correct starting position, the actual PDF output printed from position 1, 1 instead of the configured position. This was fixed, and the First Label Print Position is now retained, and the PDF output now prints the correct position.
08228003 08245501 08264202 08283722 08267822 08275555 08317676 URM-317588 APIs Previously, when running the latest Stunnnel version v5.76, an error was generated in the Stunnel log. This was fixed.
08289255 URM-322307 APIs Previously, in the Webhook Integration Profile, the Custom Header was not sent via the GET challenge request. This was fixed.
7207614 URM-226320 Fulfillment and Resource Sharing In some cases, the Create physical work orders job failed to communicate part of the remote storage request. This was fixed.
08141225 07892060 URM-247163 Fulfillment and Resource Sharing Previously, the circulation desk names were displayed in English rather than the user's selected language on the create request form. This was fixed.
08115142 08262080 08300845 URM-314166 Fulfillment and Resource Sharing Previously,Export for Current View ignored customizations and always used the default values. This was fixed.
8153470 URM-315007 Fulfillment and Resource Sharing When a citation with copyright information was copied or duplicated to another reading list, the copyright data was lost and became editable. This was fixed so that the copyright information is retained and remains disabled for editing, just as it is on the original citation.
8148886 URM-316004 Fulfillment and Resource Sharing In some cases, when searching for linked users via API source_user_id, or via UI Find user in another institution the user was not found even though the linked account already existed in the target institution. This resulted in the creation of multiple duplicate users. This was fix. Now, when searching for a duplicated linked user, Alma returns the latest created user.
8149652 URM-316007 Fulfillment and Resource Sharing In some cases, the rota template page did not display correctly. This was fixed.
8166249 URM-316033 Fulfillment and Resource Sharing Previously, the user card was visible even when the View User Card was disabled. This was fixed, and now only users with the View User Card privilege can view user cards.
08185960 08257107 08218646 08285960 08259743 08259682 08293979 URM-316175 Fulfillment and Resource Sharing Previously, a temporary CZ outage occurred during the first attempt to retrieve information, causing a runtime exception that resulted in duplication. This was fixed.
08164867 08186496 08268070 08272106 08336416 URM-316359 Fulfillment and Resource Sharing Previously, overdue fines continued accruing even when the overdue_at_lost_loan/overdue_at_claim_return_loan(Configuration Menu > Fulfillment > General > Other Settings) parameter was set to true. This was fixed. Now, when the Found Item action is used to revert a lost/claim return item back to active status, any overdue fines that were generated are waived (based on the overdue_at_lost_loan/overdue_at_claim_return_loan parameter). Once the item is actually returned, the overdue fine policies are applied to the entire overdue period.
8105010 URM-316820 Fulfillment and Resource Sharing Previously, staff could not set a shipped item to Lost when the lending request was associated with an NCIP partner. This was fixed, and a Lost action has been added that updates the borrowing request without sending a general message, enabling staff to set the item to Lost in these cases.
8215138 URM-317673 Fulfillment and Resource Sharing Previously, when creating an AFN request, the borrowing request displayed the correct pickup location, but the fulfillment request on the lending side displayed a library from another consortia institution. This was fixed.
8223017 URM-318449 Fulfillment and Resource Sharing Previously, editing a fulfillment unit whose name contained an ampersand resulted in an error. This was fixed.
8239728 URM-318484 Fulfillment and Resource Sharing In some cases, the show file action was not working. That was fixed
08231072 08287110 URM-318715 Fulfillment and Resource Sharing Previously, when editing a physical item request, the error failed to initialize the request was generated, and the pickup location was not listed. This was fixed.
8192435 URM-319580 Fulfillment and Resource Sharing Previously, the ISO 18626 message sent from Alma to Tipasa included incomplete or truncated data in the volume and issue fields. This was fixed.
8252331 URM-320918 Fulfillment and Resource Sharing Previously, when a digital borrowing request was received as Physical non-returnable and completed upon receiving, the request's additional ID was not included in the On hold shelf letter. This was fixed, and now the field in the letter XML is populated correctly.
8234435 URM-321690 Fulfillment and Resource Sharing Previously deselecting ‘I only need a specific chapter’ did not remove chapter information from Alma borrowing request. This was fixed.
8259982 URM-322192 Fulfillment and Resource Sharing SSI: Handle historical archiving - Previously, the job Status was Completed with Errors, even though there were no failed records. This was fixed.
08317665 08316927 URM-322575 Fulfillment and Resource Sharing Previously,Recalculate Partner and Reset Rota actions did not re-add partners that were already in the rota. It was fixed.
07648627 07777627 URM-235490 Metadata Management In some cases, when Record has matches was defined as an error, authority records with matches were saved, and an error was generated. This is fixed.
8039172 URM-254190 Metadata Management When a new UNIMARC authority record containing a field 815 was contributed to SBN, the tipoAuthority (authority type) attribute for the 815 link was incorrectly set to AU (Author) instead of RE (Repertoire), causing the SBN server to reject the record. This was fixed.
08249028 08258474 URM-319113 Metadata Management Previously, the Description search index didn't work with is/is not Empty. This was fixed but requires re-indexing.
08253742 08267593 08245281 URM-321043 Metadata Management In some cases, the CV-List was not displayed for repeated subfields. This was fixed.
8257076 URM-322591 Metadata Management Previously, an incorrect info card was displayed in Primo VE when no info card was displayed in Alma. This was fixed.
8134079 URM-314656 Resource Management Previously, the Springer autoholding integration generated an incorrect local date for a portfolio in the Coverage tab.
8165862 URM-315558 Resource Management Previously, the host record did not display all related holdings and all related items from the part records. This was fixed.
8187904 URM-316947 Resource Management Previously, Collections were not deleted after the Delete Collection job was run. This was fixed.
08230180 08344487 URM-318608 Resource Management Users with the role Physical Inventory Operator or Physical Inventory Operator - Limited were unable to see the Run a Job menu and run the Change Physical Items Information job. This was fixed.
08215120 08253170 08288925 URM-318615 Resource Management Previously, when relinking a holdings record to a target bib record that had a matching holdings record, the items were moved from the source holdings record to the target matching holdings record; then, the empty source holdings record was deleted (unless it was marked as committed to retain). However, the deletion process was not completed, and the empty, partially deleted source holdings record was mistakenly attached to the target bib record. This made the source holdings record searchable and editable in the MD Editor as if it were part of the target bib record. Both of these issues were fixed.
8159175 URM-319166 Resource Management Previously, parent records were deleted when a purchase request was rejected. This was fixed.
8221498 URM-319499 Resource Management Previously, the Online service order configuration was not applied. This was fixed.
8284853 URM-321110 Resource Management Previously, when the Description in the Copyrights Statements form exceeded the character limit, an error was generated. This was fixed.
8304754 URM-322352 Resource Management Previously, when a collection was created via the API, the source and creator fields were not populated. This was fixed.