Alma 2024 Release Notes
- Last updated
- Save as PDF
Upcoming Issues to Note
Update for Upload Electronic Holdings from Taylor & Francis (Journals)
Please be informed that the current upload electronic holdings from T&F journals, which operates with the CZ collection: Taylor & Francis Current Access (CZ collection ID: 611000000000002216), will be undergoing significant change: The existing collection has been identified as problematic due to its lack of comprehensive title coverage necessary for the auto holdings integration.
Effective from the August 2024 release, the integration will transition to use a new, dedicated collection: Taylor & Francis Journals Auto-Holdings Collection (CZ Collection ID: 615400000000000635).
To continue benefiting from the integration post-August 2024 release, institutions will need to activate the new Taylor & Francis Journals Auto-Holdings Collection (CZ Collection ID: 615400000000000635). For those wishing to retain acquisition details such as PO lines and licenses associated with the titles, it is recommended to employ the Move electronic portfolio information job. This will facilitate the transfer of PO lines and licenses to the new Taylor & Francis Journals Auto-Holdings Collection.
For more information, see Taylor & Francis Journals Auto-holdings Functionality.
Upcoming Issues to Note
Update for Upload Electronic Holdings from Taylor & Francis (Journals)
Please be informed that the current upload electronic holdings from T&F journals, which operates with the CZ collection: Taylor & Francis Current Access (CZ collection ID: 611000000000002216), will be undergoing significant change: The existing collection has been identified as problematic due to its lack of comprehensive title coverage necessary for the auto holdings integration.
Effective from the August 2024 release, the integration will transition to use a new, dedicated collection: Taylor & Francis Journals Auto-Holdings Collection (CZ Collection ID: 615400000000000635).
To continue benefiting from the integration post-August 2024 release, institutions will need to activate the new Taylor & Francis Journals Auto-Holdings Collection (CZ Collection ID: 615400000000000635). For those wishing to retain acquisition details such as PO lines and licenses associated with the titles, it is recommended to employ the Move electronic portfolio information job. This will facilitate the transfer of PO lines and licenses to the new Taylor & Francis Journals Auto-Holdings Collection.
For more information, see Taylor & Francis Journals Auto-holdings Functionality.
Upcoming Issues to Note
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Purchase Requests subject area have been updated:
Upcoming Issues to Note
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Within the Purchase Requests subject area, the following tables have been updated:
Upcoming Issues to Note
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Within the Purchase Requests subject area, the following tables have been updated:
Discontinuation of Support for Alma Mobile Version 1
Starting with the April release, support for Alma Mobile Version 1 will be discontinued.
Action Required: To ensure a seamless transition and continued access to the latest features, we recommend that you delete the original "Alma Mobile" app from your devices. Instead, we encourage you to install the new and improved "Alma Mobile 2" by following the links below:
- AppStore: Alma Mobile 2 on AppStore
- Google Play: Alma Mobile 2 on Google Play
Upcoming Issues to Note
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Discontinuation of Support for Alma Mobile Version 1
Starting with the April release, support for Alma Mobile Version 1 will be discontinued.
Action Required: To ensure a seamless transition and continued access to the latest features, we recommend that you delete the original "Alma Mobile" app from your devices. Instead, we encourage you to install the new and improved "Alma Mobile 2" by following the links below:
- AppStore: Alma Mobile 2 on AppStore
- Google Play: Alma Mobile 2 on Google Play
Upcoming Issues to Note
Discontinuation of Support for Alma Mobile Version 1
Starting with the April release, support for Alma Mobile Version 1 will be discontinued.
Action Required: To ensure a seamless transition and continued access to the latest features, we recommend that you delete the original "Alma Mobile" app from your devices. Instead, we encourage you to install the new and improved "Alma Mobile 2" by following the links below:
- AppStore: Alma Mobile 2 on AppStore
- Google Play: Alma Mobile 2 on Google Play
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 several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Upcoming Issues to Note
Prediction Patterns Update
During December, we identified and fixed an issue with prediction patterns, where opening over 50 predicted items for the same holdings record (e.g. weekly or daily publications) sometimes created items with wrong chronology and enumeration. We have identified all potentially affected institutions and will contact them in the upcoming weeks to ensure any impact of this issue is handled.
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 several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Main Features
Introducing the New Title Search Experience
Alma's repository search is upgraded with new UI concepts, resulting in faster, simpler searches and streamlined workflows, saving time and boosting productivity - starting with the title searches. The new search offers more actions that can be performed directly from the search and enhanced navigation options, bringing your workflows into the search page and enabling you to perform them while in the original search context. Introducing a new approach to loading the search results, the new search offers improved search performance and a gradual loading, showing information as soon as it is available and adding more details as they become ready and enabling users to start working faster.
To turn on the new title searches, click on your user icon () in Alma's persistent bar, select Feature Rollout Preferences, and activate the New Title Search toggle. For information on the coming search experience, see Introduction to the New Title Search Experience.
Manage Patron Services New UI
The Manage Patron Services UI was completely redesigned, in order to leverage new layout capabilities to support a more streamlined workflow at the circulation desk.
The new circulation desk design improves the efficiency of the circulation desk staff's work. The new design and underlying technology make the work at the desk quicker and more efficient, reducing the work load of the library staff and perhaps even more importantly, reducing the time it takes for an end user to receive the required service at the desk.
To turn on the new Manage Patron Services UI, click on your user icon () in Alma's persistent bar, select Feature Rollout Preferences, and activate the New Circulation Desk UI toggle.
For a webinar showing the new functionality, see The New Manage Patron Services Page Circulation Desk.
Automatic Loan Renew Notice
It is now possible to configure the system to send notices to patrons when loans get automatically updated by the automatic renew process.
This enables users to have earlier awareness of the due back date , and not only when they receive a courtesy reminder before the due date.
For more information see Configuring Alma Letters.
Manually Set Patron Role Expiry in Circulation Desk
Circulation desk staff can manually override the patron role expiry date that is calculated by the Patron Role Renewal Period policy in the User Registration Rules. This makes it possible for circulation desk staff to easily manage patron roles, without requiring excessive user management roles.
Activating this option requires enabling a user privilege. To activate the privilege, please contact Ex Libris support. Note that this feature is available in the new Manage Patron Services UI.
For more information see Renewing the Patron Role.
Patron Notification Letter when Hold Shelf Expiry Date is Updated
November 2024 Fulfillment and Resource Sharing Idea Exchange
The system can be set up to notify patrons when the expiry date of an item on hold shelf is changed. This enables patrons to be aware of changes in the hold shelf period that were implemented by the library staff.
For more information see Updating the Expiry Date for Requests and Letters.
Digital Requests for Partners Without Email Address Alert
November 2024 Fulfillment and Resource Sharing Idea Exchange URM-228265
When a lender ships a digital request for borrower who is an ISO partner, and the borrower email address is not supplied, an alert is now added to the lending request indicating that the borrower does not have an email address.
Override Local Holding Setting
November 2024 Fulfillment and Resource Sharing URM-228264
RapidILL checks for self ownership, and requests identified as owned receive the local holding status. When the checkbox Ignore Local Holding (Fulfillment > Resource Sharing > Partners > Parameters tab) is checked, libraries skip this self ownership check by RapidILL.
This configuration may be of particular interest to libraries using the Sending Borrowing Request Rules (Fulfillment Configuration > Resource Sharing > Sending Borrowing Request Rules) to stop requests from being automatically sent, if locally owned. In that case, if the request is manually sent via Rapid then rechecking for local ownership via Rapid may be redundant, and can therefore be prevented using this new option.
Transfer Library Pickup Location into ILLiad
The borrower request information that is pushed to ILLiad using the API integration, can now include the ID of the pickup location and its name in the API ShippingOptions field. To implement this option, please contact Ex Libris support.
The pickuplocationname is limited to 50 characters.
Library Inheritance of Calendar from Institution
It is now possible to define standard opening hours at the institution level. The institution level opening hours will be inherited by all libraries.
A library may create its own standard opening hours, effectively disconnecting from the institution level opening hours.
For more information see Configuring the Institution and its Libraries.
Block Same Day Booking
You can now configure Alma to block same day booking if the booking resolution is set to days. This is done by setting the allow_same_day_booking parameter.
For more information see Configuring Physical Fulfillment.
Conditional Automatic Forwarding of Document Delivery
Borrowers can set up rules which determine whether a digitally received resource sharing request should be automatically shared with the requesting patron, or wait for library staff handling before being forwarded to the requesting patron. For example, the document may require to be processed to increase its accessibility for a requester that requires increased accessibility.
This enables the library to better service patrons that require special handling of digital files.
The borrower_document_delivery_send_automatically parameter (Configuration > Fulfillment > General > Other Settings) to determine whether the email to the patron is sent automatically when a document is received on the borrower side is, now obsolete. For customers that have already configured this parameter in the past, the document delivery rules described below will be automatically set up to preserve the previous behaviour.
The Output Parameter for the default document delivery rule (Fulfillment > Resource Sharing > Send Borrower Document Delivery Rules) is True by default. When set to False, emails are not forwarded automatically. The parameter can be applied by User Group or User Statistical Category.
This functionality is not relevant for URLs sent from a lending request. Whether or not the URL is sent directly to the patron is controlled by the rs_send_url_directly_to_patron parameter.
For more information see Advanced Resource Sharing Configurations and Peer to Peer Resource Sharing.
Alma Integration with the NACSIS-ILL System
Alma now supports a full integration of NACSIS-ILL for resource sharing. The workflows are integrated into Alma so that all relevant capabilities required by the NACSIS-ILL operators using Alma are available in the system.
This includes the following:
- Creation of new NACSIS borrowing/lending requests
- Synchronization of NACSIS requests
- Reflection of NACSIS statuses on Alma requests in addition to other relevant NACSIS information such as member information, offset indication, etc.
- Full support of NACSIS actions based on the NACSIS request status
- Support for NACSIS shipping costs
- and more...
For more information see Integration with NACSIS-ILL.
Browse Shelf Listing Enhancements
When browsing for call number, the following enhancements are introduced:
- Author information is displayed in the browse results to help libraries that use this data for adding call number cutters.
- Call number auto-population also works for local 09X fields.
- Read-only access was added, so that all users can now browse shelf listings (similar to browse bib and authority headings).
This completes the cycle of improvements made to Browse Shelf Listing during 2024.
For more information, see Browsing the Shelf Listing.
Linking to Authority Via Dropdown Menu in Metadata Editor
A new action labeled Open Authority Headings has been added to the "Editing Actions" menu in the Metadata Editor. This feature enables users to access the lookup functionality previously available through the F3 key, making it particularly beneficial for catalogers who do not use function keys.
The Open Authority Headings action becomes available when the cataloger is in a field that supports the F3 function. It opens the same lookup for that field as the F3 key, displaying identical data (including vocabularies, headings, field indicators, etc.) and offering the same functionality, such as viewing and selecting headings.
For more information, see Metadata Editor Menu and Toolbar Options > Editing Actions Menu.
Searching Bibliographic Records by Language Code
Alma's "Language" search index, that enables users to select a language in the MARC Code List for Languages and search their catalog for records that contain its MARC code, does not support searching by other language codes from different sources that may appear in MARC 21 "041" field. A new search index, "Language code", was added to enable users to search the code directly as it appears in the record, so that non-MARC codes can be used to find bibliographic records.
This new index will be fully available after the semi-annual indexing is completed.
For more information, see MARC 21 Search Indexes.
MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
Updated - October 31, 2024 - Alma's preferred term correction previously did not handle cases where a bibliographic heading linked to an authority record via a cross-reference, but the preferred and non-preferred terms were in different fields (for instance, the preferred term in authority field 130 and cross-reference in 410). With this enhancement, libraries can configure Alma to correct bibliographic headings based on authority cross-references, updating them to the preferred term and changing the field tag in the bibliographic record accordingly (such as, from 610 to 630).
This feature improves cataloging automation, efficiency, and ensures bibliographic data stays aligned with authority records' preferred terms.
Additional Information:
To enable this functionality in your institution, input the vocabulary codes for the relevant authority vocabularies into the customer parameter authority_ptc_ignore_suffix, separated by commas.
When a bibliographic field is updated to an X30 field, the non-filing indicators in the bibliographic record will be adjusted based on the linked authority record. According to MARC21 standards, the 1st indicator of authority field 130 (Nonfiling characters) will be copied to the 2nd indicator of the X30 bibliographic field.
Once enabled, headings updated by this new behavior appear in the Authority Control Task List under a new report type, “Preferred Term Correction - Bib Heading updated and tag modified,” enabling catalogers to review and make further updates as necessary (such as, adjusting indicators).
Fields that have an Alternate Graphic Representation and their linked 880 fields will stay as is even when their corresponding vocabulary is flagged to be handled. They will not be corrected by the preferred term and the field tag will remain unchanged. Handling for these fields will be added in a future release.
For more information, see Managing Preferred Term Correction.
For more information on the report type, see Using the Authority Control Task List.
For more information on the customer parameter, see Configuring Other Settings (Resource Management).
Introducing the New AI Metadata Assistant in Preview Mode
Since the announcement of our upcoming AI Metadata Assistant—an AI tool integrated into the Metadata Editor that generates metadata suggestions to assist catalogers in creating and enhancing bibliographic records—we've received many requests for early access to test its functionality. While we couldn't accommodate all requests, we greatly appreciate the community's enthusiasm for this feature and its willingness to collaborate with us in testing and improving it. We value the diverse perspectives of our cataloging community and the valuable feedback they provide.
As a result, we have decided to enable Phase I of the AI Metadata Assistant in Preview Mode for all Alma environments as part of the November release, allowing administrators to activate it at their discretion.
The Preview Mode is not the final version of the AI Metadata Assistant! It is an initial mode designed to give libraries an opportunity to experience metadata enrichment and contribute to the feedback process.
Further improvements to the workflow and the generated metadata are expected in upcoming releases, but libraries are encouraged to explore the feature in their Sandbox or Production environments to get an initial sense of its capabilities. We welcome your feedback, which can be submitted via the AI feedback button in the MD Editor when working on a draft created or enriched by AI.
Phase I of the AI Metadata Assistant supports English-language MARC 21 records using LC subjects. For more details on how to enable this feature, how it works, and our planned enhancements, please refer to the AI Metadata Assistant in the MD Editor page.
Updates to MARC21 Profile
MARC21 update No. 38 (June 2024), includes changes resulting from proposals that were considered by the MARC 21 community since the publication of Update No. 37 (December 2023).
Bibliographic Heading Linking Updates Following the Semi-Annual Re-indexing
We would like to update that as part of the semi-annual re-indexing in November, we will be doing a quality check on bib headings linked to authority records, to validate that they are properly linked. Following this validation, some headings may need to be re-checked by Alma's automated "Authorities - Link BIB Headings" job for a matching authority.
What you might see following the re-indexing in your environment:
- The "Authorities - Link BIB Headings" job may run on larger numbers than usual.
- If a matching authority is found for these headings in the linking job, the "Authorities - Preferred Term Correction" job may run on a larger number as well.
- The Authority Control Task List may show a larger number of bibliographic headings handled by these jobs.
Improved Handling of Bibliographic Records Upon Physical Holdings' Relink or Deletion
The holdings relinking behavior was aligned with other inventory deletion, so that the operator can select how to handle the bibliographic record if it has no remaining inventory.
This is helpful for efficiently maintaining the catalog.
For more information, see Working with Holdings Records.
Automatic Upload of Electronic Holdings from Elsevier is Now Based on Unique ID
With the November 2024 release, Elsevier autoholdings transitions from ISSN/ISBN matching to a unique key matching approach. This change aims to reduce multi-match situations and enhance the autoholdings process.
Future releases will extend this approach to additional providers.
For more information, see Upload Electronic Holdings from Elsevier.
Enhancements to the Upload Electronic Holdings Job Reports
Enhancements have been made to the Upload Electronic Holdings job reports, applicable to all autoholding integrations except ProQuest Ebook Central:
-
Multimatch and missing MMS errors that were previously only available within the report’s Excel file are now displayed in the report summary.
-
The autoholding job report now includes a link to view portfolios and bibliographic records deleted by the job.
For more information, see Monitoring the Upload Electronic Holdings Job.
Update URL Suffix Using "Change Electronic Portfolio/Collection Information" Jobs
A new feature has been added to the "Change Electronic Portfolio Information" and "Change Electronic Collection Information" jobs, enabling bulk editing of static URL suffixes. Users can now add, delete, or replace suffixes, such as for logging users into a provider's platform. The updated URL will be applied to the 'Static URL (override)' field.
This enhancement streamlines the process of bulk editing static URLs.
Alma restricts the simultaneous use of prefix and suffix parameters in the "Change Electronic Portfolio Information" and the "Change Electronic Collection Information" jobs. To modify both, separate runs of the job are required.
For more information, see Manual Jobs.
Possibility to Define Linking Parser Parameters for Database Collections in Collection Level to be Used by CDI Direct Linking
Some providers require customized URLs for accessing their content, which include special credentials. Previously, linking parameters for collections with portfolios were configured at the service level. With this new development, institutions can now define linking parameters at the collection level for database-type collections. These linking parameters are used by CDI direct linking to the database. Note that only database collections that were defined this way in the Community Zone can be configured, and only the Community Zone defined linking parameters can be set.
The Community Zone will gradually add relevant linking parameters for database collections, with an initial focus on Gale and ProQuest collections.
Notifications about new database collections with available linking parameters will be provided through content release notes and the Community Zone update task list.
For more information, see:
Select DC Field to Validate Matching
The Dc Bib Find Matches Validation Task checks if there are any duplications with existing Dublin Core titles. Under the Task Parameters for this task, the DC Field and Search Index drop-down list is now available that allows you to configure the task to check for duplications either by matching the dc:identifier field or the dc:title field.
Not selecting any value does not check for duplications.
Lookup Field Now Available for Forms
You can now add the Lookup field to forms for Adding a Representation and Staff Mediated Deposit.
Lookup fields display results as you type and also have a button you can select to open a page with all of the options.
For more information on Forms, see Working with Forms.
Open Access Workflows: New License Type for Transformative Agreements
A growing number of publisher agreements present possibilities for open access publication. Furthermore, some institutions assign libraries the task of supervising allocated funds for covering article and book processing charges related to open access publication.
It is now possible to create a license representing a "transformative agreement". This license contains all the license fields available for other license types, as well as the ability to indicate the number of tokens, and to mark whether the license is limited, or “unlimited”.
This allows institutions to keep track of their open access workflows, and to identify if they utilize all the tokens. Future negotiations with providers will benefit from this information.
For more details, see:
PO Line Approver ID is Available in Analytics
The PO Line Approver ID is now saved in the Alma DB and is available in Analytics.
A PO line is considered approved when its PO is approved, in the following scenarios:
-
When approving PO's from the Approve Orders page using the Approve and send action.
-
When the institution is not working with the Approval Rules, the PO is considered approved when it is sent:
-
When selecting Save and continue for a PO in review.
-
When using the Order Now action from the PO line.
-
The approver is the user who clicked the action.
- For PO's which are sent automatically by Alma, the PO Line Approver will be "System". This happens when the "PO Lines - Packaging" job creates the PO and sends it out, when using integration with ERP, and in some cases in EOD.
- The approval data will be shown from the release date and onwards.
For more information see PO Line Approver for Analytics and Approving and Sending POs.
"Report Tax" Invoice Supported when Paying with API
It is now possible to create an _RT invoice for VAT handling when marking an invoice in the "waiting for payment" status as “paid” using the invoice service API.
POST /almaws/v1/acq/invoices/{invoice id}?op=paid&create_rt_invoice=true
An _RT invoice will be created when the following conditions exist:
- The report_tax field is true in the supplied payload. If this field is not supplied in the payload, the data on the invoice will be checked by Alma.
- The institution has an associated governmental vendor.
For more information see the Developer Network.
"Available for" Field Added to Summary Funds
The Available for field is now displayed for summary funds. The summary fund’s “Available for” will be inherited from its related ledger. Also, any allocated fund that is linked with a summary fund will now inherit the “Available for” values from the summary fund.
This allows for better flexibility in defining the funds hierarchy, and enables using the Fund ledger view by available for privilege for both allocated and summary funds. When this privilege is enabled for a user with a fund related role, scoped to a specific library, they will be able to view funds of all types, that are owned by the institution and available for the user's library.
Existing summary funds appear with the identical “available for” as their parent.
For more information see Managing Funds and Ledgers and Managing User Roles.
Match Records Created by PDA with Existing Portfolios in CZ
The Use Community Zone portfolios field was added to the Inventory Information tab of the PDA Repository import profile. This enables the matching of records created by PDA with existing portfolios in the Community Zone (CZ). This enables users to utilize CZ data when using the PDA Repository profile.
For more information see Managing Import Profiles and Patron Driven Acquisitions.
Change Currency in Packaged PO Lines
Users can now change the currency of PO lines that were packaged, in the following workflow steps:
- Ready
- Sent
- Waiting for Manual Renewal
- Recurring Renewal
- Waiting for Invoice
Consortia Authority Control Task List Enhancement
The enhanced Consortia Authority Control Task List now includes the reporting of record changes processed in the Network Zone at the Institution Zone level, enabling corrections or modifications of such records and pushing them to the entire Consortia members' Authority Control Task List. This enhancement improves the experience for Consortia member catalogers working with authorities by reflecting Network Zone linked records reporting in each Institution Zone Authority Control Task List. When one Consortia member corrects a Bibliographic record based on such reporting, this action is reflected in all Consortia members' Authority Control Task List, ensuring that authority catalogers do not need to duplicate the same work across different institutions.
Impact: This enhancement significantly streamlines the authority control process for member institutions, by reducing duplication of effort and enhancing collaboration. It allows members to view both Network Zone linked records and local authority control records, providing a comprehensive view of authority control efforts. Overall, the enhanced Consortia Authority Control Task List improves efficiency, consistency, and accuracy in authority control across the consortia, making it easier for catalogers to manage their responsibilities.
This new feature is only relevant to a member of the consortia (an institution that is part of a Network Zone).
For more information, see Using the Authority Control Task List.
Network Zone Managed Electronic Resources - Library/Campus Level
Previously, central office operators could manage electronic resources in the Network Zone and make them available either to the entire network or to specific member Institution Zones (IZ). With this new feature, central office operators can now allocate electronic resources to specific libraries or campuses within a member Institution Zone.
Upon setting the new customer parameter nz_multi_campus_members to true in the Network Zone institution, Inventory network groups in the network zone can include libraries and campuses from within member institutions:
Upon defining Network Zone electronic resources as "Available for" a group with libraries/campuses, these resources are available for these libraries/campuses, but not to others.
This enhancement improves efficiency by enabling centralized management of electronic resources for individual libraries or campuses within the member Institution Zone, benefiting institutions that require separate management for their libraries or campuses.
For more information, see Configuring Distributed Access to Electronic Resources from the Network Zone.
User Update API Restricted for Library Scope
The User Update API is now restricted in the case where the API key scope is set to a library. In this case, the User Update API will not be able to add/remove/edit roles in other libraries. For more information see Users and Fulfillment in the Developer Network.
Enhanced Library-Specific Role Management for User Management in Alma UI
The User Manager functionality was enhanced to enforce restrictions based on user manager role(s) library/ies scope. This prevents unauthorized User Managers from adding, removing, or editing roles for libraries to which they do not have access.
By ensuring that only authorized modifications can be made, this update significantly reduces the risk of unauthorized access and role changes, thereby protecting sensitive library data. This functionality also applies when adding roles through user profiles.
For more information see User Roles.
UX Improvements to the Manage Sets Page
URM-225800
A number of UX improvements were implemented on the Manage Sets page. These include:
-
Labels - Enable users to add or remove labels for sets.
Users can also now facet the sets list according to the existing labels, and see the labels in the list as badges.
For more information see Managing Labels in Alma.
-
Sliding Panel - When combining sets, the pickup field for selecting the set to combine with now opens in a sliding panel.
For more information see Combining Sets.
-
Exclude Facets - Users can now exclude facets in the Manage Sets page and also save the facets setup for future use, making it easy to reapply it in a single click.
For more information see Facets.
Feature Promotion in Alma
A new Feature Promotion functionality was added to increase awareness of specific new features in Alma and improve the user experience.
For example, in November, two major features are being promoted, i.e., the New Circulation Desk UI and the New Titles Search Experience. The Feature Promotion only notifies the user about the promoted features. However, the user can still access the functionality via the regular path, regardless whether the feature promotion is enabled or not.
The Feature Promotion functionality will be available on the Production environment, and not on Sandbox.
The Feature Promotion is auto-triggered from the home page or in the relevant context (for example when accessing the old Circulation Desk UI in November).
The following options are available:
- Cancel button (X) - Exit the dialog box (will not show up again).
- Remind Me Later - Exit the dialog box and invoke it again one day later.
- Take Me There - Takes the user to the relevant feature.
Notice: Once engaging with the feature promotion by either clicking the (X) or the Take Me There, the feature promotion popup will not show up again.
The following is required for the Feature Promotion to appear:
- The institution enabled Digital Adoption (Configuration > General > General Configuration > Digital Adoption).
- The user allowed functional cookies, either upon login or from the Cookie Preference Center (User icon > Cookie Settings).
- The user has the Enable Tips option switched on (User icon > Enable Tips). This is enabled by default. The user can switch this off to prevent the notifications from appearing.
For more information see User Menu.
Restrict Integration Profile for User API
A user API key with library-scope restrictions is now not able to add/remove/edit roles in other libraries.
For more information see the Developer Network.
New Analytics User Roles Category
When adding roles to user accounts, the Analytics roles now are located under the Analytics category and not under Miscellaneous as was the case previously:
The Analytics role category also appears when adding roles to an Analytics Object:
New Limited Design Analytics Roles for Users and System Usage
Access to the following subject areas was removed from the limited design analytics roles for Acquisitions, Fulfillment, and Resources and assigned to two new limited user roles:
- Users
- Analytics Objects
- Analytics Usage Tracking
- System Events
- DARA
- API Usage
The following new limited user roles are now available:
- Designs Analytics – System Usage: limits access to Analytics Objects, Analytics Usage Tracking, System Events, DARA, and API Usage subject areas. Includes Titles, Local Authorities, Benchmark and External Vendor data. Allows write access to analytics reports, analyses, dashboards, DV projects, etc.
- Designs Analytics – Users: limits access to Users subject area. Includes Titles, Local Authorities, Benchmark, and External Vendor data. Allows write access to analytics reports, analyses, dashboards, DV projects, etc.
- Because of the change to the existing limited roles, users previously assigned these roles will lose access to several areas with this release. To allow access to these areas, the users must be assigned additional roles.
- Limited roles that do not allow access to patron user data still allow access to staff user data. For example, borrower details are not accessible, but loan operator details are.
- To enable these roles, set the support_partial_analytics_designer parameter (Configuration > Analytics > General Configuration > Other Settings) to true.
For more information on Design Analytics roles, see Design Analytics Roles.
Shared Users Notifications Now Available
Select Admin shared a new report with user to have notifications sent to you when an administrator shares a report, dashboard, or data visualization workbook with you.
Under Notification Preferences, select the method that you want to receive the notification: Email, Pop-up, or both.
For more information, see Real-Time Notifications.
Customer Activation of Springshare Integration Profile
Table View Now Available for Analytics Objects
You can now display the Analytics Object List, the Shared with Me page, and the Out-of-the-Box Analytics page in Table View. To display these pages in Table View, select the Table View icon at the top right of the page:
From this view, you can view the analytics object information in a clear and organized format.
For more information on the Analytics Object List, see Working with Analytics Objects.
Support for OpenID Connect Logout
It is now possible to configure a Logout URL in the OpenID Connect Integration Profile to which Alma and Primo will redirect after logging out.
For more information see Creating an OpenID Connect Integration Profile.
Send Email Using MS Graph APIs
Since Microsoft deprecated Basic Auth for SMTP, Alma now supports sending emails by calling Microsoft Graph APIs. A new option of ‘Send using MS Graph API’ was added to the Mail-Handling integration profile, enabling the institution to configure the Mail Handling integration profile to send emails using MS Graph API.
For more information see Configuring Alma Letters.
Five New Optional CSP Header Directives
Five new optional CSP (Content Security Policy) header directives were added to the CSP Header Configuration page:
- style-src
- img-src
- font-src
- child-src
- default-src
For more information see Security.
Support for Linking Parameters and HAN Proxy Licenses in API
Linking parameters are now supported in API calls for E-services (at both service and group settings levels) and for database-type E-collections with defined parser parameters. Additionally, HAN proxy licenses (depending on the 'han_proxy_multi_license' customer parameter) are now supported in API calls for E-services.
This development enables the retrieval and editing of these fields via API. Users should ensure they begin with a GET request and use its payload as the basis for PUT requests to prevent unintended changes.
For more information, see the following documentation in the Developer Network:
New Modified Primary Representation Usage Type Now Available
For more information, see Adding Representations.
Indexing of PO Lines After Vendor/Invoice Update Now Done in the Background
With the September release, the indexing of PO lines following a vendor update is done by a background job. For invoice updates, a threshold of 10 was defined. If there are up to 10 related PO lines, they are indexed immediately. If there are more, they are indexed by a background job. The triggered indexing job appears in the Monitor Jobs page. The user that made the updates which triggered this re-indexing appears as the operator.
In the November release, similar logic will be added to fund changes that require re-indexing of the related PO lines. For more information see Reviewing Invoices and Managing Vendors.
NERS: Communication with Partners
It is now possible to email a partner directly from the borrowing and lending task list requests. This option eases workflows, such as when a lender wants to convey limitations, a borrowing library wants to ask a question, or for any type of messages such as a thank you note. These messages are saved in the request for future reference.
Correspondence can be initiated using the Send email to partner action or from the Start Communication button on the Communications tab.
Convert Borrowing Request Type
It is now possible to convert a resource sharing request type from Book to Article and vice versa using the Convert Request Type action from the available actions for the request. This action is available for the following statuses:
- Request created
- Ready to send
- Locate failed
- Rejected
- Resubmit
- Expired
- Recalled
- Pending approval
- Reject
- Bad citation
- Local holding
Once this action is selected, you can select the type of request to convert to and add the required information (such as pages or chapter numbers when converting to a book chapter).
Once converted, the Request type change is logged in the History and the lending request partner is recalculated.
For more information, see Converting a Borrowing Request Type.
Option to Bulk Remove 'Transit For Reshelving' Status
The Change Physical items information job can now be set to remove the Transit For Reshelving status from items. This makes it easy to correct the status of items that are incorrectly marked as in transit.
For more information see Manual Jobs.
Exclude Non-Workdays Days from Expiry Period
Resource Sharing request expiry is currently managed by The Expiry Time (days) that is defined on the partner record (borrower side) and a job that runs (on the lender side) that expires unhandled requests. To prevent lending requests from expiring during non-workdays, Alma now enables you to set days to exclude from the expiry period calculation (Configuration > Resource Sharing > Configuration > Resource Sharing Working Days).
For more information see Basic Resource Sharing Configurations.
Resupply Request for Document Delivery
For document deliveries, after a request is completed, Alma enables the borrower to request a refill for a RapidILL request in case the original request was not properly received. This is done by using the Resupply Request action. This action is available for completed Rapid ILL requests. It reopens the request on the borrower's side and notifies the lender about the resupply request.
In addition, the RapidILL lender receives an alert and a note to resupply the request.
For more information see Managing Borrowing Requests.
FRBR Keys for Bibframe to Include URIs (IDs)
FRBR keys, currently composed of text fields, are now expanded to include URIs (IDs) for BIBFRAME records as part of their matching criteria. This enhancement introduces URIs as a new match point, enabling more accurate grouping of instances. When instances share the same work URI or the works share the same expression of URI, they are assigned the same FRBR key, ensuring consistent grouping.
For more information, see Configuring the Dedup and FRBR Complete Keys in Primo VE and Understanding the Dedup and FRBR Processes (Primo VE).
Contributor Page in Metadata Editor
Alma enhances the Metadata Editor with linked open data functionalities by adding a Contributor Page to assist catalogers in identifying the correct authority for MARC records. Users are given the option (when available) within the Authority tab to view the Contributor Page. This page assists catalogers in identifying the correct authority for MARC records and displays detailed information from both external resources (Wikidata and Wikipedia) and the local catalog. This information can assist catalogers in selecting the correct authority record to link to when using authority selection. Catalogers can navigate from the Metadata Editor to a full-page view of the Contributor Page and back to the Metadata Editor.
If the description in the Contributor Page exceeds 10 rows, a link labeled "See More in Wikipedia" is displayed.
Full support for generating a new search based on the ID of the authority will be fully functional after the November 2024 indexing.
For more information, see:
- View Contributor Page
- Recording: Linked Data in Alma - Alma 2024 Roadmap Webinar Series (June 4, 2024)
- PPT Presentation: The Linked Data Info Card.pptx
Record Format Facet for Enhanced Repository Search
August 2024 Linked Open DataURM-207443
The repository search functionality has been enhanced with the addition of a new record format facet. This feature enables users to filter search results by record format, encompassing all titles, whether physical, electronic, or digital.
Record Format Facet displays only when an institution has more than one record format activated.
For more information, see Filtering Search Results.
Brief Record Ratings Now Support BIBFRAME Records
Brief record ratings now support BIBFRAME records, utilizing the same drools created for MARC records within each institution. Users do not need to create new rules specifically for BIBFRAME, as the existing MARC rules are seamlessly applied to BIBFRAME records.
For more information, see Working with Brief Record Levels.
Include Deleted Holdings When Publishing Deleted Bibliographic Record to OCLC
Previously, when a bibliographic record was deleted, the "Publish bibliographic record (DataSync) to OCLC" profile included the deleted record without its holdings. Institutions can now customize this profile to include all deleted holdings of the bibliographic record in the published file. This facilitates OCLC in matching their OCLC symbols and processing the deletion. To enable this feature, institutions can set the customer parameter "oclc_add_hol_to_deleted_bib" to "true". If this parameter is set to true, the published deleted bibliographic record will also include all of its deleted holdings, regardless of when they were deleted. This ensures that all the bibliographic record's holdings are indeed removed from the external system (this functionality has been confirmed with OCLC). The included holdings data will adhere to the mapping specified in the "Map holdings fields into Bib record" table. This feature is particularly beneficial for libraries utilizing the OCLC publishing profile rather than the general publishing profile when publishing to OCLC.
For more information, see Publishing to OCLC.
New Fields Available to Display in the Physical Items Search Results
The following fields are now available to activate in the physical items search configuration:
- Public note
- Fulfillment note
- Internal notes
- Statistics notes
- Receiving date
- Receiving operator
This is especially useful to operators who need to scan this information for multiple items, saving them the need to go into each item.
To activate these fields, click the gear () icon at the top right corner of the search results, and select the fields to add to your results.
For more information, see Customizing the Search Results Record Fields.
Enhanced "See also" Navigation in the Authorities Search
When an authority record has a 5XX field mentioning a related authority, the authorities search results contains a link to easily search for that term. If the authority vocabulary does not base these pointers on authority ID, clicking on the "See also" link generates a search for the term entered in the 5XX field. This search was enhanced to give more accurate results, by making the following changes:
- Change the search operator from "contains keywords" to "equals", to improve the accuracy of the retrieved results.
- Limit the search by originating system, so that only authorities from the same system as the authority record the search originated from will be retrieved.
- Before, the entire 5XX field was included in the search, often resulting in not finding the relevant authority. Now, only subfields indexed for search in the relevant source code (subject, personal name, corporate name, and so forth) within the 5XX field are included in the search. Information irrelevant for the search (for example, relationship information for personal name) is excluded, streamlining the results.
Institutions that prefer the previous keyword-based “See also” search behavior (for example, who work mostly with vocabularies where doing a fuzzy match is more desirable), can select to opt out of the new system by setting the customer parameter aut_see_also_link to ‘false’ to retain the old behavior.
For more information, see Performing Actions on the Repository Search Results Page > See also.
ACTL Enhancement for Consortia Members
The Authority Control Task List (ACTL) now includes a new filter for Network Zone linked records to be used by the Consortia members. Some consortia members update all BIBs from the Network Zone and do not want to view the Network Zone records in the Institution Zone. To support this and still enable other consortia members to show these records, a new filter is added to facets labeled Linked to Network Zone in addition to the existing facet Linked to Community Zone.
For more information, see Working with the Authority Control Task List > Facets.
Creating Multiple Items for a Holdings Record Using Item Templates
In Alma's ongoing effort to streamline physical resource management, users can now add multiple items to a holdings record using "Add item from template" and specifying the desired quantity. This initiates a process that generates multiple items within the holdings record, pre-filled based on the selected item template.
When using a barcode sequence, the system verifies the current sequence during each item creation to maintain barcode uniqueness. Consequently, barcodes may not appear sequential if other items are simultaneously created using the same sequence within the institution.
This feature significantly benefits physical inventory operators managing multiple copies of the same book, eliminating the need for individual additions. It complements other bulk item creation tools in Alma, such as import profiles and the "Item Creator by Excel" CloudApp introduced earlier this year. This CloudApp facilitates the creation of new physical items from Excel files, ideal for scenarios involving multiple holdings or titles, varied enumeration/chronology fields, or when item data is provided in Excel format (e.g., from vendors).
For more information, see Working with the List of Items.
New Columns Available to Display in the Physical Items List Table
The following columns are now available to activate in the physical items list table:
- Condition
- Public note
- Fulfillment note
- Internal note 1
- Statistics note 1
This enhancement is particularly beneficial for operators who need to quickly scan information across multiple items, eliminating the need to access each item individually. To activate these fields, select the gear () icon at the top right corner of the table and select the columns you want to include in your results.
For more information, see Working with Table Columns.
DARA Recommendation to Use Upload Electronic Holdings Integration with All Relevant Provider(s)
DARA now recommends the use of upload integration for all relevant providers' electronic holdings. When an institution has active collections with a vendor that supports upload electronic holdings integration but lacks an integration profile with an active schedule, a recommendation is generated. If this recommendation has expired without being implemented or dismissed, it will be regenerated after three months. Notifications inform institutions about the availability of the upload electronic holdings integration relevant to their data, allowing them to configure the integration and eliminate the need for manual portfolio management.
For more information see DARA – Data Analysis Recommendation Assistant.
Upload Electronic Holdings from Taylor & Francis (Journals) Now Uses a Dedicated Electronic Collection
Background: The Taylor & Francis Journals Autoholdings integration was initially launched in February 2024, utilizing the existing Alma Community Zone journals collection: Taylor & Francis Current Content Access (CZ Collection ID: 611000000000002216).
Since its release, there have been reports of missing content and variations in coverage dates, which were duly investigated in collaboration with Taylor & Francis. It was discovered that approximately 1000 titles, including previous editions, perpetual content no longer offered for sale, and content with a non-"current” coverage, were not included in the "Current Content Access" collection.
Transition to New Collection: After extensive discussions and analysis, it has been decided that a new, dedicated Community Zone collection will be utilized for the Taylor & Francis Journals Autoholdings functionality. The new collection: "Taylor & Francis Journals Auto-Holdings Collection" (CZ collection id: 615400000000000635), includes the complete journals title list. This collection will be regularly updated to ensure accurate coverage of all institutional titles. The provider is committed to keeping this collection full of all the titles that an institution might have access to, regardless of their nature.
Effective Date: Commencing from the August 2024 release, the integration of Taylor & Francis Journals auto-holdings will now exclusively use the new "Taylor & Francis Journals Auto-Holdings Collection" (CZ Collection ID: 615400000000000635).
This change aims to enhance the accuracy and completeness of your journal holdings data and avoid the need to perform manual actions.
What do you need to do? To continue benefiting from the integration post-August 2024 release, you need to activate the new Taylor & Francis Journals Auto-Holdings Collection (CZ Collection ID: 615400000000000635). For those wishing to retain acquisition details such as PO lines and licenses associated with the titles, it is recommended to employ the Move electronic portfolio information job. This will facilitate the transfer of PO lines and licenses to the new Taylor & Francis Journals Auto-Holdings Collection.
For more information on the transition to a new dedicated collection and the required actions, see: Taylor & Francis Journals Auto-holdings Functionality.
For general information on the autoholdings integration, see:
IPv6 Now Supported for IP Range Access Rights
IP Addresses using the IPv6 format are now supported when configuring access rights for digital representations according to IP range.
For more information, see Access Rights Policies for Digital Objects.
Order It! Now Supported When Third-party Cookies are Blocked in the Browser
In Q3 of 2024, the Chrome browser's default third party cookies will be changed to be automatically blocked (see Third Party Cookie Deprecation).
Order It! uses third-party cookies in order to support single sign in. Now, when third-party cookies are blocked in the browser, Order It! will notify the user that the Alma website needs to be added to the list of allowed sites to use third-party cookies. After the site is added, Order It! will be loaded as expected. This functionality will apply to all supported browsers.
For more information see Ordering with the Order It! Plugin.
Summary Bar Added to the Funds Section in the PO Line
A summary bar was added to the Pricing and Funding section in the PO line, indicating the total sum and the funding coverage percentage.
In addition, some minor display modifications were done to the entire Pricing and Funding Information section.
For more information see Pricing and Funding.
New Fields Added to the "Update PO Lines Information" Job
Nineteen new fields were added to the Update PO Lines Information job. In addition, the job form is now divided into sections, allowing to easily locate the required field/s to update.
This job only performs allowed updates on the selected PO lines. When trying to update a field on a PO line that cannot be updated, for example, adding a renewal note to a one time PO line, this field will not be updated and an error will be displayed in the job report.
The list of new fields is as follows:
- Additional PO line reference field
- Cancellation Restriction
- Cancellation Restriction Note
- Add labels from list
- Remove labels
- Create new label
- Reclaim interval
- Subscription interval
- Note to vendor
- Vendor reference number type
- Routing during receiving
- Binding during receiving
- Activation note
- Renewal date
- Subscription from
- Subscription to
- Renewal reminder period (days)
- Renewal note
- Internal note
For more information see Manual Jobs and Configuring Processes.
PO Line Description and Creator Fields Added to Transactions Tab
The PO Line Description and Creator fields were added to the Transactions tab for Funds and Ledgers.
To enable their display, check both fields in the table customization menu.
- The user card of the Creator field will only be displayed for transactions done after this development was released.
For more information see Managing Funds and Ledgers.
Open Access Workflows: New PO line Types for Article Processing Charges (APC)
A growing number of publisher agreements present possibilities for open access publication. Furthermore, some institutions assign libraries the task of supervising allocated funds for covering article and book processing charges related to open access publication.
It is now possible to create PO lines for Article Processing Charges (APC), using 2 new PO line types:
- Article Processing Charges (APC) – One Time
- Article Processing Charges (APC) – Subscription
The new PO line types are without inventory, as they represent the request to publish articles. It is possible to link such PO lines to the vendor for which the request to publish is being processed, and to link to the relevant license. It is possible to record the price and funding.
This information is available in Analytics and can be used by institutions for understanding the amount spent on open access publications.
Additional open access elements, such as transformative agreement, will be added to Alma in the coming releases.
For more information see Enabling/Disabling PO Line Types and PO Line Types and Statuses.
Copy PO Line Price to Replacement Cost
An option was added to copy the PO line price to the item's Replacement cost field.
The price is copied upon PO line creation, change of PO line price and addition or removal of items in the PO line.
In addition, an option was added to add or reduce an amount from the PO Line price when being copied.
For more information see Configuring Other Settings and Working with Items.
Support for Continuous PO Lines in Receive Existing Items API
The Receive an Existing Item API now supports receiving items of continuous PO lines. The same parameters should be used as for receiving items of one time PO lines. For more information see the Developer Network.
Handling of Half/Full-Width Japanese Romanized Characters
Alma now supports the transliteration of Japanese half/full-width Romanized characters. For more information, see Working with CJK Transliterations in Cataloging.
New Consortia Central Configuration Dashboard
August 2024 Collaborative NetworksURM-218334
The new Consortia Central Configuration Dashboard enhances the experience of Consortia Central Office operators responsible for managing Consortia members' configurations. The dashboard provides easy access to all Consortia members' configurations within the Network Zone, eliminating the need to log in to each member individually. It facilitates the management of members' configurations when the Central Office acts on behalf of a member and allows the distribution of Network Zone configurations to Consortia members, ensuring unified configurations across all or selected members.
This feature is exclusively relevant to an Alma Network Zone.
Enable Cloud App Activation per Role
The Cloud App configuration now includes two new options for controlling the usage of cloud apps in the institution. The administrator can configure one, both or neither of these options.
- The administrator can configure cloud apps to be available for activation only by users with the relevant role/s required by that cloud app.
Cloud Apps Tooltip
- The administrator can control which users can activate and use cloud apps by giving specific users the new Cloud App Operator role.
For more information see Configuring Cloud Apps.
Configuration of CSP (Content Security Policy) Headers
There are five new CSP headers that you can enable and configure for allowed domains.
- script-src
- form-action
- frame-src
- connect-src
- base-uri
For more information see CSP Header Configuration.
New Design for Active Facets
August 2024 User Experience, Accessibility & InfrastructureURM-221053
The UI for active facets was redesigned for better clarity and efficiency in narrowing down and viewing the search results. This applies to PO lines, resource sharing requests, sets and relevant searches such as Physical holdings.
For more information see Facets.
Indication of Active Facets in Collapsed Panel
August 2024 User Experience, Accessibility & Infrastructure
URM-217686The collapsed facets panel now indicates the existence and the number of active facets. This applies to PO lines, resource sharing requests, sets and relevant searches such as Physical holdings.
If you hover over the collapsed facets bar, a tooltip displays the selected facets.
An indicator and tooltip also appear for Library Scope (LS) in relevant search results such as Physical holdings.
For more information see Facets.
Green Dot in Filters
When a non-default filter is selected, a green dot appears next to the filter icon to indicate that the results displayed on the page are not the default ones (for example My Sets instead of All sets). This is useful for sticky filters - when the user accesses a page that has a non-default filter selected, they will get a visual cue that the that a non-default filter is selected.
In addition, the Clear All button was added to clear all the filters and set them back to the default.
This applies to PO lines, patron services and sets.
For more information see Layout 2022.
Arrangement of Header Icons in Responsive Mode
August 2024 User Experience, Accessibility & Infrastructure
The icons in the header were updated to adapt in a more responsive way when resizing the page.
For more information see Task List.
User Level Configuration of Alma Color Scheme
The Alma Color Scheme can now be configured on the user level, not just the institutional level. Users will be able for example to select a different color scheme for Production and for Sandbox, for easy differentiation between them.
For more information see User Interface Settings.
Display Related Requests for Libraries
August 2024 User Experience, Accessibility & Infrastructure
You can now view the request/s related to a specific library. This is useful for example when the user wants to delete a library, and they need to first handle the related requests. This tool is available at Configuration > General > Add a Library or Edit Library Information > Libraries.
For more information see Configuring the Institution and Its Libraries.
Next Year Option For Calendars
The Next Year button was added to all calendars where future dates are available, for example when creating or updating an invoice line..
Search Sets by User Name
In the Created by option for searching in sets, the user name (First name or Last name) is now included in the search results. This is in addition to the user Primary Identifier that was already supported.
Truncated searches are supported so that users can use an asterisk ( * ) wildcard character to search for a string that begins with the searched characters. For example, search for “gr*” to search for “green” along with “grady”.
For more information see Managing Search Queries and Sets.
Improve UX Usability of Advanced Search
When adding a rule in the advanced search using a mouse, the focus now moves automatically from the + button to the search box of the first field in the new rule, saving the user the extra click. For keyboard users the focus remains on the + button as required by accessibility guidelines.
For more information on using the advanced search see Searching in Alma.
Recent Searches Support All Search Types
The Simple and Advanced search now support recent searches for all search types, including for example Order Lines, Holdings, Users, Licenses, Reading Lists, Requests, etc.
For more information see Searching in Alma.
Open ID Connect in Base64
You can now configure your Open ID Connect authentication protocol to encode the state parameter in Base64 instead of using URL-encoding.
For more information see OpenID Connect and the Developer Network.
Enhanced Role Selection for Analytics Objects
The feature to select the roles that have access to an analytics object was enhanced. You can now open a dialog box and select the roles with which you want to share the analytics object . The roles are categorized to make it easier to find specific roles. You can select all of the roles in the category or select specific roles within a category.
For more information, see Sharing Analytics Objects with Other Users.
Pin Analytics Objects to Selected Roles and Users
You can now configure analytics objects to be pinned for all users and roles for whom the object is shared. Previously, users had to pin the objects themselves. By allowing administrators to pin shared analytics objects, this enhancement provides greater control and sharing capabilities. Additionally, it saves the user from having to pin objects themselves that the administrator believes are valuable.
To support this feature, the new Pinned to Selected Roles / Users toggle was added to the Analytics Object List page:
When this option is set to active, the object is marked as pinned in the Analytics Object List and appears under the Analytics menu for all users and roles for whom the object is shared. The user can unpin an object that was pinned by the administrator.
Under the Analytics menu, there are now two sections for pinned objects:
- My Pinned Analytics – the objects that the user pinned
- Analytics Pinned by Admin – the objects that were pinned by an administrator by selecting the Pinned to Selected Roles / Users toggle
For the objects pinned by the administrator, you can select the Pin icon to move it to the My Pinned Analytics list or select the X to delete the object from the list.
For more information, see Working with Analytics Objects and Navigating Analytics.
Support Multi-Factor Authentication (MFA)
It is now possible to configure Alma to recommend (or enforce) the use of multi-factor authentication (MFA). In addition to the regular user and password screen, the user will receive an email with a login link.
For more information see User Management.
Data Type and Section Type Added to Usage Data (COUNTER) Subject Area
The Data Type and Section Type fields were added to Usage Data (COUNTER) > Usage Data Details Release 5. They display the section type and data type of the COUNTER master reports and allow users to differentiate between journal titles and eBook titles.
For more information, see Usage Data Details - Release 5.
New Linked Open Data Dimension Added to Analytics
The new Linked Open Data dimension was added to the Titles subject area of analytics. It contains the following fields that are relevant to the new BIBFRAME metadata schema:
- Has Work – indicates that the bibliographic record has Work
- Instance URI – the Uniform Resource Identifier (URI) that identifies the instance
- Work MMSID – the MMS ID for the work of the instance
- Work URI – the Uniform Resource Identifier (URI) that identifies the work of the instance
In addition, the measure field, Num of Titles (Instances) with Work, was added to the Title Measures dimension. It measures the number of titles with a related work.
For more information on the Linked Open Data dimension, see Linked Open Data.
For more information on BIBFRAME, see BIBFRAME Support.
New Preferred Contact Information Fields For Vendors
The following preferred contact information fields were added to the Vendor dimension in the Funds Expenditure, Licenses, Purchase Requests, and Usage Data (Counter) subject areas. They display the default contact information used for the account.
- Preferred Address
- Preferred Address Note
- Preferred Email
- Preferred Phone Number
In addition, the Primary Product URL field was added to these locations. It displays the URL with URL type Primary Product. If there is more than one primary product URL, only one is displayed.
For more information, see Vendor.
Additional Local Parameter Fields Now Available
An additional 20 local parameter fields were added to the Bibliographic Details dimension in all subject areas in which it appears (for a total of 30 local parameter fields). These fields allow you to use customizable fields in your reports. Note that you must contact Ex Libris Support to add these fields.
For more information, see Local Param 1-30.
BIBFRAME Support
May 2024 Linked Open Data
Alma is a multi-format system that supports BIBFRAME Works and Instances. Records in this format are seamlessly integrated into Alma's workflows, including resource management, acquisition, fulfillment, and discovery support. For detailed insights into Alma's capabilities for managing BIBFRAME records across its diverse sections and functionalities, see BIBFRAME Support.
Filtering for History in User Details
User history that is accessed from the History tab of the User Details page, is now filtered by default to show changes from the last 30 days. Additional filtering options are for 7 days, one year, or an unfiltered view.
For more information see Viewing Changes to the History Tab.
Lender not Assigned if Locate Fails
This release introduces the rs_do_not_send_request_when_locate_fails configuration option, enhancing borrowing partner management. Should a borrower face technical issues locating a resource at the lender (for example, connection problems), this functionality automatically removes the lending partner from the borrowing rota to streamline the process.
For more information see Locating Items for Resource Sharing.
Define whether Fees are Automatically Moved to the Patron
Previously, when borrowing institution marked an item as lost, the request was changed to lost communicated and no fines and fees were applied to the lost loan. The lender received a message regarding the lost item, and they had to manually send a message with the fines and fees that would be applied to the borrowing institution. The borrowing institution had to manually add the fines and fees to the patron. Now, the borrowing library can set this this automatically based on the loan terms of use (TOU), by using the rs_use_tou_for_lost_item parameter.
For more information see Managing Lost Loans and Lost Workflow Action.
Improved Facets in Borrowing and Lending List
A number of improvements were implemented for facets in the borrowing and lending lists. These include a search feature to find facets in the list, the ability to customize facets and also to exclude facet values in the borrowing and lending lists.
For more information see Facets.
ISO 18626 Peer to Peer Communication with Tipasa/WS ILL
It is now possible to set a Tipasa or WS ILL partner as a peer to peer partner using the ISO18626 setup.
Setting the Tipasa/WS ILL requires setting up the partner record in Alma with:
- The partner’s symbol in the Symbol field
- The OCLC server URL
- An API Key provided by OCLC. Please contact OCLC to obtain this key.
For more information see Tipasa, WorldShare ILL, and Relais Parameters.
Auto Renewal After Due Date
May 2024 Fulfillment and Resource Sharing NERS Enhancement (ID# 8345) URM-194910
It is now possible to auto renew loans for which the block has been removed, even if the block was removed after the due date.
For more information see Configuring Fulfillment Jobs.
Configure Translation of Letters Available for Patron Opt-In/Out in Primo
Libraries that enable patrons to use Primo to select letters for opt-in/out can now configure and translate the letter names.
For more information see:
Homosaurus Vocabulary Added to the AlmaRefine Cloud App
Alma has now added the linked data Homosaurus vocabulary to the AlmaRefine cloud app. This now makes it possible to reconcile against the vocabulary in Alma using AlmaRefine.
For more information on the Homosaurus vocabulary, click here.
For more information on the AlmaRefine cloud app, click here.
For a blog on "How to use the Alma Refine cloud app for service Homosaurus", click here.
Linked Open Data Enrichment Configuration
Organizations have the capability to customize linked data enrichment for MARC records. They have the flexibility to select the authorities they wish to enrich and designate the appropriate subfield ($0 / $1). Additionally, they can opt to incorporate VIAF URIs and include supplementary authorities for enrichment, such as local authorities supporting URIs. This feature empowers institutions to exercise enhanced control over the linked data enrichment process for MARC records.
For more information, see Linked Data Enrichment Configuration.
Local Authority Indication in Browse Authority Headings
Libraries that manage local authority records as part of a global vocabulary can now see if an authority record is a local record they've created. This is useful when libraries want to identify and maintain their overriding local authority records, as authority vocabularies change.
For more information, see Adding a Local Authority Definition.
Prominent Indication When Editing a Community Record
The Metadata Editor now prominently highlights when a record being edited is a Community Zone record. Additionally, a warning message has been incorporated to alert users before saving changes that could affect the community. This precautionary measure is implemented to prevent librarians from inadvertently modifying a community record when their intention is to manage local information exclusively.
For more information, see Editing Community Zone Bibliographic Records.
Search by Standard Number in External Search Resources
A new field, Standard Number, is available for searching in Alma External Search Resources. For more information, see Working with Search Resources in the MD Editor.
Searching by Standard Number in External Search Resources depends on whether the Standard Number field is supported by the system that manages the search target.
Metadata Management Index Updates
New Authority Search Indexes by 885 Field
New Source of Description Note Search Index
URM-212604
Semi-Annual Re-indexing
URM-186774
- Retrieval of LOD Enriched MARC Record, see here.
- BIBFRAME Records Are Now Supported in the SRU as a New Record Schema, see here.
- Indexing the Full Call Number for Search and Browse, see here.
- New Source of Description Note Search Index, see here.
- New Authority Search Indexes by 885 Field, see here.
- New "General Note" Advanced Search Option Added to the Electronic Collection Search, see here.
Creating Record Versions for Changes in a Record's Management Tag
(Updated September 12, 2024) Previously, management tags like "Suppressed from discovery" were not logged in record versions, making it impossible to track when or by whom a record was suppressed or unsuppressed. With the recent update, this information will be recorded and visible in record versions. Whenever a record's management tag changes, a new version will be generated, displaying the previous tag value. Restoring a previous version will only affect the metadata, not other information on the versions page, such as cataloging level or management tags.
Record versions created before this update have null values for all management tags. The values for management tags will only be recorded when the record undergoes any subsequent update. Therefore, in the version created for that update, it may seem as though the user initiating the first update post-release "updated" the management tags to their existing values.
Record versions for Record's Management Tags are available only for showing changes that were locally done. For seeing locally done changes for Community Zone records, select View Versions of Original Record.
For more information, see Working with Records > View Versions.
Indexing the Full Call Number for Search and Browse
Previously, only the first part of the bibliographic call number ($$a or $$h) was used for searching and browsing. Following this enhancement:
- Additional details appear upon accessing the browse shelf listing from a MARC21 or KORMARC bibliographic record. The Call Number editing field is automatically filled with the information from $a and $b in fields 050, 055, 060, 070, 080, 082, 084, and with the information from $h and $i in field 852. In cases where multiple instances of the same subfield are present, the first occurrence will be utilized unless the cursor is positioned on a different occurrence, in which case that one is utilized.
- After the semi-annual indexing process, data from the $b subfield of the following specified fields are included in the call number search indexes within the repository search:
- LC call number: 050, 055, 090
- Universal Decimal Class Number: 080
- Dewey Decimal Class Number: 082, 092
- Other Classification Number: 084
This feature is beneficial for librarians seeking to search for the complete call number, rather than solely focusing on the classification segment.
For more information, see:
Search Titles by the Originating System ID of the Authority Record Linked to Their Bibliographic Headings
The functionality of the "Heading Information" search has been expanded to enable searching for bibliographic records based on their heading information linked to a specific authority record. A new option, "All", has been included in the Heading Type drop-down menu. When selected, users are prompted to specify the authority record's Originating System and Originating System ID. This enhancement enables users to retrieve all bibliographic records with headings linked to the specified authority record, irrespective of the heading type.
For more information, see Searching in Alma > Search Fields > Heading Information.
Updates to MARC21 Profile
MARC21 update No. 37, December 2023 is now available for bibliographic, holdings, and authority profiles.
Physical Item Templates
Alma enables users to save an existing physical item as a template and utilize it when manually creating new physical items to pre-fill fields such as notes, item policy, material type, temporary location, and so forth.
The template will encompass all the item's details except for Barcode, Inventory number, Pattern information, Process type, At (request department), Item call number prefix/suffix, and Temporary call number prefix.
Adding a new item from a template is accessible in a holdings' items list and during the editing of a holdings record in the Metadata editor. The new item will open as a draft, enabling the operator to make necessary adjustments before saving.
Note that content indicators on the tabs only appear after the item is saved, not in draft mode.
Furthermore, you can select a template to use in the Add Physical Item quick cataloging form, that automatically populates the item created by that form with the template's data.
Once an operator selects a template to work with, Alma remembers the selection for the user, reducing the need to select a template repeatedly, unless there's a change in the types of items being created.
This functionality is particularly beneficial for physical inventory operators who frequently create similar items, streamlining the item creation process and enhancing efficiency.
For more information:
- Quick Cataloging - use an item template when manually adding a physical item, see Working with Items > Adding a Physical Item to an Existing Title.
- Item List - manually adding an item from the holdings' items list and applying a template, see Working with Items > Working with the List of Items.
- Metadata Editor - add an item record to the holdings record by using a template, see Add Item from Template.
Option to Disable the Link Resolver Usage Indication in Search Results and in the Overlap Analysis Tool
Alma has added a customer parameter (allow_link_resolver_usage_indications) in Configuration > Resources > Other settings that allows users to disable the Link Resolver Usage indication in search results and in the Overlap Analysis tool. The default value for the customer parameter is set to true. When set to true, data about "link resolver usage" indication in search results and the Overlap Analysis tool is available. When set to false, data about "link resolver usage" in search results and the Overlap Analysis tool will not be available.
For more information, see:
- For customer parameter information, see Configuring Other Settings (Resource Management).
- For a general description on the way Link Resolver Usage is calculated, see Link Resolver Usage.
Automatic Upload Electronic Holdings Updates
Automatic Upload Electronic Holdings from JSTOR (Books)
Automatic Upload Electronic Holdings from Preselect
URM-202178
Automatic Upload of Electronic Holdings from Project Muse Now Includes Gratis Content
URM-210936
Automatic Upload of Electronic Holdings from Taylor & Francis is Now Based on Unique ID
New General Note Advanced Search Option Added to the Electronic Collection Search
May 2024 Electronic Resource Management Idea Exchange
This feature will be gradually available during the release as it requires indexing of the collections and services. The search indexes will appear but the result may not reflect the actual status during the first few days of the release.
Two new advanced search options were added to the Electronic Collection Advanced search option:
- Notes tab - General Notes (Electronic Collection)
- Notes tab - General Notes (Service)
These two new options enable users to locate text populated within the "General Notes" section (under the "Notes" tab) for both Electronic Collection and Service.
The name of the existing "Notes tab" search index, which resides under the Electronic portfolio advanced search, was modified to "Notes tab - General Notes" to be consistent with the two new search indexes. This name change has no other implications and the search index will keep functioning as it did.
For more information, see Search Indexes > Electronic Collections.
Digital Titles No Longer Require Collections
The requirement for digital titles to be part of a collection is now optional. If you want your institution to be able to create and maintain digital titles without them being part of a collection, contact Ex Libris Support to enable this feature.
MODS Schema Now Available for Metadata Forms
Forms consists of a template of fields to be used when creating digital titles. You can now create forms based on the MODS metadata schema. For more information, see Working with Forms.
Multi-Language Captions Now Available
- The Captions Management dialog box that appears when selecting Captions for a video file was enhanced. It now allows the uploading of multiple caption files and a drop-down list of languages, so you can assign a language to the captions file.
Captions ManagementYou can configure only one captions file per language.
- When adding files to a representation, you can include multiple files with different language extensions, such as captions.vtt.en, captions.vtt.fr, and so on. Alma allows you to select from the various caption languages in the supported viewers.
- The Digital Viewer and Universal Viewer support multi-language captions. When viewing a video file, select the language of the captions you want by selecting the closed captions icon at the bottom of the viewer.
Captions Language
For more information, see Managing Digital Files from the Digital Representation Resource Editor and The New Digital Viewer.
Quick Ordering from Amazon
Previously, when ordering a resource from Amazon, users needed to access Alma in order to record the order information. Now with the new Order It! browser add-on, the user can easily create the order automatically in Alma directly from Amazon.
Permanently Delete Licenses in Alma
From now, the Delete action will permanently delete a license from Alma. In addition, the Deactivate action was added, enabling the user to keep such licenses in the list, with the new "Inactive" status. The Activate action was added to licenses in the Inactive status, enabling users to quickly set the license to the Active status. Previously deleted licenses which up until today had the "Deleted" status, will now have the "Inactive" status.
If a shared license was distributed to members and was then deleted in in the network institution, it will be 'detached' from the network institution and will continue to be managed locally in the member institution. For more information, see Managing Licenses and Amendments.
The delete license API will continue to function as today by default. The only difference is that instead of setting licenses to the “Deleted” status it will change them to “Inactive”. A new query parameter was added: <permanent delete>. It is set to false by default. When true, it permanently deletes the license from Alma.
For more information, see the Developer Network.
Improvement to Usage Report Performance
COUNTER files are now manually loaded by a background job in order to improve the performance and avoid timeouts.
In addition, the Allow data overlap checkbox was added to give users more flexibility for handling cases of overlap between data in the system and in the uploaded file. When checked, existing data in the system will be overwritten with data from the uploaded file. When not checked, if there is data duplication, the entire file will be ignored i.e., it will not be uploaded. For more information see Managing COUNTER-Compliant Usage Data.
Enhancements for Sending POL Information with EDIs
When sending the Quantity for pricing for electronic PO Lines, instead of sending the value of 1 by default, the actual quantity in the PO line is sent. In addition, in the EDI Vendor Note Fields drop down list, the Access Model now appears as an option that can be selected for sending with the EDI.
For more information on working with EDI in acquisitions see Electronic Data Interchange.
View PO Lines that are Assigned to Others
Users with the Purchasing Operator role can now view PO Lines that are assigned to others. Note that users with this role will not be able to edit or take any action on such orders - only viewing is enabled.
Enhancements when Receiving from PO Line
When performing the Receive action in the PO line for Ordered Items, in the dialog box that appears, the receiving alerts now display.
In addition, the Item Call Number field was added to the Ordered Items table (disabled by default).
For more information see Receiving Physical Material.
Consortia Import Permission Per Member
May 2024 Collaborative Networks
The Consortia administrator now can control which member can import records into the Network Zone repository. For more information, see Selecting Where to Create New Bibliographic Records.
Restrict Deletion of Network Zone Bibliographic Records with Related Records and/or Local Extensions
The Consortia central office holds the authority to manage the deletion of Network Zone Bibliographic records and decide what would be the behavior in various cases. For example, when the records have related records and/or local extensions, the deletion of such records can be either blocked or a warning message is triggered to the operator.
For more information, see Restrict Deletion of Network Zone Bibliographic Records with Related Records and/or Local Extensions.
Support Parallel Work in Multiple Tabs in Internet-Browser
Alma introduces a new feature that enables users to open and login to the same Alma environment through multiple tabs. This improvement enhances productivity and efficiency by enabling users to simultaneously work on multiple workflows, for example, open records in distinct internet browser tabs, facilitating seamless copying of information between tabs and performing various tasks or workflows concurrently.
With the multi-tab capability, each browser tab is assigned a random ID, serving as a unique suffix for the corresponding session entries. This advancement facilitates the simultaneous operation of the same Alma session across multiple internet browser tabs. A user can now open and login to the same Alma environment in two or more tabs and work concurrently without one tab impacting the others.
- Multiple tabs functionality ONLY works if multiple browser tabs are opened for the same:
- Alma environment
- Logged-in user account
- An Alma session opened from "Open in a new tab", e.g. Opening a new tab in the browser by right-clicking a function in the Alma UI and selecting "Open in a new tab" will not work. Users will receive a "block" message.
- Trying to sign in as different users of the same institution simultaneously from the same internet browser (through different tabs of the internet browser on the same computer) – will not work (the last signed-in user will override the user in the other tab(s)).
For more information, see Alma Environment Multi Tabs.
Scheduling Support for Manual Jobs (Run a Job)
May 2024 User Experience, Accessibility & Infrastructure Idea Exchange NERS Enhancement (ID #8373)
Manual tasks necessitate the direct intervention of a user for execution. Tasks may need to be performed at a later time, potentially during the evening or even at night. Similarly, there is a demand for clients to schedule routine job runs, whether on a weekly, monthly, or other recurring basis.
When scheduling a manual job, the scheduled time is the time where the job run is triggered, and the actual run may start later (depending on system resources).
Alma now implements a new scheduler that users can proactively schedule jobs, whether they are periodic tasks or one-time operations. This feature enables jobs to be executed automatically, accommodating scenarios where tasks need to be performed outside regular working hours or when a staff member is unavailable to execute them manually. This scheduling enhancement is applied to all manual jobs that can be run via Admin > Manage Jobs and Sets > Run a Job. The Schedule form has been added to the last step of the 'Run a Job' wizard. For more information on the Schedule section of the 'Run a Job' wizard, see Manual Jobs.
The scheduled manual jobs are displayed in the newly added Scheduled Manual Jobs tab (Admin > Manage Jobs and Sets > Monitor Jobs > Scheduled Manual Jobs). This list enables users to manage the scheduled jobs, edit the schedule, delete the schedule and so forth. For more information on the Scheduled Manual Jobs tab, see Scheduled Jobs.
Sorting of Facets
Alma introduces alphabetical sorting for facets, providing enhanced organization.
Notably, the unified PO Lines list maintains its existing sorting for specific facets.
- Workflow step
- Creation date
- Sent date
- Renewal date
- Reporting code
Additionally, the "Library" facet within the physical holdings search retains its current configuration, ensuring that institutions configured to showcase their library first will continue to experience this feature as before.
For more information see Using Facets to Refine Search Results.
"Hebrew Fuzzy Search" Added to Alma Menu Search Bar
Expanding the functionality of the Alma search menu to include "smart" search capabilities in Hebrew. Historically, this feature has exclusively supported English. However, beginning in May 2024, it will also be extended to the Hebrew interface. Consequently, the search functionality will now offer suggestions for synonyms, interchangeable terms, and even assist with simple spelling errors. This improvement enhances user navigation, simplifying the process of locating items within the Alma Hebrew search menu.
Manage Sets Updates
Manage Sets - Toggle Active/Inactive Set in Record View and Bulk Action
Manage Sets - Implement Grid Table View
Manage Sets - Implement Quick Access
The Quick Access functionality will be gradually implemented in additional list pages that support the side-by-side mode.
- By utilizing the keyboard shortcut (period '.') or
- By selecting the last link labeled "Quick Access" situated below the sections links in the side menu section.
Support for OpenID Connect for Authentication Self Registration
OIDC based authentication facilitates self-registration, driven by the settings configured in the integration profile. This includes ongoing support for self-registration and updates using this authentication method.
For more information, see OpenID Connect in the Developers Network.
Add Countries to Country List
Institutions can now add or remove countries from the country list. For more information, see Countries.
Support Filter by Enabled/Disabled Rows in Mapping and Code Tables
Alma introduces a new "Enabled" filter in all relevant Mapping and Code Tables that incorporate enabled/disabled fields. The filter enables users to display All, Enabled (Yes) or Disabled (No) values. When filtering a table list, only lines within the relevant scope will be displayed. For instance, If the list is currently filtered by 'Disabled' and the user enables a line, the list will refresh to remove the recently enabled line. The same applies vice-versa if the list is filtered by 'Enabled'.
For more information, see Code Tables and Mapping Tables.
Springshare Integration with Alma
Alma Analytics now offers integration with Springshare Gate Counts and Reference data. This allows you to display LibInsights information in Alma Analytics reports.
To support this feature, the following enhancements were made:
- The new Springshare Integration Profile is now available to enable Alma to import data from the Springshare API.
- The new Import Data from Springshare job is available that imports the data from Springshare when the integration profile is configured.
- In Alma Analytics:
- The new External Vendor Data subject area is now available, which allows you to create reports that display information imported from Springshare LibInsights concerning Gate Counts and References. For more information, see External Vendor Data.
- The Library Services to Individuals and Gate Counts tabs were added to the ACRL and IPEDS dashboard. They display reports of the number of library services provided to patrons by method and the number of individuals entering or leaving the library, respectively. For more information, see ACRL and IPEDS Dashboard.
For more information concerning Springshare Integration with Alma, see Springshare Integration.
New Limited Design Analytics Roles
New design analytics roles are now available that give the user access to specific subject areas only. With these roles, administrators can limit users to view only the subject areas that are within their responsibility. All reports, both those in the catalog and those in the Shared with me area, are visible to users with the limited roles, but only ones in the subject areas to which they have access run successfully.
The new roles are the following:
- Designs Analytics – Fulfillment: limits access to the API Usage, Analytics Objects, Analytics Usage Tracking, Borrowing Requests, Course Reserves, DARA, Fines and Fees, Fulfillment, Lending Requests, Local Authorities, Requests, Resource Sharing, System Events, Title, and Users subject areas.
- Designs Analytics – Resources: limits access to the Analytics Objects, Analytics Usage Tracking, API Usage, DARA, Digital Inventory, Digital Usage, Digital Waitlist, E-Inventory, Licenses, Link Resolver Usage, Local Authorities, Physical Items Historical Events, Physical Items, System Events, Title, and Users subject areas.
- Designs Analytics – Acquisition: limits access to the Purchase Requests, Analytics Objects, Analytics Usage Tracking, API Usage, DARA, Funds Expenditure, Local Authorities, System Events, Title, Usage Data (COUNTER), and Users subject areas.
For more information on Design Analytics roles, see Design Analytics Roles.
Limited Anonymization of Report Details
Report details can be anonymized to protect patrons' privacy. Besides the option for anonymization of all user details, there is now an option to anonymize all user details, except for the following which remain visible in reports. This hides patron information while leaving information regarding library staff activities visible.
The following fields in the Users subject area:
- User Details > First Name
- User Details > Last Name
- User Details > Primary Identifier
- Email > Email
The fields in the following dimensions:
- Analytics Objects > Created by
- Analytics Usage Tracking > User Details
- Borrowing Requests > Assigned to
- Course Reserves > Librarian
- DARA > Assigned to
- DARA > Modified by
- E-Inventory > Electronic Collection PO Line Approver
- E-Inventory > Portfolio PO Line Approver
- Fines and Fees > Staff Operator Details
- Fulfillment > Loan Operator Details
- Fulfillment > Return Operator Details
- Funds Expenditure > PO Line Approver
- Lending Requests > Assigned to
- Physical Items > PO Line Approver
- Physical items > Receiving Operator
- Purchase Requests > PO Line Approver
- Purchase Requests > Purchase Request Approver
- Purchase Requests > Purchase Request Assigned To
- Purchase Requests > Purchase Request Creator
- Purchase Requests > Purchase Request Modified By
For more information, see Anonymizing Analytics Report Details.
Loan Measures Dimension Added to Physical Items Subject Area
The Loan Measures dimension was added to the Physical Items subject area. It contains measure fields that display the number of loans per item that were made either in the past two, three, four, five, or more than five years ago for either in house, not in house, or total loans.
For more information, see Loan Measures.
Lending Requests Returned to Temporary Location
Items that are shipped for fulfilling a resource sharing lending request are moved to a temporary location. If, before shipping, the item was already in a temporary location then, when returned, the item would revert back to the permanent location (instead of the previous temporary location). Now, the item will revert back to the previous temporary location.
For more information see Temporary Location Information.
Hold Shelf Policy for Resource Sharing Requests
To prevent items from sitting on hold shelves for extended periods of time, Alma now enables you to configure if the maximum time for an item to remain on a hold shelf before being returned to the lending library should be based on:
- Due Date for the request
- Circulation Desk Hold Shelf Expiration Time
For more information see Managing the Hold Shelf.
Display User's Loan Due Date in Borrowing Request Page
You can now display the Due Date of the loan associated with the borrowing request.
You can configure this in the Records Customization page.
For more information see Customizing the Record Display.
Sort Lending Resource Sharing Requests by Location
To efficiently organize your lending requests, you can now sort lending requests by location. After selecting Sort by: Shelving Location, when printing pickup slips, the pickup slips are printed in order by shelving location.
This is only relevant for requests that have not yet shipped.
For more information about working with lending requests see Managing Lending Requests.
Support for Visiting Patrons Functionality Using the Inn-Reach D2IR API
It is now possible to integrate Alma with Inn-Reach using version 3 of the D2IR API. This will enable using Alma and Inn-Reach in an integrated manner for supporting the Visiting Patrons workflow, in addition to the classic resource sharing requesting workflow.
For more information see InnReach API Implementation Guide.
Support Pickup Location for InnReach Requests
Alma now supports Pickup Location for InnReach requests. When a new borrowing request is created via the D2IR V3 call, the pickupLocation element is parsed. The information is used to identify the requested Alma pickup location. The location reported by InnReach must be a valid Alma location.
If there is no match to an existing location then the default pickup location of the owning Resource Sharing library is used (as is the case today).
For more information see InnReach API Implementation Guide.
Borrowing Task List — Print Slip in Bulk
The Print Slip bulk action enables the library staff to reprint received or returned slips in bulk. When multiple borrowing requests are selected, selecting Print Slip reprints all the slips.
For requests that were not received, no print slip is printed. For requests that were received but not yet returned, the Resource Sharing Receive Slip Letter is printed. For requests that were returned, the Resource Sharing Return Slip Letter is printed. When multiple items are selected, all slips that were received/returned are printed and a message appears indicating which slips were printed successfully and which slips could not be printed.
For more information see Managing Borrowing Requests.
Dismiss/Activate Notes Action in Right Pane of Resource Sharing Task Lists
February 2024 Fulfillment and Resource Sharing
Both the borrowing and the lending resource sharing task lists now allow dismissing or activating notes from within the right pane of the task list. This makes it easier to manage the request notes without having to navigate to the full Edit form.
For more information about working with notes see Managing Notes
Conditional Terms of Use for Digital Requests
Lenders that provide a document delivery service can now indicate whether the supplied document can be made available to the patron in digital form, or whether the digital content requires manual handling by the borrowing staff, such as printing a physical copy that can be shared with the patron as a non-returnable physical copy. This new option enhances copyright control by enabling the lender to specify to the borrower that the document cannot be shared with the patron. As a lender, you can enable the relevant terms from Configuration > Fulfillment > Resource Sharing > Shipping Terms of Use. By default, only the NONE term is enabled.
When the message is received on the borrower side and a term of use is selected by the lender, an alert is added to the request indicating that the request has a loan condition. The received digital file is not automatically forwarded to the patron, and the borrower request remains in a Shipped Digitally status.
In addition, the Shipping Terms Of Use condition appears in the Request information on the right pane.
For more information see Delivering Digitized Items Using the Document Delivery Page.
Resource Sharing Off Time Updates
Previously, Rapid users needed to update both Alma and RapidILL when setting their library off times. Now, when the parameter rs_update_rapid_with_lending_offtime (Configuration > Fulfillment > General > Other Settings) is set to true (default false), when updating the resource sharing library's Inactive dates range in Alma (Configuration > General > Libraries > Add a Library or Edit Library Information > Summary tab > check Temporarily inactive for lending), the date range in RapidILL is automatically updated with the data configured in Alma.
- The start date must be less than one year in the future.
- The duration cannot be longer than 30 days.
- Setting this configuration to true means that the configured inactive dates override the dates submitted using RapidILL webpages.
- The temporarily inactive checkbox remains selected after the date range until it is manually deselected.
Linked Open Data Enrichment for IdRef Authorities
The Linked Open Data enrichment process for bibliographic records that are linked to IdRef authorities now also generate URIs to the IdRef authority records. This enables libraries that work with IdRef authorities to benefit from their Linked Open Data capabilities. For more information, see Using Linked Open Data While Working with Bibliographic Records.
Retrieval of LOD Enriched MARC Record
Retrieval of a MARC record with Linked Open Data enrichment is now supported using the Bib GET API
For more information see the Developer Network.
BIBFRAME Records Are Now Supported in the SRU as a New Record Schema
The SRU protocol facilitates the search for a BIBFRAME instance, whether it is sought after as a BIBFRAME record or as a converted MARC record. Users can search for BIBFRAME records in the same manner as they do for other record types. BIBFRAME records seamlessly integrate into existing workflows and are treated as converted MARC records. This support for BIBFRAME enables the integration of Alma search with other automated systems, facilitating processes such as inter-library loan, copy cataloging, and selection.
For more information, see: SRU documentation in the Ex Libris Developers Network.
Read-Only Browse Bibliographic Headings Access
Previously, only users with roles permitting work in the Metadata Editor could access Browse Bib Headings. Now, a read-only Browse Bib Headings is accessible to all users, much like the repository search feature, offering greater access to the library's repository. This enhancement proves beneficial for users seeking to view a list of records by title, author, or subject, even without precise search terms for retrieval.
For more information, see Browsing Bibliographic Headings.
Repository Import - Limit Match of Bibliographic Records to a Specific Electronic Collection
Alma now facilitates targeted matching of incoming repositories specifically to a chosen electronic collection and not the entire catalog. This ensures avoidance of multiple match events, enhancing data accuracy, and simplifying management processes.
For more information, see Creating/Editing an Import Profile: Match Profile.
Option to Publish Entire Bibliographic Records Repository
Institutions now can efficiently export the complete content of their bibliographic records through a newly introduced general publishing option. This enables users to customize pertinent publishing profiles that encompass the entire repository. This option is activated by a new checkbox, Publish the entire repository in the General Profile configuration page.
This option is relevant only for bibliographic-level publishing.
For more information, see Creating a General Publishing Profile.
Filtering Holdings Sets Using Indication Rules
Alma users can now apply indication rules to filter collections of holdings records either during the process of saving a holdings search or by utilizing the "Filter Set" feature on the Manage Sets page. Additionally, when generating indication rules through a form, it is now feasible to create rules based on the metadata of holdings records. This functionality proves especially beneficial for libraries aiming to refine their holdings sets using metadata not included in the search indexes.
For more information, see Creating a Form-Based Indication Rule.
Exporting Bibliographic Rank in the General Publishing Profile
Within the General Publishing Profile, there is now a feature allowing the inclusion of the Bibliographic Rank as part of bibliographic enrichment. To enable this, mark the "Add Management Information" checkbox, provide the repeatable field where you want the enrichment placed (if not already configured), and indicate the subfield for inclusion of the bibliographic rank.
For more information on the bibliographic rank, see Bibliographic Ranking in Metadata Editor.
For more information on the general publishing profile, see Publishing and Inventory Enrichment (General Publishing).
Deletion of Community Zone Originated Records
Previously, users were able to remove a Network Zone bibliographic record from their institution tab, given that the record is created within the network zone or has a "Held by" indication. However, deleting a record that originated from the community zone was not enabled. Users are now able to delete a Network Zone bibliographic record from the Institution/Network tab, even if the record has its origins in the Community Zone.
For more information, see Deleting Bibliographic Records.
New Save and Receive Action Added to Item Editor
A recently introduced functionality, the Save and Receive action, has been incorporated into the "Physical Item Editor" page in Alma. This action will be accessible under the following conditions:
-
Users possessing Receiving Operator/Receiving Manager roles for the owning library of the Purchase Order (PO) line, and/or users with Receiving Operator/Receiving Manager roles for a library designated as "acquire for" the owning library of the PO line.
-
When the "Receiving date" field is unfilled, and the "PO line" field is populated.
This feature enables users to work on an item (in the Item Editor), save and receive the item in a single action. Upon selecting Save and Receive, a dialogue window is displayed enabling users to fill in the receiving date and choose whether to keep in department.
The department listed under "Currently At" directly impacts the ability to save and receive the item; an error occurs if the user is not in the correct department. Furthermore, the values shown in the "Next step" field within the dialogue window correspond to the "Currently At" department.
For more information, see Updating Item-Level Information.
Configurable Physical Item Condition
Libraries now can customize the selection of physical conditions available for describing items in the physical item condition field. This feature proves beneficial for libraries seeking a more diverse range of terms to accurately depict the physical condition of their items.
For more information, see Configuring Physical Item Condition.
Pre Release Indication for Upcoming Community Zone Collections
This will be released gradually during March 2024.
A new Pre Release indication is now displayed for Electronic Collections that are currently in the process of being added to the Community Zone by the Ex Libris content team. This proactive feature enables customers to stay informed about the most recent content additions, eliminating the necessity to contact Ex Libris or provider support teams for updates.
- The Pre Release indicator only appears for Community Zone Electronic Collections.
- For Electronic Collections that are Pre Release, all actions other than the "Portfolio list" are disabled.
- All Community Zone Portfolios under "Pre Release Electronic collections" also have a "Pre Release" indication and will have their actions disabled.
- Community Zone Titles that only have Pre Release portfolios associated with it also have the "Pre Release" indication and will have their actions disabled.
For more information, see Contributing to the Community Zone – Local Electronic Collections.
Automatic Upload Electronic Holdings from Taylor & Francis (Journals)
Libraries can now easily update their holdings for Taylor & Francis Journals through the Automatic Upload of Electronic Holdings feature. When activated, this process automatically downloads a file with your holdings information from the Taylor & Francis platform in a standardized format, and then updates your holdings in the Taylor & Francis collection. This integration eliminates the need for manual updates when the Taylor & Francis side makes changes.
Obtaining the token ID for the Journals integration will be available in the Taylor & Francis site from February 13.
The following Community Zone collections should be activated in order to utilize the automated process for journals:
- (Journals) - Taylor & Francis Current Content Access (Community Zone Collection ID = 611000000000002216)
- All portfolios that are updated from the various upload electronic holdings integrations modify the portfolio as "Available".
- All portfolios are activated from the Community Zone.
- A portfolio that is not found in the Community Zone, will not be created locally. The job only activates matching portfolios from the Community Zone.
For more information, see Upload Electronic Holdings from Taylor and Francis.
Collection-Level Access Model Setting
Users now have the capability to establish an access model at the collection level, with all portfolios within that collection automatically adopting it. This functionality is especially advantageous for libraries employing auto-activated collections, ensuring that each new addition seamlessly inherits the access model.
This empowers users to define and oversee access models at the collection level, promoting a consistent and efficient approach to portfolio discovery.
For institutions that have the "Ebook Central Perpetual, DDA and Subscription Titles" Collection activated from the Community Zone and have the "Upload Electronic Holdings" integration enabled with "ProQuest Ebook Central", the new "Electronic Collection Access Model" field will be disabled.
For more information, see Managing Electronic Resources.
Overlap Analysis Tool Now Presents Link Resolver Usage Data as Part of the Report
The Overlap Analysis reports have been updated with the addition of two new columns:
- Link resolver usage (access)
- Link resolver usage (appearances)
Dedicated columns have been incorporated into Electronic Portfolios within the report to showcase the Link Resolver usage of each portfolio. This data mirrors the information available in Alma analytics and can be accessed from the Alma UI under portfolio search results in the "Other details" section.
The "Analysis information" tab in the Excel report generated through the overlap analysis has been improved to display usage range information, consistently covering the past 12 months.
This enhanced information is valuable for librarians as it provides insights into the portfolio's usage, aiding in the assessment of its overall value.
If a portfolio has no associated usage, irrespective of whether it is from the Community Zone or any other portfolio, the report will display N/A as the indication.
For more information, see Overlap and Collection Analysis Reports.
Master Usage Type Renamed to Primary
As part of our continuous efforts to promote Diversity, Equity, and Inclusion and to remove any unintentional bias from our system, the digital representation Usage Type of Primary is now supported when using a CSV file to import the metadata for digital bibliographic records as well as in APIs and when using the SRU protocol. Note that Master is still a supported value for backward compatibility purposes.
OAI MODS Now Supported for Remote Digital Repositories
OAI MODS format is now supported for importing digital bibliographic records from remote digital repositories. To support this enhancement, the following changes were made:
- When configuring a remote digital repository (Configuration > Resources > Record Import > Remote Digital Repositories), OAI MODS is now available as a format. Note that you must select Other for the remote system type for this option to be available:
Remote Digital Repository Details - Format MODS
For more information, see Managing Remote Digital Repositories.
- When configuring a digital import profile (Resources > Import > Manage Import Profiles) and selecting a remote digital repository instance with OAI MODS configured as the format, the Source format and Target format fields are filled in with OAI MODS:
Import Profile Details for MODS Remote Repository
Digital Viewer Now Supports ePub
The Digital Viewer now supports the display of files in ePub format.
Collection Type Now Changeable
You can now change the collection type of a collection from logical to fixed-list and from fixed-list to logical. You can do this by selecting or clearing the Logical Collection checkbox when editing a collection. (Previously, this was non-editable.) When a logical collection is changed to a fixed-list one, the titles in the collection are changed to a fixed list and are no longer updated. When a fixed-list collection is changed to a logical one, you must add a logical set to the collection. A job updates the titles of the collection according to the set.
For more information on Collections, see Managing Collections.
Update Record Identifier with MMSID Task for MODS Now Available
The task updates the recordIdentifier element with the Alma MMS ID.
When adding this task to a process, an option is available to record the change in the recordinfoNote element under the recordIdentifier element.
Select the checkbox to have the change recorded as a note in the MODS record.
For more information on MODS normalization processes, see Working with MODS Fields, Normalization, and Validation.
Download All Files in Representation
You can now download all of the files of a representation with one action. To support this feature, a Download All link was added to the Digital Representation Resource Editor.
Selecting the Download All link saves the files of the representation to a zip file on your computer. If the total download size is very large, the new Download Digital Files job runs and downloads the files to an external server. (You can monitor the job from Admin > Manage Jobs and Sets > Monitor Jobs.) When the job finishes, you are sent an email with a link to download the files.
MODS Enhancements
The following enhancements were made to the Alma and Primo search and display fields for MODS records:
- Update to Alma search keywords:
- <physicalDescription><form> is searchable under the title’s Other Physical Details keyword.
- <physicalDescription><digitalOrigin> , <originInfo><dateOther> , <originInfo><dateCaptured> without iso8601 encoding, <language><languageTerm> with attribute type equals text is searchable under the title’s Notes keyword.
- <language><languageTerm> with attribute type equals code is searchable under the title’s Language keyword.
- <identifier> with a type attribute value that is not already mapped today (for example, not isbn, issn, ismn) is searchable under the title’s Standard Number keyword. The type attribute value is searchable under the Standard Number Source keyword.
- <location><holdingSimple><copyInformation><sublocation> is searchable under the title’s Sublocation keyword.
- <relatedItem><location><url> is searchable under the title’s Electronic Location and Note keyword. <location><url> is already searchable.
- Update to Primo display:
- <location><url> and <relatedItem><location><url> elements are displayed under the Links section in Primo.
- <physicalDescription><form> and <physicalDescription><interentMediaType> are displayed under the title’s Physical Description / Format field.
- <language><languageTerm> with attribute type equals code is displayed under the title’s Language field.
- Update to Primo search:
- <language><languageTerm> with attribute type equals code is searchable under the title’s Language keyword.
- <originInfo><dateOther> , <originInfo><dateCaptured> without iso8601 encoding, <identifier> with a type attribute value that is not already mapped today (for example, not isbn, issn, ismn) is searchable under the title’s General keyword
- For display and indexing purposes, in Alma and Primo, a colon is added to the bibliographic title between the <title> element and the <subtitle> element.
Rollout of the New Layout for the PO Lines Task List
The new, next-generation, Alma UI design is available for the PO Lines task list. In this release, the new UI is automatically set as the default for all users, with no option to opt out.
For a general overview of the new PO Lines task list, see New Unified PO Line Task List. See also Searching for PO Lines - New Layout; Managing PO Lines - New Layout.
For more information see the New Unified PO Line Task List in the Alma 2023 Roadmap Webinar Series.
There is a known issue with saving a faceted PO lines list as a logical set with the following facets:
- Owner
- Assigned user
- Vendor account ID
- Creation date
- Sent date
- Renewal date
The issue will be corrected as part of the March 2024 release. Until then, we recommend to base logical sets on advanced search query results and not on facets.
Improvement to the New Layout for PO Lines
Some improvements were implemented to the new layout for PO Lines.
- The existing Material Supplier and Fund fields were enhanced to allow users to select the value from a list which opens in a sliding panel. This is in addition to the existing option of selecting a value from the dropdown menu or typing the name of the vendor/fund.
The Change Vendor dialog box will not have the option to select a vendor from a list within a sliding panel.
-
There is now a default action in the confirmation pop up when selecting Save or Save and Continue. This saves the user from having to explicitly select the common action.
-
Changes in the PO line (such as change of material type) are now reflected in the related inventory. This is similar to the behaviour in the old layout.
-
Save and Continue is now considered to be a main action and appears more prominently on the right hand side with the institution theme color.
For more information see Editing PO Lines.
Enable Users to Keep in Department when Receiving Items from a PO Line
When performing the Receive action in the PO line for Ordered Items, a dialog box now appears enabling users to update the receiving information.
For more information see Receiving Physical Material.
The department listed under Currently At directly impacts the ability to receive the item from the PO line; an error occurs if the user is not in the correct department. Furthermore, the values shown in the Next step field in the dialogue window correspond to the Currently At department.
Bulk Deletion of COUNTER Reports
Previously when deleting COUNTER reports, users needed to delete them one by one. Now, before deleting COUNTER reports, users have an option to select multiple reports for deletion. In addition, the Select All and Delete All options were added.
This functionality is only available to the Usage Data Operator role.
For more information see Manually Uploading and Deleting COUNTER Data.
Receiving Workbench - New System Event (Webhook) for Receiving Continuous Materials
Alma Integration Profile type "Webhooks" (Configuration > General > Integration Profiles) was enhanced with a new event. This event is called Receive - continuous PO line.
When selected, an event will be triggered in the following cases:
- From the receiving workbench select the Continuous tab and then the Manage items screen. Then select Receive in the row actions menu. As a result, an event is sent for the selected item.
- From the receiving workbench select the Continuous tab and then the Manage items screen. Select multiple items and then Save & Receive in the row actions menu. As a result, an event is sent for each item which was selected.
- From the receiving workbench select the Continuous tab and then the Manage items screen. Select Receive new items.
An event upon receiving will only be triggered for an item received from the Receiving WB in the Continuous tab. The One-Time tab will not trigger an event when an item is received.
For more information see Webhooks.
Top Right Menu in Alma Now Supports 'Alt' Keyboard Shortcuts and Voice Dictation Software
Users can enhance accessibility by utilizing the 'Alt' shortcut mechanism or voice dictation software to interact with the top right menu icons. By pressing the 'Alt' key, the menu displays shortcut options, enabling users to navigate and select functions without relying extensively on mouse input.
For more information, see Global Alma Hot Keys.
For information on the keyboard shortcuts available in the MD Editor, see Metadata Editor Menu and Toolbar Options.
Letters Configuration - Easy Selection of Letter Example XML File
Previously, users had to navigate to the Letter Examples side-pane, choose the desired XML by selecting the corresponding radio button, and then click Save to pick another XML letter file for testing the XSL. Now, a new dropdown has been introduced above the XML editor, displaying all available example letters XML files. Users can effortlessly switch between files by selecting an option from this dropdown. Upon selection, the XML editor content is replaced with the information from the chosen file, and the letter preview is automatically refreshed.
For more information, see Using Example Letters for Testing.
Manage Sets List Now Customizable
Users now have the option to personalize various aspects of the Manage Sets List. This includes determining the sequence and appearance of sections and facets, as well as customizing the display of records. To begin customizing the Manage Sets List, simply select the customization icon () located at the top right corner of the page. This provides you with a range of options that enable you to configure the sections within the edit view, select the elements visible in the record view, and select the facets that are available for the list.
For more information, see Manage Sets List Customization.
Information Icon - Aria Label Enhancement
Alma now enhances the PopOver component (Information icon ) to enable support for both Click and Esc commands. When hovering over the icon, the text "More information" is revealed. Clicking the component displays more descriptive text on the focused are in the UI. Deactivating the component can be achieved by selecting the Tab button, selecting the Close icon () in the text box or clicking outside the text area. For more information, see Info Icon.
Real-Time Notification Upon Job Completion
Upon completion of a job initiated from the UI, a popup notification appears. Furthermore, all such notifications are accessible through the notification icon () on the top menu bar. Rather than repeatedly refreshing the page while awaiting job completion, you can engage in other activities, and a notification will appear regardless of your location in the UI.
For more information, see Real-Time Notifications.
Enable Filters Selection to be Sticky Cross Sessions
Previously in the Alma UI, scope filters were automatically defined by default. Consequently, every time a user visits an Alma page that was previously viewed and set with the defined filters would need to re-set the filters because the page reverted to the default settings.
To address this, Alma now enables users to define filters based on their preferences. By making the filter sticky, the recurring need to manually re-select the defined filter settings of a viewed page is eliminated.
The sticky filter feature has been implemented in the Manage Sets UI. The Scope filter, for example, is automatically saved so that the previously viewed filter settings are sticky and are saved when users re-visit the page.
For more information, see Managing Search Queries and Sets > Filtering Sets.
Customization Improvement of the New Layouts Lists
The enhancement of the latest layout lists now offers improved customization. Users are no longer required to manually drag and drop entries to conceal them. Instead, checkboxes are provided, enabling users to easily select and hide entries within the new layout lists. One instance of this improvement is found in the customization of sections for Lending Requests.
For more information, see Lists and Tables in Alma.
Recommendation for Mail Relay and Support DomainKeys Identified Mail (DKIM)
(Updated: February 22, 2024) The best practice and recommended approach is to move over to your own institutional mail relay.
Gmail and Yahoo announced that emails lacking DKIM signatures may be flagged as spam.
DKIM support is applicable to all email service providers and not just subject to Gmail and Yahoo.
DKIM, or DomainKeys Identified Mail, serves as an email authentication method specifically designed to identify fraudulent sender addresses in emails, addressing the issue of email spoofing.
It is strongly recommended to configure DKIM, especially for institutions sending emails to Gmail and Yahoo addresses. Additional email service providers are expected to follow up with similar practice in the near future.
The following instructions are relevant for institutions that have configured the Mail-Handling integration profile to utilize "Send directly from Ex Libris" while using their own domain, at the 'SMTP EnvelopeFrom address' field (as opposed to the @exlibrisgroup.com address):
Institutions that use Ex Libris’s mail relay and wish to continue using it, should configure DKIM to ensure their emails remain trusted and mitigate the risk of your emails being treated as spam.
Once the DKIM functionality is activated for your institution, the Mail-Handling Integration-Profile will include support for DKIM digital signatures in outgoing emails. Configuration instructions can be found here.
If your institution cannot undertake any of the above, please reconfigure your Mail-Handling integration profile to "Send directly from Ex Libris" and set the 'SMTP EnvelopeFrom address' field to <your_user>@exlibrisgroup.com
For more information, see:
SAML and CAS Now Available as Authentication Methods for Analytics Reports
You can now configure Analytics to use SAML and CAS as authentication methods when accessing the report URL from analytics objects. To configure SAML or CAS as the authentication method, set the analytics_auth_method parameter (Configuration > Analytics > General Configuration > Other Settings) to SAML or CAS.
Configure Custom HTTP Header to be Sent with Webhook Requests
Users can now optionally configure a custom HTTP header to be sent with each webhook request. The header name and value should be separated by “:”
For more information see Webhooks.
View Full Workbook in Analytics Link Added to DV Homepage
When a Data Visualization dashboard is added as the Alma homepage, only one tab of the dashboard is displayed. To display the full DV workbook, a new View Full Workbook in Analytics link was added to the bottom of the homepage. Selecting the link opens the DV dashboard within Alma Analytics, allowing access to all of the workbook tabs.
For more information on configuring a Data Visualization dashboard as the Alma homepage, see To select a data visualization (DV) workbook to be displayed as the Alma homepage.
Physical Books Retention and Physical Books Deselection Dashboards Now Available
The Physical Books Retention and Physical Books Deselection data visualization dashboards are now available under the Alma > Inventory folder. These dashboards provide collection managers with insights on the uniqueness and redundancy of the physical book items in the institution. The dashboards display visualizations of physical book data according to different cross-sections such as classifications, libraries, and marked for retention. In addition, there are tabular reports for in-depth analysis.
- Physical Books Retention
The Physical Books Retention dashboard is designed to provide insight about single book items in the institution and possible actions they require. For example, identifying items that must be committed to retain by the library holding them. Data is derived from Physical Items, Titles, and Fulfillment subject areas.
Physical Books Retention - Physical Books Deselection
The Physical Books Deselection dashboard is designed to provide insights about items you may want to deselecting due to low usage or alternative ways to receive the title. Data is derived from the Physical Items, Titles, and Fulfillment subject areas.
Physical Books Deselection
For documentation on the dashboards, see the Documentation tab of each dashboard as well as the information on each individual report tab.
These dashboards were added as out-of-the-box objects to the Alma menu for the following roles: Analytics Administrator, Designs Analytics, General System Administrator, Physical Inventory Operator, and Physical Inventory Operator extended.
Update to the URL Used for auto SUSHI Harvest from Ebook Central
January 2024 Acquisitions
Update January 10, 2024: The following three certified SUSHI vendors (COUNTER release 5) were updated with the new URL:
- ProQuest Ebook Central
- Ebook Central
- Proquest LibCentral
New URL: https://bookservice.proquest.com/anr/release/sushi/ebooks/r5
Institutions that have an account linked to one of these certified vendors, will get the update automatically. If an “override URL” was entered by the institution, the override URL will still be used.
Institutions that defined a local account that is not linked to a certified SUSHI vendor, will need to update the URL manually. The old URL still works for now and will need to be updated by February 28, 2024, at the latest.
Additional Enhancements
- November 2024 Linked Open Data URM-227621
The Linked Data enrichment configuration now prevents the activation of multiple URI structures for the same vocabulary code. If an attempt is made to activate more than one URI structure, an error message is displayed. For more information, see Linked Data Enrichment Configuration. - November 2024 Metadata Management URM-226848
When editing a community record, the alert pop-up is now updated at the community's request. The alert now reads: "You are about to update a Community record. Your edits will affect all Alma customers. Do you still want to save these changes?". For more information, see Editing Community Zone Bibliographic Records. - November 2024 Metadata Management URM-230056
When working in the new titles search UX, record customization now enables adding NAL (National Agricultural Library) call numbers to the displayed metadata in the search results. For more information, see Customizing the Display of Records. - November 2024 Electronic Resource Management URM-230089
The JSTOR autoholdings process now incorporates a verification step to ensure the completeness of KBART files retrieved from the publisher. This enhancement prevents the accidental removal of holdings due to incomplete data. If a partial file is detected, the system will automatically retry the process. This update mitigates the risk of updating the JSTOR autoholdings collection based on incomplete information.
Future plans include expanding this verification process to additional content providers.
For more information, see Upload Electronic Book Holdings from JSTOR. - November 2024 Acquisitions URM-225296
Three additional fields are now supported in the Legal Deposit Claim Letter: Material type, MMS ID and Frequency. In order to see them, they need to be added to the letter XSL. - November 2024 Acquisitions URM-217761
An option to search the currency dropdown field appears when there are five or more currencies. This appears in the PO line edit form, as well as in the PO line Change Currency action. - November 2024 Acquisitions URM-230026
Amazon.jp was added to the list of supported platforms for Order It! See Ordering from Amazon with the Order It! Plugin for more information. - November 2024 Acquisitions URM-230026
Some fund updates require re-indexing of all the related PO lines. In the past this was done online, immediately after the change in the fund. However, this caused a performance issue when there were many PO lines related to the fund. Now, for fund updates, a threshold of 10 is defined. If there are up to 10 related PO lines, they are indexed immediately. If there are more, they are indexed by a background job. The triggered indexing job appears in the Monitor Jobs page. The user that made the updates which triggered this re-indexing appears as the operator. In addition, a message is now displayed when the indexing job is triggered for funds, invoices and vendors.
- November 2024 Analytics and Insights / Collaborative Networks URM-229657
The following enhancements were done in the Portfolio Details for Consortia Members folder located in the E-Inventory subject area to support consortia members and networks with analyzing Network Zone e-resources together with institution e-resources:- The Electronic Collection Type Description field was added to E-Inventory > Portfolio Details for Consortia Members > Electronic Collection. It describes the electronic collection type, either Database, Aggregator Package, or Selective Package.
- The Electronic Collection MMS ID field was added to E-Inventory > Portfolio Details for Consortia Members > Electronic Collection. It displays the MMS ID of the collection.
- The Material Type field (E-Inventory > Portfolio Details for Consortia Members > Portfolio) was renamed to Portfolio Material Type Description to better describe the functionality of this field.
- The Electronic Collection Type field (E-Inventory > Portfolio Details for Consortia Members > Electronic Collection) was marked as To Be Deprecated as this field is not functional.
- November 2024 Analytics and Insights URM-225420
The following fields were added to a new Edition Simplified folder to the Bibliographic Details dimension in all subject areas in which it appears. These fields allow you to differentiate between editions of the same title for reporting purposes:- Edition Simplified (Combined) – the values of the Edition Simplified (Num) and Edition Simplified (Text) fields
- Edition Simplified (Num) – the number of the edition found in the MARC 250 field, simplified
- Edition Simplified (Text) – the text of the edition found in the MARC 250 field, simplified
These fields do not display all of the edition information in the bibliographic record and are only a tool for comparison and reporting - November 2024 Analytics and Insights URM-223432
The following two fields relating to Transformative Agreements were added to the Licenses subject area in a new Agreement Definitions folder:- Transformative Agreement Tokens Total – the number of articles that can be published in the agreement period
- Transformative Agreement Unlimited – indicates if the transformative agreement has a limited or unlimited number of articles that can be published in a year
- November 2024 Analytics and Insights URM-227355
The Created with AI and Enriched with AI fields were added the Bibliographic Details dimension in all subject areas in which it appears. These fields indicate if the bibliographic record of the resource was created or enriched with the AI Assistant.In addition. the Num of Titles Created with AI and Num of Titles Enriched with AI fields were added to Titles > Titles Measures. They indicate the number of titles created or enriched with the AI Assistant.
- November 2024 Analytics and Insights URM-225971
The following fields were added to Titles > Titles Details regarding item retention:- Has Item Committed to Retain – indicates (Yes/No) if the title has at least one item that was marked as Committed to Retain
- Item Retention Reasons – the reason selected for retaining the item. If there is more than one item with a retention reason, the reasons are concatenated.
- November 2024 Analytics and Insights URM-229401
The prompts of the ACRL/IPEDS dashboard were enhanced so that when a value is selected for one prompt in a tab only relevant values can be selected in the other prompts. This enhancement was implemented for the following tabs:- Library Number of Titles (Physical)
- Library Number of Titles (Electronic)
- Volume Count
- November 2024 Analytics and Insights URM-229833
The Has W1 field was added to The Other Classifications > NLM Classifications dimension in all subject areas in which it appears. When a bibliographic record has two values in the 060 field, one containing the code W1 and another with a different code, the second code is the one that appears in the NLM Classification Code analytics field. To indicate that the record also contains a W1 value, the W1 analytics field displays Yes. The presence of the W1 code in the bibliographic record indicates that the item is a journal. - November 2024 Analytics and Insights URM-231772
For POs sent automatically by Alma, the value in the PO Line Approver Primary Identifier field (Funds Expenditure > PO Line Approver) is System.The approval data is displayed for automatic POs sent from the November release date and later. - November 2024 Analytics and Insights URM-218315
The Rialto Analytics folder located under Alma was removed as it now exists under the Shared Folder along with Alma.
- September 2024 Analytics and Insights URM-223485
The labels for the Statistical Categories fields 1-9 were renamed, in all subject areas in which these fields appear, by adding a leading zero to the number. So, for example, Statistical Category 1 was renamed to Statistical Category 01. This change was done to enable sorting the field names properly. - September 2024 Analytics and Insights URM-222088
The IdP Service In Use and Failed Authentication fields were removed from every location in which they appear, since they are no longer used in Alma. - September 2024 Analytics and Insights URM-216751
The ACRL & IPEDS Dashboard was enhanced with the following improvements:- The text on several of the tabs was expanded to provide more information regarding the reports to help you configure the parameters according to your needs.
- The Bibliographic Details Material Type fields available for the reports under the Library Collection Number of Titles (Physical) and Library Collection Number of Titles (Electronic) tabs now displays a default value as appropriate for each report.
Review the available prompts and filter options according to your reporting criteria. Consider your local system settings, configurations, cataloging practices, and product usage to determine the best selection of options. This will help you avoid any duplications.For more information, see Industry Standard Reports and Dashboards.
- September 2024 Analytics and Insights URM-225168
The following enhancements were implemented for the Inventory dashboards:- To the Physical Books Deselection dashboard:
- The text of the Documentation tab now displays completely without the need to scroll.
- Filters were added to the Electronic Inventory with P tab for classifications and publisher.
- The Normalized Call Number field was added to the following tabs:
- Titles with Multiple Copies
- No Loans
- No Loans Past 5 Years
- Loan Ratio
- Physical items with E
- To improve the performance of the Physical Books Deselection dashboard and the Physical Books Retention dashboard (which are data-heavy dashboards):
- Filters are now set to include the selected criteria by default.
Include Selected Criteria
- Auto Apply filters is now set to Off by default. This means that filters you set are not applied until you select Apply.
Auto Apply Filters
- Brushing, where if you select one part of a table or visualization on the first tab, data in other tables that is relevant is highlighted, is no longer available.
- For filters, the Limit Values by option is now set to None by default. This ignores Limit Values set to Default for all filters and displays all selection values. It preserves the selection value limitations for any filters with Limit Values preferences set to Auto or <Filter Name>.Limit Values by None
- Filters are now set to include the selected criteria by default.
- To the Physical Books Deselection dashboard:
- September 2024 Analytics and Insights URM-225501
The Num of Days Accessed: Dashboards/Workbooks per User field was added to Analytics Usage Tracking > Usage Tracking Measures. It displays the number of days that a user accessed the dashboard/workbook.For more information, see Num of Days Accessed: Dashboards/Workbooks per User.
- September 2024 Analytics and Insights URM-203366
The Analytics Tracking Dashboard was enhanced with the following developments:- The Dashboard/Workbook Path field was added to the Report Details section on the Report Details canvas.
- The Dashboard/Workbook Path field was added to the Number of Errors per Report section on the Failed Reports tab.
- The Query Trend - last 2 years report on the Overview tab was renamed to Query Trend to better reflect that the time-frame displayed is configurable.
- The date format of the Data updated as of field was improved for clarity.
- September 2024 Analytics and Insights URM-228329
The Electronic Collection Material Type field previously located under E-Inventory > Portfolio Details for Consortia Members > --Electronic Collection was renamed to Portfolio Material Type (Code) and is now located under the --Portfolio dimension.
- August 2024 Linked Open Data URM-217761
When importing records from OCLC while merging based on 001 to MMS ID, if the checkbox is marked then the import will support adding a bf:idenfitiedBy with the OCLC number to the BIBFRAME instance as well. For more information, see Matching Import Profiles > Match Methods – Explanations and Examples. - August 2024 Linked Open Data URM-217761
OCLC numbers that are added to a bf:instance as part of the import will be saved unless overwritten with a different OCLC number when the record is updated via API. For more information, see Importing Records from OCLC Connexion / Record Manager. - August 2024 Linked Open Data URM-223852
Linked data enrichment configuration is accessible to users with the following roles:- Repository Administrator,
- Catalog Administrator,
- General System Administrator
- August 2024 Metadata Management URM-210399
When selected records are pushed to the Metadata Editor using Push selected to MDE, any errors that prevent the action from completing will no longer deselect the records. This ensures that librarians can still view the selected records and retry the action as needed. For more information, see Pushing Records to Metadata Editor. - August 2024 Metadata Management URM-223257
The date pickers for the Authorities Control Task List and the republish date range in publishing profiles have been updated to prevent selecting irrelevant future dates, making it easier to select the correct date range. - August 2024 Metadata Management URM-215461
GND Profile Updates: Ongoing GND profile updates:- Subfield $9 was added to field 043
- August 2024 Metadata Management URM-178839
In the link resolving process, the context object was sometimes built using information from related records. This caused general electronic services to have incorrect information. The context object now contains the main record’s data and not the related record's data. Note that this was corrected in ViewIt. For more information on Alma link resolver workflow, see Alma Link Resolver Workflow. - August 2024 Acquisitions URM-224304
When creating a new invoice from a PO or when updating the invoice number, the PO lines of that PO are indexed in order to retrieve them in the receiving workbench by the invoice number. If there are many PO lines to index as part of the PO, the indexing is run in the background and the user is notified. - August 2024 Analytics and Insights URM-221144
The Patron Expiry Date field was added to Fulfillment > Loan Details. It indicates the date that the patron's user account expires in the library that provided the loan. This is distinct from the Expiry Date field under Fulfillment > Borrower Details, which displays the date that the patron's user account expires in the institution.The Patron Expiry Date field is useful in a scenario where the patron has a long-term account in the larger institution but was given a short-term account in a specific library of the institution. In this case, this field allows you to run reports according to the expiry date for the specific library.
- August 2024 Analytics and Insights URM-221167
The Locked Out Date field was removed from analytics from all the subject areas in which it appeared, as it no longer exists in Alma. - August 2024 Analytics and Insights URM-222466
The DV Section field was added to Analytics Usage Tracking > Query Details. It displays the section of the Data Visualization dashboard that was used.In addition, the following fields in the Query Details dimension were renamed for better clarity:
- Dashboard Name was renamed to Dashboard/Workbook Path
- Dashboard Tab was renamed to Dashboard Tab/Workbook Canvas Name
- Object Path was renamed to Report Path
- Object Report URL was renamed to Report URL
For more information, see Query Details.
- August 2024 Analytics and Insights URM-185847
Two new out-of-the-box analytics objects were added to the Analytics Objects list for the Resource Sharing Borrowing Requests and Resource Sharing Lending Requests dashboards. - August 2024 Analytics and Insights URM-217524
In the Analytics object List, the default format to send scheduled reports is now Excel.
- July 2024 Analytics and Insights URM-214739
The Action Note field was added to the Bibliographic Details dimension for all subject areas in which it appears and the Holdings Action Note field was added to Physical Items > Holdings Details. These fields display information about the retention and the retention reason of the bibliographic and holdings records. For more information, see Action Note and Holdings Action Note. - July 2024 Analytics and Insights URM-216808
The Source of Description Note field was added to the Bibliographic Details dimension for all subject areas in which it appears. It displays a note used by the Community Zone with details on AI enrichment. For more information, see Source of Description Note. - July 2024 Analytics and Insights URM-218852
The Loan Due Date dimension was added to the Borrowing Requests (Resource Sharing) subject area. It contains several date related fields that enable you to create reports concerning the date that the patron must return the item to the library. For more information, see Loan Due Date. - July 2024 Analytics and Insights URM-216808
You can request that Ex Libris define local parameters under the Bibliographic Details dimension and the under Physical Items > Holdings Details. From this release, only the local parameters that are enabled and have labels defined for them appear in Alma analytics. This prevents fields that are not in use from being displayed. For more information, see Local Param 1-30 and Holding Local Param (1-10). - July 2024 Analytics and Insights URM-218479
The Preservation Status field was added to the Bibliographic Details dimension for all subject areas in which it appears.This field is relevant for customers with Rosetta and indicates the preservation status of the title in Rosetta Plus/Pro. For more information, see Preservation Status.
- June 2024 Analytics and Insights SF: 06666740 URM-216706
The DC Format field was added to the Bibliographic Details dimension for every subject area in which it appears. It displays the file format, physical medium, or dimensions of the resource cataloged in Dublin Core. For more information, see Bibliographic Details. - June 2024 Analytics and Insights URM-216245
The following tabs were added to out-of-the-box reports:- Bibliographic Records Committed to Retain to the Titles > Title level overlap analysis dashboard
Bibliographic Records Committed to Retain
- Physical Items Committed to Retain to the Physical Items > Physical Items dashboard
Physical Items Committed to Retain
These tabs display information concerning records and items that the library has committed to retain in their catalog or inventory. This is useful when several libraries pool their resources together and some of the library's items need to be retained even when internal usage is low. This is reflected in Alma Analytics to help libraries manage their collaborative collections. For more information, see Rentention Information.
- Bibliographic Records Committed to Retain to the Titles > Title level overlap analysis dashboard
- June 2024 Analytics and Insights URM-222088
The IdP Service in Use and Failed Authentication fields will be removed from Analytics for the September release in all locations in which they appear. These fields were removed from Alma long ago and are no longer relevant. - June 2024 Analytics and Insights URM-214572
The DC Classifications and LC Classifications values for physical items can now be taken from the bibliographical record and not just from the holdings record. To support this new feature, the existing dimensions in Physical Items subject area are now named DC Classifications - Holdings and LC Classifications - Holdings and two new dimensions were added: Dewey Classifications - Bibliographic and LC Classifications - Bibliographic that display the values from the bibliographic record.For all other subject areas, DC Classifications and LC Classifications values are taken only from the bibliographic record.For more information, see LC Classifications - Holdings, LC Classifications - Bibliographic, Dewey Classifications - Holdings, Dewey Classifications - Bibliographic.
- June 2024 Analytics and Insights SF: 05330510 URM-104724
The following fields were added to Requests > Request Details:- From Another Institution
- From Another Institution Circ Desk
- From Another Institution Library
These fields display the institution, library, and circulation desk from which items were requested in a fulfillment network.
- June 2024 Analytics and Insights URM-218314
The Rialto folder containing out-of-the-box reports under Catalog > Shared Folders > Alma has been marked to be deprecated and will be removed in a future release. It was replaced by a Rialto product folder directly under Shared Folders.
- June 2024 Analytics and Insights
During the month of May, OAS (Oracle Analytics Server) was updated to the latest version (7.0) in all of our data centers.
- May 2024 Fulfillment and Resource Sharing URM-199977
Support for additional actions was added to the integration with the NACSIS ILL system. For more information see Alma Integration with NACSIS-ILL. - May 2024 Fulfillment and Resource Sharing URM-209437
Support for the SLNP PresentVerbundDaten message is now available. This enables a network to query Alma and send requests for item information. For more information see the Developer Network. - May 2024 Metadata Management URM-199977
GND Profile Updates: Ongoing GND profile updates. - May 2024 Metadata ManagementURM-190971
The Authority Control Task List now includes two new GND reports:For more information, see Using the Authority Control Task List.- GND records split with automatic redirection
- GND records split without automatic redirection
- May 2024 Metadata ManagementURM-198289
Network Zone templates are now available for an institution to be used when cataloging Community Zone managed authorities such as GND and BARE. For more information, see Working with Record Templates. - May 2024 Metadata ManagementURM-155440
Editing long fields in Metadata Editor: The color display of subfields in the Metadata Editor distorted the cursor placement indication when editing long fields. Now, when the cursor is placed in a field containing more than 1000 characters, the subfield colors are not displayed, so that cursor placement indication is accurate. - May 2024 Electronic Resource Management URM-213020
During the portfolio contribution process, local bibliographic records are relinked to the newly created community zone record.
To preserve the network zone topology, if the local bibliographic record in a consortia member was linked to the network zone, then the network zone bibliographic record will also be linked to the same community zone record. All linked bib records in other consortia members will also be re-linked to the same community zone record.
For more information, see Contributing to the Community Zone – Portfolios. - May 2024 User Experience, Accessibility & Infrastructure
The current DigiCert SAML Certificate will expire in August 2024. If your institution uses this certificate, we recommend that you consult with the IT department in your institution, and, if required, replace the certificate for Alma and/or Primo VE. If you do replace the certificate, this must be done in coordination with your IDP. For more information see Replacing a Signed Certificate.URM-212411 - May 2024 Analytics and Insights SF: 07066307 URM-199566
The PO Line Label field was added to the following locations. It displays the labels that are assigned to the PO line:- E-Inventory > Cost Usage > Cost Usage POL
- E-Inventory > Electronic Collection PO Line
- E-Inventory > Portfolio PO Line
- Funds Expenditure > PO Line
- Physical Items > PO Line
- Purchase Requests > PO Line
- May 2024 Analytics and Insights URM-210997
The Public Access Model field was added to the E-Inventory > Electronic Collection and E-Inventory > Portfolio Details for Consortia Members > Electronic Collection. This is in addition to this field's current location under the Portfolio folders. It displays the patron facing access model, which is presented to the patron in the discovery system. For more information on Access Models in Alma, see Managing Access Models. - May 2024 Analytics and Insights SF: 06636449 URM-213455
The NLM Geographic Classifications folder was added to the Other Classifications dimension for all subject areas in which it appears. It contains the NLM Geographic Code and NLM Geographic Name fields, which display the name and code of the geographic location, used for various purposes by NLM.These fields will be populated with historical data throughout the month of May 2024 as part of the semi-annual indexing. - May 2024 Analytics and Insights URM-215382
In the Analytics Object List, the Pin to Analytics Menu button was made more accessible in split-view. Clicking this button adds a direct link to the selected analysis object from the Alma Analytics Menu. - May 2024 Analytics and Insights URM-216920
Improvements were made to the following Data Visualizations dashboards:- Books Retention – Institution
- All the filters from the first canvas were pinned, so that they carry over to the second canvas.
- Overall Titles is based on OCLC or Normalized Title Author and not MMS ID. The documentation tab in the DV was updated accordingly.
- Books Deselection – Institution: Explanatory text was improved for better clarity.
- Books Retention – Institution
- May 2024 Analytics and Insights Idea Exchange SF: 05531113 05657836 05858438 05885188 06552441 06891457 URM-211443
To support the new Deactivate feature for licenses, the status of Deleted for previously deleted licenses was changed to Inactive as these licenses still appear in the license list. Going forward, deactivated licenses will have the status of Inactive and deleted licenses will be removed from the database and not reported on in analytics. For more information, see Deleting Licenses or Amendments and Deactivating and Reactivating Licenses or Amendments. - May 2024 Analytics and Insights URM-221167
The PO Line Approver Locked Out Date field will be removed from Analytics for the August release in all locations in which it appears. This field was removed from Alma long ago and is no longer relevant.
- April 2024 Metadata ManagementURM-211160
On the Alma UI Physical Holdings search results page, the label named Create Logical Set has been changed to Create and Filter Set. For more information, see Searching in Alma.Create Logical Set button relabeled to Create and Filter Set - April 2024 Acquisitions URM-207785
PO line indexing is moving from Oracle text to SOLR. This allows for better performance in searching for PO lines, especially in the receiving workbench. This will also enable future enhancement for searching in PO lines.
Note that this infrastructure change had an unintended consequence in which bib update automatically updated bib description in PO lines. This unintended behavior took place in NA03, AP01 and EU00, during February. After identifying this, we reverted it and this behavior does not take place anymore. - April 2024 Acquisitions URM-213464
Heads up for the delete license feature that will be released in May. This enables users to permanently delete licenses from Alma. Note that existing licenses with the status "Deleted" will get the new status "Inactive", and these licenses will not be removed automatically from Alma. - April 2024 Analytics and Insights URM-213259
The E-Inventory > (Portfolio Details for Consortia >) Portfolio > Proquest Purchase Model field was renamed to Purchase Model, since the field can now display the purchase models for JSTOR in addition to Proquest.This development supports an E-Inventory development to expand integration capabilities to include JSTOR titles, which will be released in May.
- April 2024 Analytics and Insights URM-212583
The Title Author Combined and Normalized field was added to E-Inventory > Portfolio Details for Consortia > Bibliographic Details. It displays the first 100 characters of the Title field, a hyphen, and the first four characters of the Author field, in lowercase and normalized to remove all special characters. Is helpful for finding overlapping physical and electronic records, or for finding overlapping records in different institutions within a network zone. - April 2024 Analytics and Insights URM-206966
The following fields were added to E-Inventory > (Portfolio Details for Consortia >) Electronic Collection:- CDI Coverage Calculation Date – the date the CDI coverage was calculated
- CDI Coverage Percentage – the percentage of titles from a collection that has coverage in CDI. The coverage can come from the same provider or from other sources.
For more information, see Electronic Collection.
- April 2024 Analytics and Insights URM-213004
In the Usage Tracking Data Visualization dashboard, the Institution filter was moved to the top of the page:Institution FilterSelect an institution to filter the results per institution. By default, the dashboard is filtered to your home institution or Network Zone.
- April 2024 Analytics and Insights URM-208984
The new Deep Link Authentication Method Analytics configuration page is now available (Configuration > Analytics > General Configuration > Deep Link Authentication Method). It contains the analytics_auth_method parameter that was previously under Configuration > Analytics > General Configuration > Other Settings. For more information, see Analytics Configuration - Deep Link Authentication Method. - April 2024 Analytics and Insights SF: 06870146 URM-205949
The Proxy For User Type field was added to Users > Proxy For. It indicates the area for which the proxy was created – Circulation, Fulfillment, or Researchers (Esploro). This is useful for owners of both Alma and Esploro to determine if the proxy displayed in a report is relevant for Alma (Circulation / Fulfillment) or Esploro (Researchers). - April 2024 Analytics and Insights URM-206155
Leganto Analytics folders and subject areas no longer appear for Alma customers without Leganto.
- March 2024 Acquisitions URM-207785
PO line indexing is moving from Oracle text to SOLR. This allows for better performance in searching for PO lines, especially in the receiving workbench. This will also enable future enhancement for searching in PO lines. This will be implemented gradually on the various Alma environments. So far it was implemented in NA01, NA03, AP01, AP02, CA01, EU00 and EU01.
Note that this infrastructure change had an unintended consequence in which bib update automatically updated bib description in PO lines. This unintended behavior took place in NA03, AP01 and EU00, during February. After identifying this, we reverted it and this behavior does not take place anymore. If you want assistance with checking your data and identifying the impacted PO lines, please contact Support. - March 2024 Acquisitions URM-211720
Currently, when an electronic resource is created via the regular PO Line creation process, or when manually associated to a PO Line, the Process type of the resource is set to Acquisition. This is now configurable using the new pol_electronic_process_type_acq parameter (default value is true). When set to true, the process type of the electronic resource is set to Acquisition. If the user does not want the Process type of the resource to be changed, the parameter should be set to false (see Configuring Other Settings). - March 2024 Analytics and Insights URM-207087
The Has Perpetual Electronic Access field was added to the Titles > Title Details. It indicates (Yes/No) if the access type of the electronic title is Perpetual. Note that if the access type is mixed (current and perpetual) the value of this field is No.
- February 2024 Linked Open Data
The Linked Data enrichment process applied to bibliographic records connected to FAST authorities is revised to the URI format to align with the entity URI structure. The format now follows this pattern: http://id.worldcat.org/fast/XXXXX. For more information, see Linked Data in the Developer Network.URM-201398 - February 2024 Linked Open Data
Support for BIBFRAME records extends to their publication as part of general publishing. Users can leverage BIBFRAME works and instances held in Alma for use in external systems as required. For more information, see Publishing and Inventory Enrichment (General Publishing).URM-210035 - February 2024 Metadata Management
The SBN "Italian Union Catalogue (Servizio Bibliotecario Nazionale)" redirection mechanism is enhanced to support the handling of Bibliographic related records. For more information, see SBN Redirection (Fusione)URM-180702 - February 2024 Digital Resource Management URM-207912
You can now display an image in Full View when viewing images with the Digital Viewer on a mobile device in portrait orientation. To display an image in Full View, select the Full View icon or tap the image. - February 2024 Analytics and Insights URM-209773
The following fields were added to E-Inventory > Portfolio Details for Consortia Members > Institution to align it with the fields located under the Institution dimension available in every subject area:- Institution Address Line 1
- Institution City
- Institution State Province
- Institution Country
- Institution Postal Code
- Institution Timezone
- Data Available As Of
- Data Updated As Of
- February 2024 Analytics and Insights URM-193380
The ACRL and IPEDS dashboard was updated to reflect the changes made to the guidelines for 2024. - February 2024 Fulfillment and Resource Sharing URM-208240 SF: 06918869
Libraries can now configure what happens when a purchase request is relinked to a new MMS ID. When a purchase request is linked to a citation, and the purchase request is then relinked to a different MMS ID, when the parameter purchase_request_relink_citation (Configuration > Fulfillment > General > Other Settings) is set to true (default), the citation is linked to the new MMS ID. When the parameter is set to false, the citation remains linked to the original MMS ID.If the original MMS ID had an associated copyright record, the copyright is cancelled and not applied to the newly linked MMS ID, and an alert is added indicating that the copyright was cancelled.
Relink a purchase invoiceFor more information, see Creating Requests for Citations.
- February 2024 Fulfillment and Resource Sharing URM-186377
Excel files are now supported in the course loader (Configuration > General > External Integrations > Integration Profiles) directory, in addition to .csv.Input File PathFor more information, see Configuring Course Loading.
- February 2024 Fulfillment and Resource Sharing URM-191244
When configured, archived lists can be included in the Demand in other lists calculation that enables library staff to see which reading lists or courses utilize the same resource when reviewing and processing citations. When the parameter demand_in_other_lists_include archived_lists (Configuration > Fulfillment > General > Other Settings) is set to true (default false), archived lists are included in the Demand in other lists calculation and are displayed in the This Record In Other Lists table. When set to false, citations associated with at least one archived list are excluded from the Demand in other lists calculation.Demand in other lists indicationFor more information, see Configuring Other Settings (Fulfillment).
- January 2024 Acquisitions URM-203344
The new, next-generation, Alma UI design is available for the PO Lines task list. Until February, you will have the the option to move back to the older version using the Feature Rollout Preferences menu (User icon-> Feature Rollout Preferences). As of February 2024, there will be no option to opt out, and the new UI will be the only available layout for all users. It is therefore important to use the time before the February release to introduce and train your library staff regarding the new UI.
For a general overview of the new PO Lines task list, see New Unified PO Line Task List. See also Searching for PO Lines - New Layout; Managing PO Lines - New Layout.
For more information see the New Unified PO Line Task List in the Alma 2024 Roadmap Webinar Series. - January 2024 User Experience, Accessibility & Infrastructure
The "Generate Performance Tracking File" task has been modified to read as "Start Performance Tracking Session" and "Stop Performance Tracking Session and Generate File". This enables users to specifically define the time range of the performance tracking recording. For more information, see How to Report Alma Performance Issues.Updated: January 17, 2024: Watch the Performance Tracking File video (1:31 mins). - January 2024 Analytics and Insights SF: 06770947 URM-204838
The Invoice-Payment Voucher Currency field was added to Funds Expenditure > Invoice Line. It displays the currency of the voucher payment. - January 2024 Analytics and Insights URM-189873
The Object Report URL field was added to Analytics Usage Tracking > Query Details and Analytics Objects > Analytics Objects Details. It displays the report URL of the analytics object. - January 2024 Analytics and Insights URM-189231
The National Agricultural Library Call Number field was added to the Bibliographic Details dimension in all subject areas in which it appears. It displays the call number used by the American National Agricultural Library and is mapped from MARC field 070 a. - January 2024 Analytics and Insights SF: 06727765 URM-208734
The following fields were added to E-Inventory > Service Details:- Service Activation Status – Indicates if the service is available or not
- Service Portfolio Auto Activate – Indicates if automatic activation of new portfolios associated with the service is configured
- Service Site Down Message – Indicates if a message to display when the service is unavailable is configured
- January 2024 Analytics and InsightsURM-202225
The Institution filter was added to the Analytics Usage Tracking dashboard. It enables consortia to filter the data by institution. - January 2024 Analytics and InsightsURM-207694
All analytics fields available in the E-Inventory subject area for the Portfolio and Electronic Collection folders are now available for consortia members under the Portfolio Details for Consortia Members folder in the Portfolio and Electronic Collection subfolders.
Resolved Issues
- November 2024 Acquisitions SF: 07702649
URM-232954 An error occurred when changing the location of an item from the PO line. This was fixed. - November 2024 Acquisitions SF: 07201084 URM-229288
The 'Additional' physical material types showed the code value in the PO lines search facet. This was fixed. - November 2024 Acquisitions SF: 07499130 07218509 07185005 07226500 07182037 07202246 07201983 07251245 07496559 URM-228014
When searching some PO Lines created by an API, an Opps error was returned. This was fixed. - November 2024 Acquisitions SF: 07168566 URM-225557
Purged Users were counted as Interested Users in PO Lines for Analytics. This was fixed. - November 2024 Acquisitions SF: 07150642 07694716 07138400 07170864 URM-225121
Recent history for associated PO lines was not working. This was fixed. - November 2024 Acquisitions SF: 07237813 URM-228967
Purchase order lines were not correctly displayed in the new Portugal-Portuguese translated UI. This was fixed. - November 2024 Acquisitions SF: 06977291 URM-218911
The uploaded files section from the Usage data tab did not show all the files for the TAYLOR & FRANCIS GROUP LLC vendor. This was fixed. - November 2024 Acquisitions SF: 07188725 07120076 07200125 07199258 07017214 URM-226729
Material type in ordered items was not updated when saving PO lines created from a template. This was fixed. - November 2024 Acquisitions SF: 07097913 07155314 URM-225878
Duplicate emails for the same order were sent to the vendor. This was fixed. - November 2024 Acquisitions SF: 06860959 URM-211241
The icons for ordered collections in PO lines did not match when performing a search for collections. This was fixed. - November 2024 Acquisitions SF: 07244299 URM-231045
In a specific case, there was a discrepancy on the exchange rate of a closed order. This was fixed. - November 2024 Acquisitions SF: 07132292 URM-221624
Invoices attached to a specific PO Line could not be closed. This was fixed. - November 2024 Acquisitions SF: 07224692 URM-228529
The "Vendor"."Preferred Email" field appeared in the UI but not in the analytics DB. This was fixed. Note that this fix does not affect old, invalid records. The fix only applies after the email is saved again. - November 2024 Acquisitions SF: 07227737 URM-228139
A vendor account still appeared in the recent vendors selection list for PO lines after being deleted. This was fixed. - November 2024 Acquisitions SF: 07164961 URM-227604
The Update PO Lines Information - Advanced job failed for bulk operations. This was fixed. - November 2024 Analytics and Insights SF: 07225352 URM-227405
In the Analytics Object List, the "Object created by" field did not display the correct information. This was fixed. - November 2024 Analytics and Insights SF: 07194418 URM-228672
In Analytics > Funds Expenditure, the vendor contact information (preferred email, preferred address, preferred phone) was taken from the vendor account. This was fixed, and now vendor information is taken from the vendor information in Alma. - November 2024 APIs SF: 07220233 URM-227644
The API GET-code-table failed when retrieving an empty code-table. This was fixed. - November 2024 APIs SF: 07183552 07178261 URM-225387
For the Retrieve PO lines API, results were not sorted correctly when ordered by created_date. This was fixed. - November 2024 APIs SF: 07175782 07004098 URM-219217
For the requested resources API, sometimes items from other locations were shown that were not from the requested library. This was fixed and now only the items from the requested libraries are shown in the task list. - November 2024 APIs SF: 06694839 URM-201062
The API documentation of bib record creation by using an import profile has been updated to note that only the bibliographic record part of the input is processed according to the import profile (that is, if holdings and items data is also included in the input xml, it is not processed by the import). - November 2024 APIs SF: 07260546 URM-231209
Sending API requests from a Cloud App with the "lang" parameter sometimes changed the UI's language. This was fixed. - November 2024 APIs SF: 07490790 URM-231203
Links from Cloud Apps to Support or More-Info did not work. This was fixed. - November 2024 Collaborative Networks SF: 06892073 URM-214056
In fulfillment network loans for the Active Hold Shelf, the "Preferred Identifier" field displayed the primary identifier of a linked account rather than the local primary identifier of the user's home institution. This was updated, and the "Preferred Identifier" label was changed to "Remote Patron Identifier" when there is no local request. - November 2024 Collaborative Networks SF: 06832522 URM-216734
Some concurrent processes created duplicate CZ-linked titles in Network Zone institutions. The process which caused these duplicates was fixed. Any existing duplicates should be merged either by using the Duplicate Title Analysis and Merge Records and Combine Inventory processes or by Support using internal tools. - November 2024 Digital Resource Management SF: 07267114 URM-230303
When returning an audio digital file early by selecting the “Return Early” button, the audio in the file continued playing in the viewer. This was fixed. - November 2024 Digital Resource Management SF: 07166132 URM-229711
Empty DC records were imported to Alma during the MD Import job. This was fixed. - November 2024 Digital Resource Management SF: 07053138 URM-219391
The interface language changes to Hebrew after selecting Deliver for a representation. This was fixed. - November 2024 Electronic Resource Management SF: 07493235 URM-230943
Upload the electronic holdings job for ProQuest failed with an internal error. This was fixed. - November 2024 Electronic Resource Management SF: 07190345 URM-230331
The sorting options of the columns in the CDI tab inside the Collection Editor was not working. This was fixed by removing the sorting options. - November 2024 Electronic Resource Management SF: 07222385 URM-229321
For some titles, the Portfolio List was not reachable through the "All Titles" search results (NZ tab). This was fixed. Now the portfolio list displays correctly. - November 2024 Electronic Resource Management SF: 07243886 URM-229089
Overlap analysis report name was not limited and could cause an error in saving the draft if the name exceeds 200 characters. This was fixed and the report name is limited to 200 characters. - November 2024 Electronic Resource Management SF: 07232571 07259127 URM-228654
Ovid upload e-holdings job fails if the password contains special characters. This was fixed and now the password is encoded. - November 2024 Electronic Resource Management SF: 06903781 URM-216876
Ampersand was encoded incorrectly in the Dynamic URL. This was fixed using the customer parameter "uresolver_interpret_double_encoded_ampersand" = true, and saving the '&' in the dynamic URL double encoded: "%2526". - November 2024 Electronic Resource Management SF: 06495024 07014996 URM-185182
Rarely, a incorrect interface name created wrong information in Analytics. This was fixed and a data corrector was built to fix the wrong data. - November 2024 Electronic Resource Management SF: 07232825 URM-230624
The electronic collection delete job did not send an email notification upon successful completion. This issue was fixed, and the job now sends an email notification after completion. - November 2024 Electronic Resource Management SF: 07231617 URM-229668
In the title search collection tab, the collection name was linkable although the user does not have the Collection Operator role. This was fixed for the classic search UI. - November 2024 Electronic Resource Management SF: URM-227724
The issue was resolved regarding the handling of old schedules from SPRINGER and ELSEVIER with system job ID '111'. These schedules were successfully updated to the new system job ID '195' (New upload e-holdings job). - November 2024 Electronic Resource Management SF: URM-224667
The Uresolver incorrectly filtered services by date. This was fixed. Previously, for specific journal volumes, the date filter was applied to some portfolios even though they fell within the availability period. The date filter is now correctly applied as intended. - November 2024 Fulfillment and Resource Sharing SF: 06959449 URM-216333
When duplicating a fulfillment unit rule in a specific case, the policy appeared as 'not listed' and could not be changed (conditions could not be added to the rule). This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 06963600 07157120 URM-215826
In a specific case, the load desk/department operators export function did not export all operators who had roles with multiple circulation desks as parameters. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 06967900 URM-214199
An item temporary location label was not translated into Spanish. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 07175517 URM-225433
The Borrower ID filter in the Fulfillment Activity History tab returned the wrong results. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 07190812 URM-229664
When the "Create physical item work orders" job was run, the priority of population requests was always set to "Medium". This was fixed, and the priority now depends on the 'Configuring Request Type Priorities'. - November 2024 Fulfillment and Resource Sharing SF: 07047422 URM-219184
The /notification_data/request/request_type_display was empty in the XML of the Ful Transit Slip Letter. This was fixed, and it now contains the correct value. - November 2024 Fulfillment and Resource Sharing SF: 06944594 URM-211454
When attempting to create multiple requests on items under the same title for the same patron, Alma blocks the second request, unless the requests have different description/volume, etc. Previously, in this case, the failure message was "Patron has active request for selected item". To make the message more accurate, it was changed to "Patron has active request for selected title". For serial titles, the message was changed to: "Patron has active request for selected title. Note that specifying a different description/volume etc., if possible, may enable creating the request.". - November 2024 Fulfillment and Resource Sharing SF: 07077091 07188788 URM-219209
Auto rejected resource sharing lending requests were still exported to external systems. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 06843305 URM-217044
After renewing an RS loan, the Due Date was set incorrectly. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 06947029 URM-214218
In some cases, the Due date was set back incorrectly when trying to renew a lending request. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 07722702 07724368 07725144 07722603 URM-233511
Before this fix, trying to connect to the Libris Resource Sharing system caused an Authentication error because of new API Key requirement. Libraries working with Libris need to configure the API key in the integration profile. - November 2024 Fulfillment and Resource Sharing SF: 6681253 URM-190636
Previously, loans with a "Returned by patron" status were incorrectly renewed by the ISO RenewResponseskip renewal. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 07262971 URM-229578
Previously, items that included instructor tags displayed an extra space in student view. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 07268289 07165691 07231159 URM-228318
Previously, when faceting a logical set by Course Year, the results were not saved. This was fixed. - November 2024 Fulfillment and Resource Sharing SF: 07220195 URM-227442
In some cases, labels in the UILegantoNewLables table (Configuration > Leganto > General > Labels - New UI) were missing the More Actions option. This was fixed. - November 2024 Metadata Management SF: 07122824 URM-223147
When deleting a Network Zone record with its last inventory, the NZ record was not deleted when linked to a Community Zone record. This was fixed. A new customer parameter 'enable_deletion_of_linked_nz_record_from_cz_without_inventory' ('false' by default) was added. When set to 'true', deleting the last inventory of an NZ record linked to the CZ when the NZ record is not held by another Institution Zone's, also deletes the NZ record. - November 2024 Metadata Management SF: 07227728 URM-228050
Even after configuring "Run once" for the job "Republish a set of Bibliographic records to Primo", it still ran multiple times. This was fixed. - November 2024 Metadata Management SF: 07021802 URM-218960
Network general publishing profiles (where the "Publish the entire repository" option is not selected) did not republish bibliographic records when a consortia member bibliographic record was unlinked from a Network record and the member record was linked directly to the Network record. (The Network record was republished if the member record was linked with a Community record to the Network record). This has been fixed. - November 2024 Metadata Management SF: 07265599 URM-230734
Scheduled manual jobs displayed an incorrect number of events in some cases. This was fixed. - November 2024 Metadata Management SF: 07133631 URM-224973
Physical Holdings search: Searching by the title index "OCLC Control Number (035a)" with the "Is Empty" or "Is Not Empty" operators did not work properly. This was fixed. - November 2024 Metadata Management SF: 07174107 07182859 URM-228403
The "Is Free" display value was always 'No' regardless of the "Is Free" filter setting. This was fixed and the "Is Free" column now accurately displays "Yes" or "No" based on the filter. - November 2024 Metadata Management SF: 07097237 URM-222510
When searching for a bibliographic record created on a specific date by using the "MMS Creation Date (Title)" index, records created on the next day were retrieved in some cases (especially for customers in the Asia-Pacific time zone). This was fixed. For this fix to take effect, full inventory indexing should be run. - November 2024 Metadata Management SF: 07221805 URM-229161
When browsing bibliographic headings, selecting the "Open in Repository Search" button on the "Bibliographic Records (nn)" tab, did not display any results when the search value (which is also the heading text) contained the "=" (equals) sign. This was fixed. - November 2024 Metadata Management SF: 07220106 07150979 06879735 URM-227743
Multiple bib headings for the same authority record were found in browse bib headings. The November-December 2024 full inventory indexing will resolve this. - November 2024 Metadata Management SF: 07168518 URM-224481
The Browse Shelf Listing for call numbers that contained special characters (such as umlaut) were not sorted properly. This was fixed. - November 2024 Metadata Management SF: 05767812 05835863 05311740 05330440 URM-93797
When searching in Alma's repository search, facet counters showed an approximation that was sometimes inaccurate. This was fixed for the new search UX, and will be resolved as the search types move to the new search. - November 2024 Metadata Management SF: 06718352 URM-199053
OpenURL field rft.part allowed only a word character ("^\w+$") so a "space" failed to register the field to the context object. This was fixed and now the field accepts any character complying with the regular expression ("^.*$"). - November 2024 Metadata Management SF: 07187049 07152331 07229295 URM-225226
When the Customer Parameter authority_linking_strategy = id, F3 "Headings from bibliographic records" was not displaying the bibliographic records containing the unauthorized headings. This was fixed. - November 2024 Metadata Management SF: 07157835 URM-223596
When the load.balancer.cz and load.balancer.cz.master are different, each time a Community Zone record was saved in the MetaData Editor, a pop-up displayed: "An external process has changed the original record". This is fixed - November 2024 Metadata Management SF: 07038230 URM-218853
In some cases, clicking the "Search bibliographic records matching this value" button from authority records search results did not provide any bibliographic record results. This was fixed. For this fix to take effect, full inventory indexing should be run. - November 2024 Metadata Management SF: 06891329 07002225 07034433 URM-214864
In a record, selecting an authority using F3 added a duplicate subfield 0 when the URI of the authority was already present.This was fixed so that now, if the URI is already in the field, it is no longer added again. - November 2024 Metadata Management SF: 06665347 URM-194954
MARC21 Field 711 does not link to Local Authority but can be manually linked to another vocabulary. This was fixed. MARC21 field 655 with 2nd indicator 5 (Canadian Subject Headings) now has a bibliographic heading. It is browsable in the list of bibliographic headings and authority-controlled. - November 2024 Metadata Management SF: 06632551 URM-191670
The "Search bibliographic records matching this value" search failed when the authority record's direct ID was of a format that included certain "word break" characters, because the search was directed against a keyword index instead of "exact match". This has been fixed when the customer parameter is active. - November 2024 Metadata Management SF: 07687669 07221842 URM-228807
Imported numbers in bibliographic records are displayed as a decimal number with many positions after the decimal point. This was fixed. - November 2024 Metadata Management SF: 06260764 07062091 07127937 URM-171135
The "Unique OCLC Identifier Match Method" in the Repository Import Profile failed to match records. This was fixed. - November 2024 Metadata Management SF: 07247545 URM-228892
UNIMARC to MARC conversion - There was no support of multiple subfields 'c' for fields 710/711/712. This was fixed by concatenating all subfields 'c' with '#' delimiter. - November 2024 Metadata Management SF: 07216979 URM-226792
When the SBN bibliographic alignment job imported records linked to the records in the alignment job results, it included classification records in the list of linked authority records to import. Since SBN classification records are not in the same format as SBN authority records, this led to validation errors in the job report. This was fixed by filtering out classification records from the list of linked records to import. - November 2024 Metadata Management SF: 07077415 URM-223173
When the imported NACSIS record had more than one author field that was indicated to be the Main Entry Name, multiple 100 fields were created in the Alma MARC record, which caused a validation error in the MARC record, as only one 100 field is allowed. This was fixed by crosswalking any additional Main Entry Names to the MARC field 700 ("Added Entry Names"), so that the MARC record does not fail validation. - November 2024 Metadata Management SF: 07077455 URM-221742
NACSIS-CAT: IMPORT mapping change requested in NACSIS AHDNG <-> MARC 100 $d and MARC 700 $d. The author date in the NACSIS system is no longer to be wrapped in (parentheses), after the October NACSIS update. If Alma exports a MARC record where the author date is wrapped in parentheses, the parentheses are removed before exporting the date to NACSIS. - November 2024 Metadata Management SF: 07077423 URM-221741
NACSIS-CAT: IMPORT mapping change requested in NACSIS AHDNG <-> MARC 100 $d and MARC 700 $d. The author date in the NACSIS system is no longer to be wrapped in (parentheses), after the October NACSIS update. If Alma receives a NACSIS record where the author date is wrapped in parentheses, the parentheses is removed before crosswalking the date to subfield d in the MARC record. - November 2024 Metadata Management SF: 07079208 URM-219617
When contributing a MARC21 bibliographic record to NACSIS, if the 007 field positions 0 and 1 contained "sz" or "s|" (vertical pipe), the contribution faiedl in the NACSIS system, because we did not have a mapping for "s" combined with either of those two characters. This was fixed, so that in either of these cases, the second character is crosswalked to NACSIS field/value SMD=z. - November 2024 Metadata Management SF: 06960415 URM-214761
When crosswalking NACSIS bibliographic records to MARC21, the “script code” in the Alternate Graphic Representation was based on the content of the 880 field. This was fixed. The 880 field, subfield $6, is now based on the language code in the NACSIS TTLL field, rather than the content of the 880 field. Specifically, if TTLL is “jpn,” “kor,” or “chi,” the script code in 880 $6 will be “$1” for CJK, regardless of whether the text is entirely in Latin and contains no CJK characters. - November 2024 Metadata Management When crosswalking MARC21 bibliographic records to NACSIS, the first 880 field is crosswalked to the "yomi" reading value (also known simply as the reading value), and any subsequent 880 fields is crosswalked to the "other" reading values. This is now based on the order of the 880 fields, and not on the "script code" in the 880 fields.
- November 2024 Metadata Management SF: 06976591 URM-212887
A customer provided a new requirement that in NACSIS title field, the use of " . " (space + period + space) indicates the existence of a subtitle. The subtitle content is to be appended to the end of $c in the MARC 245 field, and not included in $a or $b. This was fixed. - November 2024 Metadata Management SF: 06883525 06721941 URM-194740
NACSIS Cloud App Displays One OTHN and one NBN when Multiple OTHN Exist. This was fixed and now NACSIS Cloud App displays all OTHN and NBN when multiple values exist. - November 2024 Metadata Management SF: 06580298 URM-188743
Aleph Central Catalog Integration Profile - When two records are merged, the local field added from the non-preferred record cannot be found when searching by local field. This has been fixed. - November 2024 Physical Resource Management SF: 07500359 URM-231265
When clicking the "Items" action of an entry in the Physical Items search results, the user is directed to the Physical Item editor page if the holdings record contains only one item. If the user is not authorized to edit items in the holdings library, the item editor opens in "View" mode. However, when selecting the "View all items" link on the right-hand side panel of the item editor, and then selecting "Back" in the Items List that opens, the item editor opens in edit mode, although the user is not authorized to edit the item. This was fixed. - November 2024 Physical Resource Management SF: 07196589 URM-230487
Scheduled normalization jobs were processing the same records repeatedly. This was fixed. - November 2024 Physical Resource Management SF: 07118301 URM-228534
When the customer parameter "holdings_accession_number_generation_extended" is set to "library", and an accession sequence is defined on the library level, the "Generate Accession Number" action in the MD Editor fails with the error message "Accession sequence is not defined for xxx library and yyy location" while editing a holdings record containing a library ($b) and location ($c). This was fixed. Note that this is relevant only when generating an accession number, in the MD Editor, for a physical location for which the "Accession Placement" field has been defined. - November 2024 Physical Resource Management SF: 06865878 07201830 URM-204926
Several instances of the import job for the profile "LD - CroBar receiving - update inventory" were completed with errors for larger files. Most of the files failed in additional services processing. Smaller files were imported correctly. This was fixed. - November 2024 Physical Resource Management SF: 06802042 URM-198736
When viewing a single holdings record from the Holdings action of an item in the Physical Items search results, the Edit and Relink buttons were not displayed. This was fixed. Note that the visibility of these buttons depends on the user having the relevant privileges in the library's scope. - November 2024 User Experience, Accessibility & Infrastructure SF: 07132793 URM-227789
The Export to Bursar job exported duplicated fines/fees for users with multiple identifiers of the same type. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 06958910 URM-221746
If a fee was waived after it was already exported to Bursar, Alma updated the Bursar system about the change only if the waive was done through the UI, but not if it was done through an API. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07702458 07078325 URM-219319
In a specific case, the User Purge Records job failed to handle proxy users. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07489904 07708813 07686066 URM-232102
When activating MFA for Alma, some users could not log in to Primo VE and Leganto. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07655901 URM-231346
SAML login requests sometimes included end-of-line characters in the signature, resulting in an error in some IdPs. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07408134 URM-230773
Some entries of the organization unit in the database included the ID of a library for institutions. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07042440 06946584 06330794 URM-172641
The "Successful Login" event was logged not only for Alma logins but also for Primo VE, Esploro, and Leganto logins. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 06222341 URM-168666
When exporting lists from Alma (for example from search results), the exported file only contains the first 100 000 items, A tooltip was added to make this clear. - November 2024 User Experience, Accessibility & Infrastructure SF: 07487896 URM-231630
The Saved Searches Letter, "Send example by mail", did not use the subject from the XML. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07228896 URM-227823
The "Real-Time Notification Job Finished" letter contained a broken link. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07135057 URM-224485
The Icelandic alphabet did not sort correctly in the receiving workbench. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 06867876 06871238 URM-207641
The confirmation message for payment of specific fees was not translated. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07250614 URM-229925
For Deposit Forms, checkboxes could be set as mandatary fields. This was fixed. - November 2024 User Experience, Accessibility & Infrastructure SF: 07257143 URM-229495
Cloud Apps were not showing in Esploro if Alma's 'Show Cloud Apps only for users with the role Cloud App operator' was checked. This was fixed.
- October 2024 Analytics and Insights SF: 07189719 URM-227619
Data visualization workbooks could not be saved. This was fixed. - October 2024 Electronic Resource Management SF: 07211926 URM-228884
When updating a contributed electronic collection, the counter for portfolios to delete included some portfolios that had previously been deleted. This was fixed. - October 2024 Electronic Resource Management SF: 07063372 URM-227851
Advanced search for Electronic collection with "Empty" / "Is Not Empty" Access Type gave wrong results. This was fixed. Electronic collection search by access type in the advanced search now works properly. - October 2024 Metadata Management SF: 07038223 URM-221692
Authority Controlled Fields for Unimarc records - Field 680 (Classification Number) could not be cataloged using the F3 function. This was fixed and field 680 was added as an authorized field (PTC and F3 mechanism). - October 2024 Metadata Management SF: 07162899 07119912 URM-224730
CNMARC record facet displays the English value for "Rare - Physical" format. This was fixed to show the translated format. - October 2024 Physical Resource Management SF: 6865878 07201830 URM-204926
Several instances of the import job for the profile "LD - CroBar receiving - update inventory" were completed with errors for larger files. Most of the files failed in the additional services processing. This was fixed and now the files are imported without errors. - October 2024 User Experience, Accessibility & Infrastructure SF: 07203470 URM-226087
When searching for a Kormarc record with resource type ="Rare Book" and the language set to Korean, the resource type was displayed in English. This was fixed, and the Korean translation is now shown.
- September 2024 Acquisitions SF: 07181061 URM-227178
Some PO Lines hang up when attempting to view the Invoice Lines attached to the POL. This was fixed. - September 2024 Acquisitions SF: 07173997 URM-224984
When a PO had a high number of PO lines, sometimes when trying to "approve and send" the PO stayed in approval and PO lines were not advanced to the "sent" status. This was fixed. - September 2024 Acquisitions SF: 07057223 URM-221845
When changing a vendor for physical standing orders the items were not transferred to the new PO line (from the closed one). This was fixed. - September 2024 Acquisitions SF: 07036611 URM-216254
When a PO had a high number of PO lines, sometimes when trying to "approve and send" the PO stayed in approval and the PO lines were not advanced to the "sent" status. This was fixed. - September 2024 Acquisitions SF: 07211647 URM-227246
In an already created Invoice the Explicit Ratio values were added via a Rest Invoice API, but the Expenditure Transaction was not updated with the new Explicit Ratio values. This was fixed. - September 2024 Acquisitions SF: 07158435 URM-223108
The sort in the invoice line funding section was not working. This was fixed. - September 2024 Acquisitions SF: 07063891 URM-223228
Electronic collections were not listed in the Inventory tab for licenses with more than one page. This was fixed. - September 2024 Acquisitions SF: 06922800 07153788 URM-225213
An error displayed when selecting the Analysis tab for a specific trial. This was fixed. - September 2024 Analytics and Insights SF: 07178262 URM-225155
LC classification codes were missing in Analytics. This was fixed. - September 2024 Analytics and Insights SF: 06990538 07066355 07237823 07193821 URM-215401
In the Change Physical Items Information job, when setting an items status to "Missing", an event was created, but the "PROCESS_TYPE" element of the event was empty instead of "MISSING". Additionally, when marking an item as "MISSING" with the "Save and Toggle Missing" button in the item editor or the "Toggle Missing Status" action in the Physical Items search results list, no process type change event was created. This was fixed so that for each of these actions, a "MISSING" event is created." - September 2024 APIs SF: 06924359 URM-225689
It was not possible to delete a contributed XSL in some cases. This was fixed. - September 2024 APIs SF: 07221187 URM-227389
It was not possible to add a sub-collection via API if the main collection was suppressed. This was fixed. - September 2024 APIs SF: 07138134 URM-227206
When using detailed_creator_and_modifier_for_api_changes to register the API-key name as the creator/modifier of changes, it was not always registered correctly in the item history tab. This was fixed. - September 2024 APIs SF: 07183552 07178261 URM-225387
For the Retrieve PO lines API, results were not sorted correctly when ordered by created_date. This was fixed, and now order by created_date is sorted according to the input direction that is defaulted to "desc" if the order by is created_date." - September 2024 Digital Resource Management SF: 07198195 URM-226417
Access rights with time limits are not enforced for PDF files opened in representation mode in the Digital Viewer. The user is not automatically logged out of the display after the time is over. This was fixed. - September 2024 Electronic Resource Management SF: 07211900 URM-226863
The access to download the KBART serials holdings file was denied by Taylor and Francis. This was fixed by Taylor and Francis. - September 2024 Electronic Resource Management SF: 07196027 URM-225861
Extended Export was exporting only one service. This was fixed, it exports both of the services now. - September 2024 Electronic Resource Management SF: 06479819 06695852 URM-224290
Execute for getNotActivatedPortfoliosInAutoActiveServices generates an Oops error instead of results. This was fixed. - September 2024 Electronic Resource Management SF: 07167079 06906842 07204566 URM-208200
When the input file for the portfolio loader was very large, not all portfolios were activated. This was fixed. - September 2024 Electronic Resource Management SF: 06694046 URM-190583
Portfolio loader did not handle URL type. This was fixed, and now when populating URL or PARSER_PARAMETERS, the portfolio loader selects the URL type based on the column populated with a non-empty value. - September 2024 Electronic Resource Management SF: 06600879 URM-189687
The portfolio loader previously overwrote the parser program with Bulk::Bulk when the URL column was populated in the input file, instead of using the services existing parser. This was fixed, and now the parser program will no longer be overridden and will correctly use the services designated parser. - September 2024 Electronic Resource Management SF: 06509630 06893762 URM-184504
Portfolio loader did not handle URL type. This was fixed, and now when populating the URL or PARSER_PARAMETERS, the portfolio loader selects the URL type based on the column populated with a non-empty value." - September 2024 Electronic Resource Management SF: 07166115 URM-225023
Add Titles from Manage Collection UI: It was not possible to add titles that were assigned already to a collection in the hierarchy. This was fixed. - September 2024 Fulfillment and Resource Sharing SF: 06977090 URM-218781
License terms were not displayed on the Download electronic resource page from a lending request. This was fixed. - September 2024 Fulfillment and Resource Sharing SF: 06814930 URM-213712
When creating a lending request, partners with certain umlauts could not be selected as "Supplied To" partners. This was fixed. - September 2024 Fulfillment and Resource Sharing SF: 06746682 URM-199460
In some cases, requests with an external ID that included a "+" failed during the shipping process. This was fixed. - September 2024 Fulfillment and Resource Sharing SF: 07033388 URM-221320
Alma responded with an "OK" to the creation of ISO18626 lending requests, even if the operation failed. This was fixed, and now the "messageStatus" is populated with "error" and the "errorData" section has error information added to it. - September 2024 Fulfillment and Resource Sharing SF: 07007412 URM-217074
Rapido workflow profiles were added to non-Rapido customers. This was fixed, and the non-Rapido workflow profiles were removed from the non-Rapido customers. - September 2024 Fulfillment and Resource Sharing SF: 06764363 URM-207408
The barcode was not visible in the quick view (for example brief record view), in some cases. This was fixed. - September 2024 Fulfillment and Resource Sharing SF: 07111298 URM-222425
Loan anonymization failed for loans whose items were deleted. This was fixed. - September 2024 Metadata Management SF: 06947909 URM-213746
In the Metadata Editor, saving a record as a draft automatically resets its cataloger level to 00. This was fixed. - September 2024 Metadata Management SF: 07076109 URM-223919
Bib headings were sometimes not linked to authorities via F3 when the cp unimarc_uniform_title_headings_split is true. This was fixed. - September 2024 Metadata Management SF: 06914687 URM-213738
In the Metadata Editor, when a record was opened with cursor on the last line, if this line was removed after enhancing the record, the record was not editable anymore. This is fixed. - September 2024 Metadata Management SF: 06467734 URM-188129
When tag 800 has subfield $f followed by subfield $v or $s, the punctuation rules automatically added a space and a semicolon between the two subfields, which broke the link between the bibliographic and the authority record. This was fixed. - September 2024 Metadata Management SF: 07086560 07056771 URM-218802
The Resolve Import Issues Handle Matching page for import does not show any records. This was fixed. - September 2024 Metadata Management SF: 06877674 URM-206659
The holdings call number was not indexed when the holdings record was created by the Update Inventory import profile. This was fixed. - September 2024 Metadata Management SF: 07162899 07119912 URM-224730
CNMARC record facets display the English value for Rare - Physical format. This was fixed to show the translated format. - September 2024 Physical Resource Management SF: 07171558 URM-227022
A scheduled "Withdraw physical items" job was handling the same items again and again. This was fixed. - September 2024 Physical Resource Management SF: 07208585 URM-226371
Physical Item Editor page: in some cases, entries in the "Process Type" field that should have been available according to the items holdings library were missing. This was fixed. - September 2024 Physical Resource Management SF: 07172939 URM-225696
When a physical item template name contained a special character (like # or %), the creation of physical items from this template from the Metadata Editor did not working properly. This was fixed. - September 2024 Physical Resource Management SF: 07169978 URM-224153
When using the "Change Physical Items Information" job to change an item's location, a new holding is created if there is no matching holding for the target location. This new holding is based on the source holding. If it has no call number, a call number is generated according to bib data (e.g. field 090). However, if bibliographic field 090 has subfields $a and $b mapped to holdings 852 $h and $i, the call number in the target holdings was created with only $h, containing both $h and $i. This was fixed. That is, for example, if bibliographic 090 has $a part1 and $b part2, the target holdings field 852 will have $h part1 and $i part2. - September 2024 Physical Resource Management SF: 07137228 URM-222818
Physical Item editor: when an item (which is the last one in the holdings record) is moved to another location, the holdings record is deleted without any warning to the user. This was fixed. Now there is a warning message: "This item will be moved to a new holdings. As there are no remaining items in this location, the holdings record will be deleted. - September 2024 Physical Resource Management SF: 06511135 06810379 URM-206264
When changing the permanent location of items with the "Change Physical Items Information" Job, extra spaces are added to the call number subfields in the holdings record field 852 (e.g. $h, $i). This was fixed. - September 2024 Physical Resource Management SF: 06735833 06825792 06516246 URM-186006
Records with fields 777 do not show both "Get it" and "View it" links to related records. Sometimes it only shows "View it". This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 06969022 URM-218661
In a Fulfillment Network when creating a request in Primo, campus names of pickup locations in other institutions were not translated. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07201283 URM-225688
Users with only the Read-Only "Letter Administrator" role were not able to view details for a letter configuration. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07196298 07196440 07202008 URM-226513
Multiple emails about the expiration of the SAML certificates were sent to users. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07139831 07226983 07216955 07195849 URM-225223
The "ERP export" job failed with the "invalid privatekey" error when using the ECDSA key type, even though "Test FTP" was successful. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07197686 URM-225278
Manage Widgets were not translatable. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07178122 URM-225102
Sometimes, editing one portfolio opened a different portfolio for editing for a specific user. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 06923130 URM-204138
For widgets, the Remove button still appeared after being pressed a second time. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07227952 07219600 07236075 URM-227233
Login-via-email failed when used to log in to Alma. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07199903 URM-226525
The filter label in the user details section was not translated. This was fixed. - September 2024 User Experience, Accessibility & Infrastructure SF: 07203470 URM-226087
When searching for a Kormarc record with resource type ="Rare Book" and the language set to Korean, the resource type was displayed in English, This was fixed, and the Korean translation is now shown. - September 2024 User Experience, Accessibility & Infrastructure SF: 06999447 URM-217506
The "Call number type" drop-down was not translated into non-English languages. This was fixed.
- August 2024 Acquisitions SF: 07168566 URM-225557
A purged user was counted as an Interested User in PO Lines for Analytics. This was fixed. - August 2024 Acquisitions SF: 07145681 07152882 07172232 07135810 URM-225149
There were SAML authentication issues for Order It! in Firefox. This was fixed. - August 2024 Acquisitions SF: 07115545 URM-224647
The Public Access Model field did not update when adding an additional PO line with the ‘License Upgrade’ type. This was fixed. - August 2024 Acquisitions SF: 07171455 URM-224242
Permanently deleted licenses were not fully removed from electronic collections. This was fixed. - August 2024 Acquisitions SF: 07124285 URM-223947
Access models were not assigned to electronic portfolios when the PO line was created via a template. This was fixed. - August 2024 Acquisitions SF: 06964885 URM-217774
The 5th Reporting Code field still appeared in PO lines with the new UI layout, after the table and PO lines were cleared. This was fixed. - August 2024 Acquisitions SF: 06908832 URM-221812
Non-Alma user roles appeared in the "Role" drop-down list in the Find and Manage Users page. This was fixed. - August 2024 Acquisitions SF: 07197768 07177012 URM-224303
Incorrect information was displayed for Purchase requests in review in the unassigned task list. This was fixed. - August 2024 Acquisitions SF: 07119727 URM-223832
The 'Last Updated by' value did not change when making changes to a purchase request. This was fixed. - August 2024 Acquisitions SF: 06987302 URM-221684
After accessing the Manage Purchase Requests task list from the Tasks menu and performing an All Titles search, the action buttons did not appear in the results list. This was fixed. - August 2024 Acquisitions SF: 07091827 URM-219063
The Receiving Operator Limited role was not able to view the interested user info pop-up in PO lines. This was fixed - August 2024 Acquisitions SF: 06954811 07057261 URM-218818
When creating a PO line of type "Electronic Book – One Time", the Material type field in the PO Line was empty. This was fixed. - August 2024 Acquisitions SF: 07132334 URM-221594
Invoice payment information fields were editable when accessed from the Receive New Material page for users who did not have the relevant privileges. This was fixed. - August 2024 Acquisitions SF: 07199522 07019897 07127512 07031705 07037606 07119183 07173984 07119286 07100611 07087367 07188659 07026860 07053600 07060439 URM-216030
Invoices with the Closed status could not be saved when editing the payment information fields. This was fixed. - August 2024 Acquisitions SF: 07057300 URM-219258
When creating a new PO line using a template that contained a license value, the license was not copied to the created portfolio. This was fixed. - August 2024 Acquisitions SF: 07061990 07044918 07173070 07136580 URM-222837
When an item with an illegal character ("&","%") in the title was "Saved and received" from the Item Editor, an error was displayed. This was fixed. - August 2024 Acquisitions SF: 07139528 URM-224093
The information for 'No. of Units Arrived' and 'No. of Units Ordered' in the PO Line Claim Letter was incorrect. This was fixed. - August 2024 Acquisitions SF: 07038720 06959295 06994478 06975268 06804366 06598627 06896712 06992532 06802446 06783438 07021464 07116778 07206746 URM-189545
Some PO line claiming jobs completed with errors, but there were no details regarding the reasons for these errors. This was fixed. - August 2024 Acquisitions SF: 07097234 URM-224718
The information in SUSHI COUNTER reports was incorrect in some cases after selecting Delete All in the Usage Data tab. This was fixed. - August 2024 Acquisitions SF: 06909019 URM-218446
The Interested User field was not populated in PO lines when loaded through EOD with the user email address. This was fixed. - August 2024 Analytics and Insights SF: 07102401 URM-221330
The values of Available for Group, Available for Group Members, and Available for Resource Type fields under E-Inventory > Portfolio and E-Inventory > Portfolio Details for Consortia Members > Portfolio were not accurate. This was fixed. - August 2024 Analytics and Insights SF: 07038280 URM-219040
The values of Available for Group and Available for Group Members fields in the E-Inventory subject area were not accurate. This was fixed. - August 2024 Analytics and Insights SF: 07151558 07212296 07194995 07149539 07182383 07123124 07147464 URM-222203
When the Leganto - Monthly CRL report and the Leganto - Monthly RL report were sent as Excel files by email, the files did not display any data. This was fixed. - August 2024 Analytics and Insights SF: 07119726 URM-221681
The Purchase Requests (Analytics) > Purchase Request Details > Modification Details field was removed as it does not display meaningful data. - August 2024 Analytics and Insights SF: 07079965 06709400 06846976 URM-192010
In the Analytics Object List, if you viewed the preview of an Alma Analytics report and then tried viewing the preview of a Primo Analytics report, it did not open. This was fixed. - August 2024 Analytics and Insights SF: 07016039 06983047 07081169 07008988 07116856 07127326 07156538 07058413 06953796 07099738 URM-215122
When using the Microsoft Edge browser, clicking View Full Report did not work. This was fixed. - August 2024 APIs SF: 07104000 URM-222066
When the MARC 260 or 264 field contained multiple $a sub fields, the NACSIS record would be populated with multiplefields. This was fixed. - August 2024 APIs SF: 07037646 URM-217203
The Loan By Item information API returned an INTERNAL_SERVER_ERROR. This was fixed. - August 2024 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. - August 2024 Digital Resource Management SF: 07180265 URM-224827
Files would not upload. This was fixed. - August 2024 Digital Resource Management SF: 07179872 URM-224815
Although the Digital Viewer right pane is configured to show the same fields as the Details section of the full record display, the ISBN prefix did not appear in the Digital Viewer. This was fixed. - August 2024 Digital Resource Management SF: 07168977 URM-224198
Files displayed in the Internet Archive Book Reader viewer can be downloaded even if downloading is not allowed. This was fixed. - August 2024 Digital Resource Management SF: 07166105 URM-224015
In the Add Representation Form, the configured default value was not displayed properly. This was fixed. - August 2024 Digital Resource Management SF: 07053138 URM-219391
The interface language changes to Hebrew after selecting Deliver for a representation. This was fixed. - August 2024 Digital Resource Management SF: 07178817 URM-224514
When viewing the DC field information in the Metadata Editor, the error message "301 Moved Permanently" is displayed. This was fixed. - August 2024 Electronic Resource Management SF: 07138223 URM-221755
An error that occurred when moving some portfolios to a different electronic collection was fixed. - August 2024 Electronic Resource Management SF: 06993149 URM-219087
The Inventory tab in all title searches displayed the old name for the collection, even though the collection name was updated in Community Zone. This issue has been fixed, and the collection now displays the correct new public name. - August 2024 Fulfillment and Resource Sharing SF: 07109010 URM-223621
It was not possible to remove the 'Do you need help?' button from the Deposit login menu. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 06507025 URM-183763
When sending a Loan Receipt after renewing a loan, the 'old_due_date' field in the XML of the FulLoanReceiptLetter was empty. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 07138224 URM-224313
In some cases, testing a connection for the Locate profile timed out unexpectedly. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 07041721 URM-218796
The pickup location appeared even when the Pickup Location field was removed from the request form. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 06880000 URM-212535
In some cases, not all lending requests were displayed in the Lending task list. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 06489811 URM-209147
After using an alternative pickup location when creating a non-returnable ILL request, the alternative address was reset to the owner's library when editing the request. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 06493894 07012717 07030120 06706084 06661180 06901719 06723618 07103997 07130092 06762904 06942751 06468567 URM-179649
In some cases, selecting "Show file" on a borrowing request did not open the associated file. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 06923917 URM-212892
In a specific case, in the Network Activity tab, the 'Call number' on 'Patron Loans' and 'Managed by' on 'Patron Requests' fields were shown as blanks. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 07171014 07077370 07112073 URM-217799
In some cases, when sending a borrowing request for an article, the month and day were missing from the article information. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 06687335 URM-201576
Previously, requests with the word "to" in the Pages field were not processed correctly. This was fixed. - August 2024 Fulfillment and Resource Sharing SF: 07081290 07044151 URM-166682
In some cases, the borrowing request System Control Number was not populated with the OCLC number, which caused requests to fail. This was fixed. - August 2024 Metadata Management SF: 07161666 URM-224135
Google Scholar profile email addresses was limited to 40 characters, which was not sufficient. This was fixed and the limit is now 100 characters. - August 2024 Metadata Management SF: 07179803 URM-224956
A scheduled Export Bibliographic Records job, in some cases, didn't include record updates since the previous run. This was fixed. - August 2024 Metadata Management SF: 07175289 URM-224215
In the German UI, the 'Order' Button was missing for an electronic collection in the network tab. This was fixed. - August 2024 Metadata Management SF: 06961435 URM-212762
In a search results list when a record has an alternate title, after clicking it to view the record, the back button was throwing an exception. This is fixed and now the back button is working as needed. - August 2024 Metadata Management SF: 07117040 URM-221610
In the normalization rule, the correctDuplicateFields action was not working as needed in all cases. This is fixed. - August 2024 Metadata Management SF: 06881973 06816127 06941766 06911195 06914675 URM-199500
Metadata Editor: “Merge & Combine” sometimes displayed the following error “An error has occurred, please try again later and contact the system administrator”. The second attempt to select “Merge & Combine” worked successfully. This was fixed. - August 2024 Metadata Management SF: 06936393 URM-213875
Adding a local extension for a restricted tag that starts with "6" failed and an error was displayed. This was fixed, and local extensions are possible for all restricted fields as expected. - August 2024 Metadata Management SF: 06684580 URM-197649
When opening a holdings record in the Metadata Editor, if you moved from from subfield 'a' to 'b' in field 852, subfield 'c' was cleared. This was fixed. - August 2024 Metadata Management SF: 06921051 URM-212438
When linking a field in the MD Editor to an authority record by F3, the text of the authority field is copied to the bibliographic field. However, when the authority field contains subfield $6 (which links between Latin and non-Latin representations), it is also copied to the bibliographic field. This was fixed. That is, the contents of subfield $6 are not copied. - August 2024 Metadata Management SF: 07193422 URM-225406
UNIMARC Bibliographic 7XX4-OTB vocabulary was not visible in the metadata configuration page. This was fixed and now the vocabulary is visible when assigning controlled vocabulary for a UNIMARC bibliographic field. - August 2024 Metadata Management SF: 07077526 URM-217959
NACSIS > Alma: NACSIS publication field PUB: multiple publication locations are inserted in single Alma MARC 260 field, not multiple 264 fields. This was fixed and now when the NACSISPUBP= field (place of publication) contains a " ; " (space + semicolon + space) delimiter, this indicates multiple values, each to be used to create a separate $a in the MARC field. - August 2024 Metadata Management SF: 07077397 URM-217873
NACSIS-CAT: Export: mapping change was required in MARC 264$a <-> NACSIS PUBF. This was fixed and we added mapping from MARC 264 indicator 2 to NACSISPUBF= field. - August 2024 Metadata Management SF: 07077392 URM-217869
NACSIS-CAT: IMPORT mapping change requested in NACSIS PUBF <-> MARC 264$a. This was fixed and we changed mapping from NACSISgroup data from MARC 260 to MARC 264. In addition, we added mapping from NACSIS PUBF= field to MARC 264 indicator 2. - August 2024 Metadata Management
CJK punctuation characters are now removed when searching the NACSIS catalog. - August 2024 Metadata Management
Journal Holdings in the NACSIS Cloud App contain a large amount of data which sometimes made it sometimes difficult to view the information. This was updated and now the display of holdings is limited to 30 characters. - August 2024 Physical Resource Management SF: 07153014 URM-225107
When a PO line template is selected while creating a new PO line, the PO line template appears in the "Recently Used" section of the Physical Item templates ("Save as template" popup in the item editor). This was fixed. That is, only item templates are displayed under "Recently Used". - August 2024 Physical Resource Management SF: 07127303 07127508 07123325 07167373 URM-224821
List of Items > Manage Selected > Change Holding: In some cases, after selecting the target holdings record, the items list was not refreshed, and it seems to the user that the "Change Holding" action was not properly completed. This happened because of background indexing, which was not finished before the list of items was refreshed. The following solution has now been implemented: if the bib record containing the items has a total of up to 100 items, indexing is done on the spot, and the items list always reflects the new data after selecting the target holding. If the bib contains more than 100 items, indexing is done in the background, so the following feedback message is displayed to the user: "Items successfully moved to other holdings. Note that this action may take a while. Please refresh the Items List if necessary." - August 2024 Physical Resource Management SF: 07175760 URM-224512
For a user that has role to edit item only in a specific library, the "Save And Toggle Missing Status" was displayed even on items that are not in this scope. This is fixed and now the button is displayed only if the user has the relevant role for this library. - August 2024 Physical Resource Management SF: 07091173 URM-224475
In the MD Editor, when editing a holding record and Generating an Accession Number, a repeated subfield $x from holdings 852 is removed/damaged. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 06969022 URM-218661
In a Fulfillment Network, when creating a request in Primo, campus names of pickup locations in other institutions were not translated. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 06983574 05308915 URM-122114
When using the 'Update/Notify users' job to change the user from Internal to External and vice versa, no record of that appeared in the History tab of the user. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 07043134 07053781 URM-216918
In Analytics objects, when trying to share the object for a user or trying to add a subscriber user, the user was not findable in the dropdown list when searching with a space. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 06990226 URM-216719
For consortia members, restoring letter labels restored translations to OTB values instead of values from the Network Zone. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 07010037 06985124 06977816 06741012 URM-197687
Email notification changes were not saved for discovery import profiles. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 06560703 06881423 URM-192047
For email notifications in Scheduled Jobs, in some cases, the emails/users were not saved. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 06349580 06787615 06471243 06464032 07079019 URM-171344
The report shows only IDs of the relevant institution. This was fixed. - August 2024 User Experience, Accessibility & Infrastructure SF: 06989718 06670869 06985090 URM-193417
The analytics based Recommendations job generates recommendations based on Analytics reports. If the Analytics reports contained more than 1000 results, the job generated only 30 recommendations. This was fixed.
- July 2024 Acquisitions SF:06933196 URM-215764
A Brief Bib was created when a purchase request was attempted by an expired user from Primo. This was fixed and now the user will get an Unauthorized message. - July 2024 Acquisitions SF:07005746 URM-217866
There was an issue when exporting more than 1000 PO lines in itemized sets. This was fixed. - July 2024 Acquisitions SF:06886687 07041923 URM-213294
An error occurred when selecting "All PO Lines" or "Review (PO Lines)" in the New UI. This was fixed. - July 2024 Acquisitions SF:06809734 URM-210339
In some cases, a standing order POL of type Electronic book would be in the "Waiting for invoice" status instead of "Recurring renewal". This was fixed. - July 2024 Acquisitions SF:07011207 URM-221342
An electronic collection linked to a license did not display the "View License details" link (it was only displayed after selecting the license). This was fixed. - July 2024 Acquisitions SF:07083058 URM-217592
An error was displayed when trying to delete a trial that linked to a PO Line in Recurring renewal. This was fixed. - July 2024 Acquisitions SF:07127019 URM-221211
The Ledger - Open New Fiscal Period Job got stuck in Running status for 2 days in some cases due to incorrect data. This was fixed. - July 2024 Analytics and Insights SF:07053792 URM-216428
When deleting an Analytics object with subscribers, no warning is displayed that the object has subscribers. This was fixed, and now a warning is displayed. - July 2024 Analytics and Insights SF:07099065 URM-221859
The Item Receiving Year-Month field in Physical Items > Item Receiving Date did not work properly. This was fixed. - July 2024 Analytics and Insights SF:07098532 URM-220938
The values of the Available for Group field (E-Inventory > Portfolio) in Analytics reports did not match the actual group settings in Alma. This was fixed. - July 2024 Digital Resource Management SF:07109852 URM-223500
The Quick Access module did not display representation images in Primo. This was fixed. - July 2024 Digital Resource Management SF:07099255 URM-221670
When deleting the last file from a representation, a message is displayed asking if the user wants to delete the representation. The options offerred of "Cancel" and "Confirm" do not match the question. This was fixed by changing the message to match the options offered. - July 2024 Digital Resource Management SF:07013202 URM-215445
Sometimes the Delivery Registration Status letter was sent without a link to the resource. This was fixed. - July 2024 Digital Resource Management SF:07085805 URM-217817
In the Digital Viewer, after zooming in and out, the scroll bar blocked the text being displayed. This was fixed and now the scroll bar no longer blocks the text. - July 2024 Digital Resource Management SF:07044861 07031407 URM-221067
When opening the collection editor of a logical collection, the last set that was open was automatically assigned to the collection. This was fixed and no sets are automatically assigned to a collection. - July 2024 Electronic Resource Management SF:06963080 URM-213697
The Springer Integration job is consistently slower in certain environments. This was fixed. Detailed logs and timers for the job process have been added to better analyze the issue. - July 2024 Electronic Resource Management SF:06810486 07076266 URM-198444
On occasion, when the Upload E-Holdings job activated a new portfolio with an existing title, a new (duplicate) title was created instead of the portfolio being attached to the existing title. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:07129399 07078834 07064085 07028082 06521480 05331501 05315114 05312115 05307343
06542131 URM-98344 In some cases, requests sent to a last resort supplier were not closed after being exported when they should have been closed. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:06936196, URM-208958
The XSL file that translates an ISO message into an NCIP RequestItem message is modified so that it is possible to have both the ItemId field and the BibliographicId field. - July 2024 Fulfillment and Resource Sharing SF:7169867 07139061 07101569 07088788 07055866 URM-218730
Previously, expired lending request messages were generating an error and not being sent. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:06469092 06764919 URM-178117
Before the fix, the chapter title on the borrower side was mapped to "Chapter Number" field on the lender side. Now, the fields are mapped properly. - July 2024 Fulfillment and Resource Sharing SF:07113736 URM-222792
An error occurred when trying to add a row to the General Electronic Services Bib Fields Enrichment interface. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:07099055 07152517 URM-220978
In some cases, scanning in items after receiving caused a timeout. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:06767187 06601158 URM-193135
When more than one Bursar integration profile was defined, the Transferred Balance field in the Patron Services page was sometimes missing. This was fixed. The Transferred Balance field now appears whenever there is at least one Bursar integration profile with an active Import section. - July 2024 Fulfillment and Resource Sharing SF:07002924 07029068 URM-214734
When creating a new physical location in Alma by duplicating an existing location, the new external name was not saved but changed back to the one from which the location duplicated. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:06931964 URM-211392
When an overdue fine was generated, if the overdue loan was recalled, sometimes the calculated fine amount was smaller than expected. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:06726715 URM-197271
For hold requests, the request Destination field in the request queue page sometimes incorrectly displayed a circulation desk that did not have a hold shelf. This was fixed. Now the circulation desk that is chosen as the destination is always a circulation desk with a hold shelf. - July 2024 Fulfillment and Resource Sharing SF:07156483 07169289 URM-224214
The "Distribute Central Resource Sharing Configuration" job was not working properly in some cases. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:07057906 URM-219373
When using "Shipping Items" at the Resource Sharing Library circulation desk, scanning in a barcode for a request sometimes caused an error. This was fixed. - July 2024 Fulfillment and Resource Sharing SF:06814930 URM-213712
When creating a lending request, partners with certain umlauts could not be selected as "Supplied To" partners. This was fixed. - July 2024 Metadata Management SF:07158943 07172259 07162263 07171302 URM-223503
When scheduling the job: "Identify records that are not used in the Network", the job created sets that did not appear in the list of sets because the set was not registered as created by the user scheduling the job. This was fixed. - July 2024 Metadata Management SF:07141579 URM-222081
Bib export for MODS records completes with errors. This was resolved by removing the MODS format from the 'Output format' input parameter as this job does not support exporting bib titles in MODS format. - July 2024 Metadata Management SF:07053844 URM-217934
The advance search query link in the results page for Physical Titles and Process Type “Is Empty" behaves incorrectly. This is fixed. - July 2024 Metadata Management SF:06831649 URM-204276
Advanced search for the "Language" index with the option "No information provided" (i.e. field 008 positions 35-37 is "###") does not retrieve any results. This was fixed. Note that there are cases where positions 35-37 of field 008 are empty (spaces). These records can be retrieved by searching for "Language is Empty" (if there is no language data in field 041). - July 2024 Metadata Management SF:06631655 06937649 URM-186781
Browse bibliographic records: In some cases, the records indicated on the left side (by a number beside the heading) were not shown on the right side for viewing. This was fixed and will be deployed gradually with the next semi-annual indexing. - July 2024 Metadata Management SF:06480203 URM-207550
Analytics displayed context_object lines that have Clicked Services, but no Services. This was fixed. - July 2024 Metadata Management SF:06039511 URM-95201
When navigating through bibliographic or holding records, voice recognition software in Alma responds to some, but not all voice commands. This was fixed and all voice commands in Alma work as expected - July 2024 Metadata Management SF:06957497 07022514 URM-213876
Extensions for restricted fields are removed when you change the indicator. This was fixed. Now local extensions and the indicators for restricted fields can be added and edited as expected. - July 2024 Metadata Management SF:06672012 05321685 URM-167859
When a local extension is added to a network record already opened in the member Metadata Editor using a process, after pushing/editing this record again to the Metadata Editor, the added local extension is not displayed. This is fixed. A pop up is now displayed to inform that the record has been updated by an external process. - July 2024 Metadata Management SF:07018563 URM-214176
In the Metadata Editor, deleting an authority record that was linked to a bib opened in a collapsible presenter was not removing the link to it. This was fixed and now the link is removed. - July 2024 Metadata Management SF:06759363 07079439 URM-218795
SBN alignments - related records handling did not skip relations in tag 463. This was fixed, and now when importing records from SBN, linked (related) records with tipoLegame="463" are not imported. - July 2024 Metadata Management SF:06789449 URM-207620
Linking and unlinking of related access points from the 531 field was not implemented when this field was added for version 2.03 of the SBN schema. This was fixed. - July 2024 Metadata Management SF:06580298 URM-188743
Aleph Central Catalog Integration Profile - When a record with linked records is being redirected to another record, the related records were not indexed and therefore the search for the merged record didn't return its related records. This has been fixed. - July 2024 Physical Resource Management SF:07161282 URM-224055
When all the items of a holdings record were deleted, the holdings record was not supressed. This was fixed. - July 2024 Physical Resource Management SF:07153987 07171348 07165975 07168113 URM-223528
Public Physical Item templates do not appear in the Metadata Editor's "Add Item from Template" action. This was fixed. - July 2024 User Experience, Accessibility & Infrastructure SF:07036059 URM-215271
The "Get user fine/fee" API did not return information for a closed fine/fee. This was fixed. - July 2024 User Experience, Accessibility & Infrastructure SF:07192972 07200510 07163053 URM-223809
An error occurred on the "Scheduled Manual Jobs" page when a set for a manual job was deleted. This was fixed. - July 2024 User Experience, Accessibility & Infrastructure SF:07130251 07143593 07187927 URM-222758
The EXPORT_USERS job failed to connect to SFTP using public key authentication. This was fixed. - July 2024 User Experience, Accessibility & Infrastructure SF:07178171 07186758 07153558 07083395 07011774 URM-222392
There were various issues with SFTP connection to the server. This was fixed by upgrading the SFTP client. - July 2024 User Experience, Accessibility & Infrastructure SF:07144379 URM-222047
In the Bursar Integration Profile, the list was corrupted and some lines were cut off. This was fixed. - July 2024 User Experience, Accessibility & Infrastructure SF:06784660 07030223 URM-198249
The right pane "Requested Format" field value was shown in English rather than in the configured language. This was fixed. - July 2024 User Experience, Accessibility & Infrastructure SF:07118519 URM-222548
Alma was slow when while loading the Schedule tab from the Monitor jobs page. This was fixed. - July 2024 User Experience, Accessibility & Infrastructure URM-217696
Updated: July 21, 2024
MARC fields in "Descriptive Collection" record that can always be overridden by Alma's system update are:- Collection description | 520
- Collection public name | 245
- Collection &Content type | 300 (that is repetitive field, and it will appear separately for Collection type and for Content type)
- Target ID | 904
Users are able to add/edit fields in the Collection descriptive record but 520,245,300, and 904 are always overridden by our system update.
- June 2024 Acquisitions SF: 07116818 URM-219361
Changing the Vendor Name did not update the filter label. This was fixed. - June 2024 Acquisitions SF: 07092256 URM-218969
API PUT for invoice failed to update the voucher_number field and removed the existing number. This was fixed. - June 2024 Acquisitions SF: 07042729 URM-215432
There were performance issues related to the associating/disassociating of PO lines with holdings records. A tracking mechanism was implemented to monitor this. - June 2024 Acquisitions SF: 07082697 URM-218046
In the Import profile for PO Line information, the Interested users 'Hold item' checkbox could not be unchecked. This was fixed, and it is now possible to uncheck the option. - June 2024 Acquisitions SF: 07029461 URM-218731
Creating an invoice from a PO allowed the creation of invoices with an inactive vendor on the PO line. This was fixed. Now, when trying to create an invoice from a PO that links to an inactive vendor or a vendor that does not support the owner of the PO, the following error message is displayed: "Vendor is not valid for this invoice. Please check that the vendor is active and that the invoice owner is supported by this vendor". - June 2024 Acquisitions SF: 06799215 URM-217073
In some cases, when a staff user created an invoice from a PO, they would get an error message when searching by title. This was fixed. - June 2024 Acquisitions SF: 07151957 07120108 07132860 07114354 07131036 07141590 07114678 URM-219858
In some cases, the receiving workbench did not display all the PO lines for an invoice. This was fixed. - June 2024 Acquisitions SF: 06911464 URM-207645
In some cases, there was slowness during "Save and Receive" of an item of a PO line. This was fixed. Note that the fix is relevant for a scenario where the "Keep in Department" checkbox is NOT selected. - June 2024 Acquisitions SF: 07013594 URM-216934
When the fund name was changed, the linked PO lines were not updated with the change. This was fixed and now, changing the fund name indexes the linked PO lines. - June 2024 Analytics and Insights SF: 06857704 URM-215802
There was a discrepancy between the Usage TR_J1 field (E-Inventory > Cost Usage Measures) and the TR_J1 - Unique Item Requests field (Usage Data > Usage Data Details - Release 5). This was fixed. - June 2024 Analytics and Insights SF: 06826918 URM-213085
On the Analytics Object List page, when creating an object of type Report, selecting Excel as the export format, and switching the path to a dashboard, the export format stays Excel even though the object is a dashboard that can only be exported as a PDF. This was fixed, and now the export format for the dashboard changes to PDF. - June 2024 Electronic Resource Management SF: 07037882 URM-217390
The Taylor & Francis Upload electronic holdings job failed. This was fixed by parsing the "null" string. - June 2024 Electronic Resource Management SF: 06949344 URM-216004
In the portfolio loader, if different identifiers in different rows of the import file both matched the same portfolio in the CZ, the portfolio was activated twice. This was fixed. - June 2024 Electronic Resource Management SF: 06959500 URM-214278
Upload electronic holdings job - Springer activated portfolios with the wrong coverage for groups. This was fixed and now the portfolios are populated with the correct coverage information. - June 2024 Electronic Resource Management SF: 07027479 URM-217295
Running the Update All Logical Collections job indexed every collection, which caused performance issues. This was fixed. - June 2024 Electronic Resource Management SF: 05324390 07027202 URM-158769
When searching physical holdings or physical items by permanent call number and sorting the results by call number, the sort order was not satisfactory for the customer. This was fixed by creating a new call number normalizer so that the correct sort order could be provided. Re-indexing of holdings is needed after setting customer parameter "generic_call_number_filing" to cnsort. - June 2024 Fulfillment and Resource Sharing SF: 06664603 06921088 URM-194830
In the Pick from Shelf list, the requested material sometimes displayed the wrong description. This was fixed. - June 2024 Fulfillment and Resource Sharing SF: 07140820 07140655 URM-221909
When creating an item level request with an API, sending multiple mms IDs caused the created request to be corrupted. This was fixed. - June 2024 Fulfillment and Resource Sharing SF: 07034807 07022835 06572730 URM-190724
If the hold shelf slip was enabled, when scanning an item in the Return Items page to place it on the hold shelf, both the hold shelf slip and the resource request slip were printed. This was fixed. Now only the hold shelf slip is printed. - June 2024 Fulfillment and Resource Sharing SF: 06698805 URM-216906
When an AcceptItem NCIP message was received, the outgoing request was not saved with the due date. This was fixed. Note; however, that the due date is not updated if the item was already received by the library. - June 2024 Fulfillment and Resource Sharing SF: 06917679 URM-209471
The Close Lost Loans job failed if the loans were anonymized. This was fixed. - June 2024 Fulfillment and Resource Sharing SF: 06935776 06724455 URM-194952
Previously, bar codes were missing from printouts when printing from the Printouts Queue. This was fixed. - June 2024 Metadata Management SF: 06993744 06716598 URM-192152
The behavior of the "Statistics Note" default value was misleading: Being the first value, it was appeared in all items, even though it was only a suggested value and was not applied in the item unless saved. This was fixed. Now the display reflects the true state of the item, and the default value is not always displayed when editing items, only if it is actually a note of the item. The default value is the value displayed first in the drop-down once opened. - June 2024 Metadata Management SF: 06915901 URM-217937
General publishing - Changing LDR/05 does not trigger republishing if the record is suppressed. This was fixed. - June 2024 Metadata Management SF: 06761289 06657913 06775512 URM-189957
The duplicated ampersand sign that encodes the data for specific customers caused problems. This was fixed by creating a new customer parameter labeled "encode_rss_link" that needs to be set to "False". The default value is "True". - June 2024 Metadata Management SF: 07048591 URM-217026
When the content for an itemized set was opened, the set name was displayed on top of the results list in the English UI. When switched to another language, the set name is not displayed. This was fixed. - June 2024 Metadata Management SF: 06967094 URM-211431
“Unified Canadian Aboriginal Syllabics (Cans)” - some characters disappear when pasted to the Metadata Editor. This was fixed. - June 2024 Metadata Management SF: 06942722 URM-210509
"Open in Repository Search" from "Browse Bibliographic Headings" leads to an empty search in some cases (when the heading text contains double quotes in the middle of a word, such as in Hebrew initials). This was fixed. - June 2024 Metadata Management SF: 06682907 URM-191906
When importing a record that is linked to the CZ using an import profile that is defined to 'Update CZ record with local extensions', after the import, some fields in the cached record were different than in the CZ record. This was because the 'Marc21 Bib normalize on save' normalization process contains rules that change the cached record. This was fixed and now the cached record does not change (except for local extensions, if it exists) and remains identical to the CZ record. - June 2024 Metadata Management SF: 07029994 URM-217033
When TXTL is NOT ‘jpn’ or ‘chi’ or ‘kor,’ the prefix after {volume number} is a period (“.”), so by the current mapping rule created, the {volume number} is not mapped to 505$t. This was fixed. Now, when MARC 040$b (Language of cataloging) is ‘eng’ or when MARC 040$b does not exist and MARC 008(35-37) is NOT ‘jpn’ or ‘chi’ or ‘kor’, Alma puts a period mark after the {volume number}, which is populated from MARC 505$g, within NACSIS-CAT’s CW. - June 2024 Metadata Management SF: 07029994 URM-207525
SBN Alignment Job > Occasionally, the job fails due to a timeout. This was fixed by adding a new customer parameter (sbn_alignment_retry_wait_time). When this CP is set (not '0'), the job will retry to send the request to SBN five times. - June 2024 Metadata Management SF: 07028588 URM-217031
When TXTL is NOT ‘jpn’ or ‘chi’ or ‘kor,’ the prefix after {volume number} is a period mark (“.”), so by the current mapping rule created, the {volume number} is not mapped to 505$g. This was fixed. Now, when TXTL of NACSIS is other than ‘jpn’, ' chi’, or ‘kor’, map the {volume number} from CW (which is placed before the first period mark), to the MARC 505$g - June 2024 Metadata Management SF: 05309184 06050493 06958392 URM-189536
The Data corrector - DataCorrectorRestoreMmsCorruptedFieldFromACTL did not handle multiple occurrences of field 711. This was fixed by adding treatment for fields with multiple occurrences for RestoreMmsCorruptedFieldFromACTL data corrector. - June 2024 User Experience, Accessibility & Infrastructure SF: 07121683 07082889 07090923 URM-219477
The "Users restricted for editing" setup was not working. This was fixed. - June 2024 User Experience, Accessibility & Infrastructure SF: 07060570 URM-217087
The link to the status page in the Alma login page was an HTTP link. This was fixed and the link is now HTTPS. - June 2024 User Experience, Accessibility & Infrastructure SF: 06654450 05322319 06533384 06827070 05319240 06446587 07128580 06604525 06644802 06992306 06661962 06473503 07013117 05308745 06607546 06586791 06704004 07140782 06569319 05308702 06976577 06287140 06527416 06690909 06826866 06632724 06684289 URM-167233
Library names were not translated into Japanese in the Japanese UI and were displayed in English. This was fixed and now they are displayed in Japanese. - June 2024 User Experience, Accessibility & Infrastructure SF: 06963424 URM-216792
For the Overlap analysis tool, in some rows of the report, the content shifted to the left. This was fixed. - June 2024 User Experience, Accessibility & Infrastructure SF: 07037905 URM-219107
For some jobs, the notifications occasionally appeared twice. This was fixed. - June 2024 User Experience, Accessibility & Infrastructure SF: 06949963 URM-213212
It was not possible to add the “Contact” user type as an “Interested User” in the new Unified PO Line Task List. This was fixed. - June 2024 User Experience, Accessibility & Infrastructure SF: 07055315 URM-218184
The translation of the institution name in My Library Card was not displayed. This was fixed. - June 2024 User Experience, Accessibility & Infrastructure SF: 06959214 URM-217048
For some labels, the search bar occasionally displayed English instead of German. This was fixed. - June 2024 User Experience, Accessibility & Infrastructure SF: 07000098 URM-213571
The Borrowing request facet "Completed" Activity Status was not translated. This was fixed. - June 2024 User Experience, Accessibility & Infrastructure SF: 07000053 06907704 06956288 URM-212484
In the PO Line form, the values in the drop-down list for 'Renewal reason' were displayed in English, and not translated into other languages. This was fixed.
- May 2024 Acquisitions SF: 07079140 06985607 URM-214744
The Quantity for pricing was not updated when adding or removing items. This was fixed and now the quantity and price are updated correctly. - May 2024 Acquisitions SF: 07038127 07005788 07045509 07043408 07043313 06985334 URM-213253
In the PO Line Task List, sometimes the recent selection was not displayed. Now, when searching (and choosing) a vendor (in the vendor list box), it is always displayed in the recent vendors selection list. - May 2024 Acquisitions SF: 06971575 URM-217077
The deferred POL "Reminder date is arrived" alert was not added to the Alerts facet list. This was fixed. - May 2024 Acquisitions SF: 07010143 07010619 07038664 07026191 06936882 07079112 07013730 URM-212226
When saving a POL displayed the access model Save Confirmation message every time, even when it was unnecessary. Now, if the access model of the PO line's portfolio/s is/are the same as the access model on the PO line, there is no redundant warning. - May 2024 Acquisitions SF: 06902905 URM-210405
When viewing a purchase request and selecting Cancel, the mode of the back page was wrong (pickup instead of edit). This caused lists to be in pickup mode without an option to edit. This was fixed. - May 2024 Acquisitions SF: 06648512 URM-204719
Users could not approve and order from purchase requests. The problem occurred when the default acquisition method was disabled (there was no indication and nothing happened). This was fixed, and now there is a message indicating that "The default Acquisition Method is invalid or disabled, the PO line was not created.". - May 2024 Acquisitions SF: 06988448 07079774 07038818 06894229 06860274 URM-197086
For PO lines, selecting the back arrow would bring the user to a blank page. This was fixed. - May 2024 Acquisitions SF: 07018659 07012413 URM-215103
Updating the Expected receipt date did not seem to update the Reclaim date. This was fixed and now when the Expected receipt date is updated and the PO Line has a reclaim interval greater than zero, the notification claiming date (a.k.a Reclaim date) is calculated. If the calculated date is after the current reclaim date, it is updated on the PO line. - May 2024 Acquisitions SF: 06931046 06950657 URM-213586
The PO Line Aggregated Claim Letter had the wrong number of items received. This was fixed. - May 2024 Acquisitions SF: 06979956 URM-211500
When the collection of a trial had an override URL, the URL was not populated on the trial and was not passed to the participant email. This was fixed. - May 2024 Acquisitions SF: 06922800 URM-209567
Changing the survey language to Traditional Chinese caused an error message to display. This was fixed. - May 2024 Acquisitions SF: 07115388 07038544 06815133 06953980 06928654 07051841 07102553 07026120 07076306 URM-203440
In the new UI, after saving an order, there was a difference between fund and net price. The problem occurred when there were three or more digits after the decimal point, and specifically when the third digit was 5 (there was a wrong rounding of the sum). This was fixed. - May 2024 Acquisitions SF: 06888145 URM-208595
Saving a vendor record when updating libraries did not retain the changes. This happened because the status of the vendor account was "Inactive" (therefore the save failed). This was fixed, and now a message is displayed: "Active vendors must have at least one active vendor account. Please add a vendor account or change the Vendor status to inactive.". - May 2024 Acquisitions SF: 06870478 URM-207244
In certain cases the EDI load job report said that nothing was processed even though records had been successfully processed. Prints were added to the log in order to follow up if this issue occurs again. - May 2024 Acquisitions SF: 06855613 URM-207239
The EDI - Load Files job completed successfully but invoices were not correctly created. This was fixed. - May 2024 Acquisitions SF: 06964231 06980346 07108617 06931466 06900879 06970004 06877808 07037561 06968052 07022938 07034763 06979030 07080305 07005257 06905699 06961047 06874387 07013300 URM-212757
The SUSHI harvesting job completed with failures. The handling of the vendor's response was fixed to handle responses with error codes only (without a report header structure). - May 2024 Analytics and Insights SF: 06711398 07034931 06966708 URM-199209
Usage data from several SUSHI files did not appear in Analytics. This was fixed. - May 2024 Analytics and Insights SF: 06636635 URM-191826
In the Digital Waitlist subject area, time fields displayed dates and not times, and the Internal Request ID field incorrectly contained commas. This was fixed. - May 2024 Analytics and Insights SF: 06704422 06630398 06630391 06796056 06568285 06630370 06647362 06627251 06737107 06704504 06627085 06865123 06704447 06682460 06553683 06704460 06627076 06788480 06811546 06553830 06704635 06627230 06704536 06704764 06720035 06720132 06719836 06682513 06553690 06796047 06627249 06630302 06627303 06570196 06553699 06796051 06704432 06552521 06719971 06720142 06553996 06647292 06877951 06630583 06736968 06570208 06629098 06797041 URM-181637
When exporting an analytics report in any format, the error message "Server is busy. Please retry after some time." was displayed. This was fixed by making a change in the configurations. - May 2024 Analytics and Insights SF: 06944165 URM-213119
Primo Analytics objects were not found by Primo VE users when searching for objects from the Main Analytics Menu. This was fixed. - May 2024 APIs SF: 07049227 07039545 URM-215835
The Update Portfolio API did not work when used with JSON. This was fixed. - May 2024 Digital Resource Management SF: 06966867 URM-210799
Menu options were displayed in English although the interface language was configured for Spanish on the Alma Mobile App. This was fixed. - May 2024 Electronic Resource Management SF: 06948986 URM-211703
Ovid upload electronic holdings job did not delete portfolios from the collection when the subscription ended. This was fixed and now the portfolios are deleted. - May 2024 Electronic Resource Management SF: 06690430 07013096 06928291 06949354 URM-206287
In certain instances when an Upload Electronic Holdings task was restarted midway through the job, portfolios were activated multiple times. This was fixed. - May 2024 Electronic Resource Management SF: 06940460 07027171 06745344 URM-201879
The Upload Electronic Holdings uses the ISSN to match records from the KBART file to the records in the Community Zone. There are instances in the Community Zone that a single collection has two identical portfolios and the only difference is their coverage. When Alma attempts to match the KBART files with these identical portfolios, it detects matching ISSNs and skips them due to multiple matches. This was fixed and now Alma uses the vendor's unique identifier for the record and activates the relevant portfolio. - May 2024 Electronic Resource Management SF: 07133337 07136255 07136376 07137722 07138507 07138876 07139134 07139205 07141050 07147554 URM-221782
The Synchronize Changes from CZ were failing to get updates in EU03 and EU04 due to Network overload. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06993356 06980338 URM-212936
When opening the Resource Sharing form for a title that only existed in the NZ, and the General Electronic Services Bib Fields Enrichment mapping in the IZ was customized, the form did not auto-populate. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06366844 URM-173925
The edit option was available for Transit For Reshelving requests when coming from the Place in Queue link. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06684433 URM-217050
Previously, the quick print dialog did not work as expected when shipping multiple items. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06783317 URM-196735
When accessing Rapido from Firefox, the fields in the Request form were not wide enough to display all of the entered information. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06755495 URM-196371
Previously, the ‘Requested Media’ field was not always displayed in the ‘Request Information’ section on the Borrowing Requests Resource Sharing task list. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06390023 06631176 URM-178945
Previously, when a lending request with an MMS_ID from the Network Zone was sent from RapidILL, Alma rejected the request. This was fixed. Now Alma correctly creates lending requests with Network Zone MMS_IDs. - May 2024 Fulfillment and Resource Sharing SF: 06991449 URM-212303
When updating a Display Logic Rule and running the Distribute Fulfillment Network Configuration Changes, in some cases the job added another display logic rule to the member instead of updating the existing rule. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06918107 URM-207695
The agree to copyright terms checkbox was removed from the lending task list side pane. - May 2024 Fulfillment and Resource Sharing SF: 05316811 URM-158421
Previously, renewing overdue lending requests were rejected, and the status was changed to Received by partner rather than Overdue request. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06973040 URM-213275
Previously, the locate citation order was displayed according to rank rather than by publication date. This was fixed. - May 2024 Fulfillment and Resource Sharing SF: 06946260 URM-210915
In some cases, changes to citations were not saved when working on reading lists. This was fixed. - May 2024 Metadata Management SF: 07013442 URM-216801
Publishing to OCLC (LHRS / DataSync): Values entered to the profiles followed by a space were not trimmed. As a result, published files' names included spaces. This was fixed and now every input to the profile is trimmed. - May 2024 Metadata Management SF: 06927319 06994815 07092291 URM-214040
General Publishing with electronic inventory enrichment that included a static URL output was missing the static URL for some portfolios. This was fixed. - May 2024 Metadata Management SF: 06809019 URM-206032
In the 'Change Physical Items Information' job, the report was not generated for a set of less than 10,000 records. This was because a job with fewer than 10,000 items might have resulted in changes exceeding 10,000. If the number of updates exceeded 10,000, the report would not have been generated. The old message 'The report was not generated due to the number of records required to be calculated' has been updated to 'The report was not generated due to the number of updates required to be calculated'. - May 2024 Metadata Management SF: 06545654 URM-183055
When searching Primo for items that are available in other member institutions and their own library does not hold a copy, if the record is part of a series and has a 830$w pointing to the series-record which is available in the IZ, an error "Requested resource/s temporarily unavailable" is displayed. This was fixed. Now, the search results are displayed with the related record inventory. - May 2024 Metadata Management SF: 06719324 URM-201938
Digital Object Identifier (DOI) augmentation for Book Chapters did not retrieve the correct Chapter Titles or Authors. This was fixed. - May 2024 Metadata Management SF: 07013275 URM-214812
Metadata Editor: Catalogers from an Institution Zone can delete Network Zone bibliographic records (without a warning) even though they have portfolios in the Network Zone. This was fixed. - May 2024 Metadata Management SF: 07047842 06797477 URM-198071
Metadata Editor > KORMARC: Field '007' required updating (field to be changed from Kit to Old book, and subfield "y" to be added). This was resolved and the updates were made. - May 2024 Metadata Management SF: 07027458 URM-215274
The configuration process for an OAI Import Profile, including connecting and editing, failed to function properly for certain sources. This was fixed. - May 2024 Metadata Management SF: 07026958 URM-205219
Metadata Editor: A Network Zone record could not be deleted from a member when this member has local extensions. This was fixed. - May 2024 Metadata Management SF: 06970437 URM-215325
When CNMARC is enabled in the Active Registry, some of the facets for Resource Type are duplicated. This was fixed. - May 2024 Metadata Management SF: 07014562 URM-215936
MARC21: List of countries in field 008, positions 15–17, had wrong Japanese translations and wrong English names. This was fixed by changing the country name description for codes 'xn' and 'sq'. - May 2024 Metadata Management SF: 07010745 07019835 07034942 07043260 07050720 07127746 URM-221157
Import from Sudoc: Sometimes the imported records were created without the '003' field and with an incorrect '035' field. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 07121683 07090923 URM-219477
The "Users restricted for editing" setup was not working. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 07060570 URM-217087
The link to the status page in the Alma login page is an HTTP link. This was fixed and the link is now HTTPS. - May 2024 User Experience, Accessibility & Infrastructure SF: 07047180 URM-217001
After opening an Analytics page via SAML, it was not possible to access the Alma home page and users were directed back to the Analytics pages. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 06990226 URM-216719
For consortia members, restoring letter labels restored translations to OTB values instead of values from the Ntework Zone. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 06802260 URM-180783
On occasion, resource-sharing lending requests print slips created slips with the wrong font. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 06914092 URM-217250
In the All Titles Staff Search > View Record, the "field" name shifts to the next line when the on-screen resolution changes. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 07000069 URM-212718
The scheduling options in the Analytics object list cannot be translated. This was fixed and scheduling options are now translated to the user's language. - May 2024 User Experience, Accessibility & Infrastructure URM-214605
Resolution Description: The User Statistics section (Configuration > General > Feature Rollout Configuration) page does not count the users correctly. This was fixed. Now the statistics are counted according to users (that can see and use the Feature Rollout functionality) who have the appropriate role/s that are define by the feature/development that is using the Feature-Rollout functionality (that is, either if they are STAFF, PUBLIC or CONTACT). - May 2024 User Experience, Accessibility & Infrastructure SF: 06762236 URM-199020
When selecting the "collapse by default" checkbox on the portfolio creation notification, the next notification still pops out. This was fixed and the pop-up is now collapsed. - May 2024 User Experience, Accessibility & Infrastructure SF: 07055315 URM-217030
Institution "Names" are not translated for pickup institutions in Fulfillment Networks. This was fixed and now Names are translated. - May 2024 User Experience, Accessibility & Infrastructure SF: 07044899 URM-215442
There were issues in the German UI: Calendar pop-up did not open and the Alma home page did not load. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 06891184 07116868 06827070 06586791 06937432 URM-209060
Updating translations for the Institution name and description was not saved in some cases. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 06989718 06670869 06985090 URM-193417
The Generate Recommendations Based on Analytics Reports job did not run properly. This was fixed. - May 2024 User Experience, Accessibility & Infrastructure SF: 05322319 05319240 06826866 06533384 06654450 06992306 06473503 07013117 06644802 06827070 06976577 06287140 06446587 06607546 06604525 06632724 05308745 06661962 05308702 06527416 06586791 06684289 06690909 06704004 URM-167233
In Primo VE, on some APDs, certain library names were displayed in English instead of the selected language. This was fixed and the library names now appear in the selected language. - May 2024 User Experience, Accessibility & Infrastructure SF: 05313963 05315446 06228097 06311277 06423387 06640824 06876926 URM-98271
When a PO line was paid with multiple funds and an invoice created, the exported Excel invoice only contained the first fund. This was fixed and exported Excel invoices now contain all funds that were drawn from. - May 2024 User Experience, Accessibility & Infrastructure URM-211565
For searches using the new Alma UX, the RFID button did not appear in the page persistent search. This was fixed and the RFID button now appears.
- April 2024 Acquisitions SF: 06530558 URM-186502
For missing PO lines when performing an EDI import, the error did not include the PO line or vendor reference number. This was fixed. - April 2024 Acquisitions SF: 06664602 URM-194874
An incorrect vendor was displayed when approving and ordering purchase requests. This was fixed. - April 2024 Acquisitions SF: 06990717 06930035 URM-198161
In some cases, if the PO line reference contained a backslash character / the information did not display properly in the Summary tab. This was fixed. - April 2024 Acquisitions SF: 06689326 06703920 URM-198297
Purchase request list returned duplicate values when moving in pagination; the last record in page A was the first record in page A+1. This was fixed. - April 2024 Acquisitions SF: 06672790 URM-199013
In the POL Invoice Lines tab the transactions list was filtered by the wrong invoice number. This was fixed. - April 2024 Acquisitions SF: 6672460 06923920 URM-202153
The Alma Analytics Monthly Usage Report did not show "more information" if no data was loaded. This was fixed and the "No usage data was loaded" message now displays. - April 2024 Acquisitions SF: 06856541 URM-206569
A second claim letter for the same journal issue was sent one day after the first claim was sent. This was fixed. - April 2024 Acquisitions SF: 06802421 URM-206583
The Sushi usage data time zone was inconsistently used. This was fixed. - April 2024 Acquisitions SF: 06941374 06992813 06909222 URM-208244
If a PO line was in claim, the claiming list contained all the items that were not received. This was fixed and now the claiming list only displays items that were not received and had the expected receiving date and grace period in the past. - April 2024 Acquisitions SF: 6819403 06913186 URM-208596
The "update poline - advanced" job would fail when running on a set containing PO lines attached to PO. This was fixed. - April 2024 Acquisitions SF: 06860959 06959212 URM-209936
When creating an order from CZ, the IZ indication appeared instead of CZ in the purchase order line details. This was fixed. - April 2024 Acquisitions SF: 06751108 URM-211207
A comma was added to the Item Description when modifying any field in the PO Line. This was fixed. - April 2024 Acquisitions SF: 06971734 URM-211633
In the new UI for PO lines, the Receiving operator role could not edit and save PO lines when coming from the receiving Work Bench. This was fixed. - April 2024 Acquisitions SF: 07000124 URM-212719
Receiving note and Activation note were not translated (and not translatable) in the icon when performing a mouse over. This was fixed. - April 2024 Acquisitions SF: 6946420 URM-213205
If the "QUANTITY_PER_ITEMS in PO Line" field was null, it was not possible to change the quantity in the "Update PO Line Transaction" Job. This was fixed. - April 2024 Acquisitions SF: 07040032 URM-214332
The POL Status was not included when exporting POLs. This was fixed and the POL Status was added to the export right after the Type column. - April 2024 Acquisitions SF: 6949709 06983720 URM-215352
The PDA Repository Import Profile completed with errors when processing a delete of an empty bibliographic record. This was fixed. - April 2024 Acquisitions SF: 6933196 URM-215764
A Brief Bib was created when a purchase request was attempted by an expired user from Primo. This was fixed and now the user gets an Unauthorized message. - April 2024 Acquisitions SF: 07039801 URM-217387
There was an error when making changes to the Webhooks Integration Profile. This was fixed. - April 2024 Analytics and Insights SF: 6859166 URM-207327
Subscribers to the analytics object "Fulfillment - 30 days past due" did not receive the report. This was fixed. - April 2024 Analytics and Insights SF: 06978905 URM-211672
Incorrect information was displayed in reports for the Renewals field (Fulfillment > Loan). This was fixed. - April 2024 Analytics and Insights SF: 07021720 06988546 URM-212500
Patron Statistical Category data is missing for renewals. This was fixed. - April 2024 Analytics and Insights SF: 06938757 URM-212825
The "Upload" option in the Alma Analytic folders to upload a logo to reports did not appear. This was fixed. - April 2024 Analytics and Insights SF: 06988408 URM-213204
When creating reports for fines in Alma Analytics, the report displayed multiple lines for the same fine. This was fixed. - April 2024 Analytics and Insights SF: 06942211 URM-213262
The "Expired" status was not displayed for the Patron Active Status field (Borrowing Requests (Resource Sharing) > Borrowing Request Details). This was fixed and now the "Expired" status is displayed. - April 2024 Analytics and Insights SF: 07039785 URM-215281
Permissions for data sets are not remembered by Alma Analytics and need to be reset repeatedly. This was fixed. - April 2024 APIs SF: 06490693 URM-184470
For the NACSIS-CAT Cloud App, when importing, some records did not have $$2 in field 015. This was fixed. - April 2024 APIs SF: 6800679 URM-198255
CN domain was added to JCR cloud app version 2.3.1. - April 2024 APIs SF: 07015213 07058276 URM-217719
Regenerating keys for RSA SFTP server created malfunctioning private key. This was fixed. - April 2024 Digital Resource Management SF: 07015125 06894835 URM-209104
The Digital Viewer did not display remote representation videos from YouTube. This was fixed. - April 2024 Digital Resource Management SF: 06962598 URM-214371
In some cases, the Extract Fulltext job did not extract did not extract fulltext from PDF files with special unicode characters. This was fixed. - April 2024 Electronic Resource Management SF: 06660545 URM-197131
The incremental, multi-campus mode version of the Upload Electronic Holdings job for EBC occasionally completed with errors. This was fixed. - April 2024 Electronic Resource Management SF: 06970528 URM-212931
The display of portfolios' coverage in the electronic service editor was inaccurate when using a date format with dots (dd.MM.yy). This resulted in incorrect date representation. This was fixed, now the coverage column accurately displays the date information. - April 2024 Fulfillment and Resource Sharing SF: 06974577 URM-162612
If the Booking Resolution policy was set to Days, when a patron attempted to place a same-day booking request through Primo, the request was incorrectly blocked with the error message "Date must be in the future". This was fixed and now same-day booking is allowed. - April 2024 Fulfillment and Resource Sharing SF: 06664346 URM-188966
When a Rapido request originates from a Primo VE search, the permalink is now visible in the record Permalink field. - April 2024 Fulfillment and Resource Sharing SF: 06576251 URM-189532
The Document Delivery Notification Letter had an empty <flat_d> section when the partner of the borrowing request was RapidILL. This was fixed. - April 2024 Fulfillment and Resource Sharing SF: 06852167 URM-199221
Remote storage NCIP check-in did not fulfill restore requests. This was fixed. - April 2024 Fulfillment and Resource Sharing SF: 06869663 URM-205944
The Update BLDSS Requests job did not updated the status of borrowing request to Rejected. This was fixed. - April 2024 Fulfillment and Resource Sharing SF: 06881780 URM-206930
In the physical item editor, when changing the permanent location of an item in process, the list of departments under the "At" field was not refreshed. This was fixed. - April 2024 Fulfillment and Resource Sharing SF: 06918883 URM-207929
In some cases, exporting citations from a list to Excel failed. This was fixed. - April 2024 Fulfillment and Resource Sharing SF: URM-212751
It was possible to change the code of the Remote Storage, which led to errors. This was fixed and it is no longer possible to edit the code of the Remote Storage. - April 2024 Fulfillment and Resource Sharing SF: 07041691 07041691 07041774 07047109 URM-215344
The new hold shelf policy configuration for resource sharing requests was not working correctly.This was fixed. - April 2024 Metadata Management SF: 07077415 06685663 URM-190553
The NACSIS to Alma and Alma to NACSIS crosswalks did not have handling for "parallel title" data included in the TRD ("book title") NACSIS field. This has been fixed and the field was added. - April 2024 Metadata Management SF: 06811756 URM-204398
NACSIS-CAT was incorrectly handling multiple publishers in field 264. This was fixed and if the Alma 264 field has multiple $b, then they will be concatenated into a single PUBL= field in the NACSIS record, delimited by " : ". - April 2024 Metadata Management SF: 06847922 06866858 URM-206135
In some consortiums, a consortia member was erroneously displayed in the Network Zone inventory list results (Held by). This was fixed and now the 'Held by' details page shows the correct institutions for each title. - April 2024 Metadata Management SF: 06946002 URM-209562
Physical holdings search switches to All titles when using the View-options in the results. This was fixed. - April 2024 Metadata Management SF: 06941931 URM-214565
Links between bib records (via 773 $w) were not created when the bib record had fields with text longer than 255 characters. This was fixed. - April 2024 Metadata Management SF: 06953099 URM-214691
Advanced search for “Country of Publication” = “Georgia” (008 code gau) did not find records. This was fixed. - April 2024 Metadata Management SF: 06964229 URM-215502
Export to Excel file fails when clicking on "View Holdings of related record" in the Holdings sections. This was fixed. - April 2024 Metadata Management SF: 07021802 URM-215822
General Publishing > Entire Repository mode - Records that were updated close to the publishing start runtime were sometimes not published. This was fixed. - April 2024 Metadata Management URM-141420
Previously, there was an unexpected behavior where process IDs were duplicated, resulting in entire rows being duplicated in the export file. Additionally, this led to some jobs not being included in the exported file. This was fixed. Now, in the exported Excel file, each process ID is unique, and all jobs run within the specified date range are included. Duplicate job IDs are no longer exported from the Monitor Jobs Page. - April 2024 Physical Resource Management SF: 06865905 URM-204729
Items List > Select items > Manage selected > Change Holdings: Linking selected items to another holdings record took a very long time for a bib record with many items in total (usually more than 1,000). This was fixed. - April 2024 User Experience, Accessibility & Infrastructure SF: 06762810 URM-160436
Users that have a Fulfillment Administrator role in read-only were only able to edit the configurations in the following cases:- In "opening hours" after clicking the import button
- In configuration tables that are managed by the network
Both of these issues were fixed.
- April 2024 User Experience, Accessibility & Infrastructure SF: 06976563 06731647 URM-199246
When a user's note included a "$" letter, the history user tab only displayed the text up to the $. This was fixed and now the entire note text is displayed. - April 2024 User Experience, Accessibility & Infrastructure SF: 06907704 06956288 06956288 URM-212484
In the PO Line Form, the values in the dropdown for 'Renewal reason' displayed in English but were not translated in other languages. This was fixed and the translations appear as expected. - April 2024 User Experience, Accessibility & Infrastructure SF: 06969227 URM-212905
When a new notification is added to the Alma homepage notifications via configuration, all other notifications received the same Last Updated date. This was fixed. - April 2024 User Experience, Accessibility & Infrastructure SF: 07000087 URM-213569
In (Borrowing requests -> Active requests) when cancelling a request, the Cancellation reason label was not translated. This was fixed. - April 2024 User Experience, Accessibility & Infrastructure SF: 07021199 URM-214157
Alma-D and Primo URLs were not blocked by the IFrame Embedding Options. This was fixed and all declared products are blocked. - April 2024 User Experience, Accessibility & Infrastructure SF: 07011994 URM-214799
The Internet Archive Book Reader viewer does not display any content. This was fixed.
- March 2024 Acquisitions SF: 07013070 URM-213123
When cancelling an update operation for Rush or cancellationRestriction in a PO line, the fields were still updated. This was fixed. - March 2024 Acquisitions URM-198911
When sending operational mark_in_erp the related POLs were not closed. This was fixed. - March 2024 Acquisitions SF: 06966881 06886687 URM-212289
An error was displayed when searching for a specific PO Line. This was fixed. - March 2024 Acquisitions SF: 07005500 URM-213261
In some cases users could not access certain PO Lines because their "Is integrated with vendor" field was set to null. This was fixed. - March 2024 Acquisitions SF: 06844635 06845876 06933294 06927278 06863838 URM-207065
In the new PO Line Task list, the facets for PO Line Owner displayed a mixed set of translations. This was fixed. - March 2024 Acquisitions SF: 06954716 URM-209793
When saving a PO Line in the Japanese UI, the PO Line number in the popup message was not a clickable link. This was fixed. - March 2024 Acquisitions SF: 06904035 06627403 URM-191099
The Participants tab for Trial Details indicated that content was present, but no participants were shown when selecting that tab. It happened when the trial had more than 1000 participants. This was fixed. - March 2024 Acquisitions SF: 07038544 06815133 06953980 06928654 07026120 URM-203440
In the new UI, after saving an order, there was a difference between fund and net price. The problem occurred when there were three or more digits after the decimal point, and specifically when the third digit was 5 (there was a wrong rounding of the sum). This was fixed. - March 2024 Acquisitions SF: 06929331 URM-211578
An unexpected error message was displayed when trying to add a fund to a POL. This was fixed. - March 2024 Acquisitions SF: 06935915 URM-212863
SUSHI harvesting failed in certain cases. This was fixed. - March 2024 Analytics and Insights SF: 06723090 URM-207657
When running a report with the Physical Items > Physical Item Details > Has Committed to Retain field, the count of "No" values changes when the "Retention Reason” field is added to the report. This was fixed. - March 2024 Analytics and Insights URM-210743
The options of the Type filter drop-down list in Main Menu > Analytics > Share with me / Analytics Object List did not appear in the same language as the interface. This was fixed. - March 2024 Analytics and Insights SF: 06987206 URM-211699
Exports of the Analytics Object List included a maximum of 100 items. This was fixed, and now all of the items in the list are included in the export. - March 2024 Analytics and Insights SF: 06844130 URM-201890
In the Primo analytics subject area, Customized Values Usage, the Year field displayed the thousands separator in the default format. This was fixed, and now no separator is displayed. - March 2024 Analytics and Insights SF: 06954917 06964860 06984425 07015035 06981331 07029088 06981653 06988995 06983664 URM-212483
The Fulfillment > Patron Details > Patron Group field was sometimes empty in reports for renewed items depending on the renewal date. This was fixed. - March 2024 Analytics and Insights SF: 06958367 07013378 URM-212475
Users without the Design Analytics role could not export reports with prompts. This was fixed. - March 2024 APIs SF: 06993456 06984966 URM-211606
The Retrieve Set Members API for a logical Courses set returned an error. This was fixed. - March 2024 Digital Resource Management URM-195284
Sometimes, the Remove Titles from Collection job did not remove the titles from the collection. This was fixed. - March 2024 Digital Resource Management SF: 06808477 URM-198688
The Open File icon in the embedded PDF viewer has no function in Alma. It was removed. - March 2024 Digital Resource Management SF: 06760851 URM-199106
PDFs were slow to load or failed to load in the Digital Viewer. This was fixed. - March 2024 Digital Resource Management SF: 06858429 06906455 06917123 06850299 06973180 06971798 06920194 URM-204723
The Synchronize All Logical Collections Job deleted records from the logical collection and added them back the next day when no records should have been deleted. This was fixed. - March 2024 Digital Resource Management URM-211834
PDF downloads from the embedded PDF viewer download icon were not counted in Alma Analytics, so the icon was removed. PDFs can be downloded instead from the Digital Viewer download icon. - March 2024 Digital Resource Management SF: 06917523 URM-212118
Changes to the metadata filename in CSV format in digital import profiles could not be saved. This was fixed. - March 2024 Digital Resource Management SF: 06937289 URM-212119
The Digital Viewer did not display MP4 files if the extension was in uppercase. This was fixed. - March 2024 Digital Resource Management SF: 06990386 URM-212259
The login interface from the Digital Viewer is a standalone page, which is different from PrimoVE where it is a floating window. This was fixed, and now the floating window login interface appears from the Digital Viewer as well. - March 2024 Electronic Resource Management SF: 06957775 URM-212181
A specific portfolio was not indexed correctly which caused the Upload Electronic Holdings job to fail. This was fixed. - March 2024 Electronic Resource Management URM-213088
The service type within a portfolio name will display as a translated label instead of an untranslated label key. The modification will also apply to the portfolio name column within the export file of electronic portfolio results. - March 2024 Fulfillment and Resource Sharing SF: 06791262 URM-203492
Previously, the Ful Cancel Request Letter contained the cancellation reason Code instead of the description this was fixed by changing the XSL and replacing the cancel_reason with cancel_reason_display. - March 2024 Fulfillment and Resource Sharing SF: 06805054 06850377 06939124 06777474 06381558 URM-198164
The 'Fulfillment - Handle Historical Archiving Job' was slow. This was fixed and the performance was improved. - March 2024 Fulfillment and Resource Sharing SF: 06886373 URM-206603
In a specific case, an error occurred when progressing a digitization request to the next step. This was fixed. - March 2024 Fulfillment and Resource Sharing SF: 06842498 06731087 06678871 URM-192960
The order of libraries in the Resource sharing form was incorrect. This was fixed and from now on, when configuring the alphabetical_sort_pickup_inst_lib to True (Configuration > Discovery > Other > Customer settings), the owner list is also sorted. - March 2024 Fulfillment and Resource Sharing SF: 06928456 06833923 URM-199976
The Blank ILL form opened with default as Book instead of Article and format as Physical instead of Digital. This was fixed. - March 2024 Fulfillment and Resource Sharing SF: 06909105 URM-207653
In some cases, the Received Items window Item Policy descriptions and Locations were displayed in English rather than in the selected language. This was fixed. - March 2024 Fulfillment and Resource Sharing SF: 06891855 06960866 06958253 URM-211238
In the metadata editor, when saving a record with field 006 position 0 = 'o' and a matching material is defined in the LDR field position 6 (g, k, o, or r), the warning message was displayed: "'o' not a valid code for position 0 for field 006". This was fixed and now the warning message is not displayed for this combination. - March 2024 Fulfillment and Resource Sharing SF: 06580298 URM-188743
Aleph Central Catalog Integration Profile - When a record with linked records is being redirected to another record, the related records were not indexed and therefore the search for the merged record didn't return its related records. This has been fixed. - March 2024 Metadata Management SF: 06984603 URM-212510
Inconsistent suppress icon displayed in the Metadata Editor. When navigating away from a newly suppressed record in the MDE, the 'Suppressed' icon disappears from the persistent record list. This was fixed. - March 2024 Metadata Management SF: 06655451 URM-188960
General publishing - When related record configuration was enabled, in rare cases some of the records were not published. This has been corrected. - March 2024 Metadata Management SF: 06843546 06945576 URM-209470
General Publishing > Campus level: records with both deleted portfolios and physical items were not published as deleted, This was fixed. - March 2024 Metadata Management SF: 06888317 URM-207804
When replacing sets in a logical collection, the title count combines the sets and gives an incorrect count. This was fixed and the title count now matches the set that is currently used for the logical collection. - March 2024 Metadata Management SF: 06742725 06713628 URM-192107
Terms containing Swedish characters that are indexed in two forms and also contained diacritics that should be normalized to standard ASCII were sometimes not returned in search results. This has been fixed. - March 2024 Metadata Management SF: 06917048 URM-210674
Manage Sets > Sort by > The sort by Creation Date did not sort correctly according to the creation date. This was fixed. - March 2024 Metadata Management SF: 06836348 URM-211987
When trying to create a physical holding set from a file and the header is "Holding Id" the created set is empty. This was fixed and now the set contains entries. - March 2024 Metadata Management SF: 06232949 06759158 URM-180668
CDI-only full text activation is missing for database collections with CDI type Hybrid. This was fixed by adding another condition to the display of the "CDI-only full text activation" option: CDI type is Hybrid & Alma collection type is Database. - March 2024 Physical Resource Management SF: 06309923 URM-170415
Physical Item Editor: When one of the following fields of an item in work order is updated - Material Type, Item Policy, Description - a misleading message is displayed in the save confirmation popup window: "The item is in work order, moving the item might cancel the requests if the item not requestable in the new location.". This has been fixed, i.e. this message is no longer displayed. - March 2024 Physical Resource Management SF: 06838908 06776954 06864928 06787955 URM-199090
After editing a holdings in the metadata editor and viewing its items (view related data > view items), changing the work order of an item or withdrawing one or more items resulted in a Java error message, although the operation succeeded. This was fixed and now no error message is displayed. - March 2024 Physical Resource Management SF: 06701106 URM-205051
Previously edited holdings remain stuck in the Metadata Editor when the item is saved using Write to RFID and Save. This is fixed - March 2024 User Experience, Accessibility & Infrastructure SF: 06473503 06969022 06826866 URM-178247
In a Fulfillment Network, when creating a request in Primo, pickup locations in other institutions were not translated. This was fixed. - March 2024 User Experience, Accessibility & Infrastructure SF: 06912651 URM-207631
The "Exlibris - Implementer" user role could be added to accounts via the API/cloud apps etc. This was fixed. - March 2024 User Experience, Accessibility & Infrastructure SF: 06966133 URM-212731
Sending emails from the integration profile using the Save and Test button failed with a general error message. This was fixed; A specific error message with the reason of failure is displayed. - March 2024 User Experience, Accessibility & Infrastructure SF: 06874064 URM-166007
The slash key "/" shortcut to reach the persistent search bar did not work for the physical holdings search. This is fixed and now the shortcut works as expected. - March 2024 User Experience, Accessibility & Infrastructure SF: 06825150 URM-209054
The "Alt" key did not work for some time after returning back from the Metadata Editor page. This was fixed and the "Alt" key now works as expected. - March 2024 User Experience, Accessibility & Infrastructure SF: 06958125 URM-209963
The 'Updated by' audit trail did not appear on the 'New Digital Adoption Tool' page. This was fixed and the "Updated by" indication is now displayed. - March 2024 User Experience, Accessibility & Infrastructure SF: 06877987 URM-212479
When exporting the User Statistical Categories table, the ampersand (&) in "Target Code Combo [Statistical Category]" was incorrectly converted into & amp;. This is fixed and the ampersand is exported as the character &. - March 2024 User Experience, Accessibility & Infrastructure SF: 06654450 06586791 06661962 URM-187052
In some cases, it was not possible to save a translation for a library name. This was fixed. - March 2024 User Experience, Accessibility & Infrastructure SF: 06673914 URM-196517
The Item policy translation was not used in On Hold Shelf Letter according to the user preferred language. This was fixed. - March 2024 User Experience, Accessibility & Infrastructure SF: 06891184 06827070 06586791 06937432 URM-209060
Updating translations for the Institution name and description was not saved in some cases. This was fixed. - March 2024 User Experience, Accessibility & Infrastructure SF: 06560703 06881423 URM-192047
In Email Notifications for Scheduled Jobs, in some cases, the emails/users added were not saved. This was fixed.
- February 2024 Release Update Analytics and Insights SF: 07037794 07038541 URM-215055
Primo Analytics was not available in the Alma menu. This was fixed and now the Primo link appears in the menu. - February 2024 Release Update Acquisitions SF: 07037894 URM-215102
An error occurred when the PO line receiving note contained an ampersand. This was fixed. - February 2024 Release Update Metadata Management SF: 07038033 07043333 URM-215101
An error occurred when there were Hebrew characters in the Browse Shelf Listing input form. This was fixed. - February 2024 Release Update Fulfillment and Resource Sharing SF: 07038718 07039695 URM-215261
Changing the format of a resource sharing borrowing request to digital changes the owning library. This was fixed. - February 2024 Release Update Fulfillment and Resource Sharing SF: 07009195 URM-213853
In SIP2 ACS Status (98), Alma sent Y on the 8th position in the BX field even though Alma does not support EndPatronSession. This was fixed, and Alma now sends N.
- February 2024 Acquisitions SF: 06856983 06941132 URM-199029
After deleting PO lines, the list did not refresh. This was fixed. - February 2024 Acquisitions SF: 06860134 06957562 06950279 06858390 06959022 URM-204300
Exporting to Excel for itemized sets did not work. This was fixed. - February 2024 Acquisitions SF: 06754687 URM-206633
For the New Order import profile, the interested users checked options were removed when the Scheduler status was activated. This was fixed and the interested user checkboxes are now correctly marked, even when updating a field in a different tab. - February 2024 Acquisitions SF: 06906368 URM-209063
PO lines with "No charge" were incorrectly set to "Waiting for invoice". This was fixed and No Charge PO lines are now closed after being received/activated. - February 2024 Acquisitions SF: 06922937 URM-209140
When selecting some facets for PO lines, the results included libraries that were out of scope for the user's role. This was fixed. - February 2024 Acquisitions SF: 06941890 URM-209318
In the new layout for PO Lines, changes to the material type were not copied to the items. This was fixed. - February 2024 Acquisitions SF: 06900098 06976949 06985620 06987622 06976246 07011743 06972222 06957366 06978536 URM-210935
In the new layout for Acquisitions, when removing the subscription interval, the field became null instead of 0. This was fixed here as well as for other fields in the vendor information section. - February 2024 Acquisitions SF: 07013678 07009543 07003504 07005155 07000664 URM-212846
When the license on the poline was not changed, it overrode the license of the resource. This was fixed, and now only changing the license on the PO line overrides the license on the resource. - February 2024 Acquisitions SF: 06924048 06973031 URM-209313
In the new layout for PO lines, the reporting codes were listed in a different order than configured (they were sorted alphabetically). This was fixed. - February 2024 Acquisitions SF: 06918957 06952161 06960746 URM-211016
In the new Acquisitions layout, an error was displayed when using a template for an order without inventory. This was fixed. Note that the customer needs to verify that the template matches the PO line type. - February 2024 Acquisitions SF: 06949405 06960553 06960570 URM-209514
In the new layout for PO lines, there were various issues regarding the display of certain fields and messages, such as the Save and Continue button, the Deferral reminder, the Deferring reason fields, etc. These were fixed. - February 2024 Acquisitions SF: 05310951 05317919 06656854 URM-142676
When trying to send an EDI Order, an error (EDI File created empty) was sometimes displayed. Prints were added to the log to identify the issue when it occurs. - February 2024 Acquisitions SF: 06866241 URM-206952
New order imports created multiple orders and multiple copies for the same title. This was fixed. - February 2024 Acquisitions SF: 06906912 URM-207607
In the new layout for PO lines, there was a discrepancy in the activation calculation where "Not Activated" was displayed instead of "Active". This was fixed. - February 2024 Acquisitions SF: 06956063 06959041 URM-210162
In the new layout for Acquisitions, PO lines were automatically assigned to the current user after relinking. This was fixed. - February 2024 Acquisitions SF: 06960968 URM-211676
Customers were able to (accidentally) create POs with a blank at the end of the PO number. This caused the sending of EDI files job to fail. This was fixed, and leading and trailing spaces are now trimmed before saving. - February 2024 Acquisitions SF: 06794699 06943594 06648178 06645510 06799215 URM-189549
When creating an invoice from a PO, the Search by Title option was not available. This was fixed. Note that searching by title is not available when "All" is selected for the search criteria. - February 2024 Acquisitions SF: 06733671 URM-207212
PO Line Aggregated Claim Letter: When all claimed PO Lines were from the same owning library, the sender address displayed on the notification was the institution's address instead of the library's preferred address. This was fixed. - February 2024 Acquisitions SF: 06970282 06954681 06968974 URM-211005
In the fund editor, expended and encumbered balances were not shown as links when the form was opened in view mode. This was fixed. - February 2024 Acquisitions SF: 06905126 URM-211466
Vendor Accounts did not display the institution name. This was fixed. - February 2024 Acquisitions SF: 06870478 URM-207244
In certain cases, the EDI load job report said that nothing was processed even though records had been successfully processed. Prints were added to the log in order to follow up if this issue occurs again. - February 2024 Acquisitions SF: 06275266 06564712 06621140 06573671 06638644 06963135 URM-171236
Weekly and daily prediction patterns did not count the next cycle correctly. The first cycle of "Open predicted items" worked properly, but when clicking again on the "Next predicted item's information" menu item, the dialog box presented the information from the previous cycle. This was fixed. - February 2024 Analytics and Insights SF: 06885535 URM-207839
Patron deposits appear as created by System in Analytics in the Digital Inventory subject area. The information on the patron that created the deposit is missing. This was fixed and now the patron details appear. - February 2024 Analytics and Insights SF: 06700562 URM-196712
The default data format for the Object ID in the Analytics Objects subject area inserts a comma as a thousand separator. This was fixed, and now the separator does not appear. - February 2024 Analytics and Insights SF: 06842785 URM-205355
Export from the Analytics Object List and Share with Me in the analytics new layout failed in some cases. This was fixed. - February 2024 Analytics and Insights SF: 06951833 URM-209842
The Digital Inventory > Digital File Size (In Bytes) field was in plain text format (VARCHAR) and not numeric. This was fixed. - February 2024 Analytics and Insights SF: 06697526 URM-197475
In the Analytics Object List, the time zone of the "Object created by" and "Object modified by" fields was not configured for the customer and always displayed the timezone for GMT. This was fixed, and now the date fields reflect the time zone configured for the customer. - February 2024 Analytics and Insights URM-209530
Infrastructure improvements were made to enhance overall analytics performance with an emphasis on the Network Zone. If you experience any decrease in performance or negative effects on your reports, contact Ex Libris Support. - February 2024 Fulfillment and Resource Sharing SF: 06889649 06999447 06878268 URM-206190
The list of call number types was not displayed in the Create Request tab. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06684433 06762570 06965903 06730805 06708573 06847405 06681627 06947566 06956077 06731941 URM-192103
In some cases, the Quick Print dialog window for the Resource Sharing Shipping Slip Letter was not displayed as expected. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06782142 URM-206245
The Reshelve without Transit rules between locations within the same library did not work when scanning in an item that was already in transit. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06510599 06657234 URM-181944
In some cases, an error message (Could not send message: Failed to process message) appeared for an FSU request in the Ready to be Sent status. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06493894 06706084 06661180 06901719 06723618 06762904 06942751 06468567 URM-179649
In some cases, selecting "Show file" on a borrowing request did not open the associated file. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06762029 06719009 06746060 06874839 06932465 06505299 06763320 06486736 URM-181216
In some cases, borrowing requests had duplicate active partners leading to multiple issues such as lending libraries getting two identical requests from borrowing libraries. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06931268 06834652 URM-209679
The title enriched from PubMed was different from the actual title. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06680840 06708573 06681627 06690682 URM-189608
When the print slip was sent by email, the print slip did not open even when a success message was displayed. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06822506 URM-199005
In some cases, when calculating items for serial multi volumes, an error occurred when printing all items in the letters. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06879314 URM-208252
In some cases, when users shared the same pod, a duplicate partner was created. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06929751 URM-208546
In some cases, when a request was assigned to a lender, but the request failed to be received, no error was generated. This was fixed. - February 2024 Fulfillment and Resource Sharing SF: 06978810 URM-213022
The Rapido Expand search in the Advanced Search did not work. This was fixed. - February 2024 Metadata Management SF: 06865878 URM-204926
Update inventory import profile failed with “File Failed” in Additional Services Processing. This was fixed and the files are imported correctly. - February 2024 Metadata Management SF: 6298838 06566483 URM-173323
Slowness when “Saving New Item” if Title has ~2000 Items. Unfortunately, this issue cannot be resolved and no improvements can be done about performance when creating a new item for a holdings record that has more than 2,000 items. - February 2024 Metadata Management SF: 06701845 URM-204318
When a holdings record was deleted, the modification date was not updated in field HOLDING_MODIFICATION_DATE of its equivalent INVENTORY_HOLDING record. This was fixed by including the fetched data from the MODIFICATION_DATE column. - February 2024 Metadata Management SF: 06699207 URM-197087
Previously, when using the portfolio loader to create a local portfolio with a bibliographic record linked to the CZ, the electronic material type was not appropriately considered, even though the portfolio itself was local. This issue was fixed. Now, when activating a local portfolio with a CZ-linked bibliographic record, the electronic material type is correctly utilized based on the input file, aligning with the documentation. - February 2024 Metadata Management SF: 06873294 URM-207316
Opening a Universal Viewer URL with an adjusted position or file reverted to the first file automatically. This was fixed, and now the position and file information is retained. - February 2024 Metadata Management SF: 06835505 05306392 URM-164393
Collection-related search indexes for certain bibliographic records, if they were part of a collection and also attached to an electronic collection with portfolios, were sometimes built incorrectly. This was fixed. - February 2024 Metadata Management SF: 06807914 URM-206371
The "Inventory Remote Storage Update" job only handled items that were modified since the end time of the previous job. As a result, items that were modified while a job was in process were not handled by any job. To fix this, now the job handles all items that were modified since the start time of the previous job instead of from its end time. - February 2024 Metadata Management SF: 06879954 URM-206125
When combining sets in the new UI, the option to see the recently used sets is not available. This was fixed. The recent values are added to the pickup in the manage sets merge dialog. - February 2024 Metadata Management SF: 07003427 URM-212852
The "Creator" column was missing from the Excel export in the New UX for Manage Sets. This was fixed and the column is now displayed. - February 2024 Metadata Management SF: 06708845 URM-195882
Browse Bib Headings - "Open in repository search" was not working for headings containing asterisk characters. This was fixed. - February 2024 Metadata Management SF: 06644396 URM-197628
The Dynamic URL with "REPLACE" action did not work properly. This was fixed and now the "REPLACE" action functions as expected. - February 2024 Metadata Management SF: 06720661 URM-204419
MD Editor > Holdings record: Record Actions > "Update from Bibliographic" - When the holdings record has field 852 with 1st indicator "7" and TEXT in subfield $$2, and column "852 subfield 2" of the "Call Number Mapping" table is set to TEXT, and the bib record has more than one relevant bib field (e.g. 084), Alma selects the first bib field, regardless of the contents of dssubfield $$2. This has been fixed. That is if the bib record has more than one matching field (e.g. 084), the field with the correct contents in subfield $$2 is selected for the "Update from Bibliographic" action. - February 2024 Metadata Management SF: 06776098 URM-198070
KORMARC: When adding 041 $$k, a warning was displayed saying "Sub-field "k" is not listed in profile for field 041"; however, according to KORMARC, this is valid. This was fixed and 041 $$k was added to the metadata profile. - February 2024 Metadata Management SF: 06797477 URM-198071
Metadata Editor > KORMARC: Leader position 7 was requested to be updated. This was resolved and 041 $$k, was added to the metadata profile. - February 2024 Metadata Management SF: 06835597 URM-206389
When running a normalization process with a normalization rule that checks for # or space characters in the condition part, the normalization was not applied to records created by import, which include the '#' sign in a control field and matches the condition. This was fixed and now the normalization works as expected. - February 2024 Metadata Management SF: 06700868 URM-193118
Non-filing text was not removed from the non-preferred authority heading normalized value for UNIMARC uniform title fields 430, 431, 530, 531. (It is removed from the preferred heading normalized value.) As a result, bibliographic headings linked to the non-preferred headings were marked as partial instead of full matches (indicated by a half-binocular icon instead of a full binocular icon in the MD Editor). The preferred term correction job did correctly update the bibliographic record fields, but the preferred term correction job did not change the status of the bibliographic heading "full match" property, so even after the PTC job, the bibliographic record fields still displayed a partial match icon. This was fixed by removing the non-filing text from these authority non-preferred fields so that the normalized value is the same format as that generated by the preferred field and by the field in the bibliographic record. - February 2024 Metadata Management SF: 06813234 URM-204700
The Authorities > Preferred Term Correction job duplicates subfield $$e in MARC fields 711 and 880. This was fixed. To implement the fix, set the new customer parameter "preferred_term_correction_dont_duplicate_711_sub_e" to "true". - February 2024 Metadata Management SF: 06797757 URM-210853
The Alma UI Authority record copy functionality pop-up is not translated into Spanish. This was fixed and the Alma UI Authority record copy functionality pop-up is now translated. - February 2024 Metadata Management SF: 06855072 06892524 URM-204769
When running an import job using a profile configured with 'Single match – match only record with the same inventory type' or 'match on title type' and configured to 'do not add' upon match, single matches are found but not shown on the report when previewing the matched records. This was fixed and now the matches are shown on Report > Matches found > Preview Records. - February 2024 Metadata Management SF: 06630824 URM-207835
UNIMARC Authority records display the incorrect pos. 25 in tag 100. This was fixed and the UNIMARC Authority - Field 100 position 25 was removed. - February 2024 User Experience, Accessibility & Infrastructure SF: 06768464 URM-163162
The default search drop down under Resources > Import > Import Profiles was changed to Profile Name instead of Profile Description. - February 2024 User Experience, Accessibility & Infrastructure SF: 06824195 06642135 URM-187126
Having a '$' sign in the block description caused the history tab to show an error. This was fixed. - February 2024 User Experience, Accessibility & Infrastructure SF: 06766884 06781864 URM-197847
Multi-select fields were not displayed in the search results header on advanced searches for users. This was fixed. - February 2024 User Experience, Accessibility & Infrastructure SF: 05553980 06624418 URM-61709
EDI > Invoice line contains <br> tags when you open it in View mode. This was fixed and <br> tags are not displayed. - February 2024 User Experience, Accessibility & Infrastructure SF: 06859929 URM-210556
Letter's Subject was not translated when Sending the Letter Example from the XSL Edit page. This was fixed. - February 2024 User Experience, Accessibility & Infrastructure SF: 06971955 06520653 URM-183442
License terms' values were not translated when using the Catalan UI on Primo VE. This was fixed by adding the code table LicenseTermsPermittedProhibited to the TranslationData mapping table. - February 2024 User Experience, Accessibility & Infrastructure SF: 05539323 05469450 05310992 URM-128982
IDP initiated single logout does not work. The SAML response comes back with a status of partial logout to logout requests. This was fixed. - February 2024 User Experience, Accessibility & Infrastructure SF: 06893190 06944377 URM-207238
Scheduling for the "Notifications - Send Periodic Fulfillment Activity Report" job was recalculated each time the "Fulfillment Jobs Configuration" page was accessed. This was fixed. - February 2024 User Experience, Accessibility & Infrastructure SF: 06897174 06904867 06964447 URM-207517
The "Overlap and Collection Analysis" job would sometimes fail in the finalizing stage due to failure to send the email to the user who initiated the job. This was fixed. - February 2024 User Experience, Accessibility & Infrastructure SF: 06877671 URM-208597
Local fields were not displayed in the Alma Viewer for DC records. This was fixed, and now Local fields for DC records are displayed in the Alma Viewer. - URM-198647 February 2024 Fulfillment and Resource Sharing SF: 06696033 06773525 06853099 06869112
In some cases, when a request was changed from digital to physical, the request status incorrectly changed to Returned item to partner. This was fixed. - URM-206799 February 2024 Fulfillment and Resource Sharing SF: 06848438
In some cases, the lending request would display the first value from the Requested Media drop-down list rather than a blank value. This was fixed. - URM-193553 February 2024 Fulfillment and Resource Sharing SF: 06746793
In some cases, when an item was received by the Circulation Desk, the wrong Pickup location was displayed in the right pane. This was fixed. - URM-180783 February 2024 Fulfillment and Resource Sharing SF: 06802260
In some cases, the wrong font was outputted on the print slips. This was fixed. - URM-194108 February 2024 Fulfillment and Resource Sharing SF: 06587987 06844403
In some cases, when selecting a location in the Create Move Request dialog box, the loan was not recalled, and the Ship physically was created with a "Pickup From Shelf" status rather than "Place in Queue:1". This was fixed. - URM-181216 February 2024 Fulfillment and Resource Sharing SF: 06486736 06505299
In some cases, lending libraries received duplicated requests. This was fixed. - URM-210413 February 2024 Fulfillment and Resource Sharing SF: 06656516
When Alma responded to an NCIP P2P RequestItem message, the response had some fields in the wrong order. This was fixed, and Language is now after BibliographicLevel. - URM-201825 February 2024 Fulfillment and Resource Sharing SF: 06656516
When sending a request to a NCIP P2P partner, the volume/issue/chapter/part information was sent under the Ext element. This was fixed and the information is now sent in the ItemNote element, separated by pipes, such as in the following example:
||Language: ab|| ||Pmid: PMID|| ||Volumes: Volume|| ||Issues: Issue||
- January 2024 Acquisitions SF: 06965964 06973064 06933377 06891026 06936420 06909220 06918857 06955899 URM-198595
Changing the expected receipt date on a Product Order Line did not update the receiving date for its item. This was fixed. - January 2024 Acquisitions SF: 06913249 URM-209902
Saving PO Lines resulted in an error message when there ACQ an empty Access Model. This was fixed. - January 2024 Acquisitions SF: 06616660 06802230 06788619 06810447 URM-189321
The Danish translation was not working for the PO Line Aggregated Claim Letter. This was fixed. - January 2024 Acquisitions SF: 06945630 06922974 URM-208573
An error message was displayed when trying to create a logical set from an advanced search with more than one group of queries. This was fixed. - January 2024 Acquisitions SF: 06819403 06796008 06789480 URM-198762
When trying to change the acquisition method for two migrated PO lines, the "Update PO Lines Information - Advanced" job completed with errors. This was fixed. - January 2024 Acquisitions SF: 06833198 URM-203354
When doing an advanced search for PO Lines, the disabled material types were displayed. This was fixed. - January 2024 Acquisitions SF: 06854826 URM-204918
The PO Line history showed that the “Renewal Note” was removed by the user when in fact it was not removed and still appeared in the PO Line Summary. This was fixed. - January 2024 Acquisitions SF: 06889740 06947727 06820585 06905150 06896387 URM-206798
When creating a PO Line of type 'Print Book - One Time', no material type was inserted into the ordered item. This was fixed. - January 2024 Acquisitions SF: 06672523 06924759 URM-209357
Updating a renewal date in a PO Line via the API did not update the PO Line status to Recurring Renewal. This was fixed. - January 2024 Acquisitions SF: 06954716 URM-209793
When saving a PO Line in the Japanese UI, the PO Line number in the popup message was not a clickable link. This was fixed. - January 2024 Acquisitions SF: 06702686 URM-191469
Until now, it was possible in Alma to create two invoices for the same supplier with the same invoice number. This was fixed and now, when the "invoice_not_unique" customer parameter is false, it is impossible to duplicate the invoice number of the same supplier. - January 2024 Acquisitions SF: 06826272 URM-205096
There was a data issue with invoices that had extra spaces in the invoice number (at the beginning or at the end). The job was fixed to ignore these spaces. - January 2024 Acquisitions SF: 06898063 URM-207250
The Invoice Approval Rules output parameter was disabled and could not be selected. This was fixed. - January 2024 Acquisitions SF: 06871891 06887946 06955160 06907580 06967685 URM-206703
Users received an error when searching for a fund in the "Update PO Lines transactions" job. This was fixed. - January 2024 Acquisitions SF: 06977291 06677100 06709371 URM-196842
Pagination was not working correctly for Vendor Usage Data. This was fixed. - January 2024 Acquisitions SF: 06849276 06934946 06859004 06806758 URM-204851
When viewing or downloading letters attached to users, the logo appeared as a broken image. This was fixed and the logo is now removed from the attachments when downloaded. - January 2024 Acquisitions SF: 06822332 URM-199595
The New Order Import job completed with errors. This was fixed. - January 2024 User Experience, Accessibility & Infrastructure SF: 06841563 URM-209573
In the Fine/Fee Transaction List, the column "Transaction Type" always displayed with the value in English. This was fixed and now the "Transaction Type" column is translated. - January 2024 User Experience, Accessibility & Infrastructure SF: 06770224 URM-201412
Deleting a sponsor user record via the ‘Users - Purge Records’ job manually, did not delete "Proxy for" entries in the proxy user record. This was fixed. - January 2024 User Experience, Accessibility & Infrastructure SF: 06770510 URM-206141
In the General Electronic Service List, the copy option from the Community tab was unavailable for a user that did not have the 'Catalog Administrator' role. This was fixed and the copy option is now available for users with 'Fulfillment Administrator' and 'General System Administrator' roles. - January 2024 User Experience, Accessibility & Infrastructure SF: 06903539 URM-208416
The User Identifiers section did not appear when trying to register a new user. This was fixed. - January 2024 User Experience, Accessibility & Infrastructure SF: 06946584 06330794 URM-172641
A "Successful Login" event was logged for Alma logins and also Primo VE and Esploro logins. This was fixed and now events are only logged for Alma logins. - January 2024 User Experience, Accessibility & Infrastructure SF: 06845886 06353924 URM-178880
Sending a preview of an email from the XSL editor included an XSL file as an attachment, which caused it to be filtered out by some email servers. This was fixed by removing the XSL attachment. - January 2024 User Experience, Accessibility & Infrastructure SF: 06905998 06957373 URM-209648
When updating existing users via SIS, two new entries were documented in the user history, containing roles that were removed and added again. In addition, the Patron Welcome Letter was sent to the updated user. This was fixed. - January 2024 User Experience, Accessibility & Infrastructure SF: 06905666 URM-209183
In Overlap Analysis > Compare collections, the new checkbox of physically related titles was cut off at the end of the page for small-size pages. This was fixed. - January 2024 User Experience, Accessibility & Infrastructure SF: 06452271 URM-180639
A label with the Relation Type was displayed in English when searching the NZ. This was fixed and now it appears translated, according to the UI language. - January 2024 User Experience, Accessibility & Infrastructure SF: 06749523 URM-197634
Some translations were missing in the German Alma interface. This was fixed and the translations are displayed correctly. - January 2024 User Experience, Accessibility & Infrastructure SF: 06827070 06586791 06937432 URM-209060
Updating translations for the Institution name and description was not saved in some cases. This was fixed. - January 2024 User Experience, Accessibility & Infrastructure SF: 06852556 06863747 06848719 URM-208427
General Publishing > Entire Repository for single institution > Records were incorrectly published as 'deleted'. This was fixed. - January 2024 Analytics and Insights SF: 06768996 URM-199847
Previously, event type 9110 - "Successful login" recorded successful logins for Alma, Primo, and Esploro. Now two new events were added that distinguish between the logins for Primo and Esploro - 9914 - "Successful login - Primo" and 39110 - "Successful login - Esploro". - January 2024 Analytics and Insights SF: 06844130 URM-201890
In the Primo analytics subject area, Customized Values Usage, the Year field displayed the thousands separator in the default format. This was fixed, and now no separator is displayed. - January 2024 Analytics and Insights SF: 06793372 URM-204878
The loan notes were not anonymized by the anonymization job even though the "Anonymize item loans" and "Anonymize item loans Notes" checkboxes were selected. This was fixed. - January 2024 Analytics and Insights SF: 06913155 06877204 URM-208831
An error message was displayed when trying to access a Data Visualization workbook. This was fixed. - January 2024 Analytics and Insights SF: 06939368 06904808 URM-209664
Pinned objects did not display in the "Pinned Objects" area under the main Analytics menu for some users. This was fixed. - January 2024 Analytics and Insights SF: 06867486 URM-207610
Searching for analytics objects by the creator name did not return results if the user configured the user display name format. This was fixed. - January 2024 Analytics and Insights SF: 06879710 URM-208471
When the Analytics New Layout attempted to display a report preview for very large reports, performance was slow and the page eventually crashed. This was fixed by improving performance. - January 2024 API SF: 06725312 URM-198295
When sending an invalid id_type to the user API, a misleading error message appeared. This was fixed. The new message is "Identifier type <id_type> does not exist." - January 2024 Digital Resource Management SF: 06525080 URM-180869
Thumbnails of records in the Institution Zone and Network Zone were not displayed in the Full View Search page in Primo Discovery. This was fixed. - January 2024 Digital Resource Management SF: 06852489 URM-205042
It was not possible to save access rights policies when the interface language was set to a language other than English. This was fixed. - January 2024 Digital Resource Management SF: 06783763 URM-207531
The Digital Viewer stretched images instead of displaying them in their proper proportions. This was fixed. - January 2024 Digital Resource Management SF: 06894835 URM-209104
The Digital Viewer did not display remote representation videos from YouTube. This was fixed. - January 2024 Digital Resource Management SF: 06936191 URM-209366
The import job imported records even though an Indication Rule was configured to not include them. This was fixed. - January 2024 Electronic Resource Management SF: 06638145 06630663 06651795 06556464 06665253 URM-186712
In the Upload Electronic Holdings job for Wiley, there were some cases that related (preceding/succeeding) titles were grouped with a common e-ISSN identifier which caused coverage records to be saved for the wrong portfolio in the group. We've developed an opt-in fix for this which can be activated by Support. - January 2024 Electronic Resource Management SF: 06934542 06743363 URM-207342
In Upload electronic holdings job the vendor file was downloaded partially due to a network connection issue. The job deleted portfolios that were not loaded in the file. This issue was Fixed and if the file is not fully downloaded the job will fail and not delete data. The network issue remains and is still being tested. - January 2024 Electronic Resource Management SF: 06859460 URM-208835
The Available Online Service Order list would sometimes reorder unexpectedly after using the up/down arrows. The issue was caused by previous deletions of elements from the list. This was fixed. - January 2024 Fulfillment and Resource Sharing SF: 06572730 06784765 URM-198089
When returning items on the Return Items page, quick printing would only print the last one. This was fixed and now all the letters are printed. - January 2024 Fulfillment and Resource Sharing SF: 06811842 URM-199233
“Export to Excel” from the "Loans - Overdue and Lost Item" job was not working. This was fixed. - January 2024 Fulfillment and Resource Sharing SF: 05333163 06753870 URM-149958
Requesting the item information through SIP returned incorrect current location and permanent location. This was fixed. - January 2024 Fulfillment and Resource Sharing SF: 06783363 URM-201495
The digitization requests Note field was not populated when viewing the "Monitor Requests & Items Process" page as it is in the 'Approval requests list'. This was fixed and the notes display is now aligned between the two pages. - January 2024 Fulfillment and Resource Sharing SF: 06927537 URM-198111
Link resolving was not working correctly for some portfolios with URL linking parameters that needed encoding. This was fixed. - January 2024 Fulfillment and Resource Sharing SF: 06682547 URM-198303
The Display Logic Rules for electronic collections was not working in some cases. This was fixed. - January 2024 Fulfillment and Resource Sharing SF: 06842498 06731087 06678871 URM-192960
The order of libraries in the Resource sharing form was incorrect. This was fixed and from now on, when configuring the following, the owner list will also be sorted: Configuration > Discovery > Other > Customer settings > alphabetical_sort_pickup_inst_lib to True. - January 2024 Fulfillment and Resource Sharing SF: 06845568 URM-207363
The new PO Line task list did not support Cloud Apps. This was fixed. - January 2024 Fulfillment and Resource Sharing SF: 06722286 06638742 URM-196639
When creating a move request using the lending request task list action, in certain cases it returned a general error. This was fixed. - January 2024 Fulfillment and Resource Sharing SF: 06783317 URM-196735
Prior the fix, in Firefox, each field in the “Request form (filled out by the requester)” was not wide enough to display all the information filled in by the requester and the text was cut off in the middle. This was fixed - the fields are now auto-adjusting themselves to the window size. - January 2024 Fulfillment and Resource Sharing SF: 06575033 URM-199969
'Borrowing Resource Sharing' FU rule didn't not work when it has “Request Format” = Digital, Physical non-returnable as Input Parameter. It was fixed - now the rule works with or without the parameter, accordingly. - January 2024 Fulfillment and Resource Sharing SF: 06819035 URM-204993
When manually creating a Resource Sharing request for local inventory from the borrowing requests task list in Alma, the warning message: "The institutional inventory has services for the requested title" appears. - January 2024 Fulfillment and Resource Sharing SF: 06838857 06813375 06794098 URM-205145
When selecting the "Renew" action for a blocked user, the "override and renew" button did not override the blocks. Now, selecting this button overrides the user's relevant blocks. - January 2024 Fulfillment and Resource Sharing SF: 06852437 06733299 URM-206592
When exporting borrowing requests, the Volume did not appear for items of material type other than Book. This was fixed and these now appear in the exported file. - January 2024 Fulfillment and Resource Sharing SF: 06788171 URM-197882
Previously, "Find user in other institution" allowed the user to select all of the fulfillment members, including inactive members. This was fixed, and now only active fulfillment members are selectable. - January 2024 Fulfillment and Resource Sharing SF: 06786750 06785297 URM-199980
In some cases for SLNP, borrowing and lending requests were created as an "Article" instead of a book. This was fixed. - January 2024 Physical Resource Management SF: 6865878, URM-204926
Update inventory import profile failed with "File Failed" in Additional Services Processing. This was fixed and files are processed without failure. - January 2024 Physical Resource Management SF: 06706368 URM-204528
Physical holdings advanced search results are no longer displayed when the search is saved. This was fixed and search results saved as logical sets are displayed. - January 2024 Metadata Management SF: 06896322 URM-208522
General Publishing - When publishing a combined results set to an FTP server with 'Binary' format and 'Institution Code Subfield' was not defined, the published records were not written to the file. This was fixed. A default sub-field code 'A' is used when 'Institution Code Subfield' is not defined. - January 2024 Metadata Management SF: 06877613 URM-209257
Previously it was possible to incorrectly delete a collection that is in use or has a sub-collection with titles. This has been fixed and collections in use or sub-collections with titles cannot be deleted. - January 2024 Metadata Management SF: 06586304 URM-184789
In an advanced search for Physical Holdings, setting the keyboard language to Chinese does not offer suggestions after entering the first Chinese character. This was fixed. - January 2024 Metadata Management SF: 06803548 URM-201898
Authorities Advanced Search > When changing the default index and then duplicating the condition > The default index is duplicated, not the chosen one. This was fixed. - January 2024 Metadata Management SF: 06979504 06844447 06872953 URM-206717
Assign set in the logical collection editor led to pickup without tabs. Only "My sets" was available and all/public tabs were missing. This was fixed. - January 2024 Metadata Management SF: 06868269 URM-209474
API call returned INTERNAL_SERVER_ERROR in cases that attempted to fetch a set member that was deleted (PO Line set only). This was fixed so that instead of PO Line reference number in the member, the following is returned:
<member>
<id>PO line 90333130000521 was deleted</id>
</member> - January 2024 Metadata Management SF: 06805199 URM-201659
When limiting a search to a single record, the retrieved record was not the first record retrieved when searching with a larger number of 'maximumRecords' is used. This was fixed and now when limiting for a single record in SRU, we receive the first result. - January 2024 Metadata Management SF: 06393626 URM-176744
The "time_zone" field in Rest-dlf loans API did not consider daylight saving time. This was fixed. - January 2024 Metadata Management SF: 06747893 URM-195927
Loans that were renewed did not show the last renew date field in Primo and Primo VE. This was fixed. - January 2024 Metadata Management SF: 06802730 URM-201588
852 $z notes were entered in the same order in Alma and were displayed in a different order in Primo VE. This was fixed. - January 2024 Metadata Management SF: 05311154 05316382 05316373 URM-189468
In UNIMARC, headings created from 410/411 fields are not displayed in the 'Headings from bibliographic records' tab. This was fixed. - January 2024 Metadata Management SF: 06425159 URM-175547
MDE performance issues (slow) for headings from the bibliographic records list. This was fixed and the performance improved. - January 2024 Metadata Management SF: 06715059 URM-197392
In the Browse Bibliographic Headings, when searching for Subjects (with Marc21 6XX) and the institution has defined more than one vocabulary in the 'authority_names' customer parameter, sometimes the results are not accurate. In some cases, headings from one of the name's vocabularies are not displayed in the results list. This was fixed and now the list of results is accurate and all headings are displayed sorted, as expected. - January 2024 Metadata Management SF: 06889657 URM-207642
When multiple authority vocabularies have the same Direct ID prefix, only one of the vocabularies was checked when attempting to match bibliographic headings to authority headings. This has been fixed. - January 2024 Metadata Management SF: 06800454 06709008 06948925 06767353 06757865 06747275 06750229 06754779 06947479 06747433 06984274 URM-193438
Selecting "Resolve Import Issues" gives a blank screen with an error message and a unique tracking ID. This was fixed and no errors are displayed.