Alma July 2024 Release Notes

August 2024 Feature Sneak Preview

 

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.

 

Features

Data Type and Section Type Added to Usage Data (COUNTER) Subject Area

July 2024 Analytics and Insights idea exchangeIdea ExchangeURM-125169

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.

Data is available from COUNTER reports that are loaded from July. To have historical data available, you must load the reports manually.

For more information, see Usage Data Details - Release 5.

 

Additional Enhancements

  • July 2024 Analytics and InsightsURM-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 InsightsURM-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 InsightsURM-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 InsightsURM-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 InsightsURM-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.
  •  

Resolved Issues

`
SF number Area Description
06933196 Acquisitions A Brief Bibliographic Record was created when a purchase request was attempted by an expired user from Primo. This was fixed and the user now receives an Unauthorized message.
07005746 Acquisitions There was an issue when exporting more than 1,000 PO lines in itemized sets. This was fixed.
06886687 07041923 Acquisitions An error occurred when selecting "All PO Lines" or "Review (PO Lines)" in the New UI. This was fixed.
06809734 Acquisitions In some cases, a standing order PO line of type Electronic Book was placed in the "Waiting for Invoice" status instead of "Recurring Renewal". This was fixed.
07011207 Acquisitions An electronic collection linked to a license did not display the "View License Details" link until after the license was selected. This was fixed.
07083058 Acquisitions An error was displayed when attempting to delete a trial linked to a PO Line in Recurring Renewal status. This was fixed.
07127019 Acquisitions The Ledger - Open New Fiscal Period job could remain in Running status for two days in some cases due to incorrect data. This was fixed.
07053792Analytics and InsightsWhen deleting an Analytics object with subscribers, no warning was displayed indicating that the object had subscribers. This was fixed, and a warning is now displayed.
07099065Analytics and InsightsThe Item Receiving Year-Month field in Physical Items > Item Receiving Date did not work properly. This was fixed.
07098532Analytics and InsightsThe 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.
07109852Digital Resource ManagementThe Quick Access module did not display representation images in Primo. This was fixed.
07099255Digital Resource ManagementWhen deleting the last file from a representation, a message was displayed asking whether the representation should be deleted, but the offered options ("Cancel" and "Confirm") did not match the question. This was fixed by updating the message to match the available options.
07013202Digital Resource ManagementIn some cases, the Delivery Registration Status letter was sent without a link to the resource. This was fixed.
07085805Digital Resource ManagementIn the Digital Viewer, after zooming in and out, the scroll bar blocked the displayed text. This was fixed and the scroll bar no longer blocks the text.
07044861 07031407Digital Resource ManagementWhen opening the Collection Editor for a logical collection, the last set that had been opened was automatically assigned to the collection. This was fixed, and sets are no longer automatically assigned to collections.
06963080Electronic Resource ManagementThe Springer Integration job was consistently slower in certain environments. This was fixed. Detailed logs and timers were added to the job process to better analyze performance issues.
06810486 07076266Electronic Resource ManagementIn some cases, when the Upload E-Holdings job activated a new portfolio with an existing title, a duplicate title was created instead of attaching the portfolio to the existing title. This was fixed.
07129399 07078834 07064085 07028082Fulfillment and Resource SharingIn some cases, requests sent to a last resort supplier were not closed after being exported when they should have been. This was fixed.
06936196Fulfillment and Resource SharingThe XSL file that translates an ISO message into an NCIP RequestItem message was updated so that both the ItemId field and the BibliographicId field can be included.
07169867 07139061 07101569 07088788 07055866Fulfillment and Resource SharingPreviously, expired lending request messages generated an error and were not sent. This was fixed.
06469092 06764919Fulfillment and Resource SharingPreviously, the Chapter Title on the borrower side was mapped to the Chapter Number field on the lender side. This was fixed and the fields are now mapped correctly.
07113736Fulfillment and Resource SharingAn error occurred when trying to add a row to the General Electronic Services Bibliographic Fields Enrichment interface. This was fixed.
07099055 07152517Fulfillment and Resource SharingIn some cases, scanning in items after receiving caused a timeout. This was fixed.
06767187 06601158Fulfillment and Resource SharingWhen more than one Bursar integration profile was defined, the Transferred Balance field on the Patron Services page was sometimes missing. This was fixed. The Transferred Balance field now appears whenever at least one Bursar integration profile has an active Import section.
07002924 07029068Fulfillment and Resource SharingWhen creating a new physical location by duplicating an existing location, the new external name was not saved and reverted to the original location name. This was fixed.
06931964Fulfillment and Resource SharingWhen an overdue fine was generated for a recalled loan, the calculated fine amount could sometimes be lower than expected. This was fixed.
06726715Fulfillment and Resource SharingFor hold requests, the Request Destination field in the request queue page sometimes displayed a circulation desk that did not have a hold shelf. This was fixed so that only circulation desks with hold shelves are selected as destinations.
07156483 07169289Fulfillment and Resource SharingThe "Distribute Central Resource Sharing Configuration" job did not work properly in some cases. This was fixed.
07057906Fulfillment and Resource SharingWhen using "Shipping Items" at the Resource Sharing Library circulation desk, scanning a barcode for a request sometimes caused an error. This was fixed.
06814930Fulfillment and Resource SharingWhen creating a lending request, partners with certain umlauts could not be selected as "Supplied To" partners. This was fixed.
07158943 07172259 07162263 07171302Metadata ManagementWhen scheduling the "Identify Records That Are Not Used in the Network" job, the job created sets that did not appear in the Sets list because the set was not registered as being created by the user who scheduled the job. This was fixed.
07141579Metadata ManagementBibliographic export for MODS records completed with errors. This was resolved by removing MODS from the Output Format parameter because this job does not support exporting bibliographic records in MODS format.
07053844Metadata ManagementThe advanced search query link on the results page for Physical Titles with Process Type set to "Is Empty" behaved incorrectly. This was fixed.
06831649Metadata ManagementAdvanced search using the Language index with the option "No Information Provided" (field 008 positions 35-37 = ###) did not return results. This was fixed. Records with empty spaces in positions 35-37 can still be retrieved using "Language is Empty" when no language data exists in field 041.
06631655 06937649Metadata ManagementWhen browsing bibliographic records, records counted under a heading were not always displayed in the viewing pane. This was fixed and deployed gradually with the next semi-annual indexing update.
06480203Metadata ManagementAnalytics displayed context_object entries that had Clicked Services but no Services. This was fixed.
06039511Metadata ManagementWhen navigating through bibliographic or holdings records, voice recognition software responded to some but not all voice commands. This was fixed and all voice commands now work as expected.
06957497 07022514Metadata ManagementLocal extensions for restricted fields were removed when an indicator was changed. This was fixed. Local extensions and indicators for restricted fields can now be added and edited as expected.
06672012 05321685Metadata ManagementWhen a local extension was added to a network record already open in the member Metadata Editor, reopening the record did not show the newly added extension. This was fixed. A notification now informs users when the record has been updated by an external process.
07018563Metadata ManagementIn the Metadata Editor, deleting an authority record that was linked to a bibliographic record opened in a collapsible presenter did not remove the link. This was fixed and the link is now removed correctly.
06759363 07079439Metadata ManagementSBN alignments did not skip related-record relationships in tag 463. This was fixed, and linked records with tipoLegame="463" are no longer imported from SBN.
06789449Metadata ManagementLinking and unlinking related access points from field 531 was not implemented when the field was added in version 2.03 of the SBN schema. This was fixed.
06580298Metadata ManagementIn the Aleph Central Catalog Integration Profile, when a record with linked records was redirected to another record, the related records were not indexed and could not be found when searching for the merged record. This was fixed.
07161282Physical Resource ManagementWhen all items in a holdings record were deleted, the holdings record was not suppressed. This was fixed.
07153987 07171348 07165975 07168113Physical Resource ManagementPublic Physical Item templates did not appear in the Metadata Editor's "Add Item from Template" action. This was fixed.
07036059User Experience, Accessibility & InfrastructureThe "Get User Fine/Fee" API did not return information for closed fines and fees. This was fixed.
07192972 07200510 07163053User Experience, Accessibility & InfrastructureAn error occurred on the "Scheduled Manual Jobs" page when the set associated with a manual job had been deleted. This was fixed.
07130251 07143593 07187927User Experience, Accessibility & InfrastructureThe EXPORT_USERS job failed to connect to SFTP using public key authentication. This was fixed.
07178171 07186758 07153558 07083395 07011774User Experience, Accessibility & InfrastructureVarious issues occurred when connecting to SFTP servers. This was fixed by upgrading the SFTP client.
07144379User Experience, Accessibility & InfrastructureIn the Bursar Integration Profile, the list was corrupted and some lines were cut off. This was fixed.
06784660 07030223User Experience, Accessibility & InfrastructureThe value in the right-pane "Requested Format" field was displayed in English instead of the configured language. This was fixed.
07118519User Experience, Accessibility & InfrastructureAlma was slow when loading the Schedule tab on the Monitor Jobs page. This was fixed.
N/AUser Experience, Accessibility & InfrastructureDescriptive Collection records were updated so that the following MARC fields are always overridden by Alma system updates: Collection Description (520), Collection Public Name (245), Collection Type and Content Type (300), and Target ID (904). Users can edit these fields, but any changes are overwritten during system updates.