Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Alma 2023 Release Notes

    Search for what you need
    Search: magnifying-glass-gray.png Release:
     
    Download a PDF of the Release Notes and Resolved Issues.

    Upcoming Issues to Note

    New SAML Certificate

    The current DigiCert SAML Certificate will expire on June 8th. If your institution uses this certificate, Ex Libris recommends that you consult with the IT dept. in your institution, and if required, replace the certificate for Alma and/or Primo VE. If replacing the certificate, this must be done in coordination with your IDP. For more information, see Replacing a Signed Certificate.

    If your institution uses ADFS, Ex Libris highly recommends that you replace the certificate to avoid any complications.

    No immediate action is needed. Replacing the certificate can be done at any time until its expiry on June 8th.

     
    Download a PDF of the Release Notes and Resolved Issues.
    Explore the February Release Highlights here.
    Download a PDF of the Release Notes and Resolved Issues.

    Upcoming Issues to Note

    Sandbox Refresh

    As a reminder, premium sandboxes will be updated in February according to Alma's premium sandbox refresh policy.

    Alma Roadmap Highlights

    The next version of the Alma Roadmap Highlights document is available here.

    Download a PDF of the Release Notes and Resolved Issues.

    Upcoming Issues to Note

    Sandbox Refresh

    As a reminder, premium sandboxes will be updated in February according to Alma's premium sandbox refresh policy.

    Alma Roadmap Highlights

    The next version of the Alma Roadmap Highlights document will be published in January 2023.

    Next Release Sneak Preview

    Select February 2023 Sneak Preview to view the next release sneak preview.

    Main Features

    Send Patrons Their User Data by Email

    February 2023 User ManagementURM-178249

    Users with user-management roles can now send patrons the complete XML record of the data stored about them in their user accounts, including attachments, from the User Details page. The XML file is sent to the patron's preferred email as an attachment to the Personal Information Letter. For additional information, see Managing Users.

    Additional Parameters for Automatic Loan-Renewal Rules

    February 2023 FulfillmentURM-176546URM-180231

    Two powerful new types of parameters can now be used in configuring automatic loan-renewal rules: locations and statistical categories:

    • Locations: Location-based auto-renewal parameters make it possible to create distinct rules for locations within individual libraries. For example, items in reading rooms, for which automatic renewal is not allowed, and items in other locations in the same library, for which renewals are permitted, can have different automatic renewal rules.
    • Statistical categories: Primarily used for analytical reports, statistical categories are created by institutions and assigned to patrons as required. Examples of possible statistical categories are "Citizenship" (with possible values Australia, Canada, China, and so forth) and "Degree Program" (Bachelor's, Masters, PhD, and so forth). Employing statistical categories as parameters in automatic loan-renewal rules makes it possible to fine-tune auto-renewal rules for the various types of patrons served by the institution.  

    For additional information, see Configuring Automatic Loan-Renewal Rules.

    Auto-Renew Rule Editor w Param Box.png

    Configuring an Automatic Loan-Renewal Rule with a Location Parameter

    User Statistical Categories as Parameters in Fulfillment-Unit Rules

    February 2023 Fulfillmentidea exchange Idea ExchangeURM-125680
    User-defined statistical categories can now be used as input to fulfillment-unit rules. Originally intended to be used only for analytical reports, statistical categories sometimes reflect patron attributes that affect their eligibility for fulfillment services, such as special loan-rules for patrons with disabilities. This feature makes it possible to use these statistical categories to define patrons' privileges for fulfillment services. For information about configuring fulfillment-unit rules, see Physical Fulfillment. For information about creating statistical categories, see User Details Configuration.
    Configuring a fulfillment-unit rule to use a statistical category as a parameter

    Request-Cancellation Reasons Now Customizable

    February 2023 Fulfillment  NERS NERS Enhancement (ID #7705)URM-171527

    It is now possible for each institution to customize the list of request-cancellation reasons that appears in the dropdown list of reasons when cancelling requests like holds or resource-sharing borrowing requests. The text displayed for each of the standard reasons can be modified, and reasons that are not relevant to the institution can be removed from the dropdown list. In addition, the institution can create up to ten new reasons to add to the dropdown list. These new options enable the institution to create a list of options that only includes reasons that are actually in use in their libraries, thus preventing problems that arise when an inappropriate reason is selected. The list of cancellation reasons can be edited at Configuration menu > Fulfillment > Request Cancellation Reasons. For additional information, see Configuring Request Cancellation Reasons.

    Watch the Customize Request Cancellation Reasons video (1:20 minutes).

    Customization of Resource-Sharing Record View and Row Actions List

    February 2023 Fulfillment - Resource SharingURM-180182

    Users can now customize the task lists of the resource-sharing borrowing and lending task lists by choosing which fields will appear for each item, and the order and locations in which they will appear. In addition, the order of the row actions of each task can now be configured, and options that are not required can be hidden from the list entirely.

    These new options add to the flexibility of the task lists, and enable libraries to improve the efficiency of their work by reducing clutter and making the fields required for their workflow easier to locate. Future releases will add additional fields to the task lists, further expanding the configuration options.

    For additional information, see Customizing the Record Display; More Actions and Main Action Buttons.

    Storage Location ID Updates

    February 2023 Resource Management

    The updates are especially useful for libraries that work with remote storage facilities and hold the storage ID on their physical items in Alma.

    • Including Item's Storage Location ID in Z39.50 Response

      It is now possible to include a physical item's Storage Location ID in the Z39.50 response, when querying the server using the OPAC format. This enables systems that rely on the item's Storage Location ID to expose this information for third party integration using the Z39.50 server.

      For more information, see Z39.50 Search.

    • Storage Location ID Available in the Physical Items Search Results
      The item's Storage Location ID is available to add to the physical items search results page. For more information, see Searching in Alma.
    • Storage Location ID Added to the Physical Items List
      A new column, Storage Location ID, is now available to add to the items list. For more information, see Physical Items.

    Alt Key Menu Keyboard Shortcuts in New Metadata Editor 

    February 2023 Resource ManagementURM-177101

    It is now possible to easily and quickly access the menus in the new Metadata Editor using a keyboard only, to increase cataloging efficiency and ease of use. This is especially useful for catalogers that rely on keyboard shortcuts in their work.

    For more information, see Global Alma Hot Keys.

    Watch the Alt Key Shortcuts for Metadata Editor Menus video (58 seconds).

    Open GND Authority Records in New Metadata Editor View Mode

    February 2023 Resource ManagementURM-168346

    Catalogers that do not have sufficient privileges to edit GND authority records (based on cataloging level) can now open the authority records in the New Metadata Editor view mode and perform permitted actions such as duplicate records and others. For more information, see Working with the Gemeinsame Normdatei (GND) Integrated Authority Records.

    Show List of All External Resources Instead of a Search

    February 2023 Resource ManagementURM-20266

    Previously in Alma, the Resource Management Configuration > External Resources only enabled an option to search for a specific resource. Now, Alma enables the option to Show All Resources that lists all available external resources. This allows users to browse through all resources.

    For more information, see Configuring External Search Resources.

    All available external resources in Alma

    All available external resources in Alma

    Import Enhancements

    February 2023 Resource Management idea exchange Idea ExchangeURM-95044URM-178842
    • Using Normalization Processes When Creating Inventory and POL Using Import Profiles
      Previously the inventory and POL mapping in the import profile used the source records from the input file as they appeared in the file. It is now possible to use a dedicated normalization process in the import profile to update the data used in inventory and POL mapping.  For example, a library may remove the currency information from the List price field, or add a temporary location information to the field mapped to items. The normalization will only be applied for inventory and for PO Lines, and will not be part of the record when saved to the catalog. For more information, see Creating/Editing an Import Profile: Normalization and Validation.
    • Assign Cataloging Level to Imported Records
      A new option was added to define the cataloging level assigned to records imported to Alma using the MD import profile.
      • New records - assigned with the configured cataloging level.
      • Matched records - if the existing cataloging level is equal to or lower than the cataloging level configured in the import profile, the cataloging level configured will be assigned to all matched records. Otherwise, records are rejected and reported in the import report. 

    UNIMARC Profile Updates

    February 2023 Resource Management
    • Enhancement of UNIMARC 100 Field Positions 25 and 34-35
      UNIMARC field 100 positions 25 and 34-35 now support a closed list of values.
    • Enhancement of UNIMARC 101 Field
      UNIMARC field 101 has incorporated the following enhancements:
      • Field 101 has become repeatable
      • Enhanced the usage of the second indicator
      • Added support for $2
    • Enhancement of UNIMARC Bib 100 $a-j
      UNIMARC Bibliographic field 100 subfields a-j now supports a three-letter controlled vocabulary of country codes.

    GND Profile Update

    February 2023 Resource ManagementURM-172378

    Some changes were introduced to the GND format.
    Changes were made to the CV lists of the following subfields:

    • 065 $a
    • 380 $a
    • 382 $a
    • 667 $a
    • 670 $a and $b

    Updates to MARC21 Profile

    February 2023 Resource ManagementURM-181197

    The following MARC21 updates are now available for Bibliographic, Holdings, and Authority profiles:

    • Update No. 33, November 2021
    • Update No. 34, July 2022

    In addition to the periodical updates, included are a few small fixes to the MARC 21 profiles. These fixes are detailed below:

    In the MARC 21 Bibliographic profile:

    • 383 - removed redundant values in second indicator
    • 550 – removed redundant values in Second indicator
    • Removed subfield ‘1’ from 880
    • 610 $s – changed to Repeatable
    • 034 – added subfield ‘0’

     

    In the MARC 21 Authority Profile:

    • 100 - Subfields ‘g’ and ‘s’ changed to Repeatable
    • 111- Subfield ‘d’ changed to Repeatable
    • 130- Updated the first Indicator to Undefined
    • 336, 370, 372 – added Subfield ‘0’
    • Added field 348
    • Field 378 updated to Not Repeatable

    • 382 - added subfields ‘e’ and ‘t’

    • 383 - Updated Second indicator to Undefined

    • 670 - added subfield ‘w’
    • 672 - added subfields ‘4’ and ‘5’
    • 700 - Added subfields ‘1’, ‘4’, ‘I’. Updated subfields ‘g’ and ‘s’ to Repeatable.
    • 400 – subfields ‘g’ and ‘s’ updated to Repeatable
    • 450- added subfield ‘I’
    • 500- added subfield ‘1’. Subfields ‘g’ and ‘s’ updated to Repeatable
    • 511 – added subfield ‘j’

    Control the Availability of Portfolios Automatically at a Pre-defined Date 

    February 2023 Electronic Resource Management idea exchange Idea ExchangeURM-XXXXXX

    Two additional fields have been added to the Portfolio Editor screen (as well as to the New Portfolio screen when adding a new local portfolio):

    • Available from date - Specifies when the portfolio will be automatically set to "Available."
    • Available until date - Specifies when the portfolio will be automatically set to "Not available."

    The image below presents the new fields in the portfolio editing screen: 

    "Available from date" and "Available until date" fields
    "Available from date" and "Available until date" fields

    Adding a New Portfolio

    Adding a New Portfolio

    These two fields enable users to set a date which defines:

    • When the portfolio will become "Available"
    • When the portfolio will become "Not available"
    • A date-range in which the portfolio will be "Available"

    A daily job (Electronic portfolio availability update) runs every day and checks the dates defined on the portfolios and according to these dates, sets the portfolio as "Available" or "Not available".

    These two new fields enable institutions who have electronic collections where they purchase 1 year of access for selected titles to set a date when these selected titles will be set as "Not available".

    The Available from and Available until fields were also added to the following:

    • Change Electronic portfolio information job
    • API

    Change Electronic portfolio information job

    Change Electronic portfolio information job

    For more information, see Editing a Portfolio Using the Electronic Portfolio Editor

    Ebook Central Upload Electronic Holdings - Addition of Public Access Model Information

    February 2023 Electronic Resource ManagementURM-171247

    Proquest Ebook Central Upload Electronic Holdings integration now includes information regarding the Access Model associated with the electronic resources. The Access Model information passed from Ebook Central is only passed for "Owned" titles. The Access Model information passed from Ebook Central is reflected within the "Public Access Model" field of the electronic portfolio. 

    The Public Access Model field reflects aggregated information regarding the portfolio's Access Model, see the table below for a few examples of the Access Model reflection in Alma and in Ebook Central:

    Ebook Central reflection on portfolios in Alma
    Scenario Ebook Central Public access model presented on the portfolio in Alma
    1 Title has access model 1U 1U
    2 Title has access model 2x1U 2U
    3 Title has access model 2x1U and 3U 5U
    4 Title has access model 2x1U and 3U and NL NL (5U once the NL is over)
    5 Title has access model 2x1U and 3U and UA UA

    Any new Public Access Model code and description are added to the Access Model configuration screen (Configuration > Acquisitions > Access Model).

    Customers who use the "Old" (ProQuest Ebook Central Upload Electronic Holdings) job WILL NOT benefit from this enhancement and are encouraged to move to the new job.

    To maintain the stability of the integration (as there may be many existing portfolios), Alma gradually populates the Public Access Model information for existing portfolios under the relevant ProQuest Ebook Central collection for all institutions (institutions that work with the newer job, only). Be aware that the gradual population process may take several weeks to complete.
    Regardless of the gradual population process, newly added portfolios (in the daily update) will reflect this information immediately.

    For more information, see ProQuest Ebook Central Upload Electronic Holdings Transition

    Electronic Service - Expiry Date Option for the Service Temporarily Unavailable Message

    February 2023 Electronic Resource Management idea exchange Idea ExchangeURM-170845

    Today, when the patron clicks on View it to see the services of the resource, they see the Service temporarily unavailable message (if this was set). In order to set this message, a user needs to access the Electronic Service Editor page and set the date and Temporary Unavailable reason.

    Within the Electronic Service Editor page, a new field Display unavailable message until date allows the Alma user to set a date where the Temporary Unavailable message will expire and no longer appear in the View it.
    This saves the Alma user from the need to proactively move the Display temporarily unavailable message back to No.

    The Update collection job was enhanced to add this new field.

    clipboard_e14a2e1cdff53705ec15421933b7b2ca0.png

    For more information, see Activation Tab Options.

    MARC 21 to DC Crosswalk Now Configurable

    February 2023 Digital Resource Management idea exchange Idea Exchange URM-171844

    You can now customize the XSL file that maps the MARC 21 to Dublin Core crosswalk. This allows you to determine how MARC 21 records are converted when publishing to Dublin Core or Qualified Dublin Core formats. To support this feature, the new Digital Publishing Crosswalk XSLs link was added to Configuration > Resources > Record Export. To see this link, you must have the Catalog Administrator role with the Digital Publishing Crosswalks privilege selected.

    To customize the crosswalk configuration files:
    1. Select Digital Publishing Crosswalk XSLs (Configuration > Resources > Record Export). The following appears:

      crosswalk configuration files.

      Crosswalk Configuration Files
    2. From the actions button, select Edit for the configuration file. The following appears:

      example configuration file.

      Example Configuration File
    3. Edit the file and select Save.

    The MARC 21 to DC crosswalk is implemented according to your customizations when publishing MARC 21 records to DC.

    For more information on publishing, see Publishing and Inventory Enrichment (General Publishing).

    Internet Archive Book Reader (IABR) Now Supports Right-to-Left Paging

    February 2023 Digital Resource Management URM-178267

    The Internet Archive Book Reader (IABR) now supports right-to-left paging when reading books in right-to-left languages. To support this feature, the new Paging Direction by Content Language option was added to the Service Details tab when configuring IABR (Configuration > Fulfillment > Discovery Interface Display Logic > Viewer Service > Internet Archive Book Reader).

    paging direction by content language checkbox.

    Paging Direction by Content Language
    When selecting Paging Direction by Content Language, Alma checks the 008 field or the dc:language field of the bibliographic record of the book. If the language code is one of the following right-to-left languages, the book is displayed with right-to-left paging:
    • ara - Arabicfield 
    • arc - Official Aramaic (700-300 BCE); Imperial Aramaic (700-300 BCE)
    • aze - Azerbaijani
    • div - Divehi; Dhivehi; Maldivian
    • per - Persian
    • fas - Persian
    • hau - Hausa
    • heb - Hebrew
    • kas - Kashmiri
    • khw - Khowar
    • kur - Kurdish
    • pus - Pushto; Pashto
    • sam - Samaritan Aramaic
    • syc - Classical Syriac
    • syr - Syriac
    • urd - Urdu
    • yid - Yiddish

    For more information, see Configuring Right-to-Left Paging for the Internet Archive Book Reader.

    Alma Viewer Enhanced to Improve Display of the File

    February 2023 Digital Resource Management URM-183473

    The following adjustments were made to the Alma viewer to provide enhanced focus on the file content:

    • The Alma viewer user interface was redesigned to provide more space for file content.
    • The Alma Viewer was enhanced to enable you to configure the Contents and Descriptions panes to be collapsed by default and to set a default zoom for PDF files.

      This feature is configurable from the new Expand Content Pane, Expand Description Pane, and PDF Default Zoom configuration options located at Configuration > Fulfillment > Viewer Services > Alma Viewer.

      alma_viewer_RNs.png

      Expand Content Pane, Expand Description Pane, and PDF Default Zoom Check Boxes
    • When the panes are collapsed, the buttons and file label are all located in the same toolbar.
    Watch the Improved UX in the Alma Viewer video (1:52 minutes).

    Activation Notes in Electronic Resource Activation Task List

    February 2023 AcquisitionsURM-91720 idea exchange Idea Exchange

    This feature will be supported in a future release.

    Activation notes are now included in the Electronic Resource Activation Task List (Resources > Manage Inventory > Manage Electronic Resource Activation). An activation note is a note that is added to the PO line of an electronic resource and displayed in the activation task list during activation of the resource, enabling the person creating the PO line to provide relevant information or instructions to the one activating it. They are similar to the Receiving Notes that can be attached to PO lines of physical resources (see Manually Creating a PO Line). 

    Activation note in Activation Task List

    Activation notes cannot currently be created in Alma (although they will be supported in the future – see New Unified PO Line Task List), but if a PO line for an electronic resource was migrated from another system, and it had a receiving note attached to it in the previous system, the content of that receiving note appears as an Activation Note in Alma. 

    Improve the UI/Discoverability of the License Terms Translatable Text Area

    February 2023 Administration and InfrastructureURM-92228

    Alma has improved the UI/discoverability of the translatable text area for License Terms. A globe icon is added, that when clicked, opens a screen similar to regular translatable fields. The UI will be populated based on the contents of the text area, and when closed, will add the correctly-formatted text to the text area.

    For more information, see Managing Licenses and Amendments.

    License Term Translatable Text screens

    License Term Translatable Text screens

    License Term Translatable Text screens

    Library-Level Statistical Categories 

    February 2023 Administration and InfrastructureURM-180182

    A new option, library-level statistics, has been added to Alma, and is available in institutions in which library independence has been established (see Library Independence). When this option is activated for an institution, statistical categories can be assigned to patrons per library. In this case, an owner library is added to the properties of each statistical category that is assigned to a patron. Only users whose roles are scoped to the owner library can see or access the statistical categories it owns. Statistical categories that are outside of a user's scope are not displayed to them when they view user information or retrieved in searches they perform, and are excluded from jobs and API calls they execute. 

    For information about assigning statistical categories to users, see Managing Users. For information about creating statistical categories, see User Details Configuration.

    Entity Type Dropdown in Simple Search

    February 2023 Administration and Infrastructure

    URM-171450

    Librarians can now quickly select the type of search (entity type) they are searching (in simple search) by starting to type its name in the Search field, for example "Electronic collection", and having it auto-complete in the field. This is especially helpful in saving time when the simple search dropdown contains a long list of search types (entity types).

    Moreover, this ability reduces mousing - making simple searches more accessible. For more information, see Performing a Simple Search.

    SimpleSearch_Dropdown_AutoComplete.jpg

    Simple search dropdown auto-complete - begin typing in the search field to auto-complete the search type in the list 

    Licenses - Enhancements to LicenseTermsPermittedProhibited Options

    February 2023 Administration and Infrastructure (Updated February 15, 2023)

    URM-178670

    The license term “LicenseTermsPermittedProhibited” is enhanced with additional options to match the DLF standard. The new options are:

    • Permitted (Explicit)
    • Permitted (Interpreted)
    • Prohibited (Explicit)
    • Prohibited (Interpreted)
    • Silent (Uninterpreted)

    This is in addition to the existing values of:

    • Silent
    • Uninterpreted
    • Prohibited
    • Permitted
    • Not Applicable

    For more information see Managing License Terms

    Translations for the newly added values will be available in the following Alma release. Manual translations can be added.

     

    The functionality above was introduced in a different manner in the February release and was modified on February 15th due to customer feedback. 

    Options that were available prior to the Alma February release were added back to the list of options, and additional values were added to comply with the DLF standard.

    Below is a table describing all the options for the “LicenseTermsPermittedProhibited”  license term and the changes that were done according to customer feedback.

    Drop down values Value changes
    Permitted

    Customers who had the “Permitted (Explicit)” selected in the February release will move back to this value.

    Permitted (Explicit)

    Customers who had this value selected in the February release will move back to “Permitted” value.

    Permitted (Interpreted)

    Customers who selected this value in the February release will still have this value selected.

    Prohibited

    Customers who had the “Prohibited (Explicit)” selected in the February release will move back to this value.

    Prohibited (Explicit)

    Customers who had this value selected in the February release will move back to “Prohibited” value.

    Prohibited (Interpreted)

    Customers who selected this value in the February release will still have this value selected.

    Silent

    Customers who had this value selected before the February release, and did not modify it in the February release, will have this value selected.

    Silent (Uninterpreted)

    Customers who selected this value in the February release will still have this value selected.

    Uninterpreted

    Customers who had this value selected before the February release, and did not modify it in the February release, will have this value selected.

    Not Applicable

     

    New Analytics User Interface

    February 2023 Analytics URM-175478

    The Alma Analytics user interface was redesigned with several enhanced features that improve the display of information and simplify many procedures and workflows. The new interface will be rolled out in the following stages:

    • February release – The previous version of the interface is displayed by default, but you can configure Alma Analytics to display the new version.
    • May release – The new version of the interface is displayed by default, but you can configure Alma Analytics to display the previous version.
    • August release – The new version of the interface is the only version available.

    To display the new version of the interface, select the User icon and then select Feature Rollout Configuration:

    feature_rollout_configuration.png

    Feature Rollout Configuration
    Toggle the New Analytics feature to display the new version of the interface:

    new_analytics.png

    New Analytics

    The following enhancements were implemented:

    • The options and layout when selecting Analytics from the Main Menu was enhanced:
      • At the top of the area, a list of your favorite reports and dashboards appear:

        main analytics link options.

        Main Analytics Link Options
      • From the My Analytics area you can access the Analytics Object list (if you have the relevant role) and display the new Shared with Me page where you can view the reports to which you have access:

        shared with me.

        Shared with Me
      • From the Create Analysis section, you can select the renamed Access Analytics link to create reports and access out-of-the-box reports and dashboards.
    • The Analytics Object List was redesigned:

      analytics object list.

      Analytics Objects List
    • Visual indicators mark the objects as Subscribed, Scheduled Report, Added as a Widget, and Report in Favorites.
    • Additional information appears for each object, such as the subject area the report or dashboard is from, the user who created the object and the date created, and the user who modified the object and the date modified.
    • New functionality is now available for Analytics Objects, including:
      • Editing an analytics object in split view, so that you can keep the list of objects open while you edit:

        split view.

        Split View
      • Viewing a preview of the report or dashboard so you can confirm the functioning of the reports:

        report preview

        Preview Report

    For the complete description of the features of the new Analytics Interface, see Working with Analytics Objects.

    For a description of the options on the Analytics menu, see Navigating Analytics.

    Watch the New Interface for Analytics in Alma video (5:28 minutes).

    API-Key Support for Multiple IP Ranges

    February 2023 APIURM-159919

    The existing security feature that uses API keys to limit access to Alma has been expanded. When employing this feature, customers create an API-key in https://developers.exlibrisgroup.com/manage/keys/, and then specify IP addresses from which requests can be accepted. Requests from IP addresses that are not included in the list of accepted IP addresses are rejected by Alma. Previously, Alma API keys could only be configured to accept requests from individual IP addresses or a single range of IP addresses. They can now accept multiple ranges of IP addresses; the ranges must be defined in CIDR format, and separated by commas - e.g., 1.1.1.1/27,1.1.1.3/15.

    Access to Letter Components Added to the API

    February 2023 API URM-180077
    The API for management of letter templates now enables access to the letter components (such as header.xsl and footer.xsl), making it possible to retrieve and update them. This additional functionality provides full support for local customization and versioning of these templates via the API. For additional information, see Configuration and Administration in the Developer Network.

    Access to Code-Table Translations Added to the API

    February 2023 API idea exchange Idea ExchangeURM-179802
    The API for management of code tables now enables access to translations of labels into other languages, making it possible to retrieve and update them. This additional functionality provides full support for localization via the API. For additional information, see Configuration and Administration in the Developer Network.

    Search for Reading List by List ID

    February 2023 Fulfillment - Course Reserves idea exchange Idea Exchange URM-135743

    You can now search Reading lists by List ID in Alma.

    List ID searches are not currently included in All searches. This option will be available in a later release.

    Searching a reading list by list ID.

    Searching a Reading list by List ID

    For more information, see Reading List Search Fields.

    User-Information Pop-Ups in New-Layout Task Lists Are Now Available and Customizable

    January 2023 Administration and InfrastructureURM-178645

    In the New Layout of the Resource Sharing borrowing-request and lending-request task lists, assignee and requester names are now buttons that, when selected, open pop-ups in which additional user information is displayed. Alma users can thus quickly access information such as a requester's user group or contact details, but the information does not clutter the display when it is not needed. For additional information, see New Layout 2022.

    User icon NG.jpg

    User pop-up NG 2a.jpg

    Which user information appears in these pop-ups can be configured by the institution. Thus, one institution may choose to display physical addresses and personal phone numbers in the pop-up, while another chooses to hide this information, but includes user groups and email addresses. For additional information, see Configuring User Information for Pop-ups.

    Additional Enhancements

    • April 2023 Resource Management
      Previously, edition information in the title search results was limited to the edition statement (250$$a). Now, the edition information also includes the remainder of the edition statement (250$$b), enabling librarians to fully and accurately identify the edition from the search results.
    • April 2023 Resource Management
      The 070 is the standard NAL (National Agricultural Library) call number index per library of Congress Standards. Once the semi-annual reindexing is completed, it will be included in the NAL Type Call Number search index.
    • April 2023 Administration and Infrastructure
      Alma's session timeout feature recognizes user activity in Analytics and extends the Alma session to prevent a timeout while the user is active in Analytics. This means that if the user is working in Analytics during an Alma session, their session remains active without interruption.
    • April 2023 Analytics SF: 06593328 URM-186017
      The Cost Usage Institution for Consortia folder was added under E-Inventory > Cost Usage. It contains the Cost Usage Institution Code and Cost Usage Institution Name fields. They display the institution code and institution name of the network member.
    • April 2023 Analytics URM-180828
      The Statistical Category Description field was added to Users > Statistics. It displays the statistical category description and can be used with the Statistical Category field, which displays the statistical category code.
    • April 2023 Analytics URM-182159
      Out-of-the-box reports no longer appear in the drop-down list when creating analytics objects, since they cannot be used to create analytics objects. If you want to share or schedule an out-of-the-box report, save the report in your institution folder with a new name and create the analytics object with that copy.

      For more information on analytics objects, see Creating an Analytics Object.

    • April 2023 Analytics URM-182766
      You can now export the Analytics Object List to Excel format. You do this by selecting the export icon export_icon.png located above the list. The following fields are exported:
      • Type
      • Display Name
      • Report Name
      • Description
      • Subject Areas
      • Analytic Folder
      • Add as widget
      • Out of the Box Reports
      • Schedule Report
      • Add as dashboard
      • Source System
      • Object Creator
      • Object Creation Date
    • April 2023 Analytics URM-187262
      The Report Preview area of the Analytics Objects List now also displays Data Visualization reports. This enables you to view a preview of the report without having to open it in the analytics interface.
    • April 2023 Analytics URM-184526 URM-185935
      You can now schedule Data Visualization (DV) reports as you can for analytics dashboards and reports. Users subscribed to receive the DV reports receive a link to the DV report that they can select to display the report. Since sending DV reports as an attachment is not possible, the only option is to send a link to the live report. Note that opening the link requires the receiver having the appropriate role or permissions to view the report.

      For more information, see Scheduling and Subscribing to Reports and Dashboards.

    • March 2023 Analytics URM-184642
      The Partner Institution field was added to Borrowing Requests > Partner. This field displays the partner institution, which enables better reporting of borrowing requests per the supplying institution.
    • March 2023 Analytics URM-176587
      The Statistical Category Type field was added to Users > Statistics. It displays the statistical category type, which provides additional information about statistical categories in addition to the Statistical Category field.

      For more information on configuring statistical categories for analytics, see Configuring Statistical Categories for Analytics.

      In addition, for the Borrowing Requests, Fines and Fees, Fulfillment, and Requests subject areas, the Statistical Categories 1 - 10 fields now display library level data, since their user data can be anonymized, while for all other subject areas they display institution level data.

    • March 2023 Analytics SF: 06434690 URM-184685
      When Alma attempts to match electronic resource usage from COUNTER reports with the resource in Alma, Alma now first attempts to match with the Online ISSN (called the Normalized EISSN in Alma Analytics) and if that is unsuccessful with the Print ISSN (called the Normalized ISSN in Analytics) and not the opposite as was the case previously. For more information, see Matching the resource from COUNTER report to the resource in Alma for cost per use.
    • March 2023 Analytics URM-184130
      The values of the E-Inventory > Service URL Information > Service Is Free and Service Is Free (override) fields were changed from 1/0 to Yes/No.
    • March 2023 Analytics URM-183938
      The Borrowing Requests and Lending Requests subject areas were renamed to Borrowing Requests (Resource Sharing) and Lending Requests (Resource Sharing) respectively. This is to clarify that these subject areas report on resource sharing borrowing and lending requests and not general Alma requests, which are reported on from the Requests subject area.

      In addition, the Usage subject area was renamed to Usage (COUNTER) to indicate that it reports on electronic resource usage derived from COUNTER reports.

    • March 2023 Analytics URM-184286
      The Statistical Category field (Users > Statistics) was restored to display the statistical category code as was the case before the February release.
    • February 2023 Resource Management URM-179343
      To assure a more accurate look-up of Series title and Uniform title, the access point of UNIMARC fields 410/411 and 500 will lead to the relevant entries based on a type defined in the 154 $a field.
    • February 2023 Resource Management URM-178894
      Libraries can now configure more flexible scheduling for general publishing.
    • February 2023 Physical Resource Management URM-171615
      The publishing to OCLC was enhanced to handle the reported instability of connections with OCLC FTP servers, where OCLC servers fail to receive files. The following is the enhancement:
      • If a file fails to be uploaded to the FTP server due to server instability, the publishing job will complete with errors. The job report will detail that the connection to OCLC’s FTP server failed, and it will be possible to download the failed files from the job report, so they are not lost.
    • February 2023 Analytics URM-180834
      It is now possible to have the data anonymized in the following fields of the System Events subject area:

      To request that these fields be anonymized, contact Ex Libris support.

      • Event Details > Event Key Value
      • Event Details > Event Creator
      • Security Events > Accessing User ID
      • Security Events > User ID
    • February 2023 API
      For import jobs that have run, a report showing the source file that was imported can now be generated through the API, given the Job ID. For additional information, see Configuration and Administration.
    • February 2023 API
      The Linked Data section of bibliographic records now includes Creator and Contributor Wikidata links when they are available. For additional information about linked data, see Linked Data in Repository Search Results; Linked Data.

      Linked Data - Creator.png
    • February 2023 Analytics SF: 05299713 05460695 06464393 06484214 URM-182644
      The Electronic Collection Bibliographic Details dimension was added to the E-Inventory subject area. The fields of this dimension enable you to create reports that contain information concerning the bibliographic details of electronic collections. This is especially useful for reports concerning collections without portfolios. The fields of this dimension are the same as in the Bibliographic Details dimension found in many subject areas with an added prefix of E-Collection Bib.

      For more information, see Electronic Collection Bibliographic Details.

    • February 2023 Analytics URM-182402
      The names of the Fund Ledger dimension and the following field names were changed to remove the word Ledger from their name to more accurately describe the information they display. The term Fund Ledger refers to a parent fund, while these fields display information at both the parent and child level. Note that any existing reports that use the old field names continue to work.

      The changed dimension and field names are located in the Funds Expenditure, Purchase Requests, Physical Items, and E-Inventory > Cost Usage subject areas.

      New Name Old Name
      Fund (Dimension) Fund Ledger
      Fund Code Fund Ledger Code
      Fund ID Fund Ledger ID
      Fund Name Fund Ledger Name
      Fund Status Fund Ledger Status
      Fund Owner Code Fund Ledger Owner Code
      Fund Owner Name Fund Ledger Owner Name
      Fund Name Fund Ledger Name
      Parent Fund Code Parent Fund Ledger Code
      Parent Fund ID Parent Fund Ledger ID
    • February 2023 Analytics URM-182443
      The names of the following fields in the Fund Expenditure subject area were changed to clarify that they display the name of the user:
      New Name Old Name Dimension
      Invoice - Approver Name Invoice - Approved By Invoice Line
      License Modifier Name License Modified By PO Line License
      License Creator Name License Creator PO Line License
    • February 2023 Analytics URM-184286
      The Statistical Category field (Users > Statistics) now displays the statistical category description and not the statistical category code. Any report filters that are based on the statistical category code may need to be updated.
      Watch the Additional Analytics User Statistics video (1:16 minutes).
    • February 2023 Fulfillment - Course Reserves URM-180474

      When copying a citation, the Created by on the new citation is attributed to the user who copied the citation.

    • February 2023 Fulfillment - Course Reserves URM-153988

      For consistency and clarity, the Brief Display Request Status label is now labeled Citation Status to match the Citation Status facet label and the data in analytics.

      Citation Status label on the Brief Display of a citation.

      Brief Display Citation Status
    • February 2023 Fulfillment - Course Reserves URM-178004

      The List Last Set to Complete Date field was added to the Reading Lists dimension in the Leganto Student Usage, Leganto Instructor Usage Events, and Course Reserves subject areas. It displays the most recent date that the reading list was set to complete.

    • February 2023 Fulfillment - Course Reserves SF: 06454739 URM-177711

      The Citation Hidden Links field was added to the Citations dimension of the Leganto Student Usage and Leganto Instructor Usage Events subject areas and the Reading List Citations dimension of the Course Reserves and Purchase Requests subject areas. It indicates if there are hidden links in the citation.

    • February 2023 Fulfillment - Course Reserves URM-175007
      The Reading List Type field was added to the Reading Lists dimension in the Leganto Student Usage, Leganto Instructor Usage Events, and Course Reserves subject areas. It indicates if the reading list is designated as the parent list. Possible values are Parent and blank (no value).
    • February 2023 Fulfillment - Course Reserves SF: 06481498 URM-178971
      The Start Page 2 and End Page 2 fields were added to the Citation Metadata Details dimension of the Leganto Student Usage, Leganto Instructor Usage Events, and Course Reserves subject areas. They display an additional start and end page.
      The Number of Pages field now displays the number of pages between the Start Page and End Page fields and the Start Page 2 and End Page 2 fields.

      In addition, the names of the Article Number of Pages, Article Start Page, and Article End Page were changed to Number of Pages, Start Page, and End Page.

    • February 2023 Fulfillment - Course Reserves URM-179659
      The following field names were changed in Analytics for better clarity and consistency:
      New Name Old Name Location
      Course Created By  Course Creator
      • Course Reserves > Courses
      • Leganto Student Usage > Reading Lists
      • Leganto Instructor Usage > Courses
      • Requests > Request for Course
      Reading List Created By Reading List Creator
      • Course Reserves > Reading Lists
      • Leganto Student Usage > Reading Lists
      • Leganto Instructor Usage > Reading Lists
      Number of Suggestions Leganto List Num of Student Suggestions
      • Course Reserves > Reading Lists
      • Leganto Student Usage > Reading Lists
      • Leganto Instructor Usage > Reading Lists
      Section Created By Section Creator
      • Course Reserves > Leganto Reading List Sections
      • Leganto Student Usage > Reading List Sections
      • Leganto Instructor Usage > Reading List Sections
      Citation Created By Citation Creator
      • Course Reserves > Reading List Citations
      • Leganto Student Usage > Citations
      • Leganto Instructor Usage > Citations
      • Purchase Requests > Reading List Citations
      Number of Files Downloaded Number of Files Download Leganto Student Usage > Student Usage
      Number of Student Comments Students Discussions Leganto Student Usage > Student Usage
    • February 2023 Fulfillment - Course Reserves URM-180468
      For Norwegian customers, files available from Bolk now only display to students when permitted according to the permissions set in Leganto. For example:
      • Files for citations that are not marked as complete do not display to students
      • Files only display when access to materials is allowed according to the publishing visibility 
    • February 2023 Fulfillment - Course Reserves URM-180928
      The No List Expected field was added to the Course dimension in the Leganto Student Usage, Leganto Instructor Usage Events, Course Reserves, and Requests subject areas. (Possible values: Checked and Unchecked). It indicates if the No List Expected checkbox is selected on the course record in Alma or not. For more information on this checkbox, see Indicating that Courses Deliberately Have No Reading List.
    • February 2023 Fulfillment - Resource Sharing URM-166608
      When scanning in an item on the lending side (Fulfillment > Resource Requests > Scan In Items), emails were not sent to the borrower. When an email address is configured for the Printer Details (Configuration > Fulfillment > General > Printers), the Resource Sharing Shipping Slip is now emailed.
    • January 2023 Analytics URM-180923
      In continuation of the December release, an additional five statistical categories are now available to be reported on in Alma Analytics in the following additional locations:
      The additional statistical categories added to Fulfillment > Borrower Details are only available with data added going forward.
      • Borrowing Requests > Requester
      • Fines and Fees > User Details
      • Fulfillment > Borrower Details
      • Requests > Requester
    • January 2023 Analytics URM-180834
      It is now possible to have the data anonymized in the following fields of the System Events subject area:

      To request that these fields be anonymized, contact Ex Libris support.

      • Event Details > Event Key Value
      • Event Details > Event Creator
      • Security Events > Accessing User ID
      • Security Events > User ID
    • January 2023 Analytics URM-177583
      The Available From Date and Available Until Date fields were added to E-Inventory > Portfolio. They display the start and end dates that the portfolio is available.
    • January 2023 Analytics URM-181807
      The Label and Label History fields (Borrowing Requests > Borrowing Request Details and Lending Requests > Lending Request Details) are now available to Alma customers. They display the customized labels added to borrowing and lending requests and the history of label deletions.
    • January 2023 Analytics URM-152264
      The Loan Hour field was added to Fulfillment > Loan Date. It indicates the hour of the loan in 24 hour format.

    Resolved Issues

    • February 2023 Release Update Electronic Resource Management SF: 06648372 06648374 06648382 06648398 06648796URM-187247
      Local portfolios were created with the default available from and available until dates. When the Feature Flag turned active in the February release, the job to update the portfolio availability status by dates was activated, and changed the local portfolio status. Ex Libris reverted the data and activated all local portfolios that were changed in the job.
    • February 2023 Release Update Resource Management SF: 06647912 06649885 06649922 06650085 0665020506648796URM-187312
      It was not possible to add special characters in the Metadata Editor using the ASCII codes with the February release of the new Metadata Editor keyboard shortcuts. This issue was fixed.
    • February 2023 Release Update Resource Management SF: 06648192 06648193 06648317 06648796URM-187220
      Error in MARC21 BIB 655 Controlled vocabularies. The authorities were properly coded and linked via F3 but got an error stating the value is not part of the controlled vocabulary. This was fixed.
    • April 2023 Analytics SF:06287214 URM-170424
      Chinese characters within graphs in Analytics reports were disappearing from the reports. This was fixed by a quarterly fix of the OAS.
    • April 2023 Analytics SF:06620598 URM-185289
      When filtering an analytics report in the Users subject area by email, an unexpected string of characters was displayed with the email address. This was fixed, and now the email address appears without the string of characters.
    • April 2023 Analytics SF:06643656 URM-187091
      The AE100 LC classification code was missing from the the LC Classification codes list. It was added.
    • April 2023 Analytics SF:06580889 URM-187315
      The KZ and KI schedules were missing from the the LC Classification codes list. They were added.
    • April 2023 Acquisitions SF:06512683 06561839 05313290 URM-180760
      Duplicate entries of license terms appeared in Primo and Primo VE. These duplicate entries no longer appear.
    • April 2023 Acquisitions SF:06514976 06522573 URM-181444
      Previously, when getting PO lines with interested users via the API, the PO line of the request was case sensitive. This was fixed. It is no longer case sensitive.
    • April 2023 Acquisitions SF:06378897 06522995 URM-175115
      Previously, when a user attempted to link an item to a continuous PO line, which is not a supported action (Items can be linked to one-time PO lines, but not to continuous PO lines), no alert was shown. Now, an alert is shown.
    • April 2023 Acquisitions SF:06535404 URM-181476
      Previously, approval details (approval_date, approved_by, and approved_by_id) were left blank in the XML of the Order List letter. They are now added to XML as they should be.
    • April 2023 Acquisitions SF:06566170 06597278 URM-183106
      When a Claim letter was supposed to be sent to a vendor, if the acq_vendor_account_email customer parameter was set to true, but the vendor account had no email address associated with it, the letter was not sent, even if the there was an email address associated with the vendor itself. Now, if the acq_vendor_account_email parameter is set to true, and no email is associated with the vendor account, but there is an email associated with the vendor itself, the Claim letter is sent to the vendor email.
    • April 2023 Acquisitions SF:06493219 06548850 URM-183181
      In the Electronic Resource Activation Task List, when a user selected Done, the system assumed a PO line was connected to the electronic resource. When this was not the case, an error was generated. An extra check has now been implemented when Done is selected, to ensure that a PO line is actually connected to the electronic resource before the Done action is implemented, and thus preventing this error from occurring.
    • April 2023 Acquisitions SF:05309931 06327064 URM-125695
      When a Claim letter was sent for a PO line that had no item description and used the newSubject format, the word 'null' was appended to the end of the letter's subject line where the item description would normally be appended. This was fixed; if a PO line has no item description, nothing is appended to the subject line of the Claim letter in its place.
    • April 2023 Acquisitions SF:06542574 06544040 URM-181059
      The Trial Survey Form did not work properly; participants in trials received multiple emails inviting them to take part, but the survey forms they accessed were blank. This was fixed; the survey forms contain the questions they should contain, and the email invitations are not sent more often than expected.
    • April 2023 Acquisitions SF:06519562 06583280 06628800 06631635 URM-182988
      Previously, multiple import jobs could try to update the same fund at the same time, resulting in data that was not processed. Now, the number of times each job can update a fund is minimized reducing the chances of conflicts between two separate jobs.
    • April 2023 Acquisitions SF:06496144 URM-188126
      Previously, in the Rollover Ledger report, the value of the From Year parameter was not presented in the report. Now, it appears in the report for both the Copy and the Delete actions.
    • April 2023 Acquisitions SF:06449316 05323936 06653402 06409322 06488312 URM-154898
      When two instances of the EDI-Load Files job ran simultaneously, the jobs did not always import all of the invoices from the vendor's server. Now, multiple instances of the job are not allowed to run at the same time - each new instance waist until the previous one has finished. As a result, all invoices are imported as they should be.
    • April 2023 Acquisitions SF:06594183 URM-184564
      Under certain conditions, the EDI - Loads Files RIALTO job completed with the error 'Error on creating entity from xml,' and invoices failed to import. This has been fixed; this error no longer occurs when this job runs.
    • April 2023 Acquisitions SF:06560370 URM-183197
      When an FTP transfer was interrupted during the disconnect process, after the files were actually already successfully transferred to the target server, the transfer process was repeated, resulting in duplicate copies of the files being transferred to the target. This has been fixed; if an exception is thrown during the disconnect stage of an FTP transfer, the file transfer is not repeated.
    • April 2023 Acquisitions SF:06561445 URM-183530
      Previously, when invoices were exported to external financial systems, the PO number of the PO lines included in the invoice was not exported. Now, a new po_number field was added to the po_line_info section in the exported XML. If the PO line is part of a PO, the PO number is extracted to this field.
    • April 2023 Acquisitions SF:06639221 URM-187453
      In certain cases, selecting Custom Harvest for a vendor from the Usage Data tab of the Vendor Details page opened a blank page. This was fixed; Custom Harvest now opens correctly in these cases.
    • April 2023 Acquisitions SF:06643239 URM-187448
      Previously, when an electronic PO line that was not linked to a resource was set to claim, the Claiming job failed. This was fixed; the Claiming job no longer fails in this case.
    • April 2023 APIs SF:06639092 URM-187443
      Previously, authenticating a user via the Alma Users API required an API key with a write permissions. Now, an API key with read-only access is sufficient for authenticating a user via API. This differs from the authentication requirements of other POST APIs, which continue to require write permissions, because this API does not alter data.
    • April 2023 APIs SF:06484251 URM-180684
      Previously, the full list of serial database names was not checked when determining if an imported record was a monograph or a serial. This has been fixed; the full list of serial database names is now checked during this process.
    • April 2023 Administration and Infrastructure SF:06360858 URM-173894
      Previously, when a logical set of users based on user status was created, it produced an empty set of results. This was fixed; logical sets of this sort now return the correct results.
    • April 2023 Resource Management SF:06481305 06482799 URM-179046
      Sets with a date-based field that are used in advanced search and saved during specific times of the day, the value shifts a day forward. This was fixed with a configuration adjustment to address timezone differences.
    • April 2023 Resource Management URM-182719
      Metadata Editor: Warning messages and "Record saved" messages that have interactive elements do not receive focus when tabbing through the Alma UI for screen readers. As a result, the elements cannot be operated with a keyboard. This was fixed.
    • April 2023 Resource Management URM-179090
      Metadata import created BIB version and distribution for unmodified BIB records. This was fixed by comparing the existing BIB in the database and if there are no differences, it is not saved.
    • April 2023 Resource Management SF:06455704 05310335 05310834 URM-179135
      Moving an item to another permanent location via the Change Physical Items Information job: when both 'update_call_number_type_upon_item_move' and 'use_marc_record_holdings_template' customer parameters were set to 'true', the target holdings record was not assigned the call number type defined in the target physical location; instead, the first indicator of the default holdings record template was used (a space was converted to '#'). This was fixed.
    • April 2023 Resource Management SF:06602761 URM-184822
      Previously, an issue existed in the 'Continuous Tab' (Acquisitions > Receives > Continuous Tab) where if a customer selected the Duplicate button to copy an item's details but then edited the description without updating it, the system would not display an alert for the item description. This issue has now been resolved and an alert is now shown in this scenario.
    • April 2023 Resource Management SF:05317929 URM-171701
      Community Zone update task list displayed the wrong name of the collection for a SERVICE change. This was fixed by changing 'updatePps' to take the package name from each IEPA individually, instead of taking it from the first one.
    • April 2023 Resource Management SF:05301384 URM-182682
      When searching for titles in the Community Zone scope, the count of electronic portfolios for a title was sometimes incorrect. This was fixed by a performance improvement made when creating the 'Update in Community' pop-up for a contributed collection.
    • April 2023 Resource Management SF:06474399 URM-178227
      MODS records deleted a space in the name of a collection. This was fixed.
    • April 2023 Resource Management SF:06657123 06658548 06651313 URM-188287
      Print Preview for PDFs in the Alma viewer displayed an empty page. This was fixed and now the page to be printed is displayed.
    • April 2023 Resource Management SF:06536686 06568124 URM-181966
      General Publishing: Previously, two jobs related to the same General Publishing profile could not run in parallel, where the second job was immediately aborted with the status Skipped. This is fixed, now the second job waits (status 'Pending') until the first job is completed and then continues running.
    • April 2023 Resource Management SF:06498260 URM-181958
      Headers were not displayed while searching electronic titles in the Community Zone and selecting to view the portfolio list. This is fixed and Collection Headers are added to the display.
    • April 2023 Resource Management SF:05313754 URM-123295
      The 'Catalog set' function does not work as expected for bibliographic records from the Community Zone, if the Metadata Editor is loaded for the first time. This was fixed and now the whole set is pushed to the Metadata Editor.
    • April 2023 Resource Management SF:06463158 06613730 URM-178076
      Creating a Physical Title Set using an Excel file with empty lines caused an error. This was fixed and these lines are now skipped.
    • April 2023 Resource Management SF:06442585 URM-183798
      In the link resolver, when calculating consolidated coverage for a title with multiple portfolios where one of the portfolios partially supplements the second portfolio's coverage, the consolidated coverage was not displayed correctly. This was fixed.
    • April 2023 Resource Management SF:06285033 URM-168241
      Export errors occurred to Mendeley in cases where the field 'year' contains 'u' or '?'. This was fixed and errors are now prevented.
    • April 2023 Resource Management SF:06210999 05312626 URM-157988
      The new feature: 'Metadata Editor Holdings 852 $b - Support for Libraries Sorting by User Location' was not working as expected. This was fixed. The 'Currency at' library is now displayed in the form's dropdown.
    • April 2023 Resource Management SF:06328275 06596178 URM-170931
      SBN integration profile: The 'Merge routine' did not include the disabled merge rules. This is fixed and now the list contains both enabled and disabled rules.
    • April 2023 Resource Management SF:06509466 URM-180687
      Alma normalizes 'Chinese Book Classification Call Number' headings for customers' special 'non-ASCII' sorting order. Alma also applies special normalization to the sequence number portion to sort them sequentially, rather than alphabetically. However, if there are multiple instances of a space or a forward slash followed by digits, Alma cannot identify the sequence number. This was fixed and now Alma can accurately normalize the call number.
    • April 2023 Resource Management SF:06517140 06524540 URM-180688
      Templates contributed to the Community Zone disappeared after some time. This has been fixed.
    • April 2023 Resource Management SF:06463588 URM-177820
      Authority heading lookup (F3) - When working with authority headings that contain both Hanja and Hangul in the same field, the authority was sometimes not displayed in the list of suggested headings. This has been corrected. Contact Exlibris support to activate this fix.
    • April 2023 Resource Management SF:06514525 URM-181534
      Bibliographic Record Relations are not being updated by 'MMS - Build Record Relations' after being 'Merge and Combine' in the Metadata Editor. This was fixed with a configuration update.
    • April 2023 Resource Management SF:06358027 URM-173974
      The jobs for some digital import profiles are completed with errors from time to time, but the job report shows no reason and the Events List is empty. This was fixed. Now, if a Metadata import job fails when importing records from OAI, an added event is displayed to notify users.
    • April 2023 Resource Management SF:06558869 URM-184010
      The second indicator values of the 260 field in the Ex Libris Metadata Configuration List for Marc21 Bibliographic was incorrect according to the Library of Congress. This was fixed. The indicator may have values #, 0, or 1 instead of #.
    • April 2023 Resource Management SF:06223114 URM-165977
      SBN contribution: The contribution of Uniform Titles sometimes failed due to a wrong SBN sequence number generated. This was fixed.
    • April 2023 Resource Management SF:06490811 URM-180417
      Cloud App NACSIS-CAT: The linked record IDs from <BHNT>BHBID were not copied to $w of the resulting 780 or 785 fields. This was fixed.
    • April 2023 Resource Management SF:06484247 URM-180510
      IDs from the first <AL>AID= element in a NACSIS record was erroneously reused in the subsequent <AL> group without an AID= element in the Alma records. This was fixed.
    • April 2023 Resource Management SF:06490667 URM-180513
      Records from NACSIS sometimes contain OTHN= elements with prefixes that are not capitalized correctly. This was fixed. Alma now corrects the capitalization of these prefixes: (JP-ItNTS), (JP-ToTOH), (OCoLC).
    • April 2023 Resource Management SF:06492233 URM-180648
      In some cases, when an Alma field 505 $t ended with a slash preceded by a space ' /', it duplicated the record. This was fixed by removing the slash before contributing the content for such particular fields.
    • April 2023 Resource Management SF:06490665 URM-180712
      Alma contributing records to NACSIS: 084 subfield 2 caused errors, preventing the upload of the record to NACSIS. This was fixed with additional classification codes that have been implemented.
    • April 2023 Resource Management SF:06490827 URM-180718
      Volume information was not correctly parsed from the NACSIS <CW>CWT element when the volume contained CJK characters. This has been fixed.
    • April 2023 Resource Management SF:06512606 URM-180863
      When exporting a subject heading from Alma bibliographic field 651 (Subject Added Entry-Geographic Name) to NACSIS, the subject heading field was incorrect. This was fixed with the correct subject heading type code in NACSIS which is 'F'.
    • April 2023 Resource Management SF:06494872 URM-181114
      Copy Cataloging NACSIS to Alma: The NCID numbers (uniform title record IDs) were not copied to the 130 or 730 field $0. This has been fixed.
    • April 2023 Resource Management SF:06499475 URM-182495
      When importing records from NACSIS into Alma, the complete string OTHN was not mapped into tag 035 when OTHN contains one of the following values: GPON ISSN LCCN NBN NDLCN ISBN XISBN. This has been fixed by implementing these values.
    • April 2023 Resource Management SF:06542519 URM-183035
      When tag 016 in Alma has the subfield $$2 JTNDL, the identifier from tag 016 $$a was not mapped to the NACSIS field NDLPN. This was fixed by implementing additional specifications indicating when Alma bibliographic field 016 should be exported to the NACSIS system.
    • April 2023 Fulfillment SF:06538296 06639849 06563249 06663748 06677046 URM-182351
      In some cases, a loan would be renewed when the policy did not allow it to be renewed. This was fixed; renewals in these cases are not implemented when the policy prohibits them.
    • April 2023 Fulfillment SF:06304763 05805276 06514221 05315449 06511156 05319076 05311705 URM-91472
      Previously, when a loaned item was scanned via the Scan In Items option, and the user was 'Currently At' a work order department, the 'Desk name' of the Return action that appeared in the Physical Item Editor page, in the History tab, appeared as the internal ID of the work order department instead of its name. This was fixed; the name of the work order department now appears in this location, as expected.
    • April 2023 Fulfillment SF:06301714 URM-172775
      When a borrowed item was loaned again after being returned, the borrowing request would not have the option to request a renewal. This was fixed by removing the return date from the borrowing request when the item was loaned again.
    • April 2023 Fulfillment SF:06482964 06560562 06493631 06618069 URM-180521
      Previously, when a Resource Sharing task was assigned to a user from the New Layout of the Resource Sharing Task List, and a General Assign To letter was sent to the user to inform them of the assignment, if a note was added when the assignment action was initiated, the note was not included in the letter, and a number appeared in its place in the letter. This was fixed; any notes added to an assignment now appear in the letter sent to the assignee.
    • April 2023 Fulfillment SF:06390023 06631176 URM-178945
      Creating a lending request coming from Rapid ILL would fail if the mms id sent from Rapid was an NZ mms id. This was fixed and now Alma allows creating the request also for NZ mms.
    • April 2023 Fulfillment SF:06436236 URM-174590
      Previously, loaning an item from a different institution in a fulfillment network via RFID generated an error message, 'Security bit failed to be changed: RFID error - barcode not found,' even though the loan was processed correctly. This was fixed; this message no longer appears in this case.
    • April 2023 Fulfillment SF:06442607 06504057 URM-179376
      Previously, running two Resource Sharing Integration Profile jobs, from two different profiles, in parallel was not possible, because they blocked one another. This has been fixed, it is now possible to run two of these jobs simultaneously.
    • April 2023 Administration and Infrastructure SF:06662865 URM-189183
      In the Alma UI, a clickable 'X' for a secondary search box overlapped the Search button. This was fixed.
    • April 2023 Administration and Infrastructure SF:06627842 06641487 URM-187068
      The Preferred Language drop-down included Hawaiian, even when the code table was customized to include only specific languages. This was fixed.
    • April 2023 Administration and Infrastructure SF:06410082 06337374 URM-174399
      The digital images of a representation in a collection were not displayed when clicking the delivery link URL. This was fixed.
    • April 2023 Administration and Infrastructure URM-185829
      In the Alma UI, using the globe icon that displays the list of languages configured for the institution, it was possible to translate the relevant term for all languages, but only when using the UI in English. This was fixed and it is now enabled when the UI is in another language. To enable this, set the following feature flag to active: SPECIAL_ENT_GLOBE_TRANSLATE_IMPROVE.
    • April 2023 Fulfillment - Course Reserves URM-188182 SF: 06655246
      In some cases, courses did not appear in Alma, but they did appear in Analytics. This was fixed.
    • March 2023 Acquisitions SF: 06446126 05299957 06054826 05316646 05318675 URM-164301
      When a hold request from an interested user was added to the queue, it was incorrectly added at the end of the queue, because other requests which should have had a lower priority had already been activated in the queue. The order in which these processes are performed was reversed, so that interested users are entered into the queue before activation takes place, and thus are given the correct priority in the queue.
    • March 2023 Acquisitions SF: 06469629 URM-179711
      Previously, the Rejection reason field was displayed under Request Attributes for all purchase requests, regardless of their actual status, and if its value was not set manually, its default value appeared there. This has been corrected; the Rejection reason field is now only displayed in rejected purchase requests.
    • March 2023 Acquisitions SF: 06567338 06565694 06354457 06486696 URM-180397
      In certain cases, when an API call failed after it changed some fields, the fields that were changed were not restored to their previous states as they should have been. This was fixed; if an API call fails, all changes it made before the failure are reversed.
    • March 2023 Acquisitions SF: 06502702 URM-183842
      Previously, the Purchase Requests task widget sometimes included requests that were not within the user's scope and role. This has been fixed; the Purchase Requests task widget now only includes purchase requests that belong to the user's scope and role.
    • March 2023 Acquisitions SF: 06560540 URM-184523
      Previously, in some cases, the advanced search for POs with status Sent also retrieved Closed and Cancelled POs, and did not retrieve all of the ‘Sent‘ POs. This has been fixed; the advanced search for ‘Sent‘ POs now returns the correct data.
    • March 2023 Acquisitions SF: 06531640 URM-181537
      Previously, the API documentation incorrectly labeled some of the fields of invoice-payment information (payment_identifier, payment_date, payment_currency, and payment_amount should have been voucher_number, voucher_date, voucher_currency, and voucher_amount, respectively). The API documentation has been corrected.
    • March 2023 Acquisitions SF: 06650647 06651897 06651167 06651744 06651036 06650849 06651924 06651074 URM-187318
      License Terms types were unexpectedly updated to have (explicit) and (interpreted) added without any other option. This was corrected and the new license terms were added on top of the existing ones.
    • March 2023 Acquisitions SF: 06483876 06614826 06464579 06653718 06501977 06446915 URM-178201
      When the Update PO Lines Transactions job was used to transfer PO Lines to new funds, the encumbrances on the old funds were not removed as they should have been. This was fixed; when this job runs, encumbrances on old funds are updated as they should be.
    • March 2023 Acquisitions SF: 05316533 06530746 06411285 06544103 URM-160926
      When the automatic SUSHI harvesting job returned with No valid report items found in the file, the job did not run automatically at later dates as it should have. This has been fixed; the job runs on schedule even after it returns with ‘No valid report items found in the file'.
    • March 2023 Acquisitions SF: 06397850 06327433 06409812 URM-176486
      When the automatic SUSHI harvesting job returned with No Usage Available for Requested Dates - indicating that the data was not yet available for harvesting - the job did not try to harvest the data again for the same dates the next time it ran, as it should have. This has been fixed; the job now retries its data harvesting the next time it runs when this situation arises.
    • March 2023 Acquisitions SF: 06404212 URM-178548
      Previously, when an import profile was used to import EOD and create a PO line from it if the creation of the inventory failed, the PO line was skipped, but no error message was returned. This was fixed; an error message is now returned when an EOD import fails.
    • March 2023 Administration and Infrastructure SF: 06235884 06340126 URM-177886
      Previously, if a patron's account had a credit and a fine that were both for the same amount, both the credit and the fine appeared on the User Details page in the Fines/Fees tab, and the patron was sent a letter asking them to pay their outstanding debt. This behavior has been improved: if the credit and fine are both from the same library, they now cancel one another out and are both removed from the Fines/Fees tab. A letter is sent to the patron only if the patron has a non-zero balance at one or more of the libraries in the institution, and the letter lists all the libraries at which the patron has a non-zero balance. Libraries at which the patron's balance is zero are not mentioned in the letter.
    • March 2023 Administration and Infrastructure SF: 05323949 06283816 URM-156734
      Previously, when a Purge User Records job was being configured (Admin > Purge User Records > Add a Job), the User Group field was always included in the Add Job window, regardless of what type of record was chosen under Record Type. Since the ‘User Group‘ field is not relevant to the job when the job's ‘Record Type‘ is ‘Contact,‘ the dropdown list of options for the ‘User Group‘ field contained no values when either ‘Contact‘ or ‘All‘ (which includes the ‘Contact‘ record type) were selected under ‘Record Type.‘ This field is now removed from the window when ‘Contact‘ or ‘All‘ are selected as the record type.
    • March 2023 Administration and Infrastructure SF: 06509612 06490383 URM-180666
      Previously, whenever a fine was added or waived in a user account, the user history was unnecessarily modified. This was fixed; adding or waiving a user fine no longer generates inappropriate additions to the user history.
    • March 2023 Administration and Infrastructure SF: 06314657 URM-169157
      Code Tables opened with a Non-English Language in the filter were incorrectly displaying the Description column in English. This was fixed.
    • March 2023 Administration and Infrastructure SF: 06487046 URM-183444
      Alma mashup included in Primo (classic), the Work Order type was not translated (appeared in English, even when translation existed). This was fixed.
    • March 2023 Administration and Infrastructure SF: 06518738 URM-183835
      The tooltip for the Locations Ordering Profile is misleading (regarding ‘Locations‘ instead of ‘Libraries‘) and needed to be modified. This was fixed and the tooltip now reads, ‘When selected, locations will be ordered according to discovery priority for each library in the custom Libraries Order page.
    • March 2023 Administration and Infrastructure SF: N/A URM-65142
      Many ghost records appear in SOLR but not in the Database. This was fixed by the SOLR / DB Diff job that is triggered twice a year following the semi-annual indexing. This task's aim is to handle PA jobs to ignore such ghost records.
    • March 2023 Analytics SF: 06318005 URM-173383
      Classification Code field in Analytics appears as unknown for codes that appear to be Library of Congress classifications. This was fixed and new LC classification codes were added.
    • March 2023 Analytics SF: 06595378 URM-183851
      Adding address fields to reports in the Users subject area did not display results if the reports were filtered by Primary ID. This was fixed.
    • March 2023 Analytics SF: 06591380 URM-184114
      When exporting reports as a formatted Excel after a filter is applied an error message is displayed. This was fixed.
    • March 2023 Analytics SF: 06588655 URM-184194
      The Users > User Details > Primary Identifier field did not work properly when reports were retrieved by API. This was fixed by adding the User Primary Identifier alias to the field.
    • March 2023 Analytics SF: 06574963 URM-184370
      Reports created with the campusM Home Page > Menu Clicks field displayed only the 15 most clicked menu options. This was fixed and now all menu options are displayed.
    • March 2023 Analytics SF: 06584946 06588233 06653911 06650698 06585834 06596765 06611366 URM-184738
      Adding the Retention Reason field to a report caused it to fail. This was fixed.
    • March 2023 API SF: 06529480 URM-183470
      Previously, the Manage Members API could not populate a set with PO lines, although it should have been able to do so. Now, this API can populate a set with PO lines as expected.
    • March 2023 API SF: 06503140 URM-183954
      Previously, the Update Electronic Collections API was not working properly. This was fixed; it now works as it should.
    • March 2023 API SF: 06442929 URM-184224
      Previously, when the API for deleting a bibliographic record encountered a record that could not be deleted because it had objects attached to it (such as physical items, electronic portfolios, digital representations, and/or orders) if the attachments were of multiple types, the API returned the error message, Record has attachment. This message was too vague, and also was only returned in English and was not translatable. The message has been made clearer: Record has attached entities of various types. In addition, it is now translatable.
    • March 2023 API SF: 06564938 URM-184819
      Previously, updating the Vendor Reference Number Type field of PO lines via the API did not work. This has been fixed, and now works properly.
    • March 2023 API SF: N/A URM-165411
      Previously, updating authority records via the API failed under certain conditions, with the error, "Authority creation failed." This has been corrected; updating authority records via the API no longer fails in these cases.
    • March 2023 Digital SF: 06497820 05310252 URM-132070
      Thumbnail images were created in the wrong orientation. This was fixed.
    • March 2023 Digital SF: 05301453 URM-157289
      The job to generate thumbnails did not function properly. This was fixed.
    • March 2023 Digital SF: 05321628 URM-164090
      If a title had quotes and the metadata is from Primo VE, the title in the Alma Viewer was displayed with backslashes. This was fixed.
    • March 2023 Digital SF: 06527577 URM-184310
      If the Representation Type was changed to Auxiliary with a job, the representation link was not hidden in View IT / Primo VE by the ‘Hide service Representation Delivery Service with Usage Type = Auxiliary‘ display logic rule until the representation is re-saved.
    • March 2023 Digital SF: 06623522 URM-185873
      The Registered access rights rule does not work if the user is not a member of a user group. This was fixed.
    • March 2023 Electronic Resource Management SF: 06348753 URM-171553
      The Extended Export of Electronic Portfolios job took a lengthy amount of time to complete. This issue was fixed.
    • March 2023 Electronic Resource Management SF: 06585389 06549871 URM-182233
      Export Context object to BX completes with FTP Error. This was fixed with an update to the FTP server URL.
    • March 2023 Fulfillment SF: 05323777 URM-173568
      In some cases, the Requests - Recalculate after Inventory Update did not process all the relevant requests. This was fixed; it now processes all the relevant requests.
    • March 2023 Fulfillment SF: 06509469 URM-180283
      Previously, when a loan was renewed, if there were no opening hours defined in the library's calendar for the maximum renew date and onward, and the Closed Library Due Date Management policy was set to Move to next open day, the Maximum Renewal Period policy was ignored when the renewal date was calculated. This was fixed; the renewal date in this situation is now calculated correctly.
    • March 2023 Fulfillment SF: 06543395 URM-183145
      In GetIt, for a serial record, if there were multiple identical items with the same description in the same location, the digitization link appeared only for one of them even when all were digitizable. This was fixed; the digitization link now appears for all of the items.
    • March 2023 Fulfillment - Resource Sharing SF: 06483633 06510321 06506077 06625640 06444602 06453568 06505811 06559829 URM-177931
      In certain situations, borrowing requests located items at lending institutions even when these items were unavailable. A problem with the search query on the lender's side was identified as the cause of the issue, and was fixed.
    • March 2023 Fulfillment - Resource Sharing SF: 06585537 06593389 06570823 URM-179004
      Previously, in resource-sharing task lists, selecting Edit for an item caused the selected search index in the persistent search to change to All Titles instead of remaining unchanged, as it should have. This has been fixed; selecting ‘Edit‘ in a resource-sharing task list no longer resets the search index in the persistent search.
    • March 2023 Fulfillment - Resource Sharing SF: 06501226 URM-181804
      Previously, if a resource-sharing lending library had multiple physical copies of a requested item, some of which could be shipped and some of which could not - depending on their TOUs - no warning message about this was displayed in the New Layout of the Lending Requests task list. Now, a warning message does appear in this situation.
    • March 2023 Fulfillment - Resource Sharing SF: 06478000 URM-179793
      Previously, if a borrowing request for a book contained chapter or page information when the request was sent to Illiad, it was sent as a request with the document type Book Chapter. This should not have occurred when the number of pages in the request was identical to the number of pages in the book, unless the requested format was ‘digital.‘ The process has been fixed, and the document type is now set as it should be.
    • March 2023 Fulfillment - Resource Sharing SF: N/A URM-170010
      In the Details pane of resource-sharing borrowing-request and lending-request task lists (in the New Layout), the interface of the Request form section has been improved. It now provides enhanced responsiveness and better support for non-English text.
    • March 2023 Physical Resource Management SF: 06582282 06268546 URM-174596
      Repository Search: When exporting to Excel logical physical holdings set with thousands of results, not all results were exported. This was fixed, and now the exact results‘ number is exported.
    • March 2023 Resource Management SF: 06250626 06571814 URM-170172
      A process containing two normalization rules, if the first rule was copying a field and the second was editing the field created (for example, by adding to it a subfield), only the first rule was applied. This was fixed.
    • March 2023 Resource Management SF: 06570917 06340092 06584795 URM-171346
      For network members, the publishing to Primo jobs completed with errors in certain cases. This was fixed with some code changes that were implemented to reduce the number of errors.
    • March 2023 Resource Management SF: 06606249 URM-184842
      Publishing Platform jobs fail with a deadlock detected while waiting for a resource. This was fixed by adding a technical change when running the job in republishing mode with Rebuild Entire Index to avoid deadlock errors.
    • March 2023 Resource Management SF: 06590744 URM-184052
      There was a small typo (‘were‘, instead of ‘where‘) in the report of the Change Holdings Information job. This was fixed.
    • March 2023 Resource Management SF: 06570558 06589399 URM-184021
      The file extension is not appearing in advanced searches for digital files. This was fixed and the file extension is displayed.
    • March 2023 Resource Management SF: 05304893 URM-166349
      Authorities keywords search was not preserved when switching from Simple Search to Advanced Search. This was fixed.
    • March 2023 Resource Management SF: 06584778 06498190 06529336 URM-179673
      Search by Country of Publication is not working as expected when the Alma interface language is not English. This was fixed
    • March 2023 Resource Management SF: 06302842 06427237 URM-174143
      Itemizing a logical set of users based on expiry date does not include all results. This was fixed and now the itemized set has the same number of results as the logical set upon creation.
    • March 2023 Resource Management SF: 06430080 URM-178237
      The holding accession number in Get It Hebrew UI was displayed in left to right (instead of, right to left) direction when including Hebrew letters and numbers. This was fixed.
    • March 2023 Resource Management SF: 05319695 05310115 URM-135048
      FRBR group resource type did not match the preferred record. This was fixed. When FRBR preferred criteria is configured, the FRBR group resource type matches the configured type.
    • March 2023 Resource Management SF: 05333316 05326859 URM-149882
      Primo VE - Mendeley export - only the first subject is sent; repeated occurrences are omitted. This was fixed and now all subject fields are sent to Mendeley export.
    • March 2023 Resource Management SF: 05312658 06539347 06529124 URM-161540
      Times Cited link to WoS was not proxied when a record is open access. This was fixed. Time Cited links are now always proxied when the proxy configuration is enabled.
    • March 2023 Resource Management SF: 06308710 05318593 URM-161675
      The Browse Search Label > ""nui.browseGap_message"" is disabled, but the message is displayed in the Browse Search results. A temporary workaround solution is available from the March 2023 release (and Classic Primo May 2023 release). Ex Libris added the following id=""browseGapAlertBar"" to the mentioned toast bar <prm-alert-bar> element that overrides the control of the displayed message: "Note: Some records are not displayed since they are restricted/suppressed from display". To disable the message from displaying, use CSS customization by adding the following to the custom1.css file in the customization package: #browseGapAlertBar { display: none; }
    • March 2023 Resource Management SF: 05306677 URM-162619
      Labels are missing in Primo VE for many Language codes included in Alma, causing codes to display in Primo UI. This was fixed by adding labels for the following languages so their labels will be presented in the Primo VE interface languages list and not their code: Arabic, Catalan; Valencian, Czech, Basque, Finnish, Irish, Japanese, Lithuanian, Bokmal Norwegian, Norwegian Nynorsk, Northern Sami, Traditional Chinese, Hawaiian, Maori, Ukrainian
    • March 2023 Resource Management SF: 06303196 URM-174561
      Primo VE - Sorting continues to be based on Location name rather than Library name even when Display Library name in Location facet is enabled. This was fixed.
    • March 2023 Resource Management SF: 06502342 06611885 URM-180506
      The alphabetical sorting of subjects in the Record's Full Details was incorrectly sorted for letters with accents. This was fixed and now the sorting of subjects is correctly displayed in the Record's Full Details for letters with accents.
    • March 2023 Resource Management SF: 06609576 URM-184725
      Primo VE: the Move Up/Down keys that control the order of the fields in the View Configuration > Brief Record Display tab are ineffective in controlling the order of fields. This was fixed and the Up/Down keys now enable users to set their preferred field order.
    • March 2023 Resource Management SF: 05332924 05303436 06503970 URM-150000
      The Controlled Vocabulary Registry list order can not be sorted. A functional limitation assessment rendered that this option is removed.
    • March 2023 Resource Management SF: 06219940 06314750 URM-168859
      When pushing multiple records to the Metadata Editor (MDE) at the same time, and the list of records in the MDE is sorted by entry time, clicking any record in the list caused it to jump up and change its place in the list. This was fixed and now the record stays in its place.
    • March 2023 Resource Management SF: 06368453 URM-171999
      In the Metadata Editor, the displayed user names are not affected by the Alma user name display configuration. This was fixed, and now the lists of users in the assign record to another cataloger and release all records for user pop-ups are according to the configured format.
    • March 2023 Resource Management SF: 06406322 URM-178072
      MODS: The Date part of Subject Heading is duplicated in Operational Record. This was fixed. The subject displays a single ‘Date‘ part in the operational record that can be viewed from the mms debug screen link for the title list resulting from all titles search.
    • March 2023 Resource Management SF: 06418310 URM-177792
      When cataloging fields 210 $d and $h, Alma changes the field 100 d to h in pos.8 and adds the Publication Date ‘2‘ to pos.13-16. The contribution fails because of h in pos.8. This was fixed.
    • March 2023 Resource Management SF: 06490656 URM-180416
      Cloud App NACSIS-CAT copy cataloging, some fields do not have a romanized transliteration in 880. This was fixed by adding the following missing transliterations:
      • When NACSIS record contains <AL>AHDNGR field with Hiragana or Katakana content and <AL>AHDNGVR does not exist or does not contain latin text, then <AL>AHDNGR is transliterated to latin and added to 880 field linked to 700 field.
      • When NACSIS record contains <SH>SHR field with Hiragana or Katakana content and <SH>SHVR does not exist or does not contain latin text, then <SH>SHR is transliterated to latin and added to 880 field linked to 600/610/611/630/650/651/653 field (Actual field depends on subject heading code in <SH>SHK).
    • March 2023 Resource Management SF: 06494876 URM-180814
      Cloud App - NACSIS-CAT copy cataloging, fields 730 and 130 do not have a romanized transliteration. This was fixed by adding the following missing transliteration:
      • When NACSIS record contains <UTL>UTHDNGR field with Hiragana or Katakana content and <UTL>UTHDNGVR does not exist or does not contain latin text, then <UTL>UTHDNGR is transliterated to latin and added to 880 field linked to 130 or 730 field. (130 field if <UTL>UTFLG = *, otherwise 730 field.)
    • March 2023 Resource Management SF: 05754607 05317872 06558134 URM-149800
      When signing out from the Deposit link (self-deposit page), users were redirected incorrectly to an irrelevant URL. This was fixed.
    • February 2023 Fulfillment SF: 06469678 06563250 06583362 06419522 URM-182010
      The user‘s preferred language would not always be used for the Document Delivery letter. This was fixed; the user‘s preferred language is now used for this letter.
    • February 2023 Fulfillment SF: 06353800 URM-174497
      Previously, when a digitization request for an article was created from a borrowing request, the start page and end page information was not included in the Note field of the digitization request as it should have been. This was fixed; when page information exists in a borrowing request, it is copied into the Note field of the digitization request created from the borrowing request.
    • February 2023 Fulfillment SF: 06498528 URM-180660
      In the new layout of the Resource Sharing Borrowing Requests task list, when the Request Renew action was selected for a borrowing request, the due date was not extended as it should have been. This has been fixed; the due date is now extended as it should be, based on the configuration settings of the library.
    • February 2023 Fulfillment SF: 06251453 URM-177077
      In some cases, NCIP checkout messages would reactivate completed lending requests instead of creating new ones. This was fixed; new lending requests are created in response to these messages, as appropriate.
    • February 2023 Fulfillment SF: 06262527 URM-173988
      Previously, when the link resolver received a link for an OpenURL service page from Proquest with the genre dissertations &· theses, it did not associate this genre with the existing Alma ‘dissertation‘ genre, as it should have. This has been fixed; the link resolver now associates the Proquest dissertations &· theses genre with the Alma ‘ dissertation‘ genre.
    • February 2023 Fulfillment SF: 06491901 06488627 06558899 06556429 06425145 06490679 URM-179796
      1. Previously, returning an item from a different institution in a fulfillment network failed if the item was overdue and the Block When Overdue policy was configured with an Open Days unit of measurement. This was fixed; items from other institutions in the fulfillment network can be returned in this situation. 2. Previously, overdue blocks were incorrectly calculated according to the opening hours of the loaned at library instead of the owning library. This was fixed; overdue blocks are now calculated based on the opening hours of the owning library, as they should be.
    • February 2023 Resource Management SF: 05305634 06317089 05379079 05330117 06553131 06216825 06291791 06052518 05889492 06241463 05515659 URM-105572
      FRBR key ‘ Author+Title‘ does not match when the title differs due to multiple spaces not being compressed into a single space in FRBR keys. This was fixed. To have the expected behavior, customers must run the Recalculate Operation job.
    • February 2023 Resource Management SF: 05317595 URM-163717
      Primo VE getit iframe in Leganto displayed the Primo VE footer. This was fixed and the footer is no longer displayed.
    • February 2023 Resource Management SF: 06400066 URM-175277
      Records that are not available but have an available related item display the wrong availability location. This was fixed and the correct location is now displayed.
    • February 2023 Resource Management SF: 06553519 06535660 06580494 06521420 06552808 06556936 06576970 06552530 06555075 06547620 06556146 URM-180827
      Non-Open Access Quicklinks were not proxied even though proxy configurations were set. This was fixed and now the Access Quicklinks are proxied.
    • February 2023 Resource Management SF: 06519069 06571218 06569916 URM-183118
      Open Access record backlinks are proxied despite being configured as Do not proxy OA records. This was fixed and backlinks with Do not proxy... enabled will not be proxied.
    • February 2023 Resource Management SF: 05332005 05302909 05309184 06050493 05333230 05310481 URM-128540
      MARC21 > 7xx authority records containing subfield $$e. The subfield is duplicated when linking it to the bib record. This was fixed.
    • February 2023 Resource Management SF: 06596075 URM-184033
      Manual Locate job report stated Failed to get results for Z39.50 Locate Profile. This was fixed.
    • February 2023 Resource Management SF: 06569850 URM-183537
      The Metadata Import job of type update inventory was stuck in finalization when the PO Line was not part of a PO or the PO Line did not have an invoice number populated. This was fixed.
    • February 2023 Resource Management SF: 06531604 06478093 URM-178773
      The defined subfields in the profile for the MARC21 bibliographic 377 field is incorrect. This was fixed and the subfields are corrected to align with the Library of Congress.
    • February 2023 Resource Management SF: 06558656 URM-182199
      KORMARC - The Korea government agency (38-39) dropdown field in 008 is missing some values. This was fixed and now all allowed values are displayed in the dropdown.
    • February 2023 Resource Management SF: 06548112 URM-182080
      SBN Alignment - Scheduled job fails with no response from the server. This was fixed and the scheduled job now connects to the external system.
    • February 2023 Resource Management SF: 06620612 URM-185116
      Alma - Z39.50 returned corrupted data in OPAC format. This was fixed by changing the customer parameter "rs_log_debug_enabled" to false.
    • February 2023 Physical Resource Management SF: 06257235 06336295 URM-168856
      Alma displayed the wrong information in relinking item/holding notification message, the message was: Holdings: <the library name of the first Holding>: <location of the first Holding>; <Call Number of the first Holding> was deleted. This was fixed. The message now displays the correct information about the deleted Holding.
    • February 2023 Physical Resource Management SF: 06520548 06553060 URM-181633
      The accession number configuration table is corrupted when the prefix of the sequence includes a special character. This is fixed and the table is no longer corrupted.
    • February 2023 Electronic Resource Management SF: 06424641 URM-126900
      When the portfolio loader created local portfolios for portfolios not found in the Community Zone, the downloadable Actions report still displayed Localize and Activate in the Action column. This is fixed and it will now display Create local portfolio, to differentiate these portfolios from ones that are activated from the Community Zone.
    • February 2023 Electronic Resource Management SF: 06242982 URM-170718
      When an institution is not using the functionality for limiting electronic inventory actions by library, some portfolios were automatically and incorrectly inheriting libraries from their collection. This was fixed.
    • February 2023 Electronic Resource Management SF: 06450644 06445135 URM-180730
      Portfolio loader failed to load portfolios with ISBN that contain spaces in the uploaded file. This was fixed and files are now uploaded without error.
    • February 2023 Electronic Resource Management SF: 06377246 URM-180790
      Portfolio > Edit > Attach to an electronic collection > Recently used button, the drop-down menu was cut off. This was fixed.
    • February 2023 Digital Resource Management SF: 06443353 06544588 URM-179762
      After inputting the required information into the Alma Digital Uploader, no collections are listed even though collections exist in the PSB. This was fixed.
    • February 2023 Digital Resource Management SF: 05317185 URM-159754
      The files of a representation were not displayed properly and could not be downloaded. This was fixed by upgrading the PDF viewer.
    • February 2023 Digital Resource Management SF: 06419740 URM-175956
      In the Alma Viewer, for representations with multiple PDFs, selecting the Next File button did not move you to the next file in the representation. This was fixed.
    • February 2023 Digital Resource Management SF: 06411231 URM-176049
      When PDFs were uploaded to Alma in bulk using a digital import profile, they were not displayed properly in the Alma Viewer. This was fixed, and now they are displayed properly.
    • February 2023 Digital Resource Management SF: 06464735 URM-180125
      The following issues in the Universal Viewer were fixed:
      • Could not copy embed code from the viewer to create an iframe in an external resource
      • Zoom/position coordinates (xywh values) were missing from the URL (viewing position could not be captured by share link) • Could not load manifest to most IIIF viewers when pasting to prefixes
    • February 2023 Digital Resource Management SF: 06396152 URM-180303
      Remote digital repository content embedded in the Alma Viewer was not displayed. This was fixed.
    • February 2023 Digital Resource Management SF: 06477247 URM-181428
      When viewing a digital representation using the Waitlist feature, if a user pressed the Esc key when a session expired, the digital representation would continue to be available indefinitely and a number of concurrent users in excess of the access rights would be possible. This was fixed by disabling the Esc key.
    • February 2023 Digital Resource Management SF: 06545503 URM-181780
      Some PDF files were displayed with a significantly lower resolution in the Universal Viewer compared to the Alma Viewer. This was fixed by increasing the default resolution from 0.7 to 1.0 to enhance image clarity.
    • February 2023 Digital Resource Management SF: 06572017 URM-183185
      If a digital representation had an access right that prevents it from being downloaded, the text of the PDF could still be selected and copied using CTRL+C. This was fixed and now selecting text is disabled.
    • February 2023 Digital Resource Management SF: 06506760 URM-183742
      A digital file was not displayed properly in the Alma Viewer. This was fixed by the PDF upgrade.
    • February 2023 Digital Resource Management SF: 06574114 URM-184445
      Persian script in PDFs was not displayed properly. This was fixed by the PDF upgrade.
    • February 2023 Digital Resource Management SF: 06544588 06443353 URM-179762
      After inputting the required information into the Alma Digital Uploader, no collections are listed even though they exist. This was fixed and collections are now displayed in the list.
    • February 2023 Acquisitions SF: 05314976 06213159 06560540 URM-149433
      Advanced search for PO Lines by PO Status did not work correctly when a Vendor Code was also included in the search criteria or selected in a facet. This was fixed; searching by PO Status and Vendor Code now works correctly. This fix requires full indexing of PO lines in SOLR.
    • February 2023 Acquisitions SF: 06426289 URM-180831
      Previously, a user whose account was expired in Alma could create a purchase request in Primo. This has been corrected. Now, if a user whose account is expired tries to create a purchase request in Primo, an error is returned.
    • February 2023 Acquisitions SF: 06317573 URM-175543
      Previously, performing a Receive action on a PO line for multiple copies of the same item caused all the items included in the PO line to be received, even if some of them had previously been received. As a result, previously received items that were on loan or in transit were "received" again, and the loan or transit status was cancelled. This was fixed. The Receive action now skips items in the PO line that were already received.
    • February 2023 Acquisitions SF: 06411162 URM-176429
      Previously, if a PO line for a subscription was in the claims list because some of the issues in the subscription were not received by their expected dates, although other issues were already received, changing the expected dates of the issues that were not yet received to dates in the future did not remove the PO line from the claims list. This was fixed. When the expected dates of issues that were not yet received are all changed to be in the future, the PO line is removed from the claims list.
    • February 2023 Acquisitions SF: 06472470 URM-178213
      Previously, the PO Line - Fiscal Period Rollover job failed when more than 1000 lines were processed by it. This issue was corrected as part of a reworking of the entire process, which has now been automated.
    • February 2023 Acquisitions SF: 06467159 URM-181899
      Previously, if the fund for the next fiscal period was not created before the Rollover PO Lines job was run, the job added rows in the PO line‘s History tab with Net price 0.00 and List Price 0.00. This issue was corrected as part of a reworking of the entire process, which has now been automated.
    • February 2023 Acquisitions SF: 06508689 URM-180291
      Previously, when the information in a vendor‘s EDI tab was changed, an error message appeared when the changes were saved (although the changes were, in fact, saved). This was fixed; an error message no longer appears when changes to a vendor‘s EDI information are saved.
    • February 2023 Acquisitions SF: 06357647 URM-172531
      The EDI-Load Files process sometimes attached invoices to deleted vendor accounts. This process now only attaches invoices to active vendor accounts.
    • February 2023 Acquisitions SF: 06469156 URM-178128
      Previously, when the Get Bib API was used at a Network Zone level with expand=e_avail, it only returned the AVE fields for the Network Zone, but not those for each member institution. This was fixed; the AVE fields are now returned both for the Network Zone and for all of the member institutions.
    • February 2023 Acquisitions SF: 06463693 URM-180350
      When an electronic portfolio with a static URL was created in the Network Zone using the API, the link to the URL could not be opened from the Institution Zone unless the portfolio was first opened and saved in the portfolio editor. This issue was fixed; now a portfolio that is created using the API with a static link can be accessed immediately after it is created, as expected.
    • February 2023 Acquisitions SF: 06473890 URM-182593
      The Get User Fines and Get User Fees APIs did not display the correct VAT amounts. This has been fixed; the VAT amounts are now displayed correctly.
    • February 2023 Acquisitions SF: 06486933 URM-180345
      Previously, the Update Holding endpoint performed extremely slowly in some cases. This was fixed; the endpoint now functions at the expected speed.
    • February 2023 Acquisitions SF: 06442929 URM-177772
      Previously, the MMS API for deleting bibliographic records from the Network Zone returned the generic INTERNAL_SERVER_ERROR error code when the Institution Zone had inventory for the same bibliographic record. Now, an error message that indicates the specific reason for the failure to delete the record is returned in this case.
    • February 2023 Administration and Infrastructure SF: 06518491 06518520 URM-182486
      Previously, when the integration profile was configured with the Extended Fines and Fees extension, if a patron attempted to make a payment via SIP2 when no fees or fines were outstanding, a confusing error message was displayed. This message has been replaced with a No matching fee found message.
    • February 2023 Administration and Infrastructure SF: 06219258 URM-180368
      SAML expiry mail is not sent to the address defined in the integration profile. This was fixed and the SAML certificate notifications are now sent to the defined contact email address.
    • February 2023 Administration and Infrastructure SF: 06054332 06601777 06590944 06507541 06498452 06511662 URM-167855
      Printing more than one printout from the Printouts Queue didn‘ t operate well with some fonts. This was fixed and now the printing adheres to custom CSS styles.
    • February 2023 Administration and Infrastructure SF: 06254632 URM-166837
      Exported Excel files were automatically formatted with a maximum column width of 100 pixels which was too wide for some screens. This was fixed by reducing the column width to 80 pixels.
    • February 2023 Administration and Infrastructure SF: 06433402 URM-181125
      The Manage Patron Services / Recent button doesn't t display the recent search of users as expected. This was fixed.
    • February 2023 Administration and Infrastructure SF: 06603047 06612116 URM-185139
      SFTP connection to BDS FTP server started failing after the latest upgrade of ftp.bdslive.com. This was fixed.
    • February 2023 Administration and Infrastructure SF: 06525046 URM-182690
      Parts of the Update From Central Catalog job report were only in English. This was fixed and it will now be translated into the preferred language.
    • February 2023 Administration and Infrastructure SF: 06520653 URM-183442
      License terms values are 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 2023 Administration and Infrastructure SF: 06504057 URM-180128
      When editing the Ex Libris system in the Resource Sharing integration profile, the selected schedule was not saved. This was fixed.
    • February 2023 Administration and Infrastructure SF: 06602162 URM-184040
      Save itemized set in network jobs are running very slowly. This was fixed by removing the progress bar updating (the green indication that can be observed during the job run under the Monitor Jobs > Running tab), which caused this slowness.
    • February 2023 Administration and Infrastructure SF: 06528130 06533727 06574320 06403493 06052807 06272848 URM-163869
      Digital files are not displayed properly by Web browsers. Additionally, the files are slow to load or do not load at all. This was fixed by upgrading the pdf.js to latest (v2.14.305) to resolve issues with PDF delivery.
    • February 2023 Administration and Infrastructure SF: 06260874 URM-167281
      Alma Digital PDFs uploaded to PSB do not fully display in Primo VE PSB. This was fixed with a PDF development upgrade and users can now view all PDF pages.
    • February 2023 Administration and Infrastructure SF: 06381672 URM-173100
      PDF pages not displayed - possibly related to old pdf.js version. This was fixed and users can now view all of the PDF pages.
    • February 2023 Analytics SF: 06453099 URM-183509
      When a report was created with the Primary Identifier field, not all of the Barcodes were displayed. This was fixed.
    • February 2023 Rapido SF: 06465645 06250757 06429479 06559986 URM-166557
      Multiple messages in Verification note section from RapidILL create borrowing requests will be presented instead of only showing the first one.
    • February 2023 Rapido SF: 06544847 URM-181143
      If there is an OCLC number (with OCLC prefix) we set the number as OCLC number (well-known system=4) and if there is no number with the OCLC prefix we set it as other standard id.
    • February 2023 Rapido SF: 06506030 06450014 URM-177064
      Book chapters from primo will not be calculated in the Total Copyright Work Percentage.
    • February 2023 Fulfillment - Course Reserves SF: 06550768 URM-181862
      In some cases, the Recent Changes tab indicated that the was no content even though there was content. This was fixed.
    • January 2023 API SF: 06561715 06564755 URM-183635
      With the November 2022 release, REST APIs used with JSON were unintentionally modified in two respects, which may have caused applications calling the APIs to fail. Therefore, those modifications have been reverted to their former states, as follows: 1. Empty fields returned as "null" will once again be omitted. 2. Enumeration-based fields, such as request_status, that returned textual descriptions such as "On Hold Shelf," will once again return codes such as ON_HOLD_SHELF.
    • January 2023 Acquisitions SF: 05328544 URM-147849
      Public access models could not be added to portfolios in the PDA repository because the portfolio was updated from the PO line before the linkage of the public access model took place. This was fixed by changing the code so that the linkage occurs before the portfolio is updated.
    • January 2023 Acquisitions SF: 05314647 06439695 06333864 06457150 06429680 URM-162092
      When PO-line itemized sets contained more than 900 items, opening a page of the task list that was supposed to display members number 900 or above caused an error. This was fixed. All pages of PO-line itemized sets now display properly, even if the set contains 900 members or more.
    • January 2023 Acquisitions SF: 06368555 URM-177333
      In certain cases, when an API call was used to retrieve purchase requests, an internal server error was generated. This failure was traced to a null PO line, and the problem was resolved.
    • January 2023 Acquisitions SF: 06340434 06545401 05301789 URM-178132
      When an item that was previously received, so that its PO line had the receiving status 'Yes,' was scanned a second time at the Acquisitions department, its receiving status reverted to 'No.' This was fixed; scanning a received item a second time does not change its receiving status.
    • January 2023 Acquisitions SF: 06519374 URM-180538
      The properties displayed for a PO line indicated that it had interested users, but no interested users actually existed for it. This was traced to a data-corrector issue, which was fixed.
    • January 2023 Acquisitions SF: 06525896 URM-180651
      When a PO line was created for a portfolio license upgrade, the MMS ID of the portfolio was not saved in the PO line. This was fixed; the MMS ID of the portfolio is now saved in the PO line of the license upgrade.
    • January 2023 Acquisitions SF: 06395491 URM-176361
      Invoice searches for invoice numbers that contained certain configurations of special characters failed to locate the invoices as they should have. It was determined that the error was caused by a normalization process that removed special characters from invoice numbers in a faulty way. This was fixed; normalization of this type is no longer performed, and the invoice numbers are saved as is, with the special characters included.
    • January 2023 Acquisitions SF: 06382103 URM-173482
      When a particular user attempted to move funds within a ledger hierarchy in the the Funds Transfer Page, an error occurred, causing either a blank screen or irrelevant data to be displayed. It was found that this error occurred when the user sorted the list of funds by any column other than 'Type,' which caused the query to the database to be corrupted. This was fixed; the query is no longer corrupted when the table is sorted by any of its columns, and moving funds within the ledger hierarchy works as it should.
    • January 2023 Acquisitions SF: 06557509 06213175 URM-171974
      In the Manage EDI Tasks list, when filtering for a particular Response Date Range, the filtering failed and an error message was displayed. This was fixed; filtering the Manage EDI Tasks list by Response Date Range now works as expected. 
    • January 2023 Administration and Infrastructure SF: 06485543 URM-180184
      When editing a default Rule and clicking Cancel, the changes are still saved. This was fixed and changes are only saved after clicking the Save button.
    • January 2023 Administration and Infrastructure SF: 06325157 URM-171670
      In some languages, an error appeared when trying to dismiss all tasks from Community Zone Update Tasks List. This was fixed.
    • January 2023 Administration and Infrastructure SF: 06368660 URM-175896
      The actions available for Physical holdings records are sorted in a different order in different releases and environments, with no apparent consistency. This was fixed. The order of the actions on the list is now consistent between releases.
    • January 2023 Administration and Infrastructure SF: 06295513 06267960 URM-171279
      Users in a digital waitlist were not notified when their item was available. This was fixed and now a daily system maintenance job notifies the user that the item is available.
    • January 2023 Administration and Infrastructure SF: 06359250
      URM-182052When assigning new DARA recommendations, an Oops error was displayed. This was fixed.
    • January 2023 Administration and Infrastructure SF: 05302586 URM-171345
      In the "Recommendations on job" report, the IDs are now separated by a space and a comma. 
    • January 2023 Analytics SF: 06426789 URM-177474
      When adding fields from Fines and Fees > Staff Operator Details to reports not all data was displayed. This was fixed, and now all data appears as expected."
    • January 2023 API SF: 06552293 URM-182012
      Previously, the Retrieve-Letter API failed with an Internal Server Error for letters that did not have an XSL template. This was fixed; the Retrieve-Letter API now works correctly even for letters that do not have XSL templates.
    • January 2023 API SF: 06473890 URM-182593
      The Get User Fines and Get User Fees APIs did not display the correct VAT amounts. This has been fixed; the VAT amounts are now correct.
    • January 2023 Cloud Apps SF: 06514523 URM-182638
      The Multiple Item Edit Cloud app was allowing the editing of items by users who did not have the required Physical Inventory Operator role for the relevant scope. This was fixed. The Update Item API now checks the scope of the user's Physical Inventory Operator role before performing an action. If the user doesn't have the proper scope, the item is not updated. 
    • January 2023 Digital Resource Management SF: 06499792 URM-180591
      The Universal Viewer is configured to not allow users to download videos, but users were still able to download videos. This was fixed by preventing the Save As menu from appearing when right-clicking the video.
    • January 2023 Digital Resource Management SF: 06519750 URM-181629
      New digital copyrights statements added by the customer under Configuration > Fulfillment > Copyright Management > Copyrights Statements - Digital did not appear in the Copyrights field drop-down list under Configuration > Fulfillment > Copyright Management > Access Rights. This was fixed.
    • January 2023 Digital Resource Management URM-177029
      PDF.js was upgraded to the latest version (v2.14.305) to resolve issues with PDF delivery.
    • January 2023 Electronic Resource Management SF: 06340451 05327330 URM-164275
      Extended export failed if a portfolio or collection's license had been deleted. This issue was fixed and Extended export works correctly.
    • January 2023 Electronic Resource Management SF: 06317072 URM-170531
      Upload holdings scheduled job skips since the Distribute Resource Sharing Member Configuration job is enabled and running at the same time. This was fixed and the distribute resource sharing configuration job will not block the upload electronic holdings job.
    • January 2023 Electronic Resource Management SF: 06424449 06412133 06492138 06595180 06563317 06402571 06338698 URM-177319
      The Upload Electronic Holdings Job for Ovid was not activating all of the relevant portfolios in the input file. This was fixed and now all relevant portfolios in the input file are activated.
    • January 2023 Electronic Resource Management SF: 06481447 URM-178672
      When the user clicked on Save for the first time in the portfolio editor, a change in the coverage statement field was recorded in the history tab without any changes made by the user. This issue was fixed.
    • January 2023 Electronic Resource Management SF: 06481670 06487846 URM-178949
      The Link Resolver Usage Analytics for Electronic Collection Name displayed the Interface Name instead of the Electronic Collection's Public Name. This was fixed.
    • January 2023 Electronic Resource Management SF: 06513533 06480900 URM-180399
      A bug in the Upload Electronic Holdings job prevented matching for some ISBNs. This was fixed.
    • January 2023 Fulfillment SF: 06509132 06465328 URM-180404
      It was not possible to check out Fulfillment Network (FN) items on self-check machines that send Alma an Item Information message before sending the Checkout message. This was because Alma only supported FN items in Checkout and Check-in messages. The issue was fixed by adding support for FN items in Item Information messages. Note: The Item Information response for FN items only includes the 'title' and 'owner' item fields.
    • January 2023 Fulfillment SF: 06478892 URM-180562
      Previously, the Fulfillment > Manage In Process Items page did not enable users to choose how many items to display per page; a maximum of 20 items was displayed. This was fixed, and the page now offers pagination options.
    • January 2023 Fulfillment SF: 05312724 URM-158766
      In the Fulfillment > Manage Patron Services page, in the Requests tab of a patron, the order of the options in the 'Task' dropdown list changed arbitrarily. This was fixed; the list is now in alphabetical order in every language.
    • January 2023 Fulfillment SF: 06517349 06504182 06564653 06502652 06567809 URM-180808
      Fines and fees were created wrongly when loaned items with fines or fees were recalled and then later the recall was cancelled and the status of the loans returned to normal. This occurred when the Terms of Use of the items were configured for either 'Automatic Renewal' or 'Restore Due Date'; the due date wasn't changed when the recall was cancelled, but the profile was removed, which caused overdue fines to be levied again and overdue-fine notification letters to be resent when they should not have been. This was fixed.
    • January 2023 Fulfillment SF: 06389698 URM-173984
      Under certain circumstances, if a circulation desk assigned to handle a patron request used the Skip Location option to reassign the request to a different circulation desk, Alma's confirmation message showed the ID number of the new location rather than its name. This was fixed; the location name is now shown in the confirmation message. 
    • January 2023 Fulfillment SF: 06488346 06353076 06447887 06457136 06504406 06239189 06515020 URM-178308
      The Alma Link Resolver failed to return a related service when the institution did not have a required service. The problem arose when information about related services was in the Community Zone. This issue has been fixed; the Link Resolver now returns related services that are active in the institution based on relationships that are defined in the Community Zone.
    • January 2023 Fulfillment SF: 06559054 06521087 06453571 06038384 URM-178762
      Changes that were made to user accounts in the Network Zone when user accounts are centrally managed were not consistently distributed to the Institution Zone. This was fixed; changes to user accounts that are implemented in the Network Zone are now reliably distributed to the Institution Zone.
    • January 2023 Fulfillment SF: 06504717 URM-180534
      Previously, some Overdue and Lost Item jobs failed due to location codes that contained special characters. This problem was fixed; special characters in location codes no longer cause this job to fail.
    • January 2023 Fulfillment - Resource Sharing SF: 06373844 06465218 06422934 06388482 06476218 URM-173294, URM-178147
      Previously, the Resource Sharing Completed Request Cleanup job would fail when there were a large number of requests to process. This problem was fixed; the job now runs properly even when there are a large number of requests.
    • January 2023 Fulfillment - Resource Sharing URM-181809
      In the New Layout of the resource-sharing borrowing-request list, in the Details pane, the publication date of a requested book or book chapter, and the page numbers of a requested book chapter, only appeared for physical resources. This information now also appears for digital book and book-chapter requests.
    • January 2023 Resource Management SF: 06379248 URM-173032
      An error resulted when 'Push Selected to MDE' button was pressed when adding a title to a collection. This was fixed and the 'Push Selected to MDE' button was removed from adding titles to collections.
    • January 2023 Resource Management SF: 06433257 URM-178224
      Japanese: The U+202F NARROW NO-BREAK SPACE character was not converted to a normal space character (as was already done for U+3000 IDEOGRAPHIC SPACE (also known as double-width space)). It has now been added to the list of character conversions done when the customer parameter solr_searching_language = jp.
    • January 2023 Resource Management SF: 06426835 URM-176958
      Display of Additional Staff Search Fields does not support special characters. This was fixed and the fields now support special characters.
    • January 2023 Resource Management SF: 06463158 URM-178076
      Creating a set using an Excel file with empty lines caused an error. This was fixed and these lines are now skipped.
    • January 2023 Resource Management SF: 05315795 URM-144627
      New Metadata Editor: Clicking CMD + click for rows multi-selection in the editor in macOS does not work. This was fixed.
    • January 2023 Resource Management SF: 06288070 URM-170939
      When testing a normalization rule, changes made without saving in the bib record are not considered in the preview. This was fixed. 
    • January 2023 Resource Management SF: 05331510 URM-178777
      New Metadata Editor: When the CP 'font_for_special_characters' is enabled, the font size is smaller. This was fixed.
    • January 2023 Resource Management SF: 05301855 URM-163297
      There were some values of the KORMARC control-field 008 that were missing for the rare book record type. This was fixed and all values were added.
    • January 2023 Resource Management SF: 06372926 URM-172328
      New Metadata Editor: The 'expand from template' menu action was incorrectly enabled for Community Zone records. This was fixed and the menu action is now disabled in such cases.
    • January 2023 Resource Management SF: 06546700 06560319 06546746 06513152 URM-181539
      New Metadata Editor: When a user with the correct role tries to duplicate a template, the new template can’t be saved or edited. This was fixed. 
    • January 2023 Resource Management SF: 05302909 05309184 05310481 05332005 05333230 06050493 URM-128540
      MARC21 > "7xx authority" records containing subfield $$e. The subfield is duplicated when linking it to the bib record. This was fixed.
    • January 2023 Resource Management SF: 06207291 URM-166575
      Analytics is lacking the labels for 2 values in the Authorities Heading Subject details (Chronological Subdivision, General Subdivision). This was fixed. The labels have now been added.
    • January 2023 Resource Management SF: 06338499 URM-173886
      Linked 880 fields were using punctuation rules for 8XX fields instead of from the linked field. This has been fixed.
    • January 2023 Resource Management SF: 06513357 URM-180669
      Metadata configuration list - Authority vocabularies list was not displayed when there was a local authority of type 'DCMI'. This was fixed and now the authority vocabularies list is displayed.
    • January 2023 Resource Management SF: 06333927 URM-175574
      For some users, opening the 'Monitor and View Imports' page took a long time. This was fixed. The loading time for this page was enhanced and the performance was improved. 
    • January 2023 Resource Management SF: 06441333 URM-176702
      Sequence number Maintain job: When running on a set that includes more than one record, the sequence number was not updated in the database. This was fixed. Saving sequences that already existed in the DB (compare based on prefix and sequence number), will 'skip' over all the existing sequences instead of creating duplications. In addition, the Job report will reflect all the skipped sequences. 
    • January 2023 Resource Management SF: 06345071 URM-171219
      Records marked for merge are sometimes not merged correctly in Alma. This was fixed. Two new counters were added to the job report for the SBN alignment jobs: 'Record not merged - non-preferred record doesn't exist in Alma' and 'Record not merged - preferred record doesn't exist in Alma'. This should reduce the number of records that are included in the 'Failed to merge records' without explanation.
    • January 2023 Resource Management SF: 06548112 URM-182080
      SBN Alignment job - Adding a new schedule option was added (everyday at 20:00).
    • Was this article helpful?