Alma 2025 Release Notes
- Last updated
- Save as PDF
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
Alma New UX Developments
New Manage Patron Services UI - Opt Out
Sound Alerts in New Manage Patron Services UI
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 UI - 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
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
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 update_pol_description_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.
Digital Adoption Update
In the November 2023 release, Ex Libris began deploying Pendo, a new digital adoption tool, across Alma and other components of our higher-education back-office suite. For the February 2025 release, Pendo is no longer on the sub-processor list. This was possible due to the extensive measures we are taking to anonymize the usage data and ensure full compliance with our privacy policies (see Privacy center | Clarivate).
Thumbnails Include Images from Syndetics
The infrastructure functionality for retrieving thumbnails 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 UI 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
- 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. - 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
- 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: 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 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). - 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.