Alma December 2025 Release Notes
Features
Parent Fields for COUNTER IR and IR_A1 Reports Available in Alma and Analytics
December 2025 Analytics
Idea ExchangeURM-252231
COUNTER IR and IR_A1 reports' parent fields are now saved in Alma and displayed in Analytics. This is done for data loaded to Alma starting from the December release. The full list is stated below:
- Parent Article Version
- Parent Authors
- Parent Data Type
- Parent DOI
- Parent ISBN
- Parent Online ISSN
- Parent Print ISSN
- Parent Proprietary ID
- Parent Publication Date
- Parent Title
- Parent URI
These fields are supported for both R5 and R5.1.
If these fields are not populated in Analytics, it is recommended to first verify the incoming report from the vendor. If parent fields are not included in the report, contact the vendor and request that they be added.
For more information, see Usage Data (COUNTER).
New Electronic Resource Data Visualization - Top Used Collections Based on Alma Link Resolver Clicks
December 2025 Analytics and InsightsURM-246010
A new electronic resource data visualization,Electronic Collections Resolver Usage, is available in Analytics > Access Analytics > Catalog > Shared Folders > Alma > E-Inventory > Data Visualization. This dashboard provides insights into the most accessed electronic collections via the Alma link resolver. It is designed to help library staff monitor e-resource usage trends, spot high-profile e-collections, and support data-driven decisions for acquisitions and subscriptions.
Reject Reasons Customization Added to Analytics
December 2025 Fulfillment and Resource Sharing
CERV Enhancement (ID#1253)URM-219499
When rejecting a lending request, the Reject Request screen now includes an Internal Reject Reason dropdown list. This selection is available in analytics for libraries wanting to track and report on the application and frequency of these customized reasons.
For more information, see Lending Requests (Resource Sharing).
Additional Enhancements
No additional enhancements match your criteria.
Upcoming Issues to Note
Expiration of SAML Self-Signed Service Provider Certificate in December 2025
The current self-signed SAML service provider certificate will expire in December 2025. If your institution uses this certificate, we recommend consulting with your IT department to determine whether a replacement is needed for Alma, Primo VE, or other applications. If so, the replacement should be coordinated with your identity provider administrators. For more information, see SAML SSO ΓÇô Verify and Replace 2025 Self-Signed Certificate.
Data Dictionary E-Inventory
December 2025 Analytics and InsightsURM-315997
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, several tables within the Alma Analytics Subject Area were updated:
- Configurations (Limited) - Policy Creation Date
- Configurations (Limited) - Policy Modification Date
- Cost Usage - PO Line Creation Date
- Course Reserves - Reading List Citation Creation Date
- DARA - Creation Date
- Digital Inventory - Representation Creation Date
- Digital Inventory - Modification Creation Date
- Licenses - Licenses Creation Date
- Licenses - Licenses Modification Date
Resolved Issues
| SF number | Area | Description |
|---|---|---|
| 08095560 URM-254086 | APIs | Previously, when a bibliographic record was created via the API, and the record did not contain an 001 field, the record was created without an Originating System ID, instead of having the Originating System ID set to the MMS ID of the new record, When a bibliographic record was updated via the API, and the record did not have an Originating System ID, the Originating System ID was not set to the MMS ID. This was fixed. |
| 07178261 URM-236988 | APIs | Previously, when using the API to retrieve PO lines, the results were not sorted correctly when ordered by created_date. This was fixed. |
| 08213006 URM-316997 | APIs | Previously, NACSIS-CAT CloudApp - Supplementary Multilingual Plane characters were displayed in Unicode rather than in Kanji. This was fixed. |
| 08156559 08083929 URM-317585 | Acquisitions | [Updated: 17 December 2025] Manually uploaded COUNTER reports in formats other than JSON were not saved and therefore could not be downloaded. This was fixed. Note that this will not fix existing data - only manually loaded files from the December release and on. |
| 08182912 URM-316557 | Acquisitions | Previously, when opening a new order import profile (Resources > Manage Import Profiles > Search for YBP > Edit), and the field Default PO Line owner was empty, the message "An error occurred while loading the portfolios list for this electronic service" was mistakenly displayed. Now, the correct message is displayed. |
| 08058078 08098030 URM-252577 | Acquisitions | Previously, the owner of a POL template could not delete the template if the template was Public. This was fixed. |
| 07913344 URM-243237 | Acquisitions | Previously, there was an incorrect rounding in PO Lines created from an API when applying a discount, resulting in an inconsistency between the net price and total funds amount. This was fixed. |
| 08032753 URM-253068 | Acquisitions | Previously, it was possible to create recurring invoices from a purchase order in Accrual mode. This was fixed, and it is now only possible to create one-time POLs. |
| 07982142 URM-252761 | Acquisitions | Previously, the Duplicate fund functionality did not keep the owner field and was set to be owned by the institution. This was fixed. |
| 08139158 URM-314117 | Acquisitions | Previously, the Item description changed on several PO Lines when running the Update PO line information - Advanced job. This was fixed. Now, when running the Update PO line information - Advanced job, the item description will not change for any PO Lines. |
| 08186027 URM-316555 | Analytics and Insights | Previously, the Weeding Number column was missing in the Fulfillment Subject Area. This was fixed. |
| 08232965 08093747 08098115 08048980 07951147 08204681 08204312 URM-247512 | Fulfillment and Resource Sharing | Previously, after marking an in-process item as Missing via the Toggle Missing Status, the Requests - Recalculate after Inventory Update job toggled the item back to available. This was fixed. |
| 08130973 08127484 URM-314067 | Fulfillment and Resource Sharing | Previously, non-English Alma environments displayed the address in English in the Library Connection Details > Address list. This was fixed. |
| 08035020 URM-252851 | Fulfillment and Resource Sharing | Previously, the XML of the Ful Item Change Due Date Letter did not contain the name of the loan circulation desk. This was fixed. The name of the loan circulation desk has been added to the letter. |
| 08071299 08233051 08089360 URM-254237 | Fulfillment and Resource Sharing | Previously, in the New Titles Search, users were unable to add Network Zone titles to a reading list because the Network Zone did not display in the drop down. This was fixed. |
| 08110896 URM-314615 | Fulfillment and Resource Sharing | In some cases, when performing a Locate on ISO requests, requests were sent to libraries that did not own the resource. This was fixed. |
| 08111664 08089490 URM-254552 | Fulfillment and Resource Sharing | Previously, there was an issue with exporting an Excel spreadsheet from a table with more than a thousand partners. This was fixed. |
| 07967581 URM-253689 | Fulfillment and Resource Sharing | Previously, the document delivery letter was sent to the patron's email address instead of the alternative email address. This was fixed. |
| 08033708 URM-253464 | Fulfillment and Resource Sharing | Previously, the User Card on the Borrowing and Lending Requests'History tab was not visible. This was fixed. |
| 08012784 08214645 08109787 URM-252442 | Fulfillment and Resource Sharing | In some cases, third parties received duplicate resource sharing requests. This was fixed. |
| 08061443 08225080 URM-252408 | Fulfillment and Resource Sharing | In some cases, the barcode received from the lender included the RAPIDO prefix, and in some cases, the barcode was sent without the expected prefix. This was fixed. |
| 07998740 URM-249711 | Fulfillment and Resource Sharing | Previously, the circulation-desk dependent was used for the list of available holdings for move requests. This was fixed. |
| 07936008 URM-249065 | Fulfillment and Resource Sharing | Previously, titles with specific available items created a resource sharing request with an item description by default, even when not selected. This was fixed. |
| 08005329 URM-249046 | Fulfillment and Resource Sharing | Previously, when no changes were applied to the Institution Zone, the Partner Alternate Symbol field was not distributed from the Network Zone to the Institution Zone. This was fixed. |
| 07811049 07935519 08156556 URM-243891 | Fulfillment and Resource Sharing | In some cases, the pop-up screen that appeared when an item was returned displayed the permanent location instead of the temporary location for lending requests. This was fixed. |
| 07752528 07815313 URM-242548 | Fulfillment and Resource Sharing | In some cases, the format for resource sharing requests was marked as both physical and digital in the Primo Classic form. This was fixed. |
| 08145630 URM-315771 | Fulfillment and Resource Sharing | Previously, users could not send ISO-18626 messages using the new Renew Accepted status. This was fixed. |
| 07845927 URM-249854 | Fulfillment and Resource Sharing | In some cases, certain characters in RapidILL messages caused a failure in the creation of a lending request. This was fixed. |
| 08234779 07147767 URM-246778 | Fulfillment and Resource Sharing | In some cases, the link resolver did not identify cataloged records as articles, resulting in issues with populating the digitization request form in discovery. This was fixed. Contact Support to apply the fix. |
| 08005833 07916284 08022237 07908540 08113457 URM-243332 | Fulfillment and Resource Sharing | Previously, the Alt + R shortcut for returning items did not work for users with the Circulation Desk Operator - Limited Role. This was fixed. |
| 07207614 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. |
| 07219159 URM-232025 | Fulfillment and Resource Sharing | In some cases, the display logic rules did not hide some View It services. This was fixed. |
| 08153470 URM-315007 | Fulfillment and Resource Sharing | When a citation with copyright information was copied or duplicated to another reading list, the copyright data was being 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. |
| 06484343 05310455 05331041 05313363 05924208 05916520 05393936 05309128 06523006 08097835 URM-131338 URM-314639 URM-131338 | Metadata Management | Previously, the Contains Phrase did not consider punctuation within the search term. This was fixed. |
| 06281092 URM-172676 URM-131338 | Metadata Management | In some cases, search terms that included special characters did not return the expected results. This was fixed. |
| 08027430 URM-316473 | Metadata Management | In some cases, when the same person was cataloged in both a 100 and 700 fields in the same record, the info-card only appeared in the Names section, and not in the summary. This was fixed. |
| 08091969 URM-316356 | Metadata Management | New Title search: Previously, an inactive Delete Collection button appeared for all user roles. This was fixed. |
| 08122058 URM-314539 | Metadata Management | Previously, for Physical Titles with grouped advanced searches that included the location field, the AND/OR operator was not displayed correctly. This was fixed. |
| 08040824 URM-252409 | Metadata Management | Copy to Catalog of a descriptive record of an electronic collection: Previously, when a conversion was required from MARC21 to UNIMARC, and the electronic collection had thousands of portfolios, the Copy to Catalog action failed, and an error message was displayed. This was fixed. |
| 07945799 08098257 URM-249704 | Metadata Management | Previously, when two bib records were linked to the same Network Zone record, the bib records could not be merged. This was fixed. |
| 07878849 URM-243462 | Metadata Management | Previously, the Generate Accession Number window that appears when creating Holdings in the metadata editor was not adjusted to fit the screen size. This was fixed. |
| 07251237 URM-229005 | Metadata Management | Previously, when merging and combining, the secondary record remained in the metadata editor. This was fixed, and the secondary record is now removed. |
| 08143913 URM-314658 | Metadata Management | In some cases, the Generate Chinese author call number process assigned the same call number twice. This was fixed. |
| 07866454 URM-244896 | Metadata Management | Previously, local extension fields were disappearing when Network Zone records were opened in the metadata editor. This was fixed. |
| 08119178 URM-314298 | Metadata Management | Previously, when saving, duplicating, or previewing XSL normalization rules, error and warning messages produced by validating the XSL content were not presented to the user. This was fixed. |
| 08156446 URM-316618 | Metadata Management | In BIBFRAME2MARC transformation, for bibframe records with many admin metadata sections, the 001 field did not properly populate with the mmsId value. This has been corrected. |
| 08132303 URM-313891 | Metadata Management | Previously, when navigating through an imported list, when moving between pages, the subsequent pages displayed the same list of records as the first page. This was fixed. |
| 08174058 URM-316930 | Resource Management | In some cases, there were discrepancies between an item's modification date shown in Alma and Analytics and the one shown in the REST API output. This was fixed. |
| 08152721 08112871 08151441 URM-306081 | Resource Management | When creating a local portfolio under an e-collection, if the collection selection was changed from one collection to a different one, it could cause data corruption in the portfolio. This was fixed. |
| 07913568 URM-248677 | Resource Management | Previously, DARA recommendations, Group standalone portfolios, showed incorrect numbers on Mondays. This was fixed. |
| 07973407 URM-247484 | Resource Management | CDI groups history changed after CZ updates and added attributes with created by user and not System. This was fixed. |
| 08219628 URM-317181 | Resource Management | Mapping file label in digital import with MARC subfield $8 linking number did not work. The reported issue occurred when the file name label was extracted from a 856 subfield other than the default y subfield. This was fixed. |
| 08060848 URM-254521 | Resource Management | Image did not open after watermark was added. This was fixed. |
| 07976597 URM-247091 | Resource Management | The full list of representations opened very slowly for a title with many representations. This was fixed. |
| 07819076 URM-242887 | Resource Management | Previously, when an error occurred during the processing of an indication rule, the publishing bulk was written to the output file, even though the bulk was later reprocessed because of the error, and again written to the output file. The resulted in duplicate records in the publishing output. This was fixed. |
| 08159347 URM-316585 | User Experience, Accessibility and Infrastructure | Update/Notify Users Job Report: The job report numbers were previously inaccurate in case of an error. When an error was detected, the job would trigger a retry mechanism. However, the issue was that for these retry attempts, the counters were not properly initialized and continued to accumulate values instead. This issue has now been fixed, and counters will reset correctly during retries. |
| 07964326 07974211 07972123 08246583 08272537 | User Experience, Accessibility and Infrastructure | Previously, scheduled jobs were skipped or incorrectly rescheduled when daylight savings time went into effect. This was fixed. |
Page tags: article:topicproduct:almacontent:Documentationlang:english