Alma March 2024 Release Notes
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
Features
Loan Measures Dimension Added to Physical Items Subject Area
March 2024 Analytics and InsightsURM-211946
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.
Additional Enhancements
- March 2024 Acquisitions 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
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
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.
Resolved Issues
| SF number | Area | Description |
|---|---|---|
| 07013070 | Acquisitions | When cancelling an update operation for the Rush or cancellationRestriction fields in a PO Line, the fields were still updated. This was fixed. |
| Acquisitions | When sending the operational mark_in_erp process, the related PO Lines were not closed. This was fixed. | |
| 06966881 06886687 | Acquisitions | An error was displayed when searching for a specific PO Line. This was fixed. |
| 07005500 | Acquisitions | In some cases, users could not access certain PO Lines because the "Is Integrated with Vendor" field was set to null. This was fixed. |
| 06844635 06845876 06933294 06927278 06863838 | Acquisitions | In the new PO Line Task List, the facets for PO Line Owner displayed a mixed set of translations. This was fixed. |
| 06954716 | Acquisitions | When saving a PO Line in the Japanese UI, the PO Line number in the confirmation message was not a clickable link. This was fixed. |
| 06904035 06627403 | Acquisitions | The Participants tab for Trial Details indicated that participants existed, but none were displayed when the trial contained more than 1,000 participants. This was fixed. |
| 07038544 06815133 06953980 06928654 07026120 | Acquisitions | In the new UI, after saving an order, the fund total and net price could differ because of incorrect rounding when values contained three or more decimal places and the third digit was 5. This was fixed. |
| 06929331 | Acquisitions | An unexpected error message was displayed when attempting to add a fund to a PO Line. This was fixed. |
| 06935915 | Acquisitions | SUSHI harvesting failed in certain cases. This was fixed. |
| 06723090 | Analytics and Insights | When running a report with the Physical Items > Physical Item Details > Has Committed to Retain field, the count of "No" values changed when the "Retention Reason" field was added to the report. This was fixed. |
| Analytics and Insights | The options in the Type filter drop-down list in Main Menu > Analytics > Shared with Me / Analytics Object List did not appear in the same language as the interface. This was fixed. | |
| 06987206 | Analytics and Insights | Exports of the Analytics Object List included a maximum of 100 items. This was fixed, and now all items in the list are included in the export. |
| 06844130 | Analytics and Insights | 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. |
| 06954917 06964860 06984425 07015035 06981331 07029088 06981653 06988995 06983664 | Analytics and Insights | The Fulfillment > Patron Details > Patron Group field was sometimes empty in reports for renewed items, depending on the renewal date. This was fixed. |
| 06958367 07013378 | Analytics and Insights | Users without the Design Analytics role could not export reports with prompts. This was fixed. |
| 06993456 06984966 | APIs | The Retrieve Set Members API returned an error when used with a logical Courses set. This was fixed. |
| Digital Resource Management | In some cases, the Remove Titles from Collection job did not remove titles from the collection. This was fixed. | |
| 06808477 | Digital Resource Management | The Open File icon in the embedded PDF viewer had no functional purpose in Alma. It was removed. |
| 06760851 | Digital Resource Management | PDF files were sometimes slow to load or failed to load in the Digital Viewer. This was fixed. |
| 06858429 06906455 06917123 06850299 06973180 06971798 06920194 | Digital Resource Management | The Synchronize All Logical Collections job removed records from logical collections and added them back the following day when no changes should have occurred. This was fixed. |
| Digital Resource Management | PDF downloads performed using the embedded PDF viewer download icon were not counted in Alma Analytics. As a result, the icon was removed. PDF files can now be downloaded using the Digital Viewer download icon instead. | |
| 06917523 | Digital Resource Management | Changes to the metadata filename in CSV-format Digital Import Profiles could not be saved. This was fixed. |
| 06937289 | Digital Resource Management | The Digital Viewer did not display MP4 files when the file extension was in uppercase. This was fixed. |
| 06990386 | Digital Resource Management | The login interface launched from the Digital Viewer appeared as a standalone page instead of the Primo VE-style floating login window. This was fixed and the floating login interface is now used. |
| 06957775 | Electronic Resource Management | A specific portfolio was not indexed correctly, causing the Upload Electronic Holdings job to fail. This was fixed. |
| Electronic Resource Management | The service type within a portfolio name now displays as a translated label instead of an untranslated label key. This change also applies to the Portfolio Name column in exported Electronic Portfolio results. | |
| 06791262 | Fulfillment and Resource Sharing | Previously, the Ful Cancel Request Letter displayed the cancellation reason code instead of the cancellation reason description. This was fixed by updating the XSL to use cancel_reason_display instead of cancel_reason. |
| 06805054 06850377 06939124 06777474 06381558 | Fulfillment and Resource Sharing | The Fulfillment - Handle Historical Archiving Job experienced performance issues and was slow to complete. This was fixed and performance was improved. |
| 06886373 | Fulfillment and Resource Sharing | In a specific case, an error occurred when advancing a digitization request to the next step in the workflow. This was fixed. |
| 06842498 06731087 06678871 | Fulfillment and Resource Sharing | The order of libraries in the Resource Sharing form was incorrect. This was fixed. When the customer parameter alphabetical_sort_pickup_inst_lib is set to True, the owner list is now sorted alphabetically as expected. |
| 06928456 06833923 | Fulfillment and Resource Sharing | The Blank ILL form opened with default values of Book and Physical instead of Article and Digital. This was fixed. |
| 06909105 | Fulfillment and Resource Sharing | In some cases, Item Policy descriptions and Locations in the Received Items window were displayed in English instead of the user's selected language. This was fixed. |
| 06891855 06960866 06958253 | Fulfillment and Resource Sharing | In the Metadata Editor, saving a record with field 006 position 0 = 'o' and a matching material type in LDR position 6 (g, k, o, or r) incorrectly displayed the warning "'o' not a valid code for position 0 for field 006". This was fixed, and the warning is no longer shown for valid combinations. |
| 06580298 | Fulfillment and Resource Sharing | In the Aleph Central Catalog Integration Profile, when a record with linked records was redirected to another record, the related records were not indexed and therefore could not be found when searching for the merged record. This was fixed. |
| 06984603 | Metadata Management | The Suppressed icon was displayed inconsistently in the Metadata Editor. When navigating away from a newly suppressed record, the Suppressed icon disappeared from the persistent records list. This was fixed. |
| 06655451 | Metadata Management | In General Publishing, when related record configuration was enabled, some records were occasionally not published. This was fixed. |
| 06843546 06945576 | Metadata Management | In General Publishing at the campus level, records containing both deleted portfolios and physical items were not published as deleted. This was fixed. |
| 06888317 | Metadata Management | When replacing sets in a logical collection, the title count incorrectly combined records from multiple sets. This was fixed, and the title count now reflects only the set currently used by the logical collection. |
| 06742725 06713628 | Metadata Management | Terms containing Swedish characters and diacritics that should have been normalized to standard ASCII were sometimes omitted from search results. This was fixed. |
| 06917048 | Metadata Management | Manage Sets > Sort By > Creation Date did not sort sets correctly according to their creation date. This was fixed. |
| 06836348 | Metadata Management | When creating a Physical Holdings set from a file with the header "Holding Id", the resulting set was empty. This was fixed, and the set now contains the expected records. |
| 06232949 06759158 | Metadata Management | CDI-only full text activation was not available for database collections when the CDI type was Hybrid. This was fixed by adding support for the combination of CDI Type = Hybrid and Alma Collection Type = Database. |
| 06309923 | Physical Resource Management | In the Physical Item Editor, updating the Material Type, Item Policy, or Description fields for an item in a work order displayed a misleading warning stating that moving the item might cancel requests. This was fixed, and the message is no longer displayed for these updates. |
| 06838908 06776954 06864928 06787955 | Physical Resource Management | After editing holdings in the Metadata Editor and viewing related items, changing an item's work order or withdrawing items generated a Java error message even though the action succeeded. This was fixed and the error message is no longer displayed. |
| 06701106 | Physical Resource Management | Previously edited holdings remained stuck in the Metadata Editor when an item was saved using the "Write to RFID and Save" action. This was fixed. |
| 06473503 06969022 06826866 | User Experience, Accessibility & Infrastructure | In a Fulfillment Network, pickup locations in other institutions were not translated when creating requests in Primo. This was fixed. |
| 06912651 | User Experience, Accessibility & Infrastructure | The "Ex Libris - Implementer" user role could be assigned to accounts through APIs and cloud apps. This was fixed. |
| 06966133 | User Experience, Accessibility & Infrastructure | Sending emails from an integration profile using the Save and Test button failed with a generic error message. This was fixed, and a specific error message is now displayed when a failure occurs. |
| 06874064 | User Experience, Accessibility & Infrastructure | The "/" keyboard shortcut for opening the persistent search bar did not work for Physical Holdings searches. This was fixed. |
| 06825150 | User Experience, Accessibility & Infrastructure | The Alt key did not work for a period of time after returning from the Metadata Editor. This was fixed and the Alt key now functions correctly. |
| 06958125 | User Experience, Accessibility & Infrastructure | The "Updated By" audit trail was not displayed on the New Digital Adoption Tool page. This was fixed and the information is now shown. |
| 06877987 | User Experience, Accessibility & Infrastructure | When exporting the User Statistical Categories table, the ampersand (&) in "Target Code Combo [Statistical Category]" was incorrectly converted during export. This was fixed and the ampersand is now exported correctly. |
| 06654450 06586791 06661962 | User Experience, Accessibility & Infrastructure | In some cases, it was not possible to save translations for library names. This was fixed. |
| 06673914 | User Experience, Accessibility & Infrastructure | Item Policy translations were not used in the On Hold Shelf Letter according to the user's preferred language. This was fixed. |
| 06891184 06827070 06586791 06937432 | User Experience, Accessibility & Infrastructure | Updates to Institution Name and Description translations were not saved in some cases. This was fixed. |
| 06560703 06881423 | User Experience, Accessibility & Infrastructure | In Email Notifications for Scheduled Jobs, newly added email addresses or users were sometimes not saved. This was fixed. |
