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

    Alma 2020 Release Notes

    Search for what you need
    Search: magnifying-glass-gray.png Release:
    Click to download the PDF of the Alma July 2020 Release Notes and Resolved Issues.

    Make the Most of July's Release

    Action Items
    User Sets and Advanced Search for Users - The new options to search users in advanced mode allows creating sets based on multiple search attributes. This way, you can use complex conditions to save a list of users as a set for various purposes, such as for sending a notice, running an update etc.
    Push user records from NZ not via SIS - Networks that share user records in the Network Zone can now manage the Network Zone users not only via SIS updates but also by manual or API updates, as well as by running batch user updates in the network using the Update/Notify Users job.
    Scan In Interface - Allow check in of shipped items - You can now set the system to issue a warning if an item that is scanned in is expected to be shipped for resource sharing and not expected to be scanned in.
    Enhancements to Forms - Institutions now have advanced control over the configuration of deposit forms, both staff and patron, including repeatable fields and additional filed types such as check-boxes and many more.
    Enhanced Sorting Support for Collections - Patrons are provided with a rich set of new sort routines for titles under a collection, and Alma staff can configure the default sort routine both for sub-collections and for titles under each collection level.
    Provide the ability to share and contribute GES templates in the CZ - Part II - Do you have a useful general electronic service you created? You can now share it with the community by contributing it to the Community Zone.
    CZ Contribution - Update contributed collections - Part II - Do you have a local electronic collection that will be useful to wider Alma community? You can now contribute additional information associated with your local electronic collection.

    Upcoming Issues to Note

    Security update - Removing HTTP allowed exceptions for Alma

    To align with industry standards and avoid security vulnerabilities, Ex Libris is removing its remaining HTTP allowed exception. Alma will require working with HTTPS for all incoming traffic and as result, will redirect all HTTP traffic to HTTPS traffic. This means that all browser activity will continue working as usual. For more information, see Technical Requirements for Alma and Discovery Implementation.

    Support for HTTP will be phased out as follows:

    Release Environment
    June EU00, EU01, EU02
    July NA01, NA02, NA03
    August AP01

    All other instances already support HTTPS only. We are also working to identify non-browser calls coming from specific IPs and are contacting several customers directly asking to change their calls to HTTPS.

    For further assistance, open a Salesforce case and reply with the case number.

    OAS (Oracle Analytics Server) and DV (Data Visualization)

    The OBI that is used with Alma Analytics is being upgraded to OAS (Oracle Analytics Server) which includes DV (Data Visualization). As many in the Ex Libris community are aware, the original plan was to upgrade to OBI 12. However, on January 31, 2020, Oracle released OAS (Oracle Analytics Server) to replace the OBI 12.

    To read the OAS Upgrade Q&A, click here.

    The following table details the rollout plan for the OAS:

    Environment Freeze Start Date OAS Go-Live Date

    EU03

    17.6

    21.6

    NA02

    13.7

    19.7

    NA03

    13.7

    22.7

    NA01

    13.7

    26.7

    CA01

    Q3

    Q3

    AP01

    Q3

    Q3

    EU00, EU01, EU02

    Q4

    Q4

    CN01

    Q4

    Q4

    NA04, NA05, NA06

    Q4

    Q4

    You may need to take certain steps prior to migration. See Ensuring Reports are Migrated.

    Analytics Infrastructure Performance Upgrades

    Ex Libris is currently implementing performance upgrades to the Alma Analytics infrastructure which will include the Oracle In-Memory Database. These upgrades will greatly improve performance when running analytics reports and are being rolled out gradually. The table below describes the rollout plan. For more information, see the Analytics - Infrastructure Improvements in 2020 document.

    Instance

    Will be implemented during

    NA01

    Completed

    NA02

    Completed

    NA03

    Completed

    NA04

    Completed

    NA05

    July 2020

    NA06

    Completed

    NA07

    July 2020

    NA91

    January 2021

    EU00

    Completed

    EU01

    Completed

    EU02

    Completed

    EU03

    July 2020

    EU04

    July 2020

    AP01

    July 2020

    CA01

    September 2020

    CN01

    January 2021

     

    Next Release Sneak Preview

    Select August 2020 Sneak Preview to view the next release sneak preview.

    Make the Most of June's Release

    Action Items
    Limit User Managers to Non Restricted Accounts - It is possible to restrict users that have access to user accounts so that they cannot update restricted users accounts. For example, it is possible to set that some users that have a User Manager or Circ Desk Operator role will still not be able to update accounts of library staff. Restricted accounts can be defined as accounts with given user groups or with given user roles.
    Bulk changes to Physical Items using existing jobs - Alma users are able to perform bulk changes on Physical Items directly through the Physical Items search and Items list. The changes will be done for selected records by the user using existing jobs. In addition, the user is able to create an itemized set for those records.
    Ability to change all temporary fields for Physical Items - The Change Physical Items job has been enhanced to enable the user better coverage of temporary location changes, Statistics Notes, Sequences and an improved usability of the parameters screen.

    Upcoming Issues to Note

    Security update - Removing HTTP allowed exceptions for Alma

    To align with industry standards and avoid security vulnerabilities, Ex Libris is removing its remaining HTTP allowed exception. Alma will require working with HTTPS for all incoming traffic and as result, will redirect all HTTP traffic to HTTPS traffic. This means that all browser activity will continue working as usual. For more information, see Technical Requirements for Alma and Discovery Implementation.

    Support for HTTP will be phased out as follows:

    Release Environment
    June EU00, EU01, EU02
    July NA01, NA02, NA03, AP01

    All other instances already support HTTPS only. We are also working to identify non browser calls coming from specific IPs and are contacting several customers directly asking to change their calls to HTTPS.

    For further assistance, open a Salesforce case and reply with the case number.

    Analytics Infrastructure Performance Upgrades

    Ex Libris is currently implementing performance upgrades to the Alma Analytics infrastructure. These upgrades will greatly improve performance when running analytics reports and are being rolled out gradually. The table below describes the rollout plan. For more information, see the Analytics - Infrastructure Improvements in 2020 document.

    Instance

    Will be implemented during

    NA01

    June 2020

    NA02

    Completed

    NA03

    June 2020

    NA04

    Completed

    NA05

    July 2020

    NA06

    Completed

    NA07

    July 2020

    NA91

    July 2020

    EU00

    June 2020

    EU01

    June 2020

    EU02

    June 2020

    EU03

    July 2020

    EU04

    July 2020

    AP01

    July 2020

    CA01

    September 2020

    CN01

    January 2021

     

    GND Name Authorities Changes

    The German National Bibliographic Center DNB (Deutsche Nationalbibliothek) has announced that as of 16 June 2020 the GND (Gemeinsame Normdatei) Name Authorities marked as type N will no longer be supported and will be removed from the GND authority files.

    For more information, see GND Name Authorities Changes

    Make the Most of May's Release

    Action Items
    New Metadata Editor - The new Metadata Editor is now available for your review in the sandbox. See the Metadata Editor and Rollout Plan sections on the Usability Improvements page for more information.
    Requesting Physical Items - It is now possible to set the system to ignore rota lenders that own only electronic copies of a resource, if the borrowing resource sharing request has been made to specifically request a physical resource. This can be set up by setting the new rs_ignore_electronic_for_physical_request parameter to ‘true’.
    Recent Entities for Digital Resources - Collections and Digital representations are added to the list of “Recent Entities” for quick access.
    Keyboard Shortcuts Enhancements - Users can now turn off Alma generic shortcuts when it overlaps with a special keyboard on language shortcut. Each user can access a special screen via the user menu, UI preferences.

    Upcoming Issues to Note

    Security update - Removing HTTP allowed exceptions for Alma and Primo

    To align with industry standards and avoid security vulnerabilities, Ex Libris is removing its remaining HTTP allowed exception. Alma will require working with HTTPS for all incoming traffic and as result, will redirect all HTTP traffic to HTTPS traffic. This means that all browser activity will continue working as usual. For more information, see Technical Requirements for Alma and Discovery Implementation.

    Support for HTTP will be phased out as follows:

    Release Environment
    June EU00, EU01, EU02
    July NA01, NA02, NA03, AP01

    All other instances already support HTTPS only. We are also working to identify non browser calls coming from specific IPs and are contacting several customers directly asking to change their calls to HTTPS.

    For further assistance, open a Salesforce case and reply with the case number.

    GuideMe Step-by-Step Walkthroughs

    In the Alma May release, we are introducing these new GuideMe flows in the Resource Management functional area:

    1. Export Catalog for Cleanup
    2. Import Catalog after Cleanup
    3. Create a Set for a Manual Job
    4. Save a Query for a Manual Job
    5. Create Normalization Rule for Local Extensions
    6. Create Normalization Process for Local Extensions
    7. Run Job to Add Local Extensions

    We highly recommend you take a look at these step-by-step walkthroughs available within the Alma interface (All GuideMe flows on Production). These are easily accessible from the GuideMe menu or the Alma help menu.

    If you have an idea for a new workflow to add to our growing library, please submit your suggestions at the Idea Exchange under Alma.  

     

    GND Name Authorities Changes

    The German National Bibliographic Center DNB (Deutsche Nationalbibliothek) has announced that as of 16 June 2020 the GND (Gemeinsame Normdatei) Name Authorities marked as type N will no longer be supported and will be removed from the GND authority files.

    For more information, see GND Name Authorities Changes

    Next Release Sneak Preview

    Select June 2020 Sneak Preview to view the next release sneak preview.

    Make the Most of March's Release

    Action Items
    Option to keep Rapid ILL requests open - If you use Alma to export borrowing requests to Rapid ILL, you can now keep the request active in Alma in order to further track the request in Alma until it is completed in Rapid ILL.
    Claim request based on Average Supply Time - Borrowing libraries that use Alma for peer to peer requests can now automatically send claim messages to lenders that have not fulfilled a request within a defined period of time. In addition, the borrowing libraries can automatically cancel request that they expect to have been fulfilled already.
    Support ability to change to an absolute path in the S/FTP Definition - The S/FTP definitions have been enhanced to support absolute paths in addition to the relative paths already supported. This is needed to support file transfer with specific systems provided by OCLC, which recently changed how they transfer files. 

    Upcoming Issues to Note

    Security update - Removing HTTP allowed exceptions for Alma and Primo

    To align with industry standards and avoid security vulnerabilities, Ex Libris is removing its remaining HTTP allowed exception. Alma will require working with HTTPS for all incoming traffic and as result, will redirect all HTTP traffic to HTTPS traffic. This means that all browser activity will continue working as usual. For more information, see Technical Requirements for Alma and Discovery Implementation.

    Support for HTTP will be phased out as follows:

    Release Environment
    July NA01, NA02, NA03, AP01
    April EU00, EU01, EU02

    All other instances already support HTTPS only. We are also working to identify non browser calls coming from specific IPs and are contacting several customers directly asking to change their calls to HTTPS.

    For further assistance, open a Salesforce case and reply with the case number.

    OBI Upgrade and Data Visualization (DV)

    Ex Libris is upgrading the Analytics platform from version 11 to 12 of OBIEE. As part of this upgrade, the Data Visualization tool is also being added, which adds great value to the analytics platform. To learn more about both OBI 12 and Data Visualization and how DV interacts with Alma, see Data Visualization (DV) and OBI 12. Please note that Data Visualization (DV) will be deployed in 'Preview Mode', meaning it is available for testing and evaluation but is not yet intended for full production use. We will continue to update you on plans for the general release of Data Visualization (DV) later in 2020.

    The originally scheduled release of OBI 12 and Data Visualization has been amended. For further details, see here.

    For more information, visit the FAQ page.

    Next Release Sneak Preview

    April 2020 is a maintenance release that will not contain any new features.

    Make the Most of February's Release

    Action Items
    Local Extensions for Community Zone-Linked Bibliographic Records - Are you using the Community Zone? Did you always want to add your own proprietary information to Community Zone Bibliographic records? You can now achieve this by using local extensions. For more information see Working with Local Extension Fields.
    "Quick Printing" Option for Multiple Records - Multi Select Quick printing support was added to the 'Pick From Shelf' task list.
     

    Sandbox Refresh

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

    OBI Upgrade and Data Visualization (DV)

    Ex Libris is upgrading the Analytics platform from version 11 to 12 of OBIEE. As part of this upgrade, the Data Visualization tool is also being added, which adds great value to the analytics platform. To learn more about both OBI 12 and Data Visualization and how DV interacts with Alma, see Data Visualization (DV) and OBI 12. Please note that Data Visualization (DV) will be deployed in 'Preview Mode', meaning it is available for testing and evaluation but is not yet intended for full production use. We will continue to update you on plans for the general release of Data Visualization (DV) later in 2020.

    As of December 2019, OBI 12 for Alma Analytics and DV is being used by 14 institutions as early adopters. In March 2020, both OBI 12 and DV will be available to NA01, NA02 and NA03 institutions, and during May 2020 to all other institutions. As part of the OBI upgrade from v11 to v12, institutional reports will be migrated. During the migration (a week as per the following schedule) it will not be possible to create new reports that will be migrated to OBI12. This is referred to as the 'freeze period'.

    Data Center Step Date

    Chicago Data Center

    (NA01, NA02, NA03, NA91)

    Migration of OBI11 reports to OBI12 (freeze period) February 22-28
    OBI12 Go Live March 1
    All other Data Centers Migration of OBI11 reports to OBI12 (freeze period) May 2 -8
    OBI12 Go Live May 10 (Release Update)

    For more information, visit the FAQ page.

    Next Release Sneak Preview

    Select March 2020 Sneak Preview to view the next release sneak preview.

    Make the Most of January's Release

    Action Items
    More Possibilities for the Alma Color Theme - We have added an additional 6 new colors themes for an institution to select. This provides more options to fit your institution brand and separation between environments. The colors comply with accessibility standards for contrast.
    For information on Primo VE new release features, see the Primo VE January 2020 Release Notes.

    Sandbox Refresh

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

    OBI Upgrade and Data Visualization (DV)

    Ex Libris is upgrading the Analytics platform from version 11 to 12 of OBIEE. As part of this upgrade, the Data Visualization tool is also being added, which adds great value to the analytics platform. To learn more about both OBI 12 and Data Visualization and how DV interacts with Alma, see Data Visualization (DV) and OBI 12. Please note that Data Visualization (DV) will be deployed in 'Preview Mode', meaning it is available for testing and evaluation but is not yet intended for full production use. We will continue to update you on plans for the general release of Data Visualization (DV) later in 2020.

    As of December 2019, OBI 12 for Alma Analytics and DV is being used by 14 institutions as early adopters. In March 2020, both OBI 12 and DV will be available to all NA institutions, and during May 2020 to all other institutions. As part of the OBI upgrade from v11 to v12, institutional reports will be migrated. During the migration (a week as per the following schedule) it will not be possible to create new reports that will be migrated to OBI12. This is referred to as the 'freeze period'.

    Data Center Step Date

    Chicago Data Center

    (NA01, NA02, NA03, NA91)

    Migration of OBI11 reports to OBI12 (freeze period) February 22-28
    OBI12 Go Live March 1
    All other Data Centers Migration of OBI11 reports to OBI12 (freeze period) May 2 -8
    OBI12 Go Live May 10 (Release Update)

    For more information, visit the FAQ page.

    Cost Usage Subject Area in Alma Analytics Deprecated

    Please note that in Alma Analytics, the Cost Usage subject area and its related features are deprecated for this release. This includes:
    • The fields of the Cost Usage subject area that are available when selecting New > Analysis > Cost Usage
    • The out-of-the-box reports and dashboards for Cost Usage under /shared/Alma/Cost per Use/Reports and under /shared/Alma/Cost per use via COUNTER reports and acquisitions data
    • The folder Cost per use via COUNTER reports and acquisitions data
    All reports that use the Cost Usage subject area no longer work.
    Institutions that use reports from the Cost Usage subject area can do the following:
    • Take advantage of the over 30 new out-of-the-box reports in the /shared/Alma/Cost per use via COUNTER reports e-inventory and acquisitions data/Reports folder. These reports use the new Cost Usage of the E-Inventory subject area.
    • Use the out-of-the-box Electronic Cost Usage Dashboard (which uses the above reports) located in the /shared/Alma/Cost per use via COUNTER reports e-inventory and acquisitions data/Dashboards folder.
    • Make their own customized reports using the Cost Usage dimension of the E-Inventory subject area.

    GuideMe Step-by-Step Walkthroughs

    Take advantage of our new GuideMe walkthroughs! GuideMe is a help tool layered over Alma, providing step-by-step guidance enabling you to get just-in-time help on selected workflows. These flows are segmented by role displaying flows relevant to your role in your institution. Additional GuideMe flows will be added on an ongoing basis. See GuideMe FAQ for more information.

    Next Release Sneak Preview

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

    Main Features

    Purchase Request Form Alert

    July 2020 Acquisitions NERS NERS Enhancement (ID #5685) URM-121061
    When a patron in Primo enters an ISBN or EISBN number in a blank Purchase Request form, an alert now displays indicating whether a holdings for the resource exists in the library. Primo displays a message that a holdings does not exist for the identifier placed by the patron, which may be because the resource does not exist, because there is a location, bibliographic record, or holdings that is suppressed from discovery, or because, for electronic resources, the electronic portfolio is not active. This is also relevant for network and multi-campus.
    This functionality is controlled by the customer parameter PR_indicate_for_primo_if_ISBN_exists, and is enabled by default. See Configuring Other Settings (Acquisitions).
    This enhancement is available for Primo classic only and will be made available for PrimoVE users in a future release

    Activating GOBI Real Time Orders Sent from the Relevant Portfolio in the Community Zone

    July 2020 Acquisitions idea exchange Idea Exchange SF: 00596978 00713525 00426146 URM-124024
    For orders originating from GOBI, Alma will attempt to locate the relevant portfolio located within a Community Zone collection using the vendor proprietary identifier number or the ISBN/ISSN and activate it within the relevant collection in the institution, for this functionality to work it is important that the relevant collection will be activated from the Community Zone in the institution. In cases where Alma does not find a matching portfolio in the relevant Community Zone collection or if the relevant collection was not activated in the institution, a stand-alone portfolio will be created in Alma will not be linked to a Community Zone portfolio. See GOBI vendors list for list of Community Zone collections which supports this functionality.
    Additionally, three new collections are now available in the OASIS vendors list.

    Move Invoice Owner from an Institution to a Library

    July 2020 Acquisitions idea exchange Idea Exchange SF: 00810848 URM-108432
    You can now change the owner for an invoice after it is edited. The values for the Owner list depend on the owner of the linked PO line/s, user role scope, library availability for vendor, and vendor account and funds. When saving the invoice, if the invoice owner is the institution but all the PO lines associated with the invoice lines are owned by a single library, a confirmation message displays that allows you to confirm or cancel your changes.

    Platform Field Added to the SUSHI Account Details

    July 2020 Acquisitions idea exchange Idea Exchange SF: 00799252 00800227 00801116 00802185 00802271 00807054 00810911 00814981 00818471 00831882 URM-121276
    The SUSHI Account Details page now includes a Platform field. This field should be populated for vendors that require a platform code for successful harvesting of usage data. Note that the platform code is case sensitive. Only one platform code can be used per SUSHI account.

    Advanced Search for Users

    July 2020 Administration and Infrastructure idea exchange Idea Exchange SF: 00180020 00214711 00220450 00226302 00024637 00024650 00074581 00084395 00102382 00125857 00126248 00129769 URM-127082
    You can now search for users by combining search criteria, using Alma advanced search. This is available only to users with the roles and privileges to search for users.
    The quick autocomplete search in the Patron Services Workbench currently uses the ‘All’ search, including the new indexes. In the upcoming Release Update, this will be changed so that the search will be limited to names, emails and identifiers.
    In addition, there are new search options for user records. The new search options in advanced search are:
    • User group - Equals, Is Empty, Not Equals, Is Not Empty - equals and not equals options display a multiple choice drop-down list.
    • Create date - Equals, Before, After
    • Birth date - Equals, Before, After, Is Empty
    • Expiration date - Equals, Before, After, Is Empty
    • Purge date - Equals, Before, After, Is Empty
    • Last activity date - Equals, Before, After, Is Empty
    • Statistical category - Equals, Is Empty, Not Equals, Is Not Empty - equals and not equals options display a multiple choice drop-down list.
    • Note - Contains Keywords, Contains Phrase - this option is also available on the simple search
    • Has note type - Equals, Not equals - displays a multiple choice drop-down list.
    • Has block type - Equals, Not Equals - displays a multiple choice drop-down list with block types.
    • Has Identifier type - Equals, Not equals - displays a multiple choice drop-down list.
    • Fine/fee total sum - <, <=, >, >=
    • Campus - Equals, Is Empty, Not Equals, Is Not Empty - equals and not equals options display a multiple choice drop-down list.

    New options for existing search criteria in advanced search options are:

    • Email - Equals, Is Empty
    • First Name - Contains Keywords, Contains Phrase, Is Empty
    • Identifiers - Equals
    • Job Category - Equals, Is Empty, Not Equals, Is Not Empty - equals and not equals options display a multiple choice drop-down list.
    • Last Name - Contains Keywords, Contains Phrase, Is Empty
    • Middle Name - Contains Keywords, Contains Phrase, Is Empty
    • Primary Identifier - Equals
    This feature is not deployed in the sandboxes and will be available only on production environments.

    XSL Transformation as Part of an Integration Profile

    July 2020 Administration and InfrastructureURM-80744
    Now when exporting users from Alma to SIS systems that use other data formats than Alma, you can convert Alma's data format to the specific format required by the target system. Previously, the conversion had to be done outside of Alma, and demanded specific technical knowledge and resources from institutions.
    To facilitate the conversion process, you can now do the following:
    • Define an XSLT converter to be used by Alma
    • Apply the XSLT converter to an Integration Profile that defines the way data is exported/imported from/to Alma
    • Manage XSLT converters in Alma:
      • Share converters between institutions
      • Preview results on a demo file
      • Validate converters
    Currently, this is possible for the following integration (see Student Information Systems):
    • SIS import
    • SIS synchronization
    The ability to define XSLT converters disabled by default. If your institution would like to activate this behavior, please contact Ex Libris customer support.
    To manage XSLT converters, a new page Integration XSL Converters was introduced (available from Configuration > General). This page allows creating and editing EXSL converters, as well as allows institutions to share converters in the Community Zone.

    Notification on Last Community Zone Update

    July 2020 Administration and InfrastructureURM-124180
    A notification about the date of the most recent Community Zone update was added to the Help menu located in the Main Menu Icons.

    last updated from CZ.jpg

    Institutions that work with the Community Zone expect that Community Zone resources will be up-to-date to the most recent Community Zone update. To this effect, the Synchronize Changes from CZ job runs daily in each institution updating authorities and resources from the Community Zone to the local institution.

    However, if the number of updates in the Community Zone is very large, the job cannot complete on the same day. Every day the job attempts to close the gap. Thus, in cases of very large Community Zone updates, a delay of a few days might occur in the synchronization of CZ and the local institution. However, when customers do not see the relevant resources updated in their institutions on the day of the Community Zone update, or on the next day, the discrepancy might cause alarm.

    The new notification in the Help menu lets you know the date of the last Community Zone update that was implemented in your system. If the date indicated is not today's date, the reason you do not see some Community Zone updates in your system is due to this delay. You need to wait for the following runs of the job to update your resources.

    In July-deployed environments where the Community Zone Harvesting job has not run yet this notification is not displayed. It will be displayed once the Synchronize Changes from Community Zone job has run.

    See Synchronize Changes from CZ and The Alma User Interface.

    New Alma Layout Enabled

    July 2020 Administration and Infrastructure URM-129108
    Continuing the rollout of the new Alma layout, starting from the July release, the new layout will be available for Alma users in the sandbox. Alma Administrators can turn the new functionality on for a specific user (Opt-in). Ex Libris will introduce the new layout gradually over several Alma releases (See Rollout Plan), giving users enough time to understand, experience, and get used to the changes. As part of the rollout plan, we encourage as many users as possible to get themselves familiarized with the new layout. For instructions for the Alma Administrator, see Turning On the New Layout for Users.
    Ex Libris recommends that all users gain experience with the new Alma layout prior to the new layout Go-Live, which is planned to take place with the deployment of the September 2020 release.
    New Alma Layout.png
    The new layout increases your working area, improves navigation, gives you more options to customize your menus, and facilitates improved user workflows. For a full list of changes, see Layout Improvements.

    Creation of Several Itemized Sets From File in Parallel

    July 2020 Administration and Infrastructure URM-126620
    When creating itemized sets, one of the options to add records to a set is uploading a file that contains the identifiers (MMS ID, ISSN, ISBN, and so forth). The Add Members to Set job runs and creates a set from the file. Previously, only one instance of the job could be run simultaneously. Now any number of instances of this job can run in parallel.

    See Creating Itemized Sets.

    Skipped Job Status

    July 2020 Administration and InfrastructureURM-125859
    The status of jobs that need to be skipped was changed to 'Skipped'. Previously, the status of these jobs was indicated as 'Failed', which was misleading.
    Alma skips jobs in the below cases:
    • Another instance of the job is currently running, and the job does not allow multiple instances.
    • The job is dependent on the completion of another job, and that job is still running.

    Dependent Job Waiting

    July 2020 Administration and InfrastructureURM-124837
    The below dependent jobs now wait till the completion of the job they are depended on with the status 'Pending', and start running after that job completion:
    • Authorities - Link BIB Headings
    • Authorities - Preferred Term Correction
    • Authorities - Handle Local Authority Record Updates
    • MMS - Build Record Relations
    Previously these jobs were skipped with the status 'Failed', which was misleading.

    External Users with Internal Authentication

    July 2020 Administration and InfrastructureURM-97939
    For institutions whose Student Information System (SIS) does not offer authentication services, it is now possible to create users as external in Alma, but assign passwords for them directly in Alma. In this case, all the user information, such as name, ID, etc, is managed from the SIS, but the passwords are stored in Alma and managed by the Ex Libris Identity Service.
    When this behavior is active, changing a user from external to internal (and vice versa) does not reset the user password; the existing password the user used as an external user is retained.
    This new behavior is activated by a customer parameter, upon request. If your institution's SIS does not offer authentication services and would like to activate this behavior, please contact Ex Libris customer support.

    Request Anonymization and Anonymization Rules

    July 2020 Fulfillment idea exchange Idea Exchange
    You can now define rules for all anonymization types, not just loans. The anonymization job, which runs once daily, is Fulfillment - Handle Historical Archiving. The rules are found in the Fulfillment Jobs Configuration page (Configuration Menu > Fulfillment > General > Fulfillment Jobs Configuration) next to each anonymization type. This is now the only place the anonymization rules are accessed. The link to Loan Anonymization Rules is no longer available on the Fulfillment Configuration menu.
    The customer parameter, should_anonymize_requests, which previously anonymized a resource sharing request as soon as it was completed, has been renamed to should_anonymize_requests_immediately_when_complete. Now, when set to true, Alma still anonymizes the request as soon as it is completed and also ignores the anonymization rules.
    When creating a rule for request anonymization, if choosing Library or Location as input parameters, the library and location are calculated as follows:
    When a request is completed, if there are multiple items available, if the request was attached to a specific item, for instance, item level request or item already fulfilled the request, the library and location of the item is used. If the request can still be fulfilled by multiple items, the library and location are taken from the holding selected automatically as preferred for fulfilling the request.

    As previously, checking resource sharing requests will anonymize both borrowing and lending requests. However, rules can be applied only to resource sharing borrowing requests.
    Watch the Request Anonymization and Anonymization Rules video (4:28 minutes).

    Option to Exclude the Grace Period When Calculating Fee

    July 2020 Fulfillment idea exchange Idea Exchange URM-104839
    Previously, when calculating fees, when the grace period ended, fines were immediately implemented and set for the entire period including the grace period. Now, the grace period can be set to not be included in the fine period at all. In the policy, currently, you can now configure new periods. Each of the prior periods now has a second period with excluded from day. When that period is selected, the fee calculations are the same, but they are based on the end time of the grace period instead of the due date.

    Digitization Request File Upload Limit

    July 2020 FulfillmentURM-129721
    For attachment digitization requests, the file size limit was increased from 10 MB to 25 MB.

    See Digitization Processing.

    ISO 18626 - Return Information

    July 2020 Fulfillment - Resource Sharing URM-126062
    When using the ISO 18626 resource sharing partner type, return information is now supported. The lending partner can select Send ReturnInfo on the Resource Sharing Partner page to include the information for the originating lending library instead of the resource sharing library. The ISIL code of the lending library is then included in the resource sharing request, if it is populated. The ISIL code is presented on the Resource Sharing Borrowing Task List as Return Information. It is also available in the XML for the ResourceSharingReturnSlipLetter. The field appears in the letter when populated. If the letter is customized, you must manually add the field to the XML in order for it to be populated.
    When scanning an item through the Scan In Interface, the destination information is added to each line. When returning through Returns, it is added to the pop-up display.

    Check-In for Shipped Items in the Scan In Interface

    July 2020 Fulfillment - Resource Sharing idea exchange Idea Exchange URM-71505
    You can now set a message to warn the users if they are going to complete a lending process when scanning items. On the Scan In Messages Configuration page, the Complete lending request message, which defaults to none (no message), can be set to Popup message. When this is set, if an item is scanned in and is part of a Resource Sharing Request that is linked to a lending request in status Shipped Physically, the warning message will require a Confirm or Cancel action. This way the user cannot accidentally complete the lending request. If the message is set to Feedback message, rather than Popup, the feedback will tell them that the request will be completed, but the scan in action cannot be canceled.

    Export Renew Allowed Indication in API to ILLiad

    July 2020 Fulfillment - Resource Sharing URM-122882
    The ILLiad API now supports sending the Renewals Allowed field in a resource sharing request. The 'RenewalsAllowed' indication will be set according to the lending workflow profile that is attached to the ILLiad partner. If one of the following is enabled then Alma will send "RenewalsAllowed": true
    • Patron renewal
    • Staff renewal

    If both patron and staff renewal are disabled then Alma will send "RenewalsAllowed": false.

    Distribute Users from the Network Zone

    July 2020 Collaborative Networks
    Networks that share their user list in the Network Zone can create and update the network zone users manually using the Alma Manage Users menu, the API or the Update/Notify Users job. This is in addition to the previously only option to manage the Network Zone users using SIS feeds.
    Users can now be updated in the Network Zone in the following ways, and the changes will be reflected in the Institutions that have a copy of the user record:
    • The update/notify users job
    • Using an API

    • Manually updating the user in the User Edit form

    Order Indication for Electronic Resources Ordered from NZ

    July 2020 Collaborative NetworksURM-97785
    In a Collaborative Network where electronic resources are managed centrally in the Network Zone and the orders are managed in the individual Institution Zones, institutions can order electronic collections or portfolios managed in the NZ.
    In such cases, when using the staff search for electronic portfolio and electronic collection for Network Zone resources (both combined and NZ searches), Alma will now display the order icon by the records ordered from the Network Zone. Clicking on the link of the number of orders displays the list of the PO Lines of these orders.
    order icon is network search results.jpg
    In Network search
    order icon in combined search results.jpg
    In combined search

    Saving Local Sets in Network Zone

    July 2020 Collaborative Networksidea exchange Idea Exchange URM-96388
    Now the Institution Zone staff can create a local set of bibliographic records in the Institution Zone and then save the set in the Network Zone. 

    This is useful in use cases where a set can only be built in the Institution Zone because the query uses search criteria from either localized fields in the bibliographic record or from the inventory (holdings, items, portfolio, etc.) However, you cannot run normalization rules on Network Zone bibliographic records from within the Institution Zone, since non-localized fields in the Network Zone bib records cannot be changed from within an Institution Zone.

    The current development allows the Institution Zone staff to save a local set of bibliographic records to the Network Zone, where they can then perform any actions with the set, such as running normalization on the bib records. 

    To support this functionality, the Save in Network action was added to the Manage Sets page (Admin > Manage Jobs and Sets > Manage Sets). Choosing this action saves a local set of bibliographic records to the Network Zone. See Saving Sets in Network Zone.

    The new action runs a job that creates a set in the NZ containing only the records linked to the Network out of all records. See Save Set in Network Report.

    Sharing and Contributing General Electronic Services in the Community Zone

    July 2020 Collaborative NetworksURM-126291
    Users now can contribute their General Electronic Services to the Community Zone, where other institutions can copy and use these services.
    The current functionality of distributing general electronic services from Network Zone to Institution Zone using the Distribute Fulfillment Network Configuration job remains as is (see Configuring Fulfillment Information in the Network Zone).

    See Sharing General Electronic Services in the Community Zone and Community Zone Contribution Guidelines.

    The ability to share general electronic services in the Community Zone will become available a few days after the July installation.

    Improvements to Electronic Collections Contributions 

    July 2020 Collaborative Networks URM-126061
    Electronic collection contribution was enhanced as follows:
    • Now you can contribute to additional fields, including static and dynamic URLs.
    • Now you can update additional fields of your contributed electronic collections and share your updates with the community.

    Additional Electronic Collection Fields that You Can Contribute

    The following additional fields can now be contributed:

    Collection Service Portfolio
    • Type
    • Interface name
    • Level URL
    • Is Free?
    • Description
    • Language
    • Category
    • URL type: Dynamic URL
    • Linking level
    • Service is free?
    • Crossref supported
    URL type:
    • Static URL
    • Dynamic URL

    See Managing Electronic Collections.

    Updating Your Contributed Electronic Collections

    If you are the contributor to the electronic collection, now you can update additional fields and share these updates with the Community Zone. Your changes are submitted to a job that runs overnight to update the electronic collection, its portfolios, services, and bibliographic records in the Community Zone. This job copies the information from the override fields to the main fields and then removes the override values. This synchronizes your electronic collection with the Community Zone.

    To update an electronic collection in the Community Zone:
    1. In the Institution tab of the electronic collection, enter the new values in the override fields, and select Update in Community.
      This updates the Community Zone with the new values.
    2. In the confirmation message that appears, click Yes.
      Update confirmation message.jpg

    See Updating Community Zone Contributed Electronic Collections.

    Contributing Static and Dynamic URLs 

    Now Alma supports the contribution of portfolio Static/Dynamic URL and service Dynamic URL, in addition to the existing contribution of parser parameter URL. This way, you see in the Community Zone the exact URL that you contributed.

    URL static and dynamic contribution.jpg

    Override Fields of Community Zone Electronic Collections 

    All activated Electronic Community Zone Electronic collections are edited with your own information. Your edits are only local, no changes are made to the Community Zone record.

    When editing the collection, you make your edits in the override fields. Any later updates to this electronic collection will update only the main values so that you know what the updates were. Your local override values remain unchanged.

    The following additional fields can now be edited:

    Collection Service Portfolio
    • Type (override)
    • Interface name (override)
    • Level URL (override)
    • Is Free? (override)
    • Description (override)
    • Language (override)
    • Category (override) 
    • URL type: Dynamic URL
    • Linking level (override)
    • Service is free? (override)
    • Crossref supported (override)
    URL type: 
    • Static URL (override)
    • Dynamic URL (override)

    See Managing Electronic Collections.

    Audio Visual Media type Added to the Physical Material Type Description Table

    July 2020 Resource Management URM-124669
    The Physical Material Type Description table now includes an Audio visual media option.

    July 2020 Resource Management
    For a child record, Alma now supports displaying a specific item when cataloging a specific issue, part or pages. Previously, Alma supported displaying specific items of the parent record only when cataloging a specific year, volume or barcode.

    The following item specifications are now supported:

    Item Specifications
    Value in
    $g (MARC21 / KORMARC) $v (Unimarc / CNMARC)
    Item Field
    Issue iss: Enum B
    Part pt: Enum C
    Pages p: pages

    MARC 21 example:

    For the below record, two related holdings are shown:

    MARC 21 two records.jpg

    The link in the child record is cataloged in field 773, including the new label iss: (issue):

    MARC 21 filtering.jpg

    After the filtering, only the holdings with the specific item pointed is shown:

    MARC 21 one records.jpg

    UNIMARC example:

    The parent record with many items in different years, volumes and issues:

    MARC21 related items 1.jpg

    The link in the child record is cataloged as follows, including the new label iss: (issue):

    MARC21 related items 2.jpg

    The child record shows in the repository search only the holdings referred to by this field:

    MARC21 related items 3.jpg

    See Configuring Related Records for Physical Inventory.

    MARC 21 Updates

    July 2020 Resource ManagementURM-124466
    The following MARC 21 updates (for bibliographic, authority, holdings, classification, and community information formats) have been added to Alma in the July 2020 release:
    • MARC21 BIB
      • Update No. 27 (November 2018)
      • Update No. 28 (May 2019)
    • MARC21 Holdings
      • Update No. 28 (May 2019)
    • MARC21 Authority
      • Update No. 26, April 2018
      • Update No. 28, May 2019

    Refer to http://www.loc.gov/marc/status.html for additional details regarding these MARC 21 changes.

    Reload Bibliographic Records from Central Catalog On Demand

    July 2020 Resource ManagementURM-98863
    Users working on Bibliographic records in Central Cataloging (Aleph, SBN, CALIS, etc.) need to ensure that they view and update the most recent version of a Bibliographic record.
    A new option Reload Record from Central Catalog was added to the Metadata Editor under the File menu. This option enables reloading the most recent version of the Bib record that was loaded previously from the Central Catalog. This restores the Bib entire record from the Central Catalog, removing any changes made by you.
    This action is available for Bibliographic records that are managed centrally with the required prefix in 035, and the ones that are managed locally. However, only records managed centrally are reloaded.
    reload record from central catalog.jpg

    The Reload Record from Central Catalog option is available only when both below criteria are met:

    • if you have configured a Central Catalog integration profile,
    • when working on Bibliographic records.

    See MD Editor Menu and Toolbar Options.

    Align Record Version with SBN

    July 2020 Resource ManagementURM-115683
    Now users working in SBN can align the local record version with the SBN record version, without making any additional changes to the local version. Since now the date is the same, SBN accepts the record contribution.
    A new entry Align Record Version with Central Catalog was added to the Metadata Editor (Tools > MARC Bibliographic). Selecting this option updates the local version of the record with the SBN record version.
    allign record version with central cataloging .jpg
    The option is visible only if a central catalog integration profile for SBN is defined.

    See Integrating the SBN Italian Union Catalogue and MD Editor Menu and Toolbar Options.

    Public Access Model on the Portfolio Editor

    July 2020 Resource Management
    Access Model defines how end-users can access the electronic resources. The access model has always been indicated in the PO line, but now it is also displayed in a new field Public access model that was added to the Acquisition tab of the portfolio editor. This field presets the active access model associated with the portfolio, as inherited from the PO line that created the portfolio. Any updates to the access model on the PO line are reflected in the Public access model field of the portfolio editor. See Editing a Portfolio Using the Electronic Portfolio Editor.

    You can also change the value of the Public access model field directly on the portfolio editor, and this determines the active access model of the portfolio. However, changing the access model value on the portfolio does not update the access model on the PO line. 

    In case a PO line of type 'License Upgrade' was added to the portfolio as an additional PO line, the Public Access Model field on the portfolio displays the access model associated with the license-upgrade order.

    access model on portfolio editor.jpg

    "Public access model" field on the portfolio editor

    The Include access model in portfolio public note checkbox, which previously controlled the presentation of the access model on the portfolio's Public Note field in the Alma Link Resolver, was now removed from the New Order API integration profile. See Real-Time Ordering.

    To control the presentation of the access model to patrons via Alma Link Resolver, institutions now can use a designated configuration located under Fulfillment > Discovery Interface Display Logic > Other settings. Select the checkbox Enable Display of Access Model to display in Primo the access model information located on the portfolio. 

    Primo VE will support this configuration in a future release.

    The new Enable Display of Access Model option is disabled by default. Institutions that previously had the Include access model in portfolio public note check box enabled in their integration profile, will need to select the Enable Display of Access Model option in the new configuration screen. See Configuring Other Settings.

    enable display of access model in other settings.jpg

    Manage Selected Physical Items

    July 2020 Resource Management URM-126297
    Following the changes made in June 2020 release, the actions that previously were displayed as links of the page actions, were now added to the Physical Items list, to enable you to perform actions on multiple physical items in bulk. In addition, when you select items from the list, the item counter above the list now provides an indication of the number of items selected.

    Due to changes required in the definition of columns, the default display will be restored as part of July release deployment. If display customization was applied, it will need to be redone.

    Manage selected.jpg

    Some of the actions that can be performed, such as running a job and creating/adding to the itemized set, can only be performed if you possess the required permissions.

    See Working with the List of Items.

    Watch the Manage Selected Physical Items video (0:51 minutes).

    Improvements to Electronic Collection and Portfolio Deletion

    July 2020 Resource ManagementURM-127197
    The process of electronic collection and portfolio deletion was made more user-friendly. Now the options to edit records (add, edit or delete) are disabled on electronic collections, portfolios and services once these resources are marked for deletion. In addition, now you are blocked from attaching a stand-alone portfolio to a collection that is marked for deletion (unless the portfolio has some available services). URM-127197

    Enhancements to Forms

    July 2020 Digital Resource Management URM-126496
    Several enhancements have been added to the Alma Forms feature (Configuration > Resources > Metadata Configuration > MARC21 Bibliographic or Qualified Dublin Core > Forms tab) when selecting Add fields:
    • The Checkbox field type was added.
    • The Repeatable field was added to the field types (when configured) to allow the user to add multiple instances of the field. This is available only for Patron Deposit forms.
    • For date fields, if configured to be mandatory, the Default Value field is set to the current date.

    Enhanced Sorting Support for Collections

    July 2020 Digital Resource Management idea exchange Idea Exchange URM-12620
    You can now configure the default sorting for titles and sub-collections in Primo VE, using a richer set of title-level sort routines.
    • To configure the default sorting of titles in a collection, select an option from the Sort titles by drop-down list (Resources > Manage Collections > Edit Collection > Discovery Tab):

      sort_tiles_by_with_fields.png

      Sort Titles By
    • To configure the default sorting of sub-collections in a collection, select an option from the Sort by drop-down list (Resources > Manage Collections > Edit Collection > Sub-collections tab):

      sort_by.png

      Sort By

    DARA Recommendation to Identify Missing Items

    July 2020 DARA URM-109658
    DARA now identifies items that have been missing for a significant amount of time and recommends that you handle them.
    missing_items.jpg
    Missing Items

    By default, DARA identifies items missing for more than 12 months. You can customize DARA to produce recommendations that better suit the needs of your institution. For more information, see DARA – Data Analysis Recommendation Assistant.

    Sort Request Facets

    June 2020 Acquisitions URM-122046
    All facets on the Manage Purchase Requests page, including Requester, are now sorted in alphabetical order.

    Access Model Field in POLine

    June 2020 Acquisitions URM-122990
    In the January 2020 release notes, a new option was introduced to track the access model for concurrent users, which is reflected on the PO line and portfolio (see Create Order API - Improved Matching and Creation of Portfolios to Work with Community Zone). The access model is now stored in the new Access Model field on the PO line for electronic orders. The access model also appears in the portfolio. If you modify the access model on the PO line to be different than the access model on the portfolio, the portfolio will be updated. The access model can also be changed in the Update PO Line Information job.
    There is an option to search for PO lines by access model. In the simple search, the search is by the code. In the advanced search, there is a dropdown only description.
    For PO lines of type License upgrade, the access model is set on the prerequisite page and cannot be modified on the Edit PO line page. For other types of PO lines, the Access Model field is editable on the Edit PO line page.
    The Access model field will be reportable in Analytics in a future release.

    Material Type Added to Primo Purchase Request Form

    June 2020 Acquisitions SF: 00818891 URM-122422
    The default material type option was removed from the purchase request form in Alma. To set the default material type of a new purchase request form in both Alma and Primo, a new Purchase Request Material Types configuration table was added, possible values of the new configuration table are Physical or Electronic request types. This replaces the customer parameter that previously controlled the default, purchase_request_preferred_material_type_default.

    CDI Provider Coverage Field

    June 2020 Resource Management URM-122254
    The Provider coverage field is now available on the CDI tab of the Electronic collection editor. When this read-only field is set to Yes, the collection is indexed with data received directly from the provider. When set to No, a feed from the provider is not available, but at least 80% of the content of the collection is covered in CDI by data received from other providers. The field also displays in the Electronic collection result list, in Institution, Network and Community tabs, below the In CDI field, for any electronic collection where In CDI = Yes.
    This is relevant only for CDI enabled customers.

    Semi-Annual Re-indexing

    June 2020 Resource Management URM-114997
    During June, the semi-annual re-indexing (described in greater detail in Updates) will be run. Features or resolved issues that require re-indexing to be fully functional will be addressed by the June semi-annual re-indexing. See the list below.
    ا – أ – إ – آ
    ى – ي - ئ
    ه - ة - ۀ
    و - ؤ
    ك – گ – ک
    ف - ڤ
    ز - ژ
    ب - پ
    ج - چ
    ق - ڨ
    Until re-indexing, browsing of bib headings and authorities search using F3 for these letters may not work properly.

    Authority Control of Additional Fields in UNIMARC

    June 2020 Resource Management SF: 00536407
    Authority control of the following fields was added to Alma, following their addition to the 3rd edition of the UNIMARC Authority format:
    Tags Search Index
    Uniform Title (X31, X32)
    231 a-w Uniform Title
    232 a-w Uniform Title
    431 a-w Uniform Title
    432 a-w Uniform Title
    531 a-w Related Uniform Title
    532 a-w Related Uniform Title
    Name-Title (X41, X42)
    241 a-t Name Title
    242 a-t Name Title
    441 a-t Name Title
    442 a-t Name Title
    541 a-t Name Title
    542 a-t Name Title

    These fields fully support the Alma authority control workflows, including linking, Preferred Term Correction, and F3.

    The following table identifies the search indexes to which the new UNIMARC authority tags are mapped.

    Search Index Tags
    Uniform Title
    231 a-w
    232 a-w
    431 a-w
    432 a-w
    Related Title
    531 a-w
    532 a-w
    Name Title
    241 a-t
    242 a-t
    441 a-t
    442 a-t
    541 a-t
    542 a-t

    See UNIMARC Authority Search Index Mapping.

    UNIMARC: Field 610 is Not Controlled by Authority

    June 2020 Resource Management SF: 00527854 00645001 URM-127221
    For UNIMARC bibliographic records, field 610 (Uncontrolled subject terms) is no longer controlled by authority. This means that F3 search on the field 71X no longer shows the results from field 610, and there is no linking and preferred term correction for field 610.

    To support field 610, a new source code option Uncontrolled subject terms was added to the bib headings list in the Metadata Editor available for browsing bibliographic headings. When this source code is selected, the "Vocabulary" option is not displayed because it is not controlled by authority.

    Browsing bib headings on subjects with an empty source code only retrieves results from the first five source codes (as done before this change). Headings from field 610 will not be retrieved. To see results from field 610, the "Uncontrolled subject terms" source code must be specifically selected.

    Uncontrolled subject name.jpg

    If your institution uses UNIMARC and would like to activate this behavior, please contact Ex Libris customer support.

    This feature will be available in August after the re-indexing job has completed.

    See Browsing Bibliographic Headings.

    Additional Localized Values in Originating System Table

    June 2020 Resource Management URM-124839
    The following values were added to the Import Profile Originating System code table (Configuration Menu > Resources > Record Import > Originating Systems for MD Records).
    Code Description
    RIALTO Rialto
    BRILL Brill Online Primary Sources
    EASTVIEW East View Information Services
    THIEME Thieme Verlag
    BLOOMSBURY Bloomsbury
    CRL Center for Research Libraries
    DE_GRUYTER De Gruyter
    HST Henry Stewart Talks
    INGRAM Ingram
    KYOBO Kyobo
    SYMPHONY Symphony
    ULS United Library Services

    See Configuring Originating Systems for Import Profiles.

    Advanced Search Options Expanded

    June 2020 Resource Management URM-113249
    NERS NERS Enhancement (ID #4057): Advanced search query options were expanded to include Not Contains Keywords, Is Empty and Is Not Empty. See the table below for the list of changes.
    Find Conditions Conditions Conditions
    Electronic Portfolio Electronic Collection    
     
    • Public Note (Electronic Collection) – Contains Keywords, Contains Phrase, Not Contains Keywords, Not Contains Phrase, Starts With, Not Equals, Equals, Is Not Empty and Is Empty
    • Internal Description (Electronic Collection) – Contains Keywords, Contains Phrase, Not Contains Keywords, Not Contains Phrase, Starts With, Not Equals, Equals, Is Not Empty and Is Empty
       
    Electronic Collection Electronic Collection    
     
    • Public Note (Electronic Collection) – Contains Keywords, Contains Phrase, Not Contains Keywords, Not Contains Phrase, Starts With, Not Equals, Equals, Is Not Empty and Is Empty
    • Internal Description (Electronic Collection) – Contains Keywords, Contains Phrase, Not Contains Keywords, Not Contains Phrase, Starts With, Not Equals, Equals, Is Not Empty and Is Empty
       
    This feature will be available in August after the re-indexing job has completed.
    Watch the Advanced Search Options Expanded video (1:34 minutes).

    General Publishing - Structured Coverage Information

    June 2020 Resource Management URM-116476
    Previously, Ex Libris provided the coverage and embargo information of electronic holdings in a textual human-readable format, for example: "Available from 1982 volume: 1 issue: 1. Most recent 4 year(s) not available", in multiple languages. Now, this information can be published in its raw format This enhancement is useful for integrating with 3rd-party systems that use the coverage and embargo information to calculate the availability of electronic titles.
    To support this development, new fields that allow for a more granular definition of the coverage and embargo information were added to the general publishing profile of electronic portfolios. The following fields can now be published (see the corresponding representation of these fields in the electronic resource editor below):
    • From Year
    • To Year
    • From Month
    • To Month
    • From Day
    • To Day
    • From Volume
    • To Volume
    • From Issue
    • To Issue
    • Embargo Operator
    • Embargo Number of Years
    • Embargo Number of Months

    electronic portfolio new coverage fields 1.jpg

    The new Coverage and Embargo Information fields

    The new portfolio coverage-related fields and sections were added to the Electronic Inventory Enrichment section of the Publishing Profile Details page.

    New fields in the Electronic Inventory Enrichment section.jpg

    New fields in the Electronic Inventory Enrichment section
    This is the list of the new fields in the Electronic Inventory Enrichment section.
    Publishing Profile Details Page - Wizard Step 1
    Field Description
    Portfolio Coverage Information
    Repeatable field

    Enter a field number into which to put the coverage information in the output record (one that is not used by the bibliographic record); this field is mandatory. For example, if you enter 950, the output will contain <datafield tag="950" ind1=" " ind2=" "> ... </datafield>, with the information you enter in this area in subfields of this field.

    Portfolio id subfield For each piece of coverage information that you want to be included in the output file, enter the subfield in which you want it to appear. See rows below for the coverage information you can add.
    From Year subfield

    The Coverage and Embargo information is exported according to the selection made in the "Which coverage statement will be applied?" option in the portfolio editor's Coverage tab:

    • Each value of every subfield publishes the value of its corresponding parameter from Date Information table and Embargo on the Portfolio Editor.
    • The published coverage information is simplified on the portfolio level in the following way:

    Rows that consist of date elements only (year/month/day) are consolidated into the minimum-possible representation of date range(s) that cover all the date ranges for this specific portfolio. This means that the exported date ranges completely cover the true availability of the portfolio.

    The simplification process does not occur for date-information rows that has Volume and/or Issue specified, they are published as-is.

    The embargo date range(s) are calculated and published separately in the Embargo section.

    Until Year subfield
    From Month subfield
    Until Month subfield
    From Day subfield
    Until Day subfield
    From Volume subfield
    Until Volume subfield
    From Issue subfield
    Until Issue subfield
    Portfolio Embargo Information
    Repeatable field

    Enter a field number into which to put the embargo information in the output record; this field is mandatory. For example, if you enter 950, the output will contain <datafield tag="950" ind1=" " ind2=" "> ... </datafield>, with the information you enter in this area in subfields of this field.

    Portfolio ID subfield For each piece of embargo information that you want to be included in the output file, enter the subfield in which you want it to appear.
    Operator subfield

    See above.

    In the Embargo section of the output file, the "Operator" field exports the below operators. Since '<' and '>" characters are special characters in XML, using them within the XML content might cause errors in the output. Thus, these characters are encoded in the XML output as follows:

    Published Sign Meaning Meaning within the output
    &lt; <= Less than or equals to Most recent X year(s) available
    &gt; >= Greater than or equals to Most recent X year(s) not available
    &lt;= < Less than Most recent X-1 year(s) available
    &gt;= > Greater than Most recent X+1 year(s) not available
    Number of Years subfield The number of years/months included/excluded (based on the selected operator) from the portfolio coverage.
    Number of Months subfield

    See Publishing and Inventory Enrichment (General Publishing)

    Portfolios Display Service and Collection Data

    June 2020 Resource Management SF: 00570136 00577949 00821547 00821550 00408242 00115067 NERS NERS Enhancement (ID #5054) idea exchange Idea Exchange
    Alma now displays certain electronic service and collections information as read-only information in the Portfolio Editor. This is useful for users viewing the electronic portfolio, since this service and collections information may be relevant to their needs. Now, these users do not have to open the Service Editor or Collection Editor to access this information, but can see all the relevant information in one place.
    These parameters are displayed only for portfolios included in electronic collections; they are not displayed for stand-alone portfolios.

    The following service and collection parameters are now displayed in the Portfolio Editor:

    Portfolio tab Service parameters Collection parameters
    General tab
    • Base Status,
    • Activate From,
    • Activate To,
    • Site Down,
    • Site Down Reason,
    • Site Down Date
    • Selective Indication,
    • Interface Public Name
    Linking tab
    • Crossref Supported,
    • Crossref Enabled,
    • Proxy Enabled,
    • Proxy Selected,
    • Link Resolver section (including API code, Link Resolver Plugin Status, Link Resolver Plulgin Active),
    • Linking List section
     
    Notes tab
    • Authentication Note,
    • Public Note
    • Authentication Note,
    • Public Note

    collection field in portfolio.jpg

    Service- and Collection-related parameters in the Portfolio Editor

    See Managing Electronic Resources.

    Change Physical Items job - Ability to Change all Temporary fields for Physical Items

    June 2020 Resource Management URM-124556SF: 00121556 00486264 00471848 00017848 00604866 00043563 00098197 00567256 00060934 00148673 00101955 00174362 00070445 00520048 00052510 00116547 00070339 00166961 00517178
    The Change Physical Items job has been enhanced with the following:
    • Additional parameters were added, which allow setting and clearing all parameters related to temporary location changes. The parameters correspond to the options available on the Physical Item Editor tabs that can be accessed by doing a repository search for physical items and selecting Edit for one of the items in the search results list. For the full list of fields, see Updating Item-Level Information.
    • Configurable "Statistics Notes 1/2/3" parameters were added. See Configuring Statistics Notes for information about configuring fixed dropdown lists of options for statistics notes.
    • The parameters that pertain to permanent and temporary locations were divided to separate sections to enable better visibility and clearer workflows.
    • The page layout visually reflects the dependencies between the different parameters.
    • Sequence-related parameters are supported.
    change physical item job.jpg
    The enhanced Change Physical Items job

    See Change Physical Items job.

    Manage Selected Physical Items

    June 2020 Resource Management SF: 00121556 00486264 00471848 00017848 00604866 00043563 00098197 00567256 00060934 00148673 00101955 00174362 00070445 00520048 00052510 00116547 00070339 00166961 00517178 URM-123344, 125383
    On the Physical Items list, the Manage Selected dropdown was added that holds some of the actions that can be performed on multiple physical items in bulk.
    correct manage selected .jpg

    These actions can only be performed if you possess the required permissions.

    See Working with the List of Items.

    Display Institution Name in New Alma Viewer and Deposit Interface

    June 2020 Digital Resource Management URM-122452
    You can now configure your institution name to appear in the New Alma Viewer and Deposit interface. To configure this feature, set the value of the repDeliveryViewer.Alma parameter (Configuration > Fulfillment > Digital Fulfillment > Alma Viewer Labels) to the institution name. Note that for new institutions that have not configured an institution name for the original Alma Viewer, the word Alma appears by default.

    Display Terms of Use and Copyrights in Alma Viewer

    June 2020 Digital Resource Management idea exchange Idea ExchangeURM-120582

    You can now configure the Alma viewer to display Terms of Use and Copyright information in the Descriptive Information pane in the Alma Viewer. This information is taken from MARC fields 540 $3 $a $f $u and 542 $3 $f $u respectively. To support this new feature, two new rows were added to the Delivery Profiles Metadata table for MARC records. Enable these rows to display the Terms of Use and Copyright information.

    delivery_profiles_metadata.png

    Delivery Profiles Metadata

    Customize the New Alma Viewer and Deposit Interface with Primo Studio

    June 2020 Digital Resource Management URM-121668
    You can now customize the New Alma Viewer and the Deposit Interface using Primo Studio.
    You must have a deposit profile configured to customize the deposit interface with Primo Studio.
    • For Primo VE users:
      To customize the New Alma Viewer using Primo Studio:
      1. Select the new Customization tab from the Alma Viewer configuration page (Configuration > Fulfillment > Discovery Interface Display Logic > Viewer Services > Alma Viewer).
      2. Select a Primo View, a Representation ID, and select Generate Link.

        customization_tab.png

        Customization Tab
      3. Select the Open Primo Studio link.

        Primo Studio opens, allowing you to customize the Alma Viewer. Create a customization package and upload it to Alma.

        For more information on using Primo Studio, see Using Primo Studio.

      To customize the Deposit Interface using Primo Studio:
      1. Select the new Patron Deposit Customization link (Configuration > Resources > Deposit).
      2. Select a Primo view and select Generate Link. The Open Primo Studio link appears.

        customize_deposit_UI.png

        Patron Deposit Customization
      3. Select the Open Primo Studio link.

        Primo Studio opens, allowing you to customize the Deposit Interface. Create a customization package and upload it to Alma.

        For more information on using Primo Studio, see Using Primo Studio.

    • For standard Primo users:
      To customize the Deposit Interface and the New Alma Viewer using Primo Studio:

      From the Primo Studio section on the Alma Viewer and Deposit Customization page (Configuration > General > Alma Viewer and Deposit Customization):

      customize_deposit_and_viewer.png

      Primo Studio
      • To configure the deposit interface using Primo Studio, click Customize Deposit.
      • To configure the Alma viewer using Primo Studio, enter a representation ID, and select Customize Alma Viewer.

        Primo Studio opens, allowing you to customize the Deposit Interface. Create a customization package and upload it to Alma from the Upload Package section.

        For more information on using Primo Studio, see Using Primo Studio.

    Enhancements to Forms

    June 2020 Digital Resource Management URM-121777
    Several enhancements have been added to the Alma Forms feature:
    • You can now configure vocabularies that allow you to define the possible values for the form fields from Configuration > Resources > Controlled Vocabulary Registry - Forms. For more information, see Controlled Vocabulary Registry - Forms.
    • The following field types can now be added to forms (Configuration > Resources > Metadata Configuration > MARC21 Bibliographic or Qualified Dublin Core > Forms tab) when selecting Add fields. This replaces the Type field within the form:
      • Combo box Multi-select – a drop-down list of checkboxes. Multiple checkboxes can be selected.
      • Combo box single-select – a drop-down list of checkboxes. Only one can be selected.
      • Radio Button – multiple radio buttons are displayed. Only one can be selected.
      • Text Box – replaces the text (single line) field type.

      add_form_fields.png

      Form Field Types
    • The following fields were added to the field types:
      • Tooltip – a tooltip message to display
      • Language – the languages the institution accepts as a thesis or dissertation language
      • Vocabulary – the vocabulary of possible values for the combo box and radio button fields

      add_form_fields_for_RNs.png

      Form Fields
      For more information, see Working with Forms.
    • The following enhancements were added to the Configuring Deposit Profiles page (Resources > Deposits > Manage Deposit Profiles):
      • You can now select multiple access rights policies. Depositors can select which policy they want to apply to the deposit.
      • The Public Instructions field is now translatable.
      • The User Group field was redesigned as a drop-down list and allows for multiple selections.
      • The following fields were added:
        • Maximum number of files – the maximum number of files that can be deposited per deposit
        • Maximum file size (each, in MB) – the maximum size of the files allowed in the deposit
        • Allowed extensions – the extensions of the files allowed in the deposit

      configuring_profile_details_rn.png

      Configuring Deposit Profiles

    Select Order of Holdings, Availability, and Requests in Get It

    June 2020 Fulfillment idea exchange Idea Exchange URM-106114
    Previously, when showing a holdings' availability in Get It, the sequence of the text was hard-coded (x copy, y available, z requests).
    clipboard_e40ce0b94600e950427731a2773a149ba.png
    Using the new label added to the 'Labels' configuration screen: c.search.htmlCreator.unifiedDisplay, institutions can:
    • Resequence the existing labels, for example “x available, x requests, x copies”.
    • Add a descriptive text before, after or between each one of the labels, for example “x available, resources, x requests, x copies”.
    • Remove labels which are not needed, for example "x available, x copies”

    The new label is formatted as: {{copies_labels}}, {{available_labels}}, {{requests_labels}}. All content within the curly brackets cannot be changed or translated because they represent other existing labels. Text can be added before, after or between each pair of curly brackets. If needed, there is also the option to remove one of the labels so it will not be displayed in the Get It.

    The following labels are used to populate the information within the 3 curly brackets of the new label:

    • Brackets within the new label: {{copies_labels}} will be populated with information from these existing labels:
      • c.search.htmlCreator.copy for a single copy
      • c.search.htmlCreator.copies if there are multiple copies
    • Brackets within the new label: {{available_labels}} will be populated with information from this existing labels: c.search.htmlCreator.available. If you have configured Time to reshelve, the following labels may replace it:
      • c.uresolver.getit2.item_list.status.SOME_HOLDING_ITEMS_AWAITING_RESHELVING,
      • c.uresolver.getit2.item_list.status.ALL_HOLDING_ITEMS_AWAITING_RESHELVING.
    • Brackets within the new label: {{requests_labels}} will be populated with information from these existing labels:
      • c.search.htmlCreator.request if there is a single request
      • c.search.htmlCreator.requests If there are multiple requests
      • c.search.htmlCreator.noRequests if there are no requests
    • A new label was added for zero requests.
    • The numbers were added to the existing labels. For instance, now instead of copies, the default label is {0} copies.

    Hold Request Loan Indicator

    June 2020 Fulfillment URM-113533
    If you create a hold request, the Loan Audit Trail now includes a Hold Loan field to indicate if the loan originated from a hold request. This will be reportable in Analytics in a future release.

    Request Notes in Pick from Shelf List

    June 2020 Fulfillment idea exchange Idea Exchange URM-102332
    On the Pick from Shelf list, if one or more request notes exist, they are now displayed aggregated together with a "|" (pipe symbol) in between each request. Only notes for active requests that are being picked by the current circulation desk are displayed. The notes of the active request are presented in the Pick Up Requested Resources page in no specific order. If you click the link for the request queue, all requests are displayed along with a new column that displays the request notes.
    Watch the Request Notes in Pick from Shelf List video (0:48 minutes).

    RFID Support for Scanning Multiple Items

    June 2020 Fulfillment Early Adopter Phase idea exchange Idea Exchange URM-27872
    Institutions that have RFID readers at their circulation desks now have the option to perform a single scan for multiple items positioned on the RFID reader. The support for scanning multiple items is available in all the relevant pages that allow RFID scans. The multi-item scan is being enhanced for RFID readers connecting directly to Alma, and is not related to integration of self-check machines with Alma via the SIP2 protocol. This functionality is now in the testing phase and is dependent on the RFID hardware and vendor. Due to the COVID-19 pandemic, the ability to scan multiple items may be helpful for institutions to minimize staff’s contact with physical items, if your institution would like to become an early tester and activate the multi-item scan functionality in your sandbox and/or production environments, please contact Ex Libris support.

    Searching for Resource Sharing Requests from Persistent Search Bar

    June 2020 Fulfillment Resource Sharing URM-121377
    You can now search for resource sharing requests from the persistent search bar on the top of the application. All existing search options also remain available. The default search option for the resource sharing requests is External Request ID.
    Borrowing Requests Persistent Search.png

    Limit User Manager Role by Account Type

    June 2020 Administration and Infrastructure NERS NERS Enhancement (ID #6348) SF: 00758495 URM-121009
    You can now attach an attribute to the User Manager role, as well as other roles that can manage user information, such as Circulation Desk operators, to limit the user from editing users that have specific roles or user groups.
    When adding one of the below mentioned roles to a user, a new checkbox is available on the User Roles Details page. Can't edit restricted users enables you to define that the user with this role cannot edit other users records that have been defined as 'restricted'. If all of this user's relevant roles have the Can't edit restricted users selected, the user will have edit/delete access only for users that are not restricted. The user will still be able to view the limited access user records, but not make any changes (including to contact info, etc.). If one of the users' roles is not limited, the users are is not limited in their edit/delete access.

    By default, this value is not selected.

    This is applicable for the following roles:
    • General System Administrator
    • User Administrator
    • User Manager
    • Circulation Desk Manager
    • Circulation Desk Operator
    • Circulation Desk Operator - Limited
    • Repository Manager

    User record types that are considered restricted, and therefore cannot be updated by users that have the Can't edit restricted users, can be defined by their user group or by their roles. In other words, it is possible to define that user records that have a specific user group will be considered restricted, and/or to define that user records that have a defined role will be considered restricted. Any user record that is assigned either one of the restricted user groups, or one of the restricted roles will not be updateable by users that have the Can't edit restricted users attribute activated on their above mentioned roles.

    A new configuration page, Users Restricted for Editing, is available on the User Management configuration menu to define which user roles and groups will be restricted for editing by those users that have the Can't edit restricted users check box selected.

    DARA Recommendation to Configure New Alma Viewer

    June 2020 DARA URM-119920
    DARA identifies that you have not yet configured the new Alma Viewer and recommends that you do so.
    new_viewer_recommendation.png
    Configure New Alma Viewer

    For more information, see DARA – Data Analysis Recommendation Assistant.

    June 2020 Administration and Infrastructure URM-115013
    This change continues the change made in the May release, in which the following user roles were added:
    • The Printout Queue Operator - can access the Printouts Queue, but can see only the letters they have printed (which means they do not have access to the Printed By filter).
    • The Printout Queue Manager - can access the Printouts Queue, and can see all the letters there. Has access to the Printed By filter.

    Up till the current release, all system users could access the Printouts Queue link (Admin > Printing). Starting from the current release, only these two user roles will be granted access to the Printouts Queue link. To support this, the below changes take place:

    • The Printout Queue Operator role is automatically added to all the users who have printed to the Printout Queue within the previous 30 days.
    • The Printout Queue link becomes hidden for all users without one of the above roles.

    To manage this change, Ex Libris recommends that you do the following to enable access to the Printout Queue to all users who needs this access:

    • To grant access to the Printouts Queue link only to specific users, make sure to add one of the above roles to all users that need to receive access to the link.
    • To grant access to the link to new users, add the new Printout Queue Operator role to a Role Profile. This will make the link available for all users which are created with the relevant job category or user group, and a corresponding role assignment rule for the Role Profile in place. For details about Role Profiles, see Configuring Role Profiles.

    See Printouts Queue.

    PO Lines in the Recent Entities List

    June 2020 Administration and Infrastructure URM-123157
    PO lines now appear in the Recent Entities list.

    The Recent Entities list that was introduced in the March release now lists the Purchase Order lines which were added, updated, and deleted within the last 7 days by the user. The addition of the Purchase Order line to Recent Entities is a helpful way to find the POL the user recently accessed, even if they do not remember its identifying number.

    Below is a detailed list of cases in which PO Lines appear in the Recent Entities list:

    Entity Type: Included in the Recent Entities List when: Not included in the Recent Entities List when:
    PO Lines
    • PO Line was created from the Prerequisites screen
    • PO Line was created from a Purchase Request
    • PL Line was created from the Metadata Editor
    • PO Line was edited from any of the task list screens
    • PO Line was edited from the Manage EDI tasks
    • PO Line was updated from the Receiving Workbench screen
    • PO Line was deleted from any screen
    • PO Line was created by the EOD job
    • PO Line was created by API
    • PO Line was deleted as the result of PO deletion
    • PO Line was updated by any Alma job or Process Automation
    • PO Line was updated via invoice
    • PO Line was updated via the Activation task list

    The following information is provided in My Recent Entities pane for each PO Line:

    Entity Type: Information Displayed Example

    PO Line

     

    • PO Line description
    • PO Type
    • PO Line number
    POline in recent entities page.PNG

    Outbound and Inbound Files Encryption

    June 2020 Administration and Infrastructure, 112986
    Now it is possible to encrypt files uploaded to Alma and have Alma encrypt files it created. The encryption is based on the OpenPGP standard and uses Private/Public Key encryption provided by the institution to encrypt the files. The encrypted files have the .gpg file prefix.

    The current development complements file security in Alma, which supports FTP and SFTP protocols for file encryption during transfer. This development allows encrypting files before being placed on the FTP server. This development is useful for institutions that would like to add another layer of security to sensitive data, such as patron information.

    See Developer Network

    Primo Publishing (Single & Network) - Change in Authority Synchronization Frequency

    June 2020 Administration and InfrastructureURM-124192
    Ex libris has conducted an analysis of the Primo Publishing process with the intention of increasing its overall throughput, stability and performance, and has decided to optimize the Authority synchronization and change it to run once every 24 hours. The Primo Publishing frequency will remain the same. For example, if your Primo Publishing process runs every 6 hours, then the authority synchronization will happen at the fourth run.

    Ability to create/update the vendor details on a purchase order line using APIs

    May 2020 Acquisitions URM-121529
    An option to create and/or update the fields within the Vendor Details section have been added to the Update PO Line and Create PO Line APIs.
    See Rest PO Line in the Developer Network.

    Monthly Run Option for SUSHI Harvesting Job

    May 2020 Acquisitions  idea exchange Idea ExchangeURM-121327
    The SUSHI Harvesting job can now be run on a monthly schedule, in addition to the weekly scheduling option. The monthly schedule offers four predefined optional dates across the month. This will save institutions from trying to harvest usage data each week, which can result in redundant failures in case reports are not ready yet.

    Ability to Activate Portfolio from CZ using Create Order API

    May 2020 Acquisitionsidea exchange Idea Exchange
    The functionality, which was originally introduced in the January release, is designed for orders originating from OASIS. It is now available for 11 providers (see complete list).
    This functionality eliminates the need to load full MARC records via an Import process, due to the fact that the ordered resources are activated from the Community Zone (which includes full bibliographic records for the ordered electronic resource).
    Pre-requirement: The relevant Community Zone collection must be active in your Institution Zone. If the collection is not available in the Institution Zone, a standalone electronic resource (portfolio) is created and the order is associated to it, requiring the use of a full MARC update via an Update Inventory import profile for complete descriptive information and access information.
    Example:
    An order is sent from OASIS for an electronic resource "1,000 Comic Books You Must Read" from ProQuest EBook Central. Alma associates the OASIS order with the relevant portfolio by activating the relevant portfolio from the collection "Ebook Central Perpetual, DDA and Subscription Titles", including complete descriptive information and access information.

    See Real-Time Ordering.

    New Metadata Editor

    May 2020 Resource Management URM-91952
    The new Metadata Editor is now available for your review in the sandbox. See the Metadata Editor and Rollout Plan sections on the Usability Improvements page for more information.
    Watch the New Alma Metadata Editor video (4:40 minutes). To view the video on an alternate video host, click here.

    View Community Zone Portfolio Linking Information

    May 2020 Resource Management NERS NERS Enhancement (ID #5790) idea exchange Idea Exchange URM-124230
    In order to assist with the decision of activating Community Zone portfolios, you can now view portfolio linking information from search results in the Community Zone tab. Previously in order to view the linking information of a Community Zone portfolio, you had to activate the portfolio. See Linking Information on the Searching in Alma page for more information.

    UTF-8 Special Character Handling

    May 2020 Resource Management

    Alma offers a new method of handling UTF-8 special characters (with diacritics). UTF-8 special characters may be represented in both the composed or decomposed version of the character in bibliographic or authority records. Now, you have the option to configure your system with normalize on save always to save the composed version of special characters. This may be especially useful to implement to avoid the use case where multiple records are changed due to their conversion to composed representation. Such records are marked for preferred-term correction (PTC) and cause heading updates (the only difference is the composed/decomposed nature of a special character).

    For more information, see UTF-8 Special Character Handling in Alma.docx

    Statistical Notes

    May 2020 Resource Management  idea exchange Idea ExchangeURM-116240
    In advanced search for Physical titles and Physical items, you can now search for statistical notes. See Searching for Statistical Notes for more information.
    Full inventory indexing needs to be run to enable this functionality.

    MARC 21 and UNIMARC Updates

    May 2020 Resource Management URM-116456
    The following MARC 21 holdings and authority configuration profile updates have been completed:
    • MARC 21 Holdings – Update No. 28 (May 2019)
    • MARC 21 Authority – Update No. 26 (April 2018) and Update No. 28 (May 2019)
    The following UNIMARC bibliographic configuration profile updates have been completed:
    • 135 $a/1 Special Material Designation
      • New codes: d – computer disc, type unspecified, e – computer disc cartridge, type unspecified, k – computer card, s – standalone device
      • Renamed: j – magnetic disk, r – online
    • New field 214
    • New subfield 2 for the following fields: 200, 225, 510, 532, 541
    • The following new subfields for the 602 field: c, d, o
    • The following new subfield for the 604 field: 2
    • The following new subfield for the 623 field: 3
    The following UNIMARC authority configuration profile updates have been completed:
    • 101
      • Repeatable
      • New indicator 2 – Source of code
        • # – ISO 639–2 language code
        • 7 – Source specified in subfield 2
      • New subfield 2 – System Code (NR)
    • The following new subfields for the 123 field: q, r, s, t, 2
    • The 106 field renamed to 106 CODED DATA FIELD: ENTITY NAME AS SUBJECT ACCESS POINT
    • The following new fields: 180, 370, 822
    • The following new X23 fields: 223, 423, 523, 723

    API Usage Subject Area

    May 2020 Analytics URM-120254
    The new API Usage subject area is now available. You can use the fields of this subject area to create reports that display usage of Alma Analytics by API. For more information, see API Usage.

    Add Roles from Profiles For Widgets and Dashboards

    May 2020 Analytics URM-94013
    When creating Analytics Widgets and dashboards (Configuration Menu > Analytics > Analytics Objects List or Analytics > Analytics Objects > Analytics Objects List) you can now select a profile of roles to assign to the widget or dashboard.

    analytics_configuration_ux.png

    Add from Profiles
    For more information on role profiles, see Configuring Role Profiles.

    Improved Performance For Alma Analytics

    May 2020 Analytics
    Ex Libris is currently implementing performance upgrades to the Alma Analytics infrastructure. These upgrades will greatly improve performance when running analytics reports. These upgrades will be rolled out gradually. For the May release, the upgrades will be made available to NA02.

    Normalization of Generic XML to Alma XML

    May 2020 Digital Resource Management URM-120462 URM-117924

    Alma now supports XSL transformer rules to convert generic XML files in a DCMI schema to an XML format recognized by Alma. This enables a RESTful API to load the file into Alma. For example, you can load an ETD Admin file with a SWORD API into Alma in ETD-DCAP format.

    Recent Entities for Digital Resources

    May 2020 Digital Resource Management URM-120637
    Actions performed for the following digital resources are now indicated on the Recent Entities pane:
    • Digital Collections
    • Digital Representations
    • Digital Files
    • Digital Deposits

    For more information, see Recent Entities List.

    Material Type Mapping

    May 2020 Digital Resource Management URM-120462 URM-117783

    You can now map Alma material types to DCMI types that you configure. The DCMI types that you configure are available in the Material Type drop-down lists wherever they exist in Alma. Additionally, when the DCMI types that you configure are the value in the dc:type or dcterms:type fields in a DC bibliographic record, Alma will display the record with the mapped Alma material type. To support this feature, a new mapping table is available at Configuration > Resources > Cataloging > DCMI Material Type Mapping:

    material_type_mapping.png

    Material Type Mapping
    May 2020 Digital Resource Managementidea exchange Idea Exchange URM-114001

    Related digital records are now indicated when clicking View It.

    related_records.png

    Related Records

    To support this feature, the new Disable Related Record Services for Digital configuration option is now available (Configuration > Fulfillment > Discovery Interface Display Logic > Related Records).

    disable_related_records.png

    Disable Related Record Services for Digital

    Clear this option to allow the related records indication for digital records to be displayed

    Multiple Viewers Available for Staff Delivery

    May 2020 Digital Resource Management URM-88411

    Library staff can now select which viewer is used to display a digital file. To support this feature, a new Delivery section was added to the Digital Representation Resource Editor that displays the available viewers. Unavailable viewers are marked as Disabled.

    delivery.png

    Delivery Section
    The Delivery URL is no longer displayed.

    Option for Locate of Electronic Resources

    May 2020 Fulfillment Resource Sharing URM-109656
    You can now set a policy to not send a borrowing request to a lender that has only an electronic version of the requested resource, if the request has been requested for a physical format. When the new parameter, rs_ignore_electronic_for_physical_request, is set to true, the borrowing locate process for physical requests ignores lenders’ electronic inventory, as shown in the table below. Lenders which have the requested resource only in electronic form are then removed from the rota by the locate process.

    If the Allow other formats check box is selected, when creating a new borrowing request, electronic resources are allowed, regardless of the value in the parameter.

    The below table describes how the locate process runs with regard to the possible combinations of the Ignore Electronic and Digital Resources option in the locate profile and the new rs_ignore_electronic_for_physical_request parameter

        Allow other formats is not selected Allow other formats is selected
    rs_ignore_electronic_for_physical_request = false Ignore Electronic and Digital Resources is not selected in Locate Profile Details Allow electronic regardless of format Allow electronic regardless of format
    locate profile ignore electronic is selected in LocateProfile Details ignore electronic regardless of format ignore electronic regardless of format
    rs_ignore_electronic_for_physical_request = true locate profile ignore electronic is not selected in Locate Profile Details ignore electronic if physical / physical non-returnable Allow electronic regardless of format
    locate profile ignore electronic is selected in Locate Profile Details ignore electronic regardless of format ignore electronic regardless of format
    May 2020 Fulfillment NERS NERS Enhancement (ID #5340) idea exchange Idea ExchangeURM-90487
    New configuration options are available for the Get It display, these options provide institutions the control of whether or not to present related holdings for patrons using Primo/PrimoVE. A more granular option provides the institutions with the option to present related records only for serials or only for monograph titles.

    May 2020 Administration and Infrastructure URM-115013

    Now you can grant access to the Printouts Queue link (Admin > Printing) only to specific users. To support this, two new user roles were added:

    • The Printout Queue Operator - can access the Printouts Queue, but can see only the letters they have printed (which means they do not have access to the Printed By filter).
    • The Printout Queue Manager - can access the Printouts Queue, and can see all the letters there. Have access to the Printed By filter.

    The change in Alma will be implemented gradually, over the May and June releases, as follows:

    • In May release: No change in behavior. All users can still access the Printouts Queue link.
    • In June release:
      • The Printout Queue link becomes hidden for all users without one of the above roles.
      • The Printout Queue Operator role is automatically added to all the users who have printed to the Printout Queue within the previous 30 days.

    To manage this change, Ex Libris recommends that you do the following within the duration of the May release:

    • If grant access to the Printouts Queue link to specific users, make sure to add one of the above roles to all users that need to receive access to the link.
    • To grant access to the link to new users, add the new Printout Queue Operator role to a Role Profile. This will make the link available for all users created with the relevant job category or user group, and a corresponding role-assignment rule for the Role Profile in place. For details about Role Profiles, see Configuring Role Profiles.

    In addition, in the May release the retention period for items in the Printout Queue will be increased from 7 days to 30 days, after which the Alma cleaning job will clean the items. There is currently no way for customers to control the retention period.

    See Managing User Roles.

    Keyboard Shortcuts Enhancements

    May 2020 Administration and Infrastructure URM-85963

    Now you can view the full list on the Shortcut Customization page (User menu > Shortcut Customization).

    You can also disable global Alma keyboard shortcuts. You may want to do that in cases when your language requires usage of the same keyboard keys for typing accents or diacritics. Note that you can disable the Alma shortcuts, but cannot define other Alma shortcuts for the same action.

    See Global Alma Hot Keys.

    Sorting Tables Alphabetically in All Languages

    May 2020 Administration and InfrastructureURM-30968

    Continuing the enhancements introduced in March 2020, now you can sort additional tables alphabetically in Alma, regardless of the language of the data in the table. The data is sorted according to the alphabet of the selected language.

    This was implemented in the following tables within Alma:

    • Bulk Change Due Dates table – Material Type column
    • Add Non-Repository Citation table - Material Type column
    • Edit Reading List Citation - Material Type column
    • Resource Sharing Borrowing Request table - Languages column
    • Manage Course Information table - Academic Department column

    New SAML Certificate

    May 2020 Administration and Infrastructure URM-120835

    The current DigiCert SAML Certificate will expire in January 2021. 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.

    Note: No immediate action is needed. Replacing the certificate can be done at any time till its expiry on January 1, 2021.

    DARA Recommendations for My Electronic Resources by Provider

    May 2020 DARA URM-116894

    The My Electronic Resources by Provider feature in Alma allows you to view your subscriptions with providers and their availability status in Alma and activate any resources that you access but have not activated. DARA can now determine if the feature is relevant for your institution, but is not in use, and recommend that you use it.

    my_electronic_resources_by_provider.png
    My Electronic Resources by Provider

    For more information, see DARA – Data Analysis Recommendation Assistant.

    For more information on the My Electronic Resources by Provider feature in Alma, see My Electronic Resources by Provider.

    Viewing Your Recent Documents

    March 2020 Administration and Infrastructure
    The Recent Entities, part of My Activity Center, is a system-level interface that lists all the entities you have added, updated, and deleted within the last 7 days. You can scroll through the list and select an entity to resume your work, or you can view the entity in view-only mode. The Recent Entities list is a helpful way to find the records you have recently accessed, even if you do not remember their names. It also allows you to easily view your recent changes to your records. At any moment you can open and close the Recent Entities list, and then resume your ongoing work without interrupting its context.

    recent_entries_pane_highlighted.png

    The Recent Entities pane

    From the Recent Entities pane you can:

    • Open the entity in a view-only mode or in edit mode.
    • Search for a certain entity in the list.
    • Narrow down the list to a specific type of repository entity, such as physical items, or to entities accessed on a specific day.
    • Dismiss entities from the list.
    Watch the Viewing Your Recent Documents video (1:06 minutes).

    See Recent Entities List.

    Preferred Material Type in Purchase Requests

    March 2020 Acquisitions NERS NERS Enhancement (ID #5685) idea exchange Idea Exchange URM-111775
    You can now select a material type for purchase requests in Alma. The field previously called Requested Format has been renamed to Material Type and moved to the Resource Information section. In addition to the Physical and Electronic options that appeared previously, a new option is available, Default. When selected, the Default option determines the Material Type value for the PO line based on the customer parameter, purchase_request_preferred_material_type_default. When the parameter is P (for physical), the material type is determined by the default value in the Physical Material Type Descriptions table. When the parameter is E (for electronic), the material type is taken from an internal table of electronic types, and is Book. The table of electronic material types is internal and cannot be modified. If you choose an option other than Default, a new field, Choose Type, allows you to specify the exact material type needed. This selection options for the Choose Type field are dependent on the selection in the Material Type field, so that the list will include only Electronic or Physical material types, accordingly.
    The accompanying modifications for the Primo Purchase Request Form will be added in an upcoming release.

    SUSHI Performance Improvements

    March 2020 Acquisitions idea exchange Idea Exchange URM-103950
    The SUSHI harvest process now contains new performance enhancements. Additionally, the Missing Data tab has been renamed to the Monthly Usage Data tab. The errors on this tab are now further refined to help you troubleshoot connection issues. The yellow icon (Vendor Monthly Usage Data Yellow Icon.png) indicates that the connection to the vendor was successful, but the vendor did not send any data. While the red icon (Vendor Monthly Usage Data Red Icon.png) indicates that the the vendor connection attempt was unsuccessful. The green icon (Vendor Monthly Usage Data Green Icon.png) indicates, as previously, that the usage report file was successfully uploaded.
    March 2020 Resource Management NERS NERS Enhancement (ID #6201) URM-111465
    When an OpenURL does not contain any identifiers, the link resolver matches a bibliographic record based on the OpenURL title. At times the match is inaccurate and can result in Get It services for the wrong title. You can now configure Alma to limit the link resolver to display Get It services for titles that were matched only based on identifiers. See Using Standard Identifiers for more information.

    Import Local Extensions to Community Zone Records

    March 2020 Resource Management SF: 00475068 00660007 00666609 00686792 00740123 00173800 00223460 00108985 00134538 URM-121001
    It is now possible to add local extensions via the import process. This is a continuation of functionality that was released in February that enables the addition of local extensions to Community Zone records. This capability is enabled through new configuration options in the Repository, Update Inventory, and New Order import profiles under Match Actions. See Community Zone linked records handling and Support for local extensions for bibliographic records linked to the Alma CZ for more information.
    March 2020 Resource Management SF: 00694838 URM-122909
    Similar to UNIMARC 461, Alma now supports UNIMARC 463 for related records. See display_specific_related_items and Using the UNIMARC Linking Fields for Related Records for more information.

    Bibliographic MMS ID Appears in Additional Search Results and Various Resource Editors/Lists

    March 2020 Resource Management URM-83330
    The bibliographic MMS ID now appears in search results for physical items, electronic collections, and portfolios. In addition, the MMS ID appears in the header information for the following resource editors/lists: Physical Item Editor, List of Holdings, List of Items, Electronic Collection Editor, Electronic Portfolio Editor, and the Electronic Service Editor. See below for examples.
    MMS_ID_in_Physical_Items_Search_Results_02.png
    Physical Items Search Results
    MMS_ID_in_Electronic_Collection_Search_Results_02.png
    Electronic Collections Search Results
    MMS_ID_in_Electronic_Portfolio_Search_Results_02.png
    Electronic Portfolio Search Results
    MMS_ID_in_List_of_Holdings_Header_02.png
    List of Holdings
    MMS_ID_in_List_of_Items_Header_02.png
    List of Items
    MMS_ID_in_Physical_Item_Editor_Header_02.png
    Physical Item Editor
    MMS_ID_in_Electronic_Collection_Editor_Header_02.png
    Electronic Collection Editor
    MMS_ID_in_Electronic_Portfolio_Editor_Header_02.png
    Electronic Portfolio Editor
    MMS_ID_in_Electronic_Service_Editor_Header_02.png
    Electronic Service Editor

    New Alma Viewer

    March 2020 Digital Resource Management URM-103412 URM-120778 URM-120744 URM-117479 idea exchange Idea Exchange
    The newly designed Alma Viewer is now available to view digital resources. To enable the new viewer, select the Use New Viewer checkbox in the Alma Viewer configuration (Configuration > Fulfillment > Discovery Interface Display Logic > Viewer Services > Alma Viewer):
    hide_repeated_labels.png
    Use New Viewer and Hide Fulltext
    The new viewer has the following features:
    • (URM-120778) Full-Text Display – the new viewer can display a full text file along with the digital one. To hide the full text file, select the Hide fulltext check box in the Alma Viewer configuration (Configuration > Fulfillment > Discovery Interface Display Logic > Viewer Services > Alma Viewer).
      new_alma_viewer_full_text.png
      Full Text Display
    • (URM-117479) File-level Delivery – when selecting Share Displayed File for a file in the new viewer, the link opens to the selected file of the representation.
      new_alma_viewer_share_file.png
      Share Displayed File
      In addition, you can now deliver a file from the search results when searching for a digital file:
      deliver_digital_file.png
      Deliver Digital File
    • (URM-120744) Embedded Image in Primo VE – you can configure the new Alma Viewer to appear in Primo VE in a new Quick Access section. You are able to view the files of the representation, download the files, and open them in the full viewer.
      new_alma_viewer_quick_access.png
      Embedded Image in Primo VE
      You can configure display logic rules with the new Representation Quick Access service to control the Quick Access display.
    • (URM-120706) Hide Representations with Obtrusive Copyrights from Quick Access – You can create a display logic rule (Configuration > Fulfillment > Discovery Interface Display Logic > Display Logic Rules) that hides representations with obtrusive copyrights from the Quick Access section of Primo VE.
      An upcoming Alma release will support full customization of the new Alma viewer through Primo Studio.

    Access Rights Template URL for Remote Repositories

    March 2020 Digital Resource Management 00740460 URM-120706
    You can now configure a unique URL, separate from the delivery URL, to check access rights for remote repositories. To support this enhancement, the Access Rights Template field was added to the Delivery tab of the Remote Digital Repository Details page (Configuration > Resources > Record Import > Remote Digital Repositories). It replaces the Check Access Rights checkbox.
    remote_digital_repositories_delivery.png
    Access Rights Template

    Enhancements to In Parallel Digitization Workflow

    March 2020 Digital Resource Management URM-54474
    The following workflow was added for digitization requests that are configured to be processed in parallel to the digitization workflow (Configuration Menu > Fulfillment > Copyright Management > Digitization and Copyright Rules):
    • While the request is being processed, the representation is marked as inactive.
    • If the request is approved, the representation is marked as active.
    • If the request is rejected, the representation is deleted.

    Pop-up Messages in the Scan In Interface

    March 2020 Fulfillment NERS NERS Enhancement (ID #5299) idea exchange Idea Exchange URM-63083
    You can now configure how pop-up messages will display in the Scan In Interface. All messages can be configured to appear as a pop-up message, a feedback message, or to not appear at all. This is defined in the Scan In Messages Configuration table. Additionally, a yellow icon is added to the list of scanned items for patron request of types Booking Requests, Physical Requests, and Patron Digitization Requests to draw the scanning operator's attention that some items have a patron request associated with them.
    An additional informational message was added to the Scan Items page for lost items which were returned (Lost status removed). This message appears as a feedback message and can be configured similar to all other messages in the Scan In interface to appear as a pop-up message, a feedback message, or to not appear at all.
    Watch the Pop-up Messages in the Scan In Interface video (2:04 minutes).

    Keep Rapid ILL Requests Open

    March 2020 Fulfillment Resource Sharing URM-119781
    You can now define whether the Rapid ILL API will close a request that it operates on. When the Close request when exported check box is selected on the Resource Sharing Partner page, the request is closed when exported, as it has done previously, and the request status is updated to Exported to 3rd party. This is the default. When the check box is not selected, the request remains active after it is exported to Rapid, and the request status is updated to Sent to partner. This allows the request to remain viewable in Primo even though it has been exported. Requests that are left open must be manually closed.

    Claim Resource Sharing Request

    March 2020 Fulfillment Resource Sharing NERS NERS Enhancement (ID #5632) idea exchange Idea Exchange URM-77477
    For peer-to-peer resource sharing partners, you can now trigger an automatic claim letter when a configured period of time is reached. For example, when the Automatic Claim check box is selected and the Time to Claim (days) field is set to 7, if a request was sent 7 days ago and the request's status is still Sent, a claim letter is automatically triggered and the request status is set to Claimed.

    You can also configure an option to send a cancel message and continue through the rota.

    In case of an Email/SLNP partner, the letter is sent by email.

    For ISO requests, the notice is sent in a General Message. The text in the message can be configured.

    Publishing Profile Templates for Rapid ILL

    March 2020 Fulfillment Resource Sharing
    Setting up a new integration with Rapid ILL requires defining sets of lendable and non-lendable resources, as well as publishing profiles that expose that information to Rapid ILL via OAI.
    Defining the publishing profiles can now be made using Community Zone contributed profiles. When defining a new integration with Rapid ILL, you can now localize the Community Zone publishing profiles with the description EXL profile for Rapid ILL, and attach your defined sets to the relevant profiles. Using these templates speeds up the Rapid ILL integration process. For more information, see Alma Holdings Harvest for RapidILL.

    SAML User Updates

    March 2020 Administration and Infrastructure URM-121129
    You can now map SAML assertions to a user's fields according to an uploaded XSL file. The file is uploaded in the XSL configuration file field in the Self Registration section of the SAML integration profile.
    SAML Integration Profile Self Registration section.png
    Self Registration Section of the SAML Integration Profile
    In addition, the new Recreate user roles upon login check box in the Self Registration section allows you to force a role recalculation every time a user logs into Alma, based on the Roles Assignment Rules.
    See SAML Authentication on the Ex Libris Developer Network.

    DARA Enhancements

    March 2020 DARA URM-120417 URM-120417 URM-120610 URM-120610
    DARA was enhanced with the following changes:
    • The Mark as Done and Dismiss actions were replaced by the new Remove action
    • The Let's Do It button was replaced by a button with an action specific to the recommendation, such as Create SUSHI account and View Tile in Search.
    • The Show Me Why button was renamed to More Info. The recommendation description was shortened to make it more focused and the some of the information was moved to the More Info page.
    • A new job marks recommendations as implemented even when they are handled outside of the DARA workflow.
    dara_enhancements.png
    DARA Interface Enhancements

    Cancel All on Printing Queue

    March 2020 Administration and Infrastructure
    The Printout Queue page now has an option to cancel multiple printouts by selecting all the printouts you want to cancel and selecting Cancel Selected.

    See Printouts Queue.

    Export to Excel Enhancements on Job Reports

    March 2020 Administration and Infrastructure
    When exporting the events list of a job report, Alma now limits the number of rows to 10 thousands rows. Rows above this number are not exported. To export specific rows of the job report, use the controls on the report page.

    Sorting Tables Alphabetically in All Languages

    March 2020 Administration and Infrastructure
    Now you can sort tables alphabetically in Alma, regardless of the language of the data in the table. The data is sorted according to the alphabet of the selected language.
    This was implemented in the following tables within Alma:
    • User roles table – Type/Group columns
    • User list table – Name/Account Type/Record Type columns
    • Funds and Ledgers table – Type/Status columns
    • Import Profiles table - Profile Type column
    • Resolve Import Validation Errors table - Profile Type column
    • License table - Status column
    • Process List table - Business Entity column
    • Terms of Use and Policies table – Type column
    • Policy Management table – Policy Type column

    New Letter Type on Letter Configuration

    March 2020 Administration and Infrastructure
    A new letter "Change Rapido Request Terms Letter" was added to the list of configurable letters available in Alma. This letter is part of new resource-sharing abilities that are currently being developed. Ignore it for now.

    See Letter List.

    Absolute and Relative Paths in the S/FTP Definition

    March 2020 Administration and Infrastructure SF: 00736685
    Alma now supports the ability to indicate both an absolute and a relative path to the input directory in the S/FTP import protocol when creating import profiles to third-party systems.

    Real Time Ordering - Purchase Type License Upgrade as an Additional PO Line

    February 2020 Acquisitions URM-113805
    PO lines with a Purchase Type of License Upgrade created via New Order API will be associated to the relevant portfolio as an additional PO line. Previously, PO lines with a Purchase Type of License Upgrade were associated to the relevant portfolio as a main PO line. Now, the main PO line reflects the original PO line that initiated the order, while the PO line with a purchase type of License Upgrade complements the main PO line. 

    Suppress Access to PO Line Summary Information

    February 2020 Acquisitions URM-117290
    You can now disable access to review a PO line and view in-depth acquisitions information for users with the roles of Repository Manager, Physical Inventory Operator, or Electronic Inventory Operator. To do so, contact Ex Libris customer support.

    Improved Claiming Functionality for Continuous PO Lines

    February 2020 Acquisitions idea exchange Idea Exchange Previously, if an item's due date arrived and the item was not received, a claim letter was sent to the vendor. Now, if the next expected item also does not arrive, you can send an additional letter to the vendor which includes details for both items which did not arrive. This function is enabled when the claim_continuous_item_level parameter is set to true.

    Entering PO Line Number in Item Editor

    February 2020 Resource Management URM-95139
    When entering the PO line number in the Item Editor page, the number is now validated, even when typing the number instead of selecting it from the pick list.
    Watch the Entering PO Line Number in Item Editor video (0:48 minutes).

    Search Indexes for Specific OCLC Numbers

    February 2020 Resource Management URM-116893
    For simple and advanced titles searches (All titles, Physical titles, Electronic titles, and Digital titles), the following search indexes were added: OCLC Control Number (019), OCLC Control Number (035a), OCLC Control Number (035a+z), and OCLC Control Number (035z).
    OCLC_Search_Indexes_02.png
    Search Indexes for Specific OCLC Numbers
    With these new indexes, you can now locate specific OCLC numbers for improved search results and improved Excel exports.
    See OCLC Control Number for more information.

    Local Extensions for Community Zone Bibliographic Records

    February 2020 Resource Management SF: 00475068 00660007 00666609 00686792 00740123 00173800 00223460 00108985 00134538 URM-117332
    All institutions can now create and maintain local extensions to Community Zone bibliographic records in order to record their own proprietary information.
    With this capability, institutions can enter and maintain local information in the MARC 21 77X/78X, 09X, 59X, 69X, and 9XX fields. This can be done with the MD Editor for one record at a time, or for multiple records by running a job with a normalization process that updates local extension fields. Local extension data can be searched, exported, published (general publishing and to Primo) and handled using APIs (see Bibliographic Records and Inventory in the Developer Network). When linked bibliographic records are synchronized during Community Zone updates, the local extension content is not overridden.
    Please note that the March release will include the ability to load local extensions to Community Zone records via the import process.

    Suppress Bibliographic Record from External Search

    February 2020 Resource Management
    You can configure Alma to suppress bibliographic records from external searches. To perform this configuration, first configure the SRU or Z39.50 integration profiles to suppress searches of records with the Suppress from External Search tag:

    supress_from_external_search_integration_profile.png

    Suppress Records from External Searches - Integration Profile
    The Z39.50 and SRU protocols have different behavior when the Suppress records based on "Suppress from external search" option is selected:
    • Z39.50 – Records that are tagged as Suppress Records from Publish/Delivery are also suppressed from external searches even if they do not have the Suppress from External Search tag.
    • SRU – Only records tagged as Suppress from External Search are suppressed from external searches.

    You can tag records to be suppressed from external searches in the following areas:

    • From the Metadata Editor – select Suppress from External Searches (Tools > Management Tags) for a record.

      supress_from_external_search.png

      Suppress from External Searches - MD Editor
    • In the Set Management Tags tab of import profiles (all types except Update Inventory, Authority, Initial Authority) for records imported using the profile:

      supress_from_external_search_import_profile.png

      Suppress Records from External Searches - Import Profile
    • From the new Set Management Tags job:

      set_management_tags_job.png

      Set Management Tags

    In addition, it is possible to search for bibliographic records that are suppressed from external search:

    searching_for_records_supressed_from_external_search.png

    Searching for Records Suppressed from External Search
     
    Watch the Suppress Bibliographic Records from External Search video (4:53 minutes).

    Enhanced Configuration of Deposit Status Update Letter

    February 2020 Digital Resource Management SF: 00709117 URM-115572
    You can now customize the Deposit Status Update Letter using the same workflow as other Alma letters from Configuration > General > Letters > Letters Configuration. This allows you to configure additional elements of the letter, including a reason for the letter, a delivery URL, and a note.

    deposit_status_update_letter.png

    Deposit Status Update Letter

    For more information, see Configuring Alma Letters.

    Improved Performance For Alma Analytics

    February 2020 Analytics
    Ex Libris is currently implementing performance upgrades to the Alma Analytics infrastructure. These upgrades will greatly improve performance when running analytics reports. These upgrades will be rolled out gradually. For the February release, the upgrades will be made available to NA04.

    Last Patron Activity Date

    February 2020 Administration and Infrastructure NERS NERS Enhancement (ID #5631) idea exchange Idea Exchange URM-84167
    You can now view the last activity date for specific activities in the Last Patron Activity Date field of the User Details Page. The field is display only and will be available for analytics in an upcoming release. Due to privacy concerns, data will only be collected from activation of this new feature onward. If the option is disabled, all data collected in this field will be deleted for all users. When enabled, this field is updated when any of the following activities are executed:

    • Placing a request of any type - hold, booking, digitization, acquisition, resource sharing
    • Borrowing an item (all workflows, including self-check / API)
    • Returning an item (all workflows, including self-check / API)
    • Loan renewal (except automatic renewal), or renewal request (for resource sharing loans)
    • Update of user information from Primo

    The following activities do NOT update the Last Patron Activity Date field:

    • Using the Pay button on the Manage Patron Services page
    • Canceling a request in Alma or Primo
    • Patron Purchase Request sent from Primo - this will be added in a later release

    To enable this option, select yes in the new Record Last Patron Activity Date page (Configuration > User Management > General).

    Watch the Last Patron Activity Date video (1:36 minutes).

    See Managing Users and Configuring Last Patron Activity Date.

    Absolute and Relative Paths in the S/FTP Definition

    February 2020 Administration and Infrastructure SF: 00736685
    Alma now supports the ability to indicate both an absolute and a relative path to the input directory in the S/FTP import protocol when creating import profiles to third-party systems. See Managing Export Profiles.

    UPDATE: This feature has been temporarily disabled. It will be reinstated in the future. For now, indicate the output path to the FTP as a relative path: do not preface the path with the '/' sign.

    Quick Printing Option for Multiple Records

    February 2020 Fulfillment 

    When printing call slips for multiple items, you can select several items and print slips for all of them in one action with the Quick Print functionality. The quick print functionality aggregates all the slips into a single PDF (within a popup window) and allows the operator to either send these to a designated printer or save the created PDF to a file. See Pickup at Shelf.

    February 2020 DARA URM-107009
    Based on ISSN / ISBN matching, DARA now recommends local standalone portfolios for linking to the Community Zone. Linking to the Community Zone enables you to receive updates automatically without the need to update the portfolio manually.
    URM-107009_DARA_Recommendation_to_Link_Standalone_Portfolio_to_CZ_02.png
    DARA Recommendation to Link Standalone Portfolio to the Community Zone
    URM-107009_DARA_Show_Me_Why_02.png
    Show Me Why for Linking a Standalone Portfolio to the Community Zone
    URM-107009_DARA_Lets_Do_It_02.png
    Let's Do It for Linking a Standalone Portfolio to the Community Zone
    For more information about linking, see Link to Community.

    DARA Recommends Linking Local Electronic Collections to the Community Zone

    February 2020 DARA URM-108527
    Based on the electronic collection name, DARA now recommends local electronic collections for linking to the Community Zone. Linking to the Community Zone enables you to receive updates automatically without the need to update manually.
    URM-108527_DARA_Recommendation_to_Link_Electronic_Collection_to_CZ_02.png
    DARA Recommendation to Link Electronic Collection to the Community Zone
    URM-108527_DARA_Show_Me_Why_02.png
    Show Me Why for Linking an Electronic Collection to the Community Zone
    URM-108527_DARA_Lets_Do_It_04.png
    Let's Do It for Linking an Electronic Collection to the Community Zone
    For more information about linking, see Linking a Local Electronic Collection to the Community Zone.

    Library Filter Added to Recommendations List

    February 2020 DARA URM-119136
    A new Library filter was added to the List of Recommendations that you can use to filter the list by library. This feature is relevant for recommendations such as Unavailable Portfolios, Missing Items, and Local Electronic Collections.

    library_filter.png

    Library Filter

    New Columns Added to DARA Export File

    February 2020 DARA URM-119136
    The following columns were added to the Excel file that is produced when you export recommendations using the Export icon:
    • Entity Type – for example: Electronic Service, Physical Item, Electronic portfolio
    • Entity ID – for example: the Electronic Service ID, the Item PID, or the Electronic portfolio PID
    • Additional Info – for example: the columns of the analytics report or the Access type, Authentication note, and Public note of the electronic collection

    DARA Now Recommends Configuring Description Templates

    January 2020 DARA URM-117933
    DARA now identifies that you have not configured description templates, which are used to generate descriptions for physical items based on ENUM/CHRON information, and directs you to configure them.
    description_templates_recommendation.png
    DARA – Description Templates
    For more information on configuring Description Templates, see Configuring Description Templates.

    Role Configuration for DARA Recommendations

    January 2020 DARA URM-110137
    You can now configure DARA Recommendations on the new Configuring DARA Recommendations page (Configuration > General > General Configuration > DARA Recommendations):

    dara_recommendations_configuration.png

    DARA Recommendations Configurations
    Move the slider to activate/deactivate a recommendation for your institution. When deactivating a recommendation, an option to dismiss all existing recommendations of that type is displayed. This functionality was moved to this page from the Data Sharing profile page.
    Select the Actions button to display the list of roles that are configured for the recommendation. You can remove or add one of the configured roles.
    recommendation_type_roles.png
    Recommendations Roles

    Bulk Dismissal of DARA Recommendations

    January 2020 DARA URM-117109
    You can now dismiss several recommendations at one time by selecting the recommendations and clicking Dismiss selected.

    dara_bulk_dismiss.png

    DARA Bulk Dismiss

    Create Order API - Improved Matching and Creation of Portfolios to work with Community Zone

    January 2020 Resource Management URM-118756
    When the New Order API runs, Alma now uses the vendor proprietary identifier number or the ISBN/ISSN to search and match the incoming order to an existing portfolio in an electronic collection. If no match is found Alma will attempt to activate the relevant portfolios from the collection in the Community Zone.

    The newly created PO line will be associated to the existing portfolio as the main PO line, and if a PO line already existed on the portfolio this PO line will be set as an additional PO line. The access model description, as defined in the Access Model table, is added to the PO line Notes tab and to the portfolio's Public Notes field for display in Primo.
    The access model description is only added to the portfolio's Public Notes field if the Include access model in portfolio public note check box is selected on the New Order API integration profile.
    This functionality is currently supported for orders originating from OASIS for ProQuest EBook Central content. A future release will include additional providers.

    New Purchase Type License Upgrade Available for Purchase Order Lines

    January 2020 Acquisitions URM-113509
    A New purchase type License Upgrade is available for Purchase Order lines, this will enable institutions to record purchases which reflect license upgrades purchase model. Additionally, a PO line can now be created without a fund and price for scenarios such as described above where a License upgrade has no charge and needs to be recorded in the system. The option to set a PO line as no charge is compatible with the following acquisition methods: Purchase, Approval Plan, and Purchase at Vendor System. When selecting any of these values in the Acquisition Method of the PO line, the No Charge check box appears. When this check box is selected, the Funding and Pricing sections are hidden.

    COUNTER Release 5

    January 2020 Acquisitions
    URM-116815With the January 2020 release Alma is now fully compliant with COUNTER release 5.  COUNTER Release 4 will continue to be supported along with COUNTER release 5.  This is the case for both Alma as well Alma Analytics.  For more information, see video COUNTER Release 5 in Alma and Alma Analytics as well as Knowledge Center entry Managing COUNTER-Compliant Usage Data.

    As COUNTER Release 5 is a new functionality for both Alma as well as for multiple vendors which supports this and other which will support this in the future, there may be several issues which can raise during the initial adjustment period. Below you can find a few scenarios and their possible solution. At any case if you are unable to work as expected with a certain vendor it is recommended to approach the vendor as well as contact ExLibris support so that both parties can try and investigate.

    Possible Issues/Solutions:

    • Issue: I cannot harvest from a specific vendor.

    Possible solution: Determine if the "test connection" functionality works as expected (at the level of the SUSHI account). If not, confirm that the following credentials are configured correctly:

    • Vendor URL, it is recommended to use certified SUSHI vendors from the "quick pick" list, if one does not exists and you manage to configure a new vendor and harvest the data successfully, please help other members of the community by contributing this vendor as a certified SUSHI vendor.
    • Customer ID
    • Requester ID
    • User name / Password
    • API key (for vendors which support this type of connection)

    Possible solution: If the Test Connection works as expected, manually harvest each report configured on the account (each report has a "harvest now" row action). Possible analysis to provide to ExLibris support or the vendor: use the URL below, substituting the vendor-supplied information to see if the report is presented. If the report cannot be retrieved, an error is displayed in the Exception section with details from the vendor (for example: Requestor is Not Authorized to Access Usage for Institution).
    If the report is retrieved, save the downloaded report in JSON format and manually upload it to Alma. If the manual upload fails, this may be a phrasing issue either at Alma or the vendor. The URL format is: https://<Vendor_SUSHI_Harvest_URL>/reports/<report_type>?customer_id=XXXXX& api_key=XXXXX&begin_date=YYYY-MM-DD&end_date=YYYY-MM-DD. To form the URL, use the credentials supplied by the vendor, and omit redundant or superfluous parameters (for example, when API_key is not needed).

    • Issue: Alma cannot "Save" newly created account.

    Possible workaround: This issue may occur for vendors which use an API key as an identifier. This is caused by a wrong structure of the vendor's "Reports" API which Alma calls to check if the configured reports on the vendor accounts are supported by the vendor. To solve this, create an account and configure the reports, save it, edit it again and add the API key.

    For any issue with COUNTER 5, please contact ExLibris support.

    Phrase Search in the Simple Search Box

    January 2020 Resource Management idea exchange Idea Exchange SF: 00668493 URM-52270
    Alma now supports phrase search in the simple search box. All entities and index types that have the option to use phrase search in Alma's advanced search also have this capability with simple search when using double quotation marks to identify the phrase. See Performing a Simple Search for more information.

    BIBFRAME Added to the Export Bibliographic Records Job

    January 2020 Resource Management URM-73131
    Alma now supports exporting bibliographic records in the BIBFRAME and RDA/RDF output formats. See Export Bibliographic Records for more information.
    Watch the Export Records in BIBFRAME Format video (1:31 minutes).

    Community Zone Set Management

    January 2020 Resource Management URM-116800
    In addition to the Community Zone set management announcements made in the December release (see Community Zone Set Management), the January release adds the following Community Zone sets features:
    • Cataloging an authority record set of Community Zone records
    • Exporting a set of Community Zone records (with Export Authority Records or Export Bibliographic Records)
    • Creating or updating a set of Community Zone records via API (see Rest APIs – Configuration and Administration in the Developer Network)
    See Managing Search Queries and Sets for more information.
    Watch the Community Zone Set Management video (2:38 minutes).

    Alma-Based Authority Management

    January 2020 Resource Management URM-108675
    Alma now supports contribution of authorities that are managed in an Alma institution. For an institution that manages local authority records and publishes them to the Community Zone, there is now the option to have the Alma community contribute to these authority records (like the National Library of Israel (NLI) implementation). If you are an institution that 1) currently manages an authority file locally, 2) publishes it to the Community Zone, and 3) wants to have other authorized members of the Alma community contribute changes to this authority file, contact Ex Libris to analyze the feasibility of your request. If your authority requirements match the criteria for this functionality, Ex Libris will work with you to implement this capability. See Working with NLI Integrated Authority Records for an example of how this is feature is used, and see Alma-Based Authority Management for more information.

    Download Original File in Universal Viewer

    January 2020 Digital Resource Management SF: 00700969 URM-114885
    You can now download a file from the Universal Viewer in the original format in which it was uploaded to Alma. To download the original file, select the download icon.
    You configure the icon to appear from Configuration > Fulfillment > Discovery Interface Display Logic > Viewer Service > Universal Viewer. Select the Display Original Image Download Link checkbox:

    display_original_image_download_link.png

    Display Original Image Download Link

    Deposit Interface Customization

    January 2020 Digital Resource Management idea exchange Idea Exchange SF: 00593963 00709116 URM-70922
    You can now customize the Deposit user interface. To support this feature, a new configuration page was created at Configuration > General > User Interface Settings > Alma Viewer and Deposit Customization:

    alma_viewer_and_deposit_customization.png

    Alma Viewer and Deposit Customization
    You can perform the following customizations from this page:
    • Upload a customization package created in Primo Studio
    • Upload a logo image file
    • Enter a URL that is opened when you select the logo
    In a future release, you will be able to customize the Alma Viewer from this page as well.

    Network Zone Import with Local Extensions

    January 2020 Collaborative Networks SF: 00474265 00490469 00510530 00537427 00549465 00694413 00200674 00210745 00018526 00105104 00106863 00119947 URM-117585
    For Network Zone member institutions, import can now be used for adding / managing local extensions in the Network Zone. See Adding Local Extensions Using Import for more information.

    Fulfillment Network Pickup Locations

    January 2020 Fulfillment / Collaborative Networks URM-115438
    The calculations of a pickup location for a Primo patron request will be now be modified for institutions that are part of more than one fulfillment network. As an example, institutions A and B are a fulfillment network, while institutions A and C are a separate fulfillment network:
    Previously, when a patron from institution B finds a title in institution A, the pickup locations presented are from all three institutions because A is the owner of the item and A is in networks with both B and C.
    Now, rather than displaying all possible pickup locations based on the item owner, Alma will also utilize the Primo login institution, institution B, and only display the pickup locations that can serve both item owner (A) and login institution (B), in this scenario, A and B.

    Leganto Configuration Menu

    January 2020 Fulfillment URM-113303
    All Leganto configuration links that previously appeared in the Leganto sub-section of the Fulfillment tab in the Alma configuration menu are now moved to a single Leganto tab on the configuration menu (for those institutions that are configured for Leganto). The Settings mapping table now appears in each of the Legano tab's sub-sections. Only those customer parameters that are pertinent for that section are displayed in each link.

    More Possibilities for the Alma Color Theme

    January 2020 Administration and Infrastructure idea exchange Idea Exchange URM-93534
    Adding to the existing 11 color schemes on the Branding Management Page (Configuration Menu > General > User Interface Settings > Alma Logo and Color Scheme), you can now select from the following new colors: Denim Blue, Pine Green, Teal Green, Cerise, Violet, and Brown.
    alma_viewer_and_deposit_customization.png
    Alma Color Palette

    Cloud Passwords

    January 2020 Administration and Infrastructure URM-84585
    In the next step of the move to Ex Libris Identity Service, which launched in January 2019, we are removing all passwords from the Alma database. See the Ex Libris Identity Service in the Developer Network.
    This change only affects users that have not logged in since the beginning of 2019. However, if you have Primo/PDS which hasn't been upgraded for some time, there could be active users which still have passwords in the Alma database. This will only be users whose passwords are not strong enough to be written into the Identity Service automatically.
    To handle users without passwords, you can do any of the following:
    1. Add a "forgot password" link to Primo which will be useful also for users without password. See the Knowledge Article, How to add a 'Forgot My Password' link to the login page in the new UI when using Alma for authentication
    2. Create a list of the relevant users using an Analytics report and send them an email using the Update/Notify Users job (with a link to page where they can create a new password). See Editing/Messaging Users in Bulk
    3. Do nothing. The patrons who cannot login will approach a librarian who will set a new password for them.

    Reusing Already Digitized Files Between Citations

    June 2020 Fulfillment - Course ReservesURM-89490
    Librarians can now search for and copy files between citations to avoid the need to digitize files that have already been digitized. Select Attach Existing File from a citation's actions list.
    URM-89490_1.png
    Searching for and Adding Similar Citations with Attached Files to the Current Citation
    The next screen will display a result screen showing all citations with similar identifiers or titles which include an attached file.
    URM-89490_2.png
    Result Screen - Similar Citations with Files
    You can select a citation by selecting the radio button corresponding to the citation and clicking Select. Selecting a citation on this screen copies and attaches the file to the original citation.
    If a file already exists on the citation, attaching a new file will replace the existing one. Also, In Progress digitization requests on the citation will be canceled.

    Instructor Personal Copy Management

    May 2020 Fulfillment - Course Reserves
    Alma now includes enhanced workflows to enable instructors to lend their personal copies of items to the library for circulation. This allows the library to catalog instructor-owned copies, track which instructor owns the item, and easily re-use previous items in subsequent terms.

    When enabled, library staff can indicate that an item is a personal copy when creating a Brief Citation (Add Citation > Add Brief) and enter the instructor’s name. Alma will store information about all instructor-owned copies using dedicated personal copy locations. Locations in the library are automatically created when the instructors' copies are cataloged, with one location per instructor. All items deposited by the instructor will be created in that same location.

    instructor_name_for_personal_copy.PNG

    Instructor's Name for Personal Copy

    Personal copy locations indicate that the items are owned by the instructor, and also allow the library to track items that are not physically in the library at that time, but rather, in the instructor’s possession. All personal copy locations and the items in them will be suppressed. When the instructor lends the item to the library, the item can be moved to a temporary location representing a non-personal copy location in the library, where it will circulate according to standard fulfillment rules. For example, library staff may move the item to the temporary location of “Course Reserves” with a due back date of the end of the term. The item will temporarily circulate as part of the library collection, but with the instructor’s name stored as the permanent location, indicating the person to which the item should be returned at the end of the term.

    copy_moved_to_desired_location.PNG

    Copy Moved to Desired Location

    When the item is moved back to its permanent location, which is the personal copy location, it will automatically be suppressed. The item can then be returned to the instructor, but the record does not need to be deleted and can be easily re-used in subsequent terms by following the workflow above.

    To enable this feature, configure the following parameters:

    Personal copy library: To enable the personal_copy_library flag (Fulfillment > General > Other Settings) you must enter a library code as the parameter value, such as MAIN. This code corresponds to the library where the personal copy locations will be created.

    Personal copy fulfillment unit: To enable the personal_copy_fu flag, you must enter a fulfillment unit code as the parameter value. Fulfillment terms for items in the instructor-owned locations are determined by the rules set in this Fulfillment Unit. Keep in mind that the intended workflow is that items in an instructor location are not currently part of the library collection and are physically stored with the instructor.

    For more information on adding citations to a reading list, see  Contributing Instructor Resources to a Reading List.

    Managing Purchase Requests Created From Citations

    March 2020 Fulfillment - Course Reserves
    The Course Information table has been added to the Purchase Request form, displaying basic information about the course.

    Course_Information_Table.png

    Course Information Table

    The following facets have been added to the Manage Purchase Requests screen (Acquisitions > Manage Purchase Requests):

    • Processing department

    • Academic department

    • Campus

    • Course year

    • Course term

    • Citation tag

    Facets Added to the Manage Purchase Requests Screen.png

    Facets Added to the Manage Purchase Requests Screen

    The following search criteria have been added:

    • Course Code

    • Course Instructor

    • Requester

    Added Search Criteria.png

    Added Search Criteria

    For more information on managing purchase requests, see Managing Purchase Requests.

    For more information on the Leganto purchasing and acquisition workflow, watch the Leganto Purchasing and Acquisition Workflow training video.

    Automate Reading List Status While Course Active or Inactive

    March 2020 Fulfillment - Course Reserves
    From the Activate/Deactivate Courses section, staff can now automate the reading list status for a course while it is either Active or Inactive. For example, staff can set a reading list status to be Being Prepared while a course is active, and to change to Archived when a course has been deactivated (when it has ended) (Fulfillment > General > Fulfillment Jobs Configuration).

    URM-114154_1.png

    Automating Reading List Status While Active or Inactive

    For more information on activating/deactivating schedule jobs, see Viewing Scheduled Jobs and navigate to Activate/Deactivate Courses in the Scheduled Jobs table.

    Publisher Parameter Checks All Publishers When Submitting Copyrights

    March 2020 Fulfillment - Course Reserves SF:
    Leganto now allows you to set the parameter publisher to check against all publishers when you submit a copyright request (Fulfillment > Copyright Management > Digitization and Copyright Rules).

    Publisher_Parameter_Checks_Against_All_Publishers.png

    Publisher Parameter Checks Against All Publishers

    All publishers are stored in the Copyright Publishers table (Fulfillment > Copyright Management > Leganto Copyright Settings).

    For more information about adding a digitization and copyright rule, see Configuring Leganto Copyright-Related Procedures.

    For more information about adding all publishers at once, see Adding a Digitization and Copyright Rule and navigate to Publisher in the Digitization and Copyright Rule Clause Types table.

    Rollover Newer List

    January 2020 Fulfillment - Course Reserves SF: 00712048 00742202 00745287 00754472 URM-117274
    You can now roll over a course with single list creation mode. Additionally, a new check box was added to course loader, On Rollover copy only newest list. This avoids duplicated lists during rollover if, for some reason, multiple lists are associated to your course.

    On_Rollover_Copy_Only_Newest_List.png

    On Rollover Copy Only Newest List Check Box

    Additional Enhancements

    • July 2020 Acquisitions SF: 00564392 00636479 URM-1073543
      A new filter, Equals, is available for the PO line pickup form. This means that the vendor code/name must be a 100% match for the name in the search box, including case sensitivity.
    • July 2020 Acquisitions URM-124875
      A new field, redistribute_funds, was added to the Update PO Line API. When the field is true, Alma now splits the new price per fund according to its percentage in the order (similar to the redistribute lines in the PO Line details). When the field is false, which is the default, the previous functionality is maintained. The field is sent as a parameter on the URL (redistribute_funds=true) and relevant only for Update PO Line (PUT).
    • July 2020 Acquisitions URM-107815
      Performance has been improved for the Received Items List. As a result, the PO line list on the page is now sorted by creation date, from newest to oldest.
    • July 2020 Acquisitions SF: 00532439 URM-93421
      You can now define the address From value for conversation emails as either the current user's email or the library's email. Set the conversation_send_from_logged_in_user_address parameter to true to use the current user's email, or false for the library's email.
    • July 2020 Administration and Infrastructure
      The footer bearing the Ex Libris logo was introduced on Alma pages.
    • July 2020 Fulfillment SF: 00818602 URM-127879
      Users with the Circulation Desk Operator role can now access the Advanced Tools section of the main Fulfillment menu. See User Roles - Descriptions and Accessible Components.
    • July 2020 Fulfillment SF: 00811064 00833669 00835370 00840241 URM-128191
      The Requests - Recalculate After Inventory Update job now processes inventory changes only for the last seven days. See Viewing Scheduled Jobs.
    • July 2020 Fulfillment URM-130244
      You can now add the External ID of the resource sharing request to the fulfillment request slip.
    • July 2020 Fulfillment SF: 00643324 00646605 URM-110856
      Previously, for resource sharing borrowing requests, locating a resource at partner configured with Locate Profile of type ‘Z39.50’ failed if the title or author of the borrowing request contained the '&' sign. Now, the '&' sign can be removed before the locate process is executed. The rs_z39_locate_replace_amp parameter defines what will be substituted in place of the '&' sign. When set to NONE, which is the default, the '&' sign remains in place and is not removed. When set to AND, it is replaced with " AND ". When set to BLANK, it is replaced with a space. See Configuring Other Settings (Fulfillment).
    • July 2020 Fulfillment SF: 00638391 00640030 00790183 00795599 URM-105798
      In resource sharing requests, Ship Physically and Ship Digitally are now available in the configurable request statuses on the Request Pickup Configuration page.
    • July 2020 Fulfillment SF: 00797108 URM-127819
      Previously, on the Courtesy Letter, the renew status appeared on the notification to the patron with the default text instead of a customized description. This was fixed.
    • July 2020 Analytics URM-126083
      The Monthly Usage Data out-of-the-box report was added to the Usage Via COUNTER Reports - Release 5 folder. It is based on the information displayed in the Monthly Usage Data tab of Alma (Acquisitions > Import > Load Usage Data) and displays for each platform what data was and was not loaded for each month.
    • July 2020 Analytics URM-123854
      The following fields for linked records were added to the Bibliographic Details dimension in every subject area in which it appears:
      • Link ID – the link ID
      • Linked to CZ – indicates if the record is linked to the Community Zone
      • Linked to NZ – indicates if the record is linked to the Network Zone
    • July 2020 Analytics URM-123102
      The Chinese Classifications (Taiwan) folder was added under the Other Classifications folder in the subject areas in which it appears. You can use the fields of this folder to create reports relating to the classification system used for Chinese in Taiwan.
    • July 2020 Analytics URM-113534
      The following fields were added to the Fulfillment subject area regarding requests:
      • Loan Details > Is Hold Request Loan – indicates if the loan was initiated by a hold request
      • Loans > Loans (Not In House) from Hold Request – the number of not in house loans that came from a hold request
      • Loans > Loans (Not In House) from Booking Request – the number of not in house loans that came from a booking request
    • July 2020 Analytics SF: 00816223 URM-128988
      The Creation Date and Time and the Modification Date and Time fields were added to Purchase Requests > Purchase Request Details. These fields expand on the existing Creation Date and Modification Date fields by displaying the time together with the date.
    • July 2020 Analytics URM-127735
      The Portfolio Details for Consortia dimension in the E-Inventory subject area was renamed to Portfolio Details for Consortia Members to clarify that it is to be used by the network members.
    • July 2020 Analytics SF: 00824333 00824805 00833645 URM-125121 URM-128695
      The following fields were added to E-Inventory > Electronic Collections to support the new Central Discovery Index (CDI):
      • No. of Electronic Collections (In Repository + In CDI)
      • No. of Electronic Collections (In Repository + Not In CDI)
      • In CDI
      • Active for Fulltext In CDI
      • Active for Search In CDI
      • CDI Full Text Linking
      • CDI Full Text Rights
      • CDI Newspapaers
      • CDI Number of Records
      • CDI Resource Types
      • CDI Search Rights
      • CDI Update Frequency
      • CDI Provider Package Code
      • CDI - Subscribe to only some titles in this collection
      • CDI - Do not show as full text available even if active in Alma
      • CDI Local Note
    • July 2020 Analytics SF: 00626259 00686799 00708175 URM-122878
      idea exchange Idea Exchange Database usage is now included in usage statistics in the E-Inventory subject area.
    • July 2020 Analytics URM-125527
      For UNIMARC records, Bibliographic Details > Publication Date is now taken as follows:
      • the bibliographic details publication date comes from 210 subfield d (no change from current behavior)
      • If there is no 210 subfield d, the publication date comes from field 214 subfield d.
      • if both fields do not exist, the publication date comes from field 100 subfield a pos. 9-12 
      This feature will be available in August after the re-indexing job runs.
    • July 2020 APIs URM-128239
      When creating a patron digitization request using API, it is now possible to define also the following fields (relevant for partial digitization request): Volume, Issue, Part, Publication Date. See https://developers.exlibrisgroup.com/alma/apis/xsd/rest_user_request.xsd/.
    • July 2020 APIs URM-127091
      The Update user API now supports the option to recalculated user roles based on role assignment rules.
    • July 2020 APIs URM-123124
      The create purchase request API now supports defining of the requested material type. When purchase request is approved (in UI or using the API), the corresponding PO line will be created accordingly.
    • July 2020 APIs URM-128502
      The User Request API now includes managed by code and description.
    • July 2020 APIs URM-128152
      The Invoice export XML now includes the number of attachments.
    • June 2020 Acquisitions SF: 00693223 URM-116258 URM-128045
      The Vendor field in Import profile of type Update Inventory is now mandatory.
    • June 2020 Acquisitions SF: 00792980 URM-124863
      Users with the PHYSICAL_INVENTORY_MANAGE privilege can now edit the holdings record from the Receive New Material page.
    • June 2020 Acquisitions URM-121177
      The COUNTER 5 report types were added to the existing report type filter on the SUSHI Account list. Additionally, a new filter was added for the COUNTER release.
    • June 2020 Acquisitions SF: 00684631 00722807 00798105 00799762 00802108 00808311 00810525 00817615 00817616 URM-112449
      The new barcode field on the Scan-In Change Item Information page is now cleared between one scan-in operation and another.
    • June 2020 Resource Management URM-128585
      Based on customer feedback, the following changes were made to clarify search activation:
      • Previously, a number of collections had the In CDI flag set to No. This indicates that the collection cannot be activated for search separately from the search activations. However the collections could still be indexed in CDI. Now, the In CDI = No flag will not be displayed. The In CDI = Yes stays as it was to indicate collections that can be activated for search separately from the full text activation.
      • The In CDI = Yes flag now includes a tool-tip on mouse-over to provide more information about that status.
    • June 2020 Resource Management URM-119751
      Support for SFX shared holdings is now available with CDI.
    • June 2020 Resource Management URM-119751
      The CDI activation required indicator is now available for customers that are using the EasyActive setting to databases that are not activated by default because they require a subscription. This applies for cases such as Scopus and Web of Science. The indicator appears for collections that are marked as in CDI: Yes and that are not free for search. The indicator appears in two places:
      • The CDI tab of the electronic collection editor
      • The results list of an electronic collection search

      A new filter is now available on the advanced search. CDI activation required has options for Equal or Not Equals Yes.

    • June 2020 Fulfillment URM-125115
      In the Scan In Items page, every scan operation now adds a new row to the scanned items list.
    • June 2020 Fulfillment SF: 00582843 00595624 00744976 00745688 00752320 00752428 00146355 447078 URM-46346
      The Fine fee payment receipt letter now uses the value of payment method from the Payment Method configuration page.
    • June 2020 Fulfillment - Resource Sharing SF: 00747822 URM-120755
      When receiving a borrowing resource sharing that has no external identifier yet, such as for a BLDSS partner, and the generate_resource_sharing_temp_barcode parameter is set to true, the temporary barcode is now taken from the stub item's barcode.
    • June 2020 Fulfillment - Resource Sharing SF: 00729018 URM-118754
      Suppressed holdings are ignored now for the purpose of considering self ownership in Logic Rules. For example, if a customer sets a logic rule to hide the resource sharing request link when Ownership=true, and a record has only suppressed holding records with items, the link is still displayed. The self ownership condition was not actually taking into account the suppressed location, but now also the availability check may be affected.
    • June 2020 Analytics URM-100653
      The Modified By and Creator fields were added to Funds Expenditure > Vendor.
    • June 2020 Analytics URM-106974
      The Num of Research Assets (Active) and Num of Research Asset Files fields were added to Titles > Title Measures.
    • June 2020 APIs URM-122178
      A new API allows retrieving the attachments under a specific invoice, GET /acq/invoices/{invoice_id}/attachments/{attachment id}. For more information, see the Developer Network.
    • June 2020 APIs URM-120626
      You can now create a request using API for pickup in a different institution. This is relevant for fulfillment networks. Additionally, managed by information is now available in the user request API.
    • June 2020 DARA URM-119920
      DARA now supports R5 COUNTER Reports for SUSHI Vendors for the Automate Usage Data and Load Usage Data recommendation types. For more information, see DARA – Data Analysis Recommendation Assistant.
    • May 2020 Resource Management URM-123783
      The controlled vocabulary of subfield 4 for the following fields in the GND Authority metadata configuration was updated: 500, 510, 511, 550, and 551.
    • May 2020 Resource Management URM-123941
      The Bibliographic Alignment Configuration and the Authority Alignment Configuration section in the SBN integration configuration profile is no longer under construction. In addition, the job reports are now ready for bibliographic and authority alignment (see SBN Job Report for Bibliographic and Authority Alignment).
    • May 2020 Resource Management URM-118204
      The Alma import profile crosswalk conversion for DANMARC to MARC 21 was enhanced. See Source format for more information.
    • May 2020 Fulfillment SF: 00477529 00514344 00524344 00554469 00597712 00614459 00705363 00721465 00754884 00811039 00435898 URM-76929
      On the In Process Items page, the order of the filters has changed for acquisition departments.
    • May 2020 Fulfillment URM-123499
      On the request form in Get It, once a patron clicks on the Submit button, the button is disabled so that it cannot be clicked twice.
    • May 2020 Fulfillment - Resource Sharing URM-110927
      When creating a digitization request because of an AFN request for a digital copy, the following fields should be added in the note:
      • Article\Chapter Title
      • Volume
      • Issue
      • Chapter
      • Pages
      • Year
      Note: If any of these values exist, the digitization request is created as a general digitization request with the Partial Digitization attribute enabled.
    • May 2020 Fulfillment - Resource Sharing idea exchange Idea Exchange URM-87575
      On the Primo Resource Sharing Request form, the text of the Home Address and Work Address options in the pickup locations list now pulls the values from the Labels. They are listed separately from the other pickup locations, as they are for hold requests.
    • May 2020 Fulfillment - Resource Sharing URM-118863
      A new field is now available on the PUSH API transaction for ILLiad, The CitedIn field differentiates between a request imported from Alma and a request submitted directly to ILLiad. When coming from Alma, the CitedIn field contains Sent from Alma.
    • May 2020 Fulfillment - Resource Sharing URM-96121
      For the resource sharing real time item level requesting process, the barcode is now populated in the lending request regardless of the request format and whether the lender has activated the Locate By Barcode option.
    • May 2020 Fulfillment - Resource Sharing / Collaborative Networks SF: 00694833 URM-115937
      The user's selection for Activity Status on the Resource Sharing task lists is now always retained for the user. Previously, the value was only retained during a given session. Additionally, when attempting to show all completed tasks in the task lists, an error message now displays to indicate that you must enter a search term when selecting an activity status other than Active.
    • May 2020 Analytics URM-101763
      The No. of Available Portfolios and No. of Unavailable Portfolios fields were added to E-Inventory > Portfolio.
    • May 2020 Analytics SF: 00626259 00686799 00708175 URM-120737
      You can now create reports for electronic collections without portfolios from the E-Inventory subject area in Alma Analytics. To support this enhancement the No. of Electronic Collections Without Portfolios (In Repository) field was added to E-Inventory > Electronic Collection.
    • May 2020 Analytics URM-123493
      The following new out-of-the-box reports were added to shared/Alma/Titles/Reports:
      • Titles with physical inventory received in the last month
      • Titles with electronic inventory activated in the last month
    • May 2020 Analytics URM-122020
      The following fields relating to place of publication were added to the Bibliographic details shared dimension for every subject area in which it appears.
      • Place of Publication - Country
      • Place of Publication - State
      • Place of Publication - City
    • May 2020 Administration and Infrastructure SF: 00754378 00756448 00793632 00824171 URM-120430
      The following letters are now listed in the letter list. The first four can only be activated or deactivated:
      • AssignToLetter
      • UserRegistrationLetter
      • ProcessCreationLetter
      • InvoicePaymentLetter
      • ExportUserLetter - this letter will not have an option to generate a preview.
    • May 2020 Administration and Infrastructure idea exchange Idea Exchange URM-106010
      The City and Postal Code from a user's physical address are now visible in the Contact Information page.
    • May 2020 APIs SF: 00178286 URM-51134
      The GET ITEMS API (GET /almaws/v1/bibs/{mms_id}/holdings/{holding_id}/items) has the following new options.
      New query parameters. Dates have the format YYYY-MM-DD.
      • create_date_from, create_date_to - filter based on item creation date
      • modify_date_from, modify_date_to - filter based on item modification date
      • view - the currently supported value: label. When this parameter is retrieved, label information for each item will be returned - in the same way view=label works for a single item.
    • May 2020 APIs URM-111752
      You can now download log files in the Developer Network, with one line per API request, including date/time, IP address, the API called, the request method and response code. To enable the log file, in the Developer Network, go to Build my APIs > Reports > History, enter the configuration for a specific API-key, and select Save detailed log files.
    • May 2020 APIs SF: 00745740 URM-121943
      The GET Fees API now includes external_transaction_id.
    • May 2020 APIs URM-122111
      The Get-Printouts API now supports filtering by specific printer IDs. For more information, see the Developer Network.
    • March 2020 Fulfillment - Resource Sharing / Collaborative Networks SF: 00694833 URM-115937
      The user's selection for Activity Status on the Resource Sharing task lists is now always retained for the user. Previously, the value was only retained during a given session. Additionally, when attempting to show all completed tasks in the task lists, an error message now displays to indicate that you must enter a search term when selecting an activity status other than Active.
      Due to technical issues, this feature was not released in the March release. It will be deployed in an upcoming release.
    • March 2020 Fulfillment - Resource Sharing / Collaborative Networks URM-117678
      You can no longer create broker partners in a Network Zone institution. NCIP, BLDSS, RapidILL, and INNReachAPI must be created only in a member institution.
    • March 2020 Fulfillment - Resource Sharing URM-121879
      You can now configure whether the Distribute Central Resource Sharing Configuration job will distribute the value in the Shared Barcodes field on the Resource Sharing Partner page. To maintain the value locally, which is the existing behavior, set the customer parameter, rs_override_local_partner_shared_barcodes, to false. This is the default. When the parameter is set to true, the Shared Barcodes field is disabled at the local institution level and can only be updated by the network.
    • March 2020 Analytics NERS NERS Enhancement (ID #5631) URM-120275
      The Last Activity Date field was added to every place that user details appear. It indicates the last date that a patron was active (for example, made a request or borrowed, renewed, or returned an item).
    • March 2020 Analytics SF: 00632314 00661797 URM-118502
      The following fields were added to the Fulfillment subject area. They provide information concerning the institution at which an item was loaned when it is not the institution that owns the item:
      • Loan Details > Loaned at Another Institution
      • Loan Details > Loaned at Institution Name
      • Loan Circulation Desk > Loaned at Institution Circulation Desk
    • March 2020 Analytics URM-100390
      The following fields were added to the Physical Items subject area under Physical Item Details and Fund Information > Fund Measures. They allow you to create reports according to the type of request.
      • Num of Requests (Booking)
      • Num of Requests (Digitization)
      • Num of Requests (General Hold)
      • Num of Requests (Physical Item)
      • Num of Requests (Total)
    • March 2020 Analytics URM-89274
      The Shipping Date and Shipping Date (Calendar) fields were added to Borrowing Requests > Borrowing Request Details. They indicate the date the lender shipped the item to the borrower.
    • March 2020 Administration and Infrastructure URM-121580
      A new Alma extension is available that helps you automatically print letters and slips from the Alma print queues. With this new print deamon extension, there is no need to use email based printing. It also automatically updates itself when new versions are available for easy management and upkeep. The application can be found at https://github.com/ExLibrisGroup/alma-print-daemon and in the Ex Libris Developer Network App Center.
    • March 2020 APIs URM-113760
      Additional fields have been added to the Create and Update Vendor and Create PO Lines APIs. For more information, see Rest PO Line and Rest Vendor in the Developer Network
    • February 2020 Resource Management URM-120792
      The controlled vocabulary for 043 $c and 075 $b were updated in the GND Authority metadata configuration. The 043 $c was updated to address a new country code and 075 $b was updated to correct a typo.
    • February 2020 Digital Resource Management URM-105562
      The Originating System ID field for remote digital repositories was renamed to Originating Record ID when adding digital representations. This field is already indexed and searchable.

      originating_record_id.png

      Originating Record ID
    • February 2020 Fulfillment - Resource Sharing SF: 00708054 URM-118587
      You can now reactivate a borrowing request for all partner types. In order to reactivate the request, the following conditions must be met:
      • The user must have the Reactivate privilege.
      • The request is in a final status (for the complete list of final statuses, see Workflow Actions).
      • The requester is an active user.
      • If an active partner exists, the workflow profile for the partner must include Reactivated.
    • February 2020 Fulfillment - Resource Sharing SF: 00624287 00630819 URM-111738
      On the Receive Items page, the Location field no longer changes when a new due date is entered. The field now changes only when the item creation rule is triggered.
    • February 2020 Fulfillment - Resource Sharing SF: 00524851 URM-118564
      You can now control the behavior of resource sharing requests that fail to send a message to the partner. To eliminate the need to manually dismiss the notes, set the rs_failure_note_need_dismiss to false. When the parameter is set to true, which is the default, the existing behavior (notes requiring manual dismissal) is retained. See Configuring Other Settings (Fulfillment).
    • February 2020 APIs URM-120274
      The GET-Representations API now includes a new parameter, originating_record_id, which enables filtering remote representations by the unique ID of the object in the remote repository.
    • February 2020 APIs NERS NERS Enhancement (ID #6430) URM-111751
      In order to better view the details of a low traffic API, the Traffic History report on the Developer Network API dashboard now includes options to select a date range and select a specific API key when API key is selected in the Group By drop-down list. See the Developer Network.
    • February 2020 APIs URM-119485
      Two new Printouts APIs allow you to communicate with the Online Print Queue. You can check for new printouts using the GET API. The POST API marks the files printed. For more information, see the Developer Network.
    • February 2020 APIs URM-1225
      You can now manage purchase order requests via APIs. This includes options to get, update, approve or reject purchase requests, or fetch a purchase request list. For more information, see the Developer Network.
    • February 2020 Analytics URM-119228
      The new Funds Overview for Fiscal Period report was added to the Acquisitions folder and dashboard. It includes the new Fund Transaction fields that were added for the January release.
    • February 2020 Analytics URM-118444
      The following fields were added to Titles > Title Measures:
      • Number of Titles with Physical Items (Active)
      • Number of Titles with Physical Items or Holdings Records (Active)
      • Number of Titles with Holdings Records and No Items (Active)
      • Number of Titles with Electronic Portfolios (Active)
      • Number of Titles with Electronic Collections (Active)
      • Number of Titles with Digital Representations (Active)
    • February 2020 Analytics idea exchange Idea Exchange URM-117084
      The Electronic Resource Collection Overlap folder under Shared/Alma was removed, because the information in this folder is now available in the Titles with Multiple Portfolios report located under /shared/Alma/Cost per use via COUNTER reports e-inventory and acquisitions data/Reports.
    • February 2020 Analytics URM-114165
      The Return After Lost field was added to to Fulfillment > Loan. It indicates the number of items returned with the Lost process status.
    • February 2020 Analytics URM-100652
      The new Fund Rules dimension was added to the Fund Expenditure subject area. It includes the following fields:
      • Expenditures prior to fiscal period (days)
      • Fiscal period end encumbrance grace period (days)
      • Encumbrances prior to fiscal period (days)
      • Fiscal period end expenditure grace period (days)
      • Overencumbrance allowed
      • Overencumbrance limit percent
      • Overencumbrance warning percent
      • Overexpenditure allowed
      • Overexpenditure limit sum
      • Overexpenditure warning sum
      • Override Rules Information (Yes/No)
      • Transfers prior to fiscal period (days)
    • January 2020 Acquisitions SF: 00730306 URM-118240
      You can now update a vendor with the PUT API with an existing EDI code.
    • January 2020 Digital Resource Management URM-73558
      Alma now supports the auto-generation of thumbnail files for the jpeg2000 format.
    • January 2020 Fulfillment SF: 00753133 00449565 00724914 00380383 00595649 00696222 00718324 00364224 00722572 00714969 00740348 00756284 00363006 00733243 00547021 URM-67685
      The performance of the Send Courtesy Notices and Handle Loan Renewals job is improved. Additionally, loans for a single user are now aggregated into one letter. If there are more than 100 loans, they will be split into an additional letter.
    • January 2020 Fulfillment SF: 00710105 00732714 URM-114505
      Merge users now includes options to migrate purchase requests, and data from Primo VE and Leganto from the source to the target user.
    • January 2020 Fulfillment SF: 00506433 00508143 URM-85957
      The Export Users job now allows you to rerun failed jobs. Jobs that failed due to a server restart will rerun automatically. All other failed jobs can be rerun from the Jobs History list.
    • January 2020 Fulfillment / Collaborative NetworksURM-109947
      The Pick From Shelf Task List and the Request Monitor now include the Fulfillment Network Institution Code and the Fulfillment Network Borrowing ID in order to facilitate troubleshooting between network fulfillment institutions. These fields can also now be searched using persistent search bar.
    • January 2020 Fulfillment Resource Sharing SF: 00685289 00753932 URM-110728
      The Distribute Central Resource Sharing Configuration job now correctly updates rota template members. Additionally, partners with inactive status will also be added to the rota template. Known issue: Inactive partners appear as active in the Rota Template, but will not be considered when running the Sending Rules.
    • January 2020 Administration and Infrastructure URM-106693
      For customers who do not have an Alma premium sandbox, the Standard Sandbox link has been added to the Help Menu to allow them to access their sandboxes from Alma.

      ALMA_SB_Link.png

      Standard Sandbox Link on Help Menu
        

      If your sandbox cannot be located after selecting the link, please open a Support case and provide the URL for your sandbox.

    • January 2020 Administration and Infrastructure URM-110134
      Previously, the DARA icon, which provides a shortcut to the Manage Recommendations page (Admin > Recommendations > Manage Recommendations), displayed when any recommendations were available. With this enhancement, the icon will also display the number of recommendations that are available.

      Alma_DARA_Icon_With_Indicator.png

      DARA Icon with Count Indicator
    • January 2020 Administration and Infrastructure URM-47080
      The list of preferred languages in the user record are now sorted by the language the user is in and not by the English text or English code. See an example of this change below.

      Language_Sort_06.png

      Language Sort
    • January 2020 Analytics URM-116987
      The following shared reports were added:
      • Acquisitions:
        • POLs which have a renewal date in the next three months (next quarter) with bibliographic and POL information
        • Expenditure trends for physical and electronic resources for last 8 full quarters
        • Serial Issues Claims Report (Items with material type issue and expected receiving date greater than seven days that have not been received)
        • Non-Serial Issues Claims Report (Items without material type issue and expected receiving date greater than seven days that have not been received)
      • Usage via Alma Link Resolver:
        • Alma Link Resolver Usage Requests for the last complete 24 months
        • Alma Link Resolver Usage Requests from Primo and not Primo for the last complete 24 months
      • Usage via COUNTER reports:
        • COUNTER report loading analysis for the last complete 24 months
      • Titles:
        • Deleted Records Report
      • Events:
        • Events of type Physical Item went into transit and transited in less than 24 hours for the last year
      • E-Inventory:
        • Portfolios with portfolio library unit different than electronic collection library unit
    • January 2020 Analytics URM-115090
      In the Usage by title report (shared/Alma/Usage/Reports) the month labels at the bottom of the graph were moved to be vertical instead of horizontal to be more readable.
    • January 2020 Analytics URM-114282
      The name of the Library Name field in reports and prompts located under shared/Alma/Inventory/Reports was changed to Library (Active).
    • January 2020 Analytics URM-111515
      The Cost Usage subject area and its related features are deprecated. This includes:
      • The fields of the Cost Usage subject area that are available when selecting New > Analysis > Cost Usage
      • The out-of-the-box reports and dashboards for Cost Usage under /shared/Alma/Cost per Use/Reports and under /shared/Alma/Cost per use via COUNTER reports and acquisitions data
      • The folder Cost per use via COUNTER reports and acquisitions data
      All reports that use this subject area no longer work.
      Institutions that use reports from the Cost Usage subject area can do the following:
      • Take advantage of the over 30 new out-of-the-box reports in the /shared/Alma/Cost per use via COUNTER reports e-inventory and acquisitions data/Reports folder. These reports use the new Cost Usage of the E-Inventory subject area.
      • Use the out-of-the-box Electronic Cost Usage Dashboard (which uses the above reports) located in the /shared/Alma/Cost per use via COUNTER reports e-inventory and acquisitions data/Dashboards folder.
      • Make their own customized reports using the Cost Usage dimension of the E-Inventory subject area.
    • January 2020 Analytics URM-112031
      The Week Number and Start of Week fields were added to all Date dimensions in Alma Analytics. In addition, all Date dimensions were aligned to include the same fields.
    • January 2020 Analytics SF: 00689762 00714049 URM-110362
      The Author (Contributor) field was added to the Bibliographic Details folder for all subject areas in which it appears. For MARC21 the data for this field comes from MARC fields 700, 710, and 711, and for CNMARC it comes from the 702, 711, and 712 fields.
    • January 2020 Analytics URM-89956
      The Uniform Resource Identifier field was added to the Bibliographic Details folder for all subject areas in which it appears. The data for this field comes from MARC field 856, subfield u.
    • January 2020 Analytics idea exchange Idea Exchange NERS NERS Enhancement (ID #5619) URM-100251
      The following fields containing the OCLC control number were added to the Bibliographic Details folder for all subject areas in which it appears. The data for these fields comes from MARC fields 019 and 035.
      • OCLC Control Number (019)
      • OCLC Control Number (035a)
      • OCLC Control Number (035a+z)
      • OCLC Control Number (035z)
    • January 2020 Analytics URM-108703
      The following fields were added to Fund Expenditure > Fund Transaction:
      • Transaction Cash Balance: Allocated Balance – Expenditure Balance
      • Transaction Available Balance: Allocated Balance – Expenditure Balance - Encumbered Balance
      • % remaining (Considering expended and encumbered): (Available Balance / Allocated Balance) * 100
      • % remaining (Considering only expended): (Cash Balance / Allocated Balance) * 100
    • January 2020 Analytics SF: 00524082 URM-97665
      The user detail fields in the Requester subject area are now anonymized. For more information about the anonymization of Analytics reports, see Anonymizing Analytics Report Details.
    • January 2020 Analytics URM-109751
      The Call Number Prefix field was added to Physical Items > Holding Details. The data for this fields comes from MARC field 852, subfield k.
    • January 2020 Analytics URM-117087
      The shared Electronic Resource Collection Overlap folder under Shared/Alma will be deleted for the February release. The information in this folder is included in the Titles with multiple portfolios report located under /shared/Alma/Cost per use via COUNTER reports e-inventory and acquisitions data/Reports.
    • May 2020 Fulfillment - Course ReservesURM-75225
      Excel exports from the Edit Citations screen now include the Course Code, Course Term, No. of Participants, and Academic Department columns.
    • May 2020 Fulfillment - Course ReservesURM-120552
      Previously, when a librarian issued a digitization request for an item on a reading list, the email notification the librarian received with the digitized file lacked some of the information needed to associate the file with the correct citation. The following information is now included in the email notification so that librarians will know which citation to associate this file with:
      • Name of the reading list
      • Citation ID
      • Creator of the request (the person who submitted the request).
    • May 2020 Fulfillment - Course ReservesURM-118898
      When working with the DCS, instructors can now make digitization requests for citations on reading lists that are not associated with a course or courses. For more information, see Integrating with the UK's Digtal Content Store (DCS).
    • May 2020 Fulfillment - Course Reserves URM-114084
      In the Edit Citations screen, Alma now provides a link to reading lists in each citation in Alma.

      Edit Citations Screen.png

    • May 2020 Fulfillment - Course Reserves / Analytics URM-113404
      In the the Course Reserves subject area, the Leganto Citation Library Discussions field was added to Reading List Citation dimension and the Leganto List Library Discussions field was added to Reading List dimension. They display the library discussions.
    • January 2020 Fulfillment - Course Reserves / Analytics URM-80996
      The Number of Student Suggestions field was added to Reading Lists dimension of the Leganto Student Usage, Leganto Instructor Usage Events, and Course Reserves subject areas.

    Resolved Issues

    • June 2020 Release Update Administration and Infrastructure 
      The User Restriction parameter restricted operators even on inactive user roles. This was fixed.
    • June 2020 Release Update Administration and Infrastructure SF: 00849299 00849317 00849324 00849388 00849399 00849807 00850147URM-131633
      Users with Circulation Desks Manager/Operator roles could not add segments to users. This was fixed.
    • June 2020 Release Update Resource Management SF: 00849256 00849258 00849264 00849277 00849368URM-131610
      In some cases, the Expired Hold Shelf page was not loading properly. This was fixed.
    • June 2020 Release Update Resource Management SF: 00849136 00849143 00849153URM-131572
      When saving records that contain Hebrew fields, the following error would occasionally appear: 'Subfield "" is not listed in profile for field XXX, Space character expected after $$'. This was fixed.
    • June 2020 Release Update Resource Management SF: 00849141 00849142URM-131562
      The Arabic Authorities were not displayed correctly in F3 Search. This was fixed.
    • May 2020 Release Update Resource Management SF: 00793677URM-127363
      A 240 field was added to authorize publishing fields that are available to be published in case of a link. To use this function, run a republish, either full or a set.
    • May 2020 Release Update Administration and Infrastructure SF: 00838131 00838223 00838321URM-129571
      Users with a SAML profile could not open the Local/LDAP link to their premium sandbox. This was fixed.
    • May 2020 Release Update Administration and Infrastructure SF: 00838226 00838263 00838304URM-129583
      The persistent search bar was not appearing as designed. This was fixed.
    • March 2020 Release Update Analytics SF: 00808024 00809948 URM-125153
      The user identifiers Identifier1 and Identifier2 did not work as expected. This was fixed.
    • March 2020 Release Update Resource Sharing URM-125743
      When running the Update BLDSS Requests job, requests were created a day after the job ran. This was fixed.
    • March 2020 Release Update Resource Management SF: 00818975 00818977 00818980 00818984 00818987 00818992 00818998 00819011 URM-126372
      Publishing to Primo job, configured with Linked-Data enrichment, reported errors for some records. This was fixed.
    • March 2020 Release Update Resource Management SF: 00792532 00808405 00809422 00809619 00809832 00810074 00810223 00810334 00810932 00810962 00811395 00811621 00811854 00812239 00812339 00812434 00812514 00813828 00814206 00814255 00814340 00815346 00816694 00816880 00817237 00818408 00818424 URM-125152
      New Order Import ended with status 'Failed'. PO lines and bibs were created, but PO lines did not advance from 'In Review' status due to 'Exception: Cause: {1}' message. This was fixed.
    • March 2020 Release Update Resource Management SF: 00816820URM-126036
      Updating author information when contributing records to SBN failed in some cases. This was fixed.
    • March 2020 Release Update Resource Management SF: 00819310 URM-126509
      Publishing Platform job report did not match the actual exported files. This was fixed.
    • March 2020 Release Update Resource Management SF: 00819923 00820064 00820240 00820246 00820281 00820592URM-126513
      The New Order Import profiles were creating unexpected items. This was fixed.
    • February 2020 Release Update Acquisitions SF: 00807839 00807977 00809090 URM-124747
      Users with roles Fund Manager and Ledger Manager could view/edit PO lines from other sub-libraries. This was fixed.
    • February 2020 Release Update Administration and Infrastructure SF: 00808037 00808053 URM-124768
      When multiple SAML profiles were configured, login failed in some cases. This was fixed.
    • February 2020 Release Update Resource Management SF: 00807920 00808116 00808118 00808124 00808564 00808682 URM-124758
      When running the "Change Holding Information" job and the holdings did not match the normalization rule, the holdings were changed anyway. This was fixed.
    • February 2020 Release Update Digital Resource Management SF: 00808289 URM-124821
      In some case, icon indicators for Electronic Portfolios and Electronic Collections in Community Tab Search Results was not displayed as expected. This was fixed.
    • February 2020 Release Update Administration and Infrastructure SF: 00808782 URM-124823
      In some cases, on physical titles search results, after clicking the NZ icon, the NZ and CZ tabs disappeared. This was fixed.
    • February 2020 Release Update Resource Management URM-124735
      Authority changes caused relinking of irrelevant bibs. This was fixed.
    • February 2020 Release Update Resource Management SF: 00788636 00807876 URM-121274
      In the Metadata Editor, when clicking F3 on various fields, no matches were found. This was fixed.
    • February 2020 Release Update Administration and Infrastructure SF: 00807849 00807903 00808385 00808404 00808466 00808507 00808539 URM-124756
      When a printer was defined as Printout Queue, and Quick Print was active, the "Overdue and Lost Item" job failed, providing false reports when sending emails. This was fixed.
    • January 2020 Release Update Fulfillment SF: 00797183 00797572 00797586 URM-122985
      A fund indexing error occurred when searching for certain funds. This was fixed.
    • January 2020 Release Update Administration and Infrastructure SF: 00696703URM-120699
      Linked users were not found using Self Check. This was fixed.
    • January 2020 Release Update Resource Management SF: 00734680URM-118865
      Blocks on user records were deleted during user synchronization. This was fixed.
    • January 2020 Release Update Resource Management SF: 00725563 URM-121060
      A subfield in UNIMARC was not published correctly to Primo Central. This was fixed.
    • January 2020 Release Update Resource Management SF: 00754006 00793216 URM-120107
      The Z39.50 protocol was not working properly. This was fixed.
    • January 2020 Release Update Fulfillment SF: 00797743 URM-123132
      The Send Resource Sharing overdue messages to borrower job fails during lending requests with multiple barcodes. This was fixed.
    • January 2020 Release Update Fulfillment URM-121877
      The customer parameter temp_set_attribute_in_uresolver was not set to true for all customers. This was fixed.
    • January 2020 Release Update Resource Management SF: 00797333 URM-122956
      The Expand function was not set as the default in the authority browse list. This was fixed.
    • January 2020 Release Update Administration and Infrastructure URM-123027
      The statistics gathering rate was too low. This was fixed.
    • June 2020 Acquisitions SF: 00824172 00756602 00820715 URM-121655 PO Line that has items with Expected receiving date in the past and arrival date is empty did not go in to claim list. This was fixed and now PO Line that has items with Expected receiving date in the past and arrival date is empty is set to Claim even if the expected receiving date of the PO Line is in the future.
    • June 2020 Acquisitions SF: 00757262
      The Query to requester letter was not marked as Patron Facing in the Letters Configuration page. This was fixed.
    • June 2020 Acquisitions SF: 00756111
      The Purchase Requests labels from PurchaseRequestStatus were not translated properly. This was fixed.
    • June 2020 Acquisitions SF: 00802858
      On the Manage Purchase Requests page, assigning an old purchase request sometimes failed. This was fixed.
    • June 2020 Acquisitions SF: 00733730 00735241 00734629 00758520 00735153 00743778 00736304 00733665 00735583
      On the Receive New Material page, It was not possible to search and find PO Lines with special characters (""?, ?, ?, ?""). This was fixed.
    • June 2020 Acquisitions SF: 00733944 00725447 00708804
      On the In Process Items page, the filter change was incorrectly indicated and the check boxes were cleared. This was fixed. Now when selecting Done, the check boxes remain selected.
    • June 2020 Acquisitions SF: 00788558 00731832 00733608 00755417 00711275 00715519 00682815 00820300 00709013 00724532 00803528 00802837 00716970 00732970 00727471 00730225
      On the E-activation task list, an error message was displayed when selecting Done. This was fixed.
    • June 2020 Acquisitions SF: 00805776 00810902 00805360 00811037 00812173 00840951 00802874 00796875 00828630
      When saving a new SUSHI account, if there was a problem verifying the report type(s) with the vendor, the account was not saved. This was fixed. Now, the user is informed of the problem via a confirmation message and the account can be saved.
    • June 2020 Acquisitions SF: 00800873
      In the SUSHI harvesting job, the word retrieved was misspelled. This was fixed.
    • June 2020 Administration and Infrastructure SF: 00486570 00669543 00592486 00751698 00614625 00669055 00730731 00734083 00792265 00615607 00728348 00743968 00639741 00655349 00818122 00729353 00734810 00747349 00741419 00742648 00626193 00727434 00751040 00574099 00702146 00611356 00606641 00628801 00822909
      Some Alma menus did not appear when working with Alma in Chrome. This was fixed.
    • June 2020 Administration and Infrastructure SF: 00791495
      In some cases, attempting to edit the User Notifications Letter resulted in an error. This was fixed.
    • June 2020 Administration and Infrastructure SF: 00745285
      The letter ILL_EMAIL_TO_USER was missing on the Letter Configuration page. This was fixed. Please note that only the Activation Status and Retention Period of this letter are controlled via the Letter Configuration page.
    • June 2020 Administration and Infrastructure SF: 00795641
      In some cases, an error appeared when a user logged int. This was fixed.
    • June 2020 Administration and Infrastructure SF: 00818479
      On the new Rialto menu, the Analytics menu is missing the Data available as of and Data updated as of information. This was fixed.
    • June 2020 Administration and Infrastructure SF: 00832212
    • June 2020 Administration and Infrastructure SF: 00388886 00554658 00407637
      When creating a Resource Sharing request via Primo, the Requested Media field was not set to the default value Any in languages other than English. This was fixed. If the field is left empty, the default value is now set to Any in all languages.
    • June 2020 Administration and Infrastructure SF: 00754992 00792615 00785391 00804629
      Fixed.
    • June 2020 Administration and Infrastructure SF: 00719689
      Sometimes when opening the deposit page, if the language was changed, the form language still defaulted to the previous language. This was fixed.
    • June 2020 Analytics SF: 00731299
      The OBI displayed the wrong number of citations for lists associated with multiple courses. This was fixed.
    • June 2020 Analytics SF: 00747199
      Notes from the 852 field were truncated in the Holding Local Param fields to 500 characters. The was fixed by increasing the size limit of the fields to 4000 characters.
    • June 2020 Analytics SF: 00799268
      Analytics export to CSV was limited to 250K rows. This was fixed by expanding the limit to 500K rows.
    • June 2020 Analytics SF: 00754949
      In the Course Reserved subject area, the Copyright Status field was empty even when in Alma the copyright status was 'Not determined'. This was fixed, and now the Copyright Status field in analytics displays 'Not determined'.
    • June 2020 API SF: 00803524
      The Update/Notify Users Job was could not change users from External to Internal and send the Identity service mail at the same time. This was fixed.
    • June 2020 API
      The Linked data API returned invalid XML when including links to portal.dnb.de. This was fixed.
    • June 2020 API SF: 00791906
      The Get-POL-Items API can now be run with limit and offset parameters. By limiting the number of items returned the API can respond quicker.
    • June 2020 API SF: 00790601
      In the Update-Portfolio API, the <static_url> field did not take effect, This was fixed.
    • June 2020 API
      The Delete-Bib API removed a bibliographic record without warning even when it had a linked local portfolio. This was fixed.
    • June 2020 API SF: 00796432
      In some cases, the Get-invoices API returned an incorrect invoice_date. This was fixed.
    • June 2020 API SF: 00814667
      Previously, the Update-Vendor API deleted and created new vendor accounts and interfaces each time the API was used. Now when using the Get-Vendor API, IDs for the accounts and interfaces will be retrieved, when included in the Update-Vendor payload, to identify the existing accounts and interfaces.
    • June 2020 API SF: 00621714 00757380 00808321
      The 'Retrieve Job Instance Details' API did not retrieve the 'Rejected users' alert from the SIS job. This was fixed.
    • June 2020 Fulfillment SF: 00740116
      Alma quick printing did not work when RFID was active. This was fixed.
    • June 2020 Fulfillment SF: 00747624 00817997
      On the Scan-In Change Item Information page, an asterisk was added to the Location field to indicate that it is a mandatory field.
    • June 2020 Fulfillment SF: 00824941
      In the Change Bulk Due Date job, the FTP test, when applicable, is now executed once per job instead of once per notification.
    • June 2020 Fulfillment
      Previously, when scanning in an incomplete multi-part item via RFID, if the operator chose to continue the scan anyway by clicking the Confirm button in the warning popup which is displayed in this case, sometimes instead of scanning in the current barcode, a previously scanned barcode was scanned again. This was fixed.
    • June 2020 Fulfillment SF: 00800639
      If an item was in department at a process, scanned in with no following requests and was designated to transit for reshelving, the description, call number and other fields were not displayed in the items details within the list. This was fixed.
    • June 2020 Fulfillment
      When using RFID and returning an item, if the security bit update failed, clicking Retry set the security bit to the wrong value. This was fixed.
    • June 2020 Fulfillment SF: 00820005
      An error occurred when editing a loan limit rule containing an input parameter with a value that no longer exists, such as a library or location. This was fixed.
    • June 2020 Fulfillment SF: 00663937 00694029
      In a SIP2 patron information request from a Bibliotheca kiosk, the Overdue Items request was not aligned with the Charged Items request. This was fixed. Now, Alma returns only the overdue items without the charged items. Also, when BP or BQ message elements are requested, Alma now returns only the requested items.
    • June 2020 Fulfillment SF: 00725360
      For a title with multiple items, of which some were digitizable and some were not, Get It sometimes displayed all the items as not digitizable. This was fixed.
    • June 2020 Fulfillment SF: 00496219 00642577
      On Manage Patron Services, in the Request tab, the Not Started option in the Task filter did not work. This was fixed.
    • June 2020 Fulfillment SF: 00791142
      To improve performance, optimizations were performed for the reading rooms desks, active hold shelf pages.
    • June 2020 Fulfillment
      On the Return items page, when using RFID, if the security bit update failed, an error was generated when selecting Retry. This was fixed.
    • June 2020 Fulfillment SF: 00703944
      The potential accrued overdue fine sometimes did not appear in the Overdue And Lost Loan Notification letter. This was fixed.
    • June 2020 Fulfillment SF: 00630663 00690064 00806630 00732232
      Selecting Submit Request on the Manage Patron Services page occasionally resulted in an error, typically when selecting the second time. This was fixed.
    • June 2020 Fulfillment SF: 00663701 00637694 00630971 00794626 00634371 00637626
      When an item was put into transit to fulfill a Personal Delivery request, the From locations for transit were incorrectly listed as the same as the To locations. This was fixed.
    • June 2020 Fulfillment SF: 00685089
      Restore requests were incorrectly triggering an Item is Requested by Another Patron block. This was fixed.
    • June 2020 Fulfillment SF: 00742228
      Placing a shipping request from the lending institution's Manage Fulfillment Option failed when the holding had a description but the items did not. This was fixed.
    • June 2020 Fulfillment SF: 00653309
      Previously, the locate job did not check if the location of the item was suppressed or not, so items from suppressed locations were retrieved. This was fixed.
    • June 2020 Fulfillment
      In a fulfillment network, the Hold Shelf list did not display items from a different institution if the other institution was from a different server. This was fixed.
    • June 2020 Resource Management SF: 00754782
      The Authority Control Rules menu was not visible for some allowed users (for roles Cataloger_administrator and General_System_Administrator). The was fixed.
    • June 2020 Resource Management SF: 00806297 00827966 00802931 00813156 00797996 00803517 00790964 00788304
      Merging a patron with Primo VE preferences into an internal user and an external user (checking 'Copy as internal' checkbox) failed and left the patron inactive. This was fixed.
    • June 2020 Resource Management SF: 00176545 00644159
      OCLC connection always returned success message even though the record was not exported. This was fixed and now, in case of failure there will be an error message: Import failed. Reason: <>
    • June 2020 Resource Management SF: 00734291 00819136 00754714
      Update inventory import's job was updating "Set Management Tags" section of a bib record, although this section is not included on profile configuration. This was fixed.
    • June 2020 Resource Management SF: 00661261
      In unusual scenarios, using UI or API, it was possible to create two items with the same barcode when barcodes are generated automatically. This was fixed.
    • June 2020 Resource Management SF: 00674416 00836833
      When running the 'Change Holding Information' job and the holdings did not match the normalization rule, the holdings, incorrectly, were changed anyway. This issue was fixed.
    • June 2020 Resource Management SF: 00842693 00736470 00832790
      Customer's time zone impact on the following date fields that are in 'Electronic Service Editor' page: 'Active from date', 'Active until date' and 'Service unavailable message as of date' was fixed.
    • June 2020 Resource Management SF: 00820518 00842519 00804252 00815740 00838597 00801832 00831166 00829208 00839264 00843627 00816022 00799787 00758131 00798045 00841939 00843722 00828470 00813914 00828537
      Fixed adding services so that they were not properly displayed.
    • June 2020 Resource Management SF: 00712276 00715321 00530054
      Space characters in portfolio linking static URLs were encoded as '+' instead of '%20', leading to some broken links. This has been fixed.
    • June 2020 Resource Management SF: 00801236
      Fixed, serviceId will not hold the collection id after data corrector work.
    • June 2020 Resource Management SF: 00806126
      When using create E activation task from the electronic resource if the PO Line is not found an error message is displayed. This was fixed.
    • June 2020 Resource Management
      Fixed an error caused by an empty list in some environments.
    • June 2020 Resource Management SF: 00810193
      Connecting to a remote digital repository that required authentication did not work. This was fixed.
    • June 2020 Resource Management SF: 00815223
      A user with the Digital Inventory Operator role could not manage or create sets with a content type of Digital Titles. This was fixed by giving the Digital Inventory Operator role the SETS_EDIT privilege.
    • June 2020 Resource Management SF: 00745243
      Fixed handling of deleted holdings + items in member to trigger publishing from NZ.
    • June 2020 Resource Management SF: 00512291 00559868 00478466
      Search for portfolios with a URL that contains 'www.' and/or special characters (period, hyphen etc.) returned with no results.
    • June 2020 Resource Management SF: 00797459 00759443
      Searching for Storage Location ID 'Is Empty' under 'Physical Items' did not work properly. This has been corrected. For this fix to take effect, full inventory indexing must be run.
    • June 2020 Resource Management SF: 00679421 00528284
      The hyphen ‘-‘ from the authority field 400 $$d appeared in front of the year. This was fixed. 
    • June 2020 Resource Management SF: 00790201
      Sets with a forward slash '/' character in the set name caused an error in analytics. This was fixed.
    • June 2020 Resource Management SF: 00407637
      The 'All' (default) option was not the first in other languages. This was fixed.
    • June 2020 Resource Management SF: 00659615 00658769 00688591
      Normalize apostrophe (in the four forms listed) to nothing instead of space when creating filing value (which is used for searching and sorting bib headings). U+0027
    • June 2020 Resource Management SF: 00721702
      In the MDEditor when browsing title heading and the active registry has unimarc kormarc or cnmarc activated, if a title heading match more than one registry the view is showing only the first bib for the first registry. The issue has been fixed and now the user show all the bib of the different registry.
    • June 2020 Resource Management SF: 00694437 00758504
      In some cases, an SRU search in the Network Zone with the Enrich with Members Availability option selected caused an error message when holdings for a member consisted only of collections. This was fixed.
    • June 2020 Resource Management SF: 00792125 00815482
      Merge records and combine inventory for network records: In some cases (mostly when the primary network record was linked to a CZ authority record), the local (cached) secondary record – of the member institution performing the merge action - was not deleted, and its inventory was not transferred to the primary record; in addition, the primary record was locked for editing. Both these issues have been fixed.
    • June 2020 Resource Management SF: 00753109
      Changed order of filters in Solr configuration for text_japanese fields so that both pre-composed diacritics and combining diacritics are normalized to the same values.
    • June 2020 Resource Management SF: 00527082
      Browse Bibliographic Heading -> choose a heading first time (click 'view') resets the scroll bar of the headings window. This was fixed.
    • June 2020 Resource Management SF: 00502554
      Switching between previous versions in the MD Editor does not reset the scroll bar. This was fixed.
    • June 2020 Resource Management SF: 00714086
      In some cases, when a member institution performed 'Merge & Combine' from the MD Editor on two network records, the 'primary' network record was locked. This has been corrected.
    • June 2020 Resource Management SF: 00736194
      When returning to MD Editor from Item/Portfolio/POL creator in Hebrew UI there is an error. This was fixed.
    • June 2020 Resource Management SF: 00686125 00789542 00791248
      Merge records and combine inventory for network records: In some cases (mostly when the primary network record was linked to a CZ authority record), the local (cached) secondary record – of the member institution performing the merge action - was not deleted, and its inventory was not transferred to the primary record; in addition, the primary record was locked for editing. Both these issues have been fixed.
    • June 2020 Resource Management SF: 00668558
      Merge records and combine inventory for network records: In some cases (mostly when the primary network record was linked to a CZ authority record), the local (cached) secondary record – of the member institution performing the merge action - was not deleted, and its inventory was not transferred to the primary record; in addition, the primary record was locked for editing. Both these issues have been fixed.
    • June 2020 Resource Management SF: 00838563 00833116
      New MDE - Push to MDE is not working when a record does not have a modification date. This was fixed.
    • June 2020 Resource Management SF: 00741786
      Preferred Term Correction job must check $6 linkage when matching the value of the linked datafield in the bib heading record with the source datafield's $6 value in the bib record when dealing with 880 fields, otherwise, if multiple 880 fields are linked to the same heading, only the first matching 880 field will be corrected.
    • June 2020 Resource Management SF: 00789824 00754247
      Local Authorities had extra spaces - resulted with them being able to be found by F3, but not linked. The issue will be solved by running full inventory index on authorities - with recalculate MMS Opr and recalculate Auth heading.
    • June 2020 Resource Management
      Headings 800, 810 with $$e unlinked after PTC - when auth priority is defined for a subject. This was fixed.
    • June 2020 Resource Management SF: 00803094
      F3 did not show matched authority for linked headings. This was fixed. The $w was removed from the filling value of the 650 field.
    • June 2020 Resource Management SF: 00666607
      The BIBFRAME view of bibliographic records was missing links for local authority records. This was fixed.
    • June 2020 Resource Management SF: 00752996
      When trying to resolve multi-match issue of MD Import, which required manual handling, the 'Approve Import' button appeared - this was fixed. 'Approve Import' will appear only in cases of issues that have been assigned to handling type 'Manual'.
    • June 2020 Resource Management SF: 00813099 00800488
      New Order/Metadata Import fails with an error. This was fixed.
    • June 2020 Resource Management SF: 00810041
      When working with an Aleph central catalog integration profile, it is possible to use the Z39.50 target that is defined in the profile as an external search target (without configuring it in the external search resources/profiles) The attributes for searching this target were not customizable. This was fixed and now the Z39.50 attributes can be customized by modifying the 'Z39 Term Transformation' mapping table. This can be done by Ex Libris staff only.
    • June 2020 Resource Management SF: 00815780
      When contributing a record to SBN it was not possible to reload the record from SBN when contribution fails. This was fixed.
    • June 2020 Resource Management SF: 00827795 URM-128384
      Publishing information for the Central Discovery Index was missing. This was fixed.
    • June 2020 Resource Management SF: 00825111 URM-127698
      A database collection that was deactivated in Alma still got published to CDI. This was fixed.
    • June 2020 Resource Management SF: 00825966 00827809 URM-129087
      Changes to the CDI Selective settings for Aggregator or Selective collections did not get published to CDI correctly, which resulted in incorrect availability information in CDI. This was fixed.
    • June 2020 Resource Management URM-130388
      The facet count in for CDI related facets was not always correct after searching for an electronic collection. There is currently no solution to provide accurate numbers for the CDI related facets, so they were removed to avoid confusion.
    • June 2020 Resource Management SF: 00756125
      Similar Arabic letters will be treated as the same letter. Each of the letters below, which are in the same row, will be treated as the same letter:
      • ا – أ – إ – آ
      • ى – ي - ئ
      • ه - ة - ۀ
      • و - ؤ
      • ك – گ – ک
      • ف - ڤ
      • ز - ژ
      • ب - پ
      • ج - چ
      • ق - ڨ
      This new functionality requires reindexing, and until the reindexing occurs, browsing of bib headings, and authorities search using F3, may not work properly.
    • July 2020 Acquisitions SF: 00757142 00830347 00719198 00757646 00796170 00815392 00725019 00727030 00724503 00729501 00727818 00754788 00715117 00807475 URM-118723
      Improvements were made for the slow response time on the Receive New Material page.
    • July 2020 Acquisitions SF: 00791901 00734706 URM-123602
      Performance improvements were made for the Receiving Department Items loaded page.
    • July 2020 Acquisitions SF: 00793139 URM-125692
      In some cases, adding an email address to a work order caused it to fail. This was fixed.
    • July 2020 Acquisitions SF: 00641376 URM-117936
      When entering a material type of JOURNAL in the PO line, it was saved as Journal Package. This was fixed.
    • July 2020 Acquisitions SF: 00736046 00752661 URM-123931
      When creating a new purchase request that creates the bibliographic record, the record is suppressed from publishing but it is not indexed as such. Because of this, it could not be found as a record with Tag Suppressed (Title) = 'Yes'. This was fixed.
    • July 2020 Acquisitions SF: 00593516 00817537 URM-123702
      When receiving a new item for a continuous PO line, an incorrect calculation caused the item status to be 'in place' instead of 'not in place'. This was fixed.
    • July 2020 Acquisitions SF: 00788285 URM-126975
      In some cases, using a prediction pattern to receive an unreceived journal caused the process fail. This was fixed.
    • July 2020 Acquisitions SF: 00715242 URM-115299
      Previously, when the MMS ID equaled zero in the Electronic Resource Activation Task List, the URL did not display or export. This was fixed.
    • July 2020 Acquisitions SF: 00791724 00648063 00650554 00599063 00834322 URM-104410
      E-books unexpectedly appeared in the Claim list. This was fixed.
    • July 2020 Acquisitions SF: 00794334 URM-129670
      A tooltip in the Vendor EDI Add Organization Unit was not correct. This was fixed.
    • July 2020 Acquisitions SF: 00813037 URM-120251
      In the Harvest Now process, when one report failed, all other reports failed as well. This was fixed.
    • July 2020 Acquisitions SF: 00821922 00799361 00820939 00846528 00800843 00813098 00810358 00837632 URM-125855
      In the SUSHI harvesting process, when a vendor returned an error about date arguments, the harvest process failed. This was fixed.
    • July 2020 Acquisitions SF: 00791077 URM-126784
      When sorting by SUSHI account in the SUSHI vendor list, some SUSHI accounts were missing. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00819599 URM-127706
      In the Fines/Fees Notification Profile Record, the maximum amount was not saved. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00792037 URM-126969
      Previously, every fine/fee which was created manually was written with a creator and modifier by the first and last names of the operator. This was fixed. Now it is written with the operator's user name so it will be aligned with fines fees created automatically.
    • July 2020 Administration and Infrastructure SF: 00829990 URM-130270
      On the Payment Receipt Letter, the barcode now appears for fines that were attached to barcodes but are not attached to loans.
    • July 2020 Administration and Infrastructure SF: 00646323 URM-109605
      When attempting to add a service unit to the Receiving Operator Role after it was created, an error was generated. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00711273 00683998 00813793 00718441 00713315 00715329 00835417 00821778 00709386 00735257 00722852 00843064 URM-117185
      In some cases, the History tab of the User Details page appeared with the blue indicator on the tab, but there were no changes. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00769496 URM-124910
      In some cases, on the User Management Information page, when selecting the Force password change on next login checkbox, the selection was retained between users. This was fixed.
    • July 2020 Administration and Infrastructure URM-125594
      On the User Record page, the Contact Information tab was accessible even though it should have been restricted. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00821765 00813150 URM-125661
      In some cases, logging into to Alma failed due to certain Service Units used in 'Currently at'. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00823694 URM-127815
      When creating a Quick Registration in a member institution, some user fields were not updated by the Network SIS loader. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00842264 00831324 00843538 URM-129405
      In some cases blank address information displayed as 'Null' in user contact information tab. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00825934 URM-128100
      In the resetting the password with the Forgot Password option, some of the error messages appeared in English regardless of the user's selected language. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00656217 00668227 00734071 00590725 00648393 00697253 00720620 00655322 URM-107613
      The Ex Libris footer sometimes appeared in the middle of the page. This was fixed in new Alma layout.
    • July 2020 Administration and Infrastructure SF: 00793460 URM-122619
      The Alma course search criteria appeared cut. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00579885 URM-96188
      Inconsistent naming between navigation links and page titles. This was fixed in Alma new layout
    • July 2020 Administration and Infrastructure SF: 00571440 00601352 00815480 00625940 00599103 URM-97342
      Heading shifts side to side made it difficult to select configuration menu. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00804213 00752066 00805055 URM-126202
      Quick User information automatically populated PIN and sent emails (Chrome, German interface). This was fixed.
    • July 2020 Administration and Infrastructure URM-127863
      When using the new menu, running 'Move set of portfolios' job reverted the interface back to the regular interface. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00634501 URM-104849
      In the Approval Requests List, The contents of the Digitization Type and Warning columns were not translated. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00553228 00794082 URM-96937
      Request button in Get It not fully clickable in Firefox. This is fixed
    • July 2020 Administration and Infrastructure SF: 00833857 URM-129031
      QuickAccess display (embedded in the new Alma viewer) for Network Zone, Institution Zone, and related records is not working. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00798177 00828521 00831894 00793551 00797609 00746802 00834883 00738472 00739039 00787476 00745299 00746782 00757744 URM-119389
      The Letters purge with retention job was always ending with a failure result, even though it had executed successfully. This was fixed.
    • July 2020 Administration and Infrastructure SF: 00746782 00746802 00829876 00830601 00835901 00841620 00842305 00845005 URM-121311
      The Letters purge with retention job ended with a failure result for some customers who set no retention value on any letter. This was fixed.
    • July 2020 Analytics SF: 00816692 URM-127856
      Analytics “Interface status” has numeric value instead of Active/Inactive
    • July 2020 Analytics SF: 00832429 URM-129284
      The Newly Created Portfolios out-of-the-box report referred to private folders or unconfigured prompts. This was fixed.
    • July 2020 Analytics SF: 00622887 00791102 URM-101539
      In Analytics, in the Fulfillment subject area under the Loan Details folder, the Loan Note field contained no data even when the loan had a note. This was fixed.
    • July 2020 Analytics SF: 00625633 00795793 00847844 00650924 00733831 00795408 00792709 00840418 00817982 URM-102556
      The Daily Book Request report sent an error message instead of the report. This was fixed.
    • July 2020 Analytics SF: 00752860 00739058 00794706 URM-118673
      The Physical Items > Holding Details > Holdings Record Creation Date analytics field displayed the same value as the Holding Details > Holdings Record Modification Date analytics field and not the holding record's creation date as it appears in Alma. This was fixed.
    • July 2020 Analytics SF: 00642793 URM-120604
      The Transaction Type Pie chart on the Acquisitions dashboard could not be edited to display the remaining allocation regardless of status. This was fixed.
    • July 2020 Analytics SF: 00832277 00756030 00823270 URM-123206
      There was no difference between the data in the Fulfillment subject area between the Patron Details folder and the Borrower Details folder. This was fixed, and now the Patron Detail folder displays information from the time of the loan and the Borrower Details folder displays the current information.
    • July 2020 Analytics SF: 00753773 00842063 00845646 URM-127479
      Results did not appear for reports with the Bibliographic Details > Language of Cataloging field in Analytics reports if the record does not include an 040 $b field. This was fixed.
    • July 2020 Analytics SF: 00827498 URM-129770
      The Portfolio Access Type field (Inventory >Portfolio Details) returned two values for 'None'. This caused portfolio duplication in the report. This was fixed and now only one record is displayed in the report.
    • July 2020 Analytics SF: 00819855 URM-130097
      LC Classification range 195.001 to AC199.999 showed incorrect groups. This was fixed.
    • July 2020 API SF: 00720750 00720048 00551789 URM-92322
      The New Order API was not recording the version when holdings were updated. This was fixed.
    • July 2020 API SF: 00798293 URM-126000
      The GET Purchase-Requests API failed when the relevant user was missing a first or last name. This was fixed.
    • July 2020 API SF: 00821361 URM-126748
      The Update-Portfolio API was updating the portfolio incorrectly when the payload included more than one local_date_coverage_parameters. This was fixed.
    • July 2020 API SF: 00820598 URM-127149
      The Retrieve Electronic Collections API was slow when called without any search parameters. This was improved.
    • July 2020 API SF: 00813079 URM-127565
      Hold Requests created by API didn't include item barcode. This was fixed.
    • July 2020 API SF: 00819485 URM-127862
      The GET-Users API, when used with wrong search syntax for the 'q' parameter, wasn't returning the expected error message. This was fixed.
    • July 2020 API SF: 00836954 URM-130033
      The Get-Requests-By-Bib-mms-id was skipping digitization requests in some cases. This was fixed.
    • July 2020 API SF: 00695928 URM-130497
      The Create Portfolio API (POST /bibs/{mms_id}/portfolios/) was creating multiple IEE records. This was fixed.
    • July 2020 API URM-130616
      The GET-Bibs API was not returning the total_record_count field. This was fixed.
    • July 2020 API SF: 00840598 URM-130617
      The GET-Bibs API returned an error when, according to the search parameters, no record was found. It now returns an empty list of records.
    • July 2020 CDI URM-121861
      Display issues on the the CDI Collection Tab were fixed.
    • July 2020 CDI URM-129640
      Publishing to CDI failed when there was an empty publishing profile. This was fixed.
    • July 2020 CDI URM-129959
      DB type collections showed the selective indication option in multi-campus. This was fixed.
    • July 2020 Fulfillment URM-28998
      Previously, you could not place a manual description request if the item was in a temporary location. This was fixed.
    • July 2020 Fulfillment SF: 00492161 URM-86980
      A performance improvement has been made for selecting a new processing location in Alma.
    • July 2020 Fulfillment SF: 00635597 00793126 URM-108430
      Request recalculation ignored the On Shelf request policy. As a result, recalculation of a request sometimes caused the request to switch to an available item even if the On Shelf request policy did not allow it. This was fixed.
    • July 2020 Fulfillment SF: 00648548 URM-117929
      The Primo Get-It pane loading time was slow for serial titles that had many related records. The loading time was improved. Additional improvements are in progress.
    • July 2020 Fulfillment SF: 00824480 URM-127670
      Under certain circumstances, the last renew status of a loan was incorrect. This was fixed.
    • July 2020 Fulfillment SF: 00809021 URM-127731
      A content indicator was added to the Instructors tab in the course details page.
    • July 2020 Fulfillment SF: 00842579 00823488 URM-127746
      The Quick Print Preview of Ful Resource Request Slip Letter was not Supporting Japanese Characters. This was fixed.
    • July 2020 Fulfillment URM-127988
      If the Notifications - Send Courtesy Notices and Handle Loan Renewals job failed to send emails because of users with no preferred email address, the job completion status was set to either Completed with Errors or Completed with Warnings according to the percentage of failures. Now the the job completion status is always set to Completed with Warnings in this case, regardless of the number of failures.
    • July 2020 Fulfillment URM-128201
      A performance improvement has been added in the fulfillment area.
    • July 2020 Fulfillment SF: 00809197 URM-128608
      When cancelling a request from the Patron Services page, the cancellation reasons did not appear in the order of the code table, as they do when cancelling form the Monitor Requests page. This was fixed.
    • July 2020 Fulfillment URM-128824
      If the Loans - Overdue and Lost Item job failed to send emails because of users with no preferred email address, the job completion status was set to either Completed with Errors or Completed with Warnings according to the percentage of failures. Now the the job completion status is always set to Completed with Warnings in this case, regardless of the number of failures.
    • July 2020 Fulfillment URM-130339
      Translations were added for labels and buttons within the user summary section of the Patron Services page.
    • July 2020 Fulfillment SF: 00726894 00759677 00698458 URM-113736
      Alma does not support sending emails to invalid addresses. This is now reflected on the job report.
    • July 2020 Fulfillment SF: 00743690 URM-119517
      When importing a calendar from an excel file, events with 'Yearly' recurrence were incorrectly imported as 'Weekly' events. This was fixed.
    • July 2020 Fulfillment SF: 00756146 URM-120196
      Some performance improvements were done for handling NCIP messages. Additional improvements are planned for future releases.
    • July 2020 Fulfillment SF: 00432307 URM-130464
      The Pick from Shelf print slip report is now sorted in the same order as the UI list.
    • July 2020 Fulfillment SF: 00414707 00474012 00801139 00549665 00451924 00459766 00612811 00526298 00392229 00736894 00460182 00558398 URM-73571
      The content indicator of requests and returns tabs on the Patron Services page are now populated when coming from user details Manage Fulfillment Activities.
    • July 2020 Fulfillment SF: 00740059 00574434 URM-95580
      When trying to place a request from Patron Services, and the record had only items in a temporary location, the Booking button that not appear within the Submit Request popup. This was fixed.
    • July 2020 Fulfillment SF: 00789385 00790545 00812022 00798431 URM-124866
      When a physical item request was in the pick from shelf stage, and then the item information was changed, the resource request slip was immediately printed a second time. Now, a new resource request slip is printed in this case only if one of the following fields is changed: Location, Description, Material type, Item policy, Process type. Note: If the request will not be handled (i.e. it is still in the pick from shelf stage) until the next execution of the Requests - Recalculate after Inventory Update job, the job will process the request and will trigger a printing of a new slip regardless of which fields were changed.
    • July 2020 Fulfillment SF: 00792171 00826975 00799440 00794008 URM-124869
      The reshelving of an item was wrongly considered an inventory update and therefore incorrectly triggered request recalculation by the Requests - Recalculate after Inventory Update job. Since the job also reprints resource request slips during the recalculation, this caused the slips for these items to be printed a second time for no reason. This was fixed. Now reshelving will no longer trigger request recalculation and therefore the slips will not be reprinted.
    • July 2020 Fulfillment URM-126831
      Patron information will now be exported within the exported document (XML) for any request type with such information.
    • July 2020 Fulfillment URM-127891
      When an AFN request was created for an item that was temporarily in remote storage, the request was sometimes placed in Pick from Shelf status instead of Waiting for Remote Storage status. This was fixed.
    • July 2020 Fulfillment SF: 00701755 URM-116967
      The XML of the Resource Sharing Shipping Slip Letter was missing the issue_level_description information. This was fixed.
    • July 2020 Fulfillment SF: 00690928 URM-118641
      The series title number was not added to FulOutgoingEmailLetter and QueryToPatronLetter. This was fixed.
    • July 2020 Fulfillment SF: 00746820 00805568 URM-121774
      When trying to renew a lending request either manually or automatically, and the Resource Sharing library has no opening hours, the renew response was sent without a due date and an internal error displayed to the page in the manual action. This was fixed. Now, in this circumstance, the renew action is not performed, no message is sent to borrower and an informative error displays on the page.
    • July 2020 Fulfillment URM-121870
      When converting an article resource sharing request to a digitization/hold request, the note did not include the Article Title and Author information. This was fixed.
    • July 2020 Fulfillment SF: 00812077 00821850 URM-126875
      In some cases, shipping a lending request digitally resulted in an error. This was fixed.
    • July 2020 Fulfillment SF: 00694833 URM-129106
      The parameter rs_override_local_partner_shared_barcodes to override the shared barcodes in the distribution of partners was enabled for all BIBSYS institutions.
    • July 2020 Fulfillment SF: 00800370 URM-124764
      When sending an NCIP AccepItem message for a borrowing request that was initially created by Alma, Alma ignored the DateForReturn field and did not update the request due date accordingly. This was fixed. Alma now updates the borrowing request with the new due date if sent. No change is done in the loan due date in case the item is loaned already.
    • July 2020 Fulfillment SF: 00740309 00453083 00731900 00736130 00728401 00741175 00626932 00623005 URM-102946
      Notes containing a carriage return in ISO messages sometimes caused the message to fail. This was fixed, Carriage returns are now removed from the notes of all ISO messages.
    • July 2020 Fulfillment SF: 00648258 00684788 URM-110602
      The dynamic URL was not encoded properly. This was fixed.
    • July 2020 Fulfillment SF: 00460098 00715241 00450769 00580891 URM-80868
      Previously, if the ful_network_default_pickup_inst parameter was set to the patron, the initial value of the pickup institution field in a fulfillment network request form was left blank. This was fixed. Now, when the parameter is set to patron, the initial value is set to the patron's institution, meaning that linked account users show the patron's source institution. Note that this depends on the configuration of the item's owning institution and not on the logged in primo user.
    • July 2020 Fulfillment URM-129314
      The pickup institutions list in Alma and Getit request forms is now alphabetically sorted.
    • July 2020 Fulfillment SF: 00751777 00729366 00727865 URM-126749
      A performance improvement was made to the Loan - Overdue and Lost Item job.
    • July 2020 Fulfillment SF: 00831954 URM-128574
      Previously, the Request Send Report job always appeared as active on the Fulfillment Jobs Configuration page, although the job was actually inactive. This was fixed.
    • July 2020 Fulfillment URM-122367
      In some cases, the External_System_RS_Export job failed to export the request due to a change in the request or item during the job execution. This was fixed.
    • July 2020 Resource Management SF: 00756530 URM-122211
      In Repository Search, when searching in advanced search using Additional Publication year > Contains keywords = &#xC2;, the results page was not loaded properly. This was fixed.
    • July 2020 Resource Management SF: 00792655 URM-123708
      When merging secondary bib record 'A' (attached to an Electronic Collection) into a primary bib record 'B', the Electronic Collection was correctly attached to record 'B'. However, a redundant representation of the primary record 'B' remained active, which caused this record to be published twice. This was corrected. The redundant representation of the primary record 'B' is deleted as part of the merge and combine process.
    • July 2020 Resource Management SF: 00826000 URM-128153
      'Physical Inventory Operator' role does not work as expected, causing users without Repository Manager role unable to see the holdings/items links when opening a public itemized set. This was fixed.
    • July 2020 Resource Management SF: 00788933 00816952 00759342 URM-121338
      The 500 Internal error was issued when attempting to save predicted items. This was fixed.
    • July 2020 Resource Management URM-124209
      The relinking option of a holding or an item (functionality available for the Physical Inventory Operator/Extended/Manager/Repository Manager/Purchasing Operator/Purchasing Manager roles) was allowed for any holding or item even when they are not in the same library scope.
    • July 2020 Resource Management SF: 00789803 00789816 URM-128214
      When holdings had more than one item and one of the items changed his location to a new holdings, the Modify column contained wrong data. That was fixed. Old data wasn't fixed, to fix it, re-save the item.
    • July 2020 Resource Management SF: 00812367 URM-129406
      In the Physical Item 'view' mode, the 'Relink to another bibliographic record' button is now visible only to the following roles, which include the 'PHYSICAL_INVENTORY_MANAGE' privilege: Repository Manager, Physical Inventory Operator (+ extended), Purchase Operator, Purchase Manager.
    • July 2020 Resource Management SF: 00239222 URM-90658
      After contributing an electronic collection to the Community Zone, updating the URL of a portfolio in the collection changed the local portfolio but not the Community Zone. This was fixed.
    • July 2020 Resource Management SF: 00688677 URM-120236
      When a portfolio already had a license attached and the import profile did not contain a license, portfolio license was not deleted. This was fixed.
    • July 2020 Resource Management SF: 00754725 URM-124842
      Portfolio with a big amount of coverages caused overlap analysis to fail. This was fixed.
    • July 2020 Resource Management URM-125186
      Deleting e-collection by a job while restarting the batch, caused the e-collection to remain in 'In deletion' status.
    • July 2020 Resource Management SF: 00799486 URM-125304
      Upload Electronic Holdings job for Ovid was not activating or updating monographs when multiple profiles were set up in a multi-campus environment. This was fixed.
    • July 2020 Resource Management SF: 00828538 00804299 00824720 URM-125338
      When an identifier from an Upload Electronic Holdings job input file already existed in at least two different bibliographic records within an institution, the portfolio was not activated or updated by the job. This was fixed.
    • July 2020 Resource Management URM-125943
      'Type' label appeared twice in the 'Manage Column Display' when searching for electronic collections. This was fixed to appear only once.
    • July 2020 Resource Management URM-125946
      The 'Service' label that appeared in the 'manage column display' when searching for electronic collections was removed נecause the 'Services' label already exists and therefore, the 'Service' label is unnecessary.
    • July 2020 Resource Management SF: 00826322 URM-127832
      The Upload Electronic Holdings job used to update and reindex every active portfolio in the input file, even if no changes were made. The job now checks for changes before updating portfolios.
    • July 2020 Resource Management SF: 00827823 00828566 URM-128086
      The upload electronic holdings job used to update and reindex every active portfolio in the input file, even if no changes were made. The job now checks for changes before updating portfolios.
    • July 2020 Resource Management SF: 00838823 00827077 00841414 00827875 00826257 URM-128774
      A new data corrector,&#xA0;DataCorrectorDeleteCollection, was created in order to manually delete collections were the deletion job failed. This can be run from the Data Corrector page.
    • July 2020 Resource Management SF: 00839043 URM-130482
      The “Selected Full Text' service could not be deleted from electronic collection. This was fixed.
    • July 2020 Resource Management SF: 00809493 URM-126463
      In some cases, removing a link to a bibliographic record in an electronic collection did not trigger the publishing of the bib record as deleted. This was fixed: now when a bib record is separated from a collection, it is properly published as deleted.
    • July 2020 Resource Management SF: 00731853 URM-118030
      With the October release, the Publish Electronic Records to CDI job was made available for all customers, even when the parameter publish_to_central_index was set to 'PC only'. This was fixed.
    • July 2020 Resource Management SF: 00794242 URM-126615
      In enrichment publishing, the Create Date/ Modification Date was wrong in some cases. This was fixed.
    • July 2020 Resource Management SF: 00796215 URM-125041
      Error messages displayed when trying to delete collections relating to a workflow, such as import, profile/deposit, and profile/digitization profile did not provide enough information. This was fixed.
    • July 2020 Resource Management SF: 00814009 00802283 URM-126256
      A new data corrector&#xA0;DataCorrectorDeleteCollection, was created to manually delete collections where the deletion job failed.
    • July 2020 Resource Management SF: 00827068 00798456 URM-126262
      Running Update Electronic Holdings Integration Profile for SPRINGER produced the error 'An error occurred while downloading vendor's file'. This was fixed. The jobs that did not complete successfully, now provide the right indication.
    • July 2020 Resource Management SF: 00829504 URM-128589
      In some cases, 'Combine set' showed as failed, but succeeded to create the new set. This was fixed.
    • July 2020 Resource Management SF: 00791647 URM-122057
      Portfolios that were linked to more than one service (wrong service ID in TPS) caused a different number for collection and service. A data corrector was added to fix the issue.
    • July 2020 Resource Management URM-126321
      'Held By' page – Summary Holdings: previously only field 866 subfields $a and $z were displayed. This was fixed. If the holdings record contains fields 866, 867, or 868 (all three are repeatable) with subfields $a (non-repeatable) and $z (repeatable), all of them will be displayed. Fields are separated with “ ; “ (space semicolon space), and subfields with “ – “ (space dash dash space).
    • July 2020 Resource Management SF: 00701001 URM-126884
      Browse Shelf Listing of Dewey call numbers: the sorting of the browsed results has been corrected for Dewey call number that contain an underscore (“_”). This fix is relevant only when the “Dewey_normalization_numeric_sort_after_underscore” customer parameter is set to “true”. In addition, full inventory indexing is required, with the “recalculate Holdings Operational” option enabled.
    • July 2020 Resource Management SF: 00602927 00479956 00826458 00627399 00666413 00602926 URM-85434
      Advanced search with the “Contains Phrase” operator (and also “Starts With”, which is available for some indexes) did not work for search phrases that included an apostrophe. This was fixed.
    • July 2020 Resource Management SF: 00808612 URM-126740
      When an itemized set with deleted bib records was used for the “Delete Bibliographic records” job, the counter [X] in the message “The selected set contains [X] members” included the deleted records. In addition, the “Number of bibliographic records deleted” in the job’s report included previously deleted records. Both issues were fixed.
    • July 2020 Resource Management SF: 00818932 URM-127631
      Linking fields to related inventory – 773$$g (MARC21) or 461$$v and 463$$v (UNIMARC): when there were multiple subfields to filter both by year (Chronology I) and volume (Enumeration A or barcode), e.g. 461 $$v yr:1998 $$v no:19, related holdings records were filtered only according to volume (no:19) and not by year (yr:1998). This was fixed.
    • July 2020 Resource Management SF: 00661567 URM-121039
      A UResolver request with rft.doi containing a DOI's base URL caused an incorrect target URL. The base URL was removed from the rft.doi and fixed the target URL.
    • July 2020 Resource Management SF: 00517671 00742671 URM-123581
      DOI title parsed with many spaces that causes incorrect target URL. This was fixed.
    • July 2020 Resource Management SF: 00818824 URM-126445
      Previously, when creating a local authority in the MDE, it created a local authority record with the originating system id = '001' field, even if this originating system and originating system id already exist. This was fixed. Now, it validating if an authority record with the same originating system and originating system id already exist, and issues an error if so.
    • July 2020 Resource Management SF: 00453801 URM-80162
      When cataloguing in Hebrew, and adding a Hebrew letter directly after $$, the key Backspace does not work. When the 'show directional characters' option is on, the 'backspace' key does not work at all on '$$ש' (for example). If the 'show directional characters' option is off, only clicking twice on the backspace key works. Both issues were fixed.
    • July 2020 Resource Management SF: 00658944 00670815 00752783 URM-107912
      Previously, when saving a record and the record was not changed, the 'Modified By' did not change, but the 'Modification Date' did change. This was fixed. Now the 'Modified By' does change when the record is saved and no change was made.
    • July 2020 Resource Management URM-120794
      In some cases, when a network institution member tried to delete a network bib record (which cannot be deleted) from the Metadata Editor, a warning message was displayed, followed by a system error message; as a result, the record was deleted although it should not have. This was corrected.
    • July 2020 Resource Management SF: 00759171 URM-123223
      CNMARC profile - content code values for field 100 position 17 had the same value for 2 codes. The value of code k at position 17 of field 100 was updated.
    • July 2020 Resource Management SF: 00681621 URM-124955
      After browsing for an item with a specific source of classification or shelving scheme (call number type = source specified in subfield $2) through the 'Browse Shelf Listing' feature, editing it and then returning back to the MD Editor by selecting 'Cancel,' 'Save' or the 'Back' arrow, the user was not directed back to the Browse Shelf Listing with the previous parameters settings. This was fixed.
    • July 2020 Resource Management SF: 00814758 URM-127094
      Relinking holdings did not remove the merged empty holding. This was fixed.
    • July 2020 Resource Management SF: 00830152 URM-128670
      MD Editor New UI - problematic display of info message 'Alma has attempted to link the bib heading...'. This was fixed.
    • July 2020 Resource Management SF: 00702239 URM-122401
      The headings of field 490 were wrongly linked to authorities. The data was fixed (link removed), and added code that prevents future link of unauthorized fields.
    • July 2020 Resource Management SF: 00754256 00790005 00707903 URM-122586
      AUTH heading - punctuation was removed when linking an authority record via F3, even though parameter add_punctuation_for_heading was set to “N”. This was fixed.
    • July 2020 Resource Management SF: 00795572 URM-122687
      When Editing CZ NLI Authorities, no drop-down list for Expand from Template appeared. This was fixed.
    • July 2020 Resource Management SF: 00798137 URM-123375
      CZ authority records for NLI - F3 was not working in 37X-fields for some institutions. This was fixed.
    • July 2020 Resource Management SF: 00744438 URM-123935
      Field 075 (Type of entity) was missing in the MARC21 Authority profile. This was fixed.
    • July 2020 Resource Management SF: 00813630 URM-126702
      After updating a BARE authority record, the 035 was missing. This was fixed.
    • July 2020 Resource Management SF: 00820894 00629897 00667186 00504073 00500239 00602332 URM-99168
      An error was reported for a specific case when running the Update Inventory import profile. It was fixed.
    • July 2020 Resource Management SF: 00743313 URM-122636
      In some cases, a New Order import job that imported greater than 50 records that all used the same PO created the PO twice. This was fixed.
    • July 2020 Resource Management SF: 00821832 URM-126796
      Alma was slow when opening 'Monitor and View Imports'. This was fixed.
    • July 2020 Resource Management SF: 00819352 URM-128118
      While updating an existing import profile, the confirmation message indicated that a new profile was added. The feedback massage was fixed.
    • July 2020 Resource Management SF: 00811504 URM-126028
      312, 314, 320 and 330 UNIMARC fields were not converted to MARC21 fields during import. This was fixed.
    • July 2020 Resource Management SF: 00822760 URM-127112
      Contribution of SBN Authority record of type Authore failed after modification. A specific error message was added.
    • July 2020 Resource Management SF: 00822752 URM-127115
      Contribution of Titolo Uniformi authority records generated a different response from SBN than other authority types. Alma functionality was modified to handle this.
    • July 2020 Resource Management SF: 00553890 URM-90896
      For UNIMARC Browse Bibliographic Headings, some titles did not display properly. This was fixed. A full inventory re-indexing (including 'recreate bib headings') needs to be run for this fix to be fully functional.
    • July 2020 Resource Management SF: 00813711 00742324 URM-120796
      SBN integration - Search for fingerprint (T012) was missing for materials other than Music. Impronta search fields were added.
    • May 2020 Acquisitions SF: 703086 URM-113374
      The PO line advanced search did not take the scope into account. This was fixed.
    • May 2020 Acquisitions SF: 632395 URM-115763
      When executing import EOD for Electronic Resource and the Do not create Eactivation task field was selected, the creation of activation tasks was not skipped. This was fixed.
    • May 2020 Acquisitions
      The MR1 SUSHI harvest failed because the title was not sent. This was fixed.
    • May 2020 Administration and Infrastructure SF: 793075 URM-124418
      There is a new configuration option that can be set by Support to address this issue. See the UTF-8 Special Character Handling section in the May 2020 release notes for details.
    • May 2020 Administration and Infrastructure SF: 00675534 00694010 URM-111520
      Using '@' for email addresses in Swiss & German keyboards, in Edge and IE browsers did not work. This was fixed.
    • May 2020 Administration and Infrastructure SF: 733011 URM-118230
      Using the AltGr+S hotkey to type the Polish letter ‘?’ opened the Scan In Items page instead. This was fixed.
    • May 2020 Administration and Infrastructure SF: 00755480 00802287 00806050 00799674 00757561 00751297 00791907 00751472 00798026 00751896 00808876 00749748 URM-119902
      After the removal of the XML to Letter Admin page, XML notices continued to be sent with no way to remove them. This was fixed.
    • May 2020 Administration and Infrastructure SF: 00798967 00800321 00812794 URM-123468
      When trying to log in to Alma via SAML, and then, on the same browser, going to the local authentication, the second link displayed the IdP login page again. This was fixed.
    • May 2020 Administration and Infrastructure SF: 816651 URM-126016
      In the new Alma layout, clicking 'Save' after creating a physical item via the Metadata Editor saved the item successfully but did not leave the Metadata Editor page. This is fixed.
    • May 2020 Administration and Infrastructure SF: 713313 URM-118797
      We refresh the search labels cache after distributing code tables
    • May 2020 Administration and Infrastructure
      The ALTO search could not find punctuation marks. This was fixed.
    • May 2020 Administration and Infrastructure SF: 435157 URM-76369
      Slow upload times were noted in production. This was fixed.
    • May 2020 Analytics SF: 00206593 00659631 00788435 URM-57018
      In Analytics, data was not returned for roles in the Events subject area. This was fixed.
    • May 2020 Analytics SF: 560641 URM-96189
      The 'Updated by' field now shows the logged in user that made the change and not the default Ex Libris user.
    • May 2020 Analytics SF: 00622887 00791102 URM-101539
      In Analytics, in the Fulfillment subject area under the Loan Details folder, the Loan Note field contained no data even when the loan had a note. This was fixed.
    • May 2020 Analytics SF: 796152 URM-122872
      The Storage Location ID field was missing from the Physical Item Details folder in the Physical Item Historical Event SA. The field was added.
    • May 2020 API SF: 745259 URM-119717
      The Update Electronic Collection API did not work with JSON. This was fixed.
    • May 2020 API SF: 755430 URM-122647
      The GET Bibs API was returning an incorrect error message when searching for a non-existent Holding record by API. This was fixed.
    • May 2020 API SF: 720739 URM-123169
      The Create invoice API was slow in some cases. The performance of the API was improved.
    • May 2020 API SF: 742722 URM-120224
      In the PUT/POST Partners APIs, address, emails and phones did not support 'ALL' as an option. This was fixed.
    • May 2020 Digital Resource Management SF: URM-105985
      When uploading a folder with multiple files using the digital uploader, a timeout occurred before all of the files were uploaded. This was fixed.
    • May 2020 Digital Resource Management SF: 00746220 URM-122893
      When deleting digital representation and title, and restoring it back - process didn't re-index the mms, thus title didn't appear in the collection editor as assigned. This has been fixed. Tested successfully in release env.
    • May 2020 Digital Resource Management
      Labels generated by file name during upload were truncated after the first period to remove the file extension. This was changed to the last period in case the file name contains a period.
    • May 2020 Digital Resource Management
      Changes to a label in the digital representation editor were not saved after sorting the files of the representation. This was fixed.
    • May 2020 Fulfillment SF: 00560122 00704105 00795363 URM-94139
      Previously, refreshing a linked user duplicated the local Fines and Fees without identification. This was fixed.
    • May 2020 Fulfillment SF: 00671156 00740455 URM-109926
      Previously, if a user could not be deleted during the Purge Users job, the job failed. Now, the job will continue processing the other users.
    • May 2020 Fulfillment SF: 698572 URM-118612
      Previously, you could update the user Primary ID with value of one of its identifiers. This was fixed and will now cause a validation error.
    • May 2020 Fulfillment SF: 706151 URM-115419
      The block period of overdue blocks was sometimes one day longer than the expected period. This was fixed.
    • May 2020 Fulfillment SF: 755073 URM-121551
      Previously, when creating a new item in a department on the Scan-In Interface - Quick Cataloging, the item status appeared as In Place. This was fixed. Now, the item will automatically appear as in process.
    • May 2020 Fulfillment
      The Interested Users filter on the In Process Items page is now visible only to an acquisitions department.
    • May 2020 Fulfillment SF: 789946 URM-123566
      A performance improvement was made for laptop loans on the Physical Item Editor page.
    • May 2020 Fulfillment SF: 792211 URM-123254
      Previously, when a requested item was scanned and went into hold shelf processing, the label was not translated. This was fixed.
    • May 2020 Fulfillment SF: 752360 URM-120356
      After logging in successfully to an Alma account on a self-check machine, if the user attempted to toggle to the renew function, the application crashed with error “SelfCheck station is not available. Please contact library staff.” This was fixed.
    • May 2020 Fulfillment - Course Reserves SF: 813666 URM-125539
      In Alma, a reading list that has an large number of Instructors on the course has an issue in that the “view in Leganto” click through is not displaying has been fixed.
    • May 2020 Fulfillment - Resource Sharing SF: 00453083 00736130 00626932 00736136 00623005 00396861 URM-75696
      In some cases, an ISO message for lending resource sharing requests did not reach the partner but a 'failed to send' note was not added to the request. This was fixed.
    • May 2020 Fulfillment - Resource Sharing SF: 00715708 00789988 00797208 URM-115794
      Updating the Calendar via the Opening Hours caused the Locate By Fields to be removed from the library's configuration. This was fixed.
    • May 2020 Fulfillment - Resource Sharing SF: 00757888 00713861 URM-119196
      When a patron canceled a resource sharing request after the lender has already shipped an item to fulfill it, no return slip was sent to the circulation desk printer when receiving the item. This was fixed.
    • May 2020 Fulfillment - Resource Sharing SF: URM-121405
      A borrowing request that was mistakenly handled as Expired could not have been processed as Lost. This is not a valid scenario, but the Lost operation should not fail. This was fixed.
    • May 2020 Fulfillment - Resource Sharing SF: 00797850 00704709 URM-123060
      Multiple workflow profiles existed with the same name after a Resource Sharing distribution from the Network. This resulted in actions that are allowed in the profile not working as expected. This was fixed, the local duplicate entries were removed.
    • May 2020 Resource Management SF: 00744929 00755431 00822996 URM-120597
      Multiple Unpaywall Open Access service links were appearing, all leading to the same page. This was fixed.
    • May 2020 Resource Management SF: 00436593 00086774 00156886 00389885 00606963 00023575 00393482 URM-22889
      The number of items in the MD Editor > View Inventory > Holdings tab did not reflect the total number of items but, instead, just the items which were not in a temporary location. This was fixed; a new counter of items in a temporary location was added.
    • May 2020 Resource Management SF: 00619843 00566391 00758554 00576447 00528941 00569039 URM-95012
      Previously, not all operations were updating the Modified By column for Item History. This was fixed.
    • May 2020 Resource Management SF: 637543 URM-107900
      In the Item Sequences Configuration page, when using the Recent Searches functionality in the 'Library' field, the 'Library' field was populated with corrupt data. This is fixed
    • May 2020 Resource Management
      The 'Delete Holdings' link in the 'List of Holdings' page, which was visible to users with the 'Physical Inventory Operator' role, is now visible only to users who have the 'Physical Inventory Operator Extended' role.
    • May 2020 Resource Management SF: 653695 URM-110417
      Alma Analytics displayed collections in a library when none actually existed. This was fixed.
    • May 2020 Resource Management SF: 710203 URM-113873
      Previously, the short title appeared in the Community Zone Updates Task List. Now, instead, the full title appears in the Community Zone Updates Task List.
    • May 2020 Resource Management SF: 00721519 00785187 00713860 00725762 00735823 00715415 00721481 00740421 00724700 00738299 00727882 00725700 00746946 00730607 00687731 00758191 00818363 00726866 00728080 00822794 00733854 00742798 00715115 00686458 00799591 00725372 URM-114875
      The issues with deleting electronic collections have been fixed.
    • May 2020 Resource Management SF: 00715159 00716908 URM-115403
      This was a data issue. With a new data correction tool, Support is now able to address this data issue.
    • May 2020 Resource Management SF: 703769 URM-121350
      Group settings without date information were not handled correctly for all cases when publishing to Primo Central. This was fixed.
    • May 2020 Resource Management SF: 719349 URM-122918
      The holdings file included two entries for the same MMS ID (one with coverage lines and one without), and this caused the wrong availability to appear in Primo. This was fixed.
    • May 2020 Resource Management
      A portfolio with more than one Available For group with no date information caused the coverage line to disappear from the institution file. This was fixed.
    • May 2020 Resource Management SF: 00800627 00613840 URM-102638
      The output message to the System aborted job was changed.
    • May 2020 Resource Management SF: 00660320 00690610 URM-111081
      Portfolios with embargoes were not handled as expected in the 'Overlap and Collection Analysis.' New logic was added to apply the embargo on the coverage(s).
    • May 2020 Resource Management SF: 00704675 00803581 00713184 URM-118585
      Alma did not show thumbnails while Primo did show thumbnails. This is fixed.
    • May 2020 Resource Management
      The label of the item-level advanced search index 'Item Creation Date' was incorrect; it was 'Creation Date (Title).' It was changed to 'Creation Date (Physical Item).'
    • May 2020 Resource Management SF: 640658 URM-105350
      The “Starts With” operator in Advanced Search did not retrieve any results when the searched value contained an apostrophe (e.g. America’s). This has been corrected. This fix is relevant for all indexes and all search types (e.g. “Authorities”, “All Titles” etc.).
    • May 2020 Resource Management SF: 751131 URM-123194
      Support is able to use DB/Solr diff to resolve the specific problem, and additional development was completed to prevent future occurrences of the issue.
    • May 2020 Resource Management SF: 00715383 00715065 URM-116170
      In some cases, there were missing entries in the browse shelf listing. This was fixed. In addition, a data issue was fixed.
    • May 2020 Resource Management SF: 689944 URM-119007
      A link from the SFX API did not display properly in ViewIt. This was fixed.
    • May 2020 Resource Management SF: 703383 URM-119246
      Hanzi to Pinyin transliteration did not display certain words. This was fixed.
    • May 2020 Resource Management SF: 00457470 00669321 00380400 00812026 00797958 00634818 00559471 00800600 00629754 00528741 00797802 URM-73354
      Text in angle brackets <> was not displayed in the Metadata Editor F3/ View and in Browse Bib headings. This was fixed.
    • May 2020 Resource Management SF: 582715 URM-101757
      Accented characters in Alma were encoded in two different ways, depending on whether they were loaded through the migration process or through manual input via the Alma user interface. This was fixed.
    • May 2020 Resource Management SF: 00684642 00719956 00704993 00689036 URM-110441
      Validation Form of Material MARC21 adds alerts to records where there is no issue. This was fixed.
    • May 2020 Resource Management SF: 590998 URM-115687
      In the Metadata Editor, the controlled vocabulary did not work correctly for field 317. This was fixed for subfield $$5.
    • May 2020 Resource Management SF: 00710285 00600825 00686205 00753177 URM-118683
      In some cases, records from the Community Zone linked to the Network Zone linked to the Institution Zone appeared in the repository and could not be saved. This was fixed.
    • May 2020 Resource Management SF: 00713297 00698811 00683610 URM-110988
      When updating authorities by import from a different originating system, 'ghost' authority headings remained in the system. This was fixed.
    • May 2020 Resource Management SF: 751589 URM-121679
      In the Metadata Editor when using F3 on bibliographic headings and viewing more than one authority record and after clicking Edit on the authority record on the right side, all the viewed authorities were opened. This was fixed.
    • May 2020 Resource Management SF: 734584 URM-118588
      The 'Single match same inventory' parameter in the Repository PDA profile was disabled. This was fixed.
    • May 2020 Resource Management SF: 00802735 00803944 URM-124212
      The ISBN (exact sub-field match)/ 024 / 035 Match Method did not appear as a non-serial match method in the import profile. This was fixed.
    • May 2020 Resource Management SF: 00823462 00824326 00825553 00825572 00828484 URM-127410
      There was a problem with the search activation in the Electronic Resource Editor that caused search activations to fail. This was fixed.
    • May 2020 Resource Management URM-121862
      Based on customer feedback, the labels for CDI in the brief records on Alma where changed as follows:
      Active for Full Text in CDI only to Full Text active in CDI only
      CDI Search Rights to Search Rights in CDI
      CDI Full Text Rights to Full Text Rights in CDI
      CDI Full Text Linking to Full Text Linking in CDI
    • May 2020 Resource Management URM-115987
      There was an issue with the CrossRef collections caused by a recent release. Items from a CrossRef collection that where available for search were incorrectly flagged as full text available on Primo. This was fixed and already rolled out with an injection.
    • May2020 Resource Management SF: 00570136 00577949 00821547 00821550 00408242 00115067 URM-XXXXX
      Portfolio Resource Editor now presents data elements that are inherited from collection/collection service in a read-only mode.
    • March 2020 Analytics SF: 00718544 URM-120528
      When there is no Creative Commons License, its status is marked as NOTDETERMINED, which causes the data from the analytics report to not be displayed. This was fixed, and now the when there is no Creative Commons License, it is marked as NONE and the data is retained.
    • March 2020 Analytics SF: 00733619 URM-122124
      On the Fulfillment dashboard, for the 'Recalled items', 'Loans by title', and 'Loan items ratio' tabs, selecting a library from the prompt does not filter the data according to the selected library. This was fixed.
    • March 2020 Analytics  URM-122279
      Reports with fields from the Fulfillment > Location dimension did not work because the reports were not updated to the new name of the dimension 'Item Location at time of loan'. This was fixed.
    • March 2020 Analytics SF: 00717850 URM-118799
      An item which received today didn't filter in the items list, that was fixed.
    • March 2020 Analytics URM-12493
      Users with fund manager and purchasing operator could view and edit po lines from libraries out of the purchasing operator scope. This was fixed.
    • March 2020 Analytics SF: 00563366 URM-92971
      In the Invoices tab of a vendor, when the user clicks Export to Excel the Excel file had duplicate invoice records. This was fixed.
    • March 2020 Analytics SF: 00474875 00506687 00501341 URM-85673
      The PO Line index was enhanced to recognize TSVCC Chinese characters when searching PO Lines by title.
    • March 2020 Analytics SF: 00693673 00687775 URM-114755
      At last page of results in Receiving Department Items, clicking on the second or subsequent results navigates to the incorrect record. This was fixed.
    • March 2020 Analytics SF: 00710006 00720642 00738299 00789801 00804131 00724535 00785097 00789312 00686458 00751176 00666128 00732123 00755738 00793303 00785315 00699674 00742718 URM-113553
      The electronic activation job Ebook Central Academic Complete UKI Edition created many electronic collections due to a problem caused by restarts on the server or a one-time failure. This was fixed, and the activation job should activate only one electronic collection as expected.
    • March 2020 Analytics SF: 00668826 00654532 00658372 00661555 URM-109308
      In the PO Line Claim Letter, Subject and newSubject were not translated. This was fixed.
    • March 2020 Analytics SF: 00686401 URM-109902
      The Trial notification job sent the notification even for draft trials. This was fixed.
    • March 2020 Analytics SF: 00697123 00800887 00799574 URM-119242
      In the Missing Data page, duplication occurred due to case sensitivity. This issue was fixed in the new Monthly Usage Data tab which was developed as part of the SUSHI Performance handling story. See March release notes
    • March 2020 API SF: 00675602 URM-114024
      Retrieve Logical Set members API was repeating members in some cases. This was resolved.
    • March 2020 API SF: 00674879 00751850 URM-116514
      Update License API was not working with controlled vocabulary terms - this was fixed.
    • March 2020 API SF: 00751542 URM-119994
      Create hold-request API: when a user has 2 patron roles, one in the relevant library (expired) and the other in ANOTHER LIBRARY (without expiration date). When this patron will try to create a request for an item in the library where the expiration date for its role is in the past, although the TOU would enable this request, the request will be blocked in the UI, but worked by API. Now it will be blocked in the API as well.
    • March 2020 API SF: 00756689 URM-123638
      The GET-item-by-barcode API, when called with format=json was redirecting without including the format=json parameter. This was fixed.
    • March 2020 Administration and Infrastructure SF: 00792366 URM-122503
      On the Bulk Fine Waiving page, the Maximum Fine Threshold to Waive field now allows only numbers to be entered.
    • March 2020 Administration and Infrastructure SF: 00565625 URM-107765
      In some cases submitting any user details from Primo duplicated the user address. This was fixed.
    • March 2020 Administration and Infrastructure SF: 00526195 00683661 00594501 00593504 URM-115224
      Updating the password from Primo without entering the old password displayed a success message without actually updating the user password. The was fixed, an error message is now displayed.
    • March 2020 Administration and Infrastructure SF: 00784779 URM-121387
      A user name for anonymized users could not have been used for new users. This was fixed.
    • March 2020 Administration and Infrastructure SF: 00806662 URM-124521
      In some cases the schedule was not registered for the network so it was not triggered as expected. This was fixed.
    • March 2020 Administration and Infrastructure SF: 00726836 00811228 00723953 00728941 00734979 00712692 00809109 00745078 00724300 00789589 00812360 00728588 00726902 00724726 00809762 00752282 00721973 00809317 00689866 00720414 00811799 00812080 00724745 00715568 00745556 00728204 00802979 00727572 00754705 00728623 00753252 00806557 00810404 00726794 00741888 00752152 00727195 00732236 00810329 00752202 00708803 00790953 00725663 00812135 00740922 00751259 00720417 00749650 00754260 00723949 00810039 00727498 00747160 00727529 00743037 00753144 URM-116978
      The 'Synchronize Changes from CZ' job was hanging in status 'Pending'. This was fixed.
    • March 2020 Administration and Infrastructure SF: 00711365 00662917 URM-116808
      In the Browse Shelf Listing, the call number drop-down was not translated. This was fixed.
    • March 2020 Administration and Infrastructure URM-12472
      Could not publish to Primo from Alma Sandbox. This was fixed.
    • March 2020 Resource Management SF: 00725313 URM-118389
      When a record in the Metadata Editor is shared with the Network Zone and matches exist and the user selects to review them, the drop-down list of actions is limited to only Edit and Link actions. This fixes the issue where previously there were multiple, unclear steps presented.
    • March 2020 Resource Management SF: 00741644 00631221 00405927 URM-75309
      The inventory_item and hdemetadata tables now provide the date and changed-by operator values of deleted items for reporting in Analytics. Previously, the values provided by these tables did not reflect the date and operator of deleted items. This was fixed. Note that this fix applies to deleted items in Alma going forward from the implementation of this fix and that old data cannot be corrected.
    • March 2020 Resource Management SF: 00601054 URM-97778
      Previously when the 'display_specific_related_items' customer parameter was set to 'true,' there was an issue in the scenario described below where the related items from record “C” are displayed under record “A” only when searching for record “C,' and when searching for record “A” or “B,” record “A” is included in the results list, but the related items from record “C” are not displayed under it. Scenario: * Record A - A bibliographic record with no inventory related via the 773 field to two bibliographic records (and the two related records had items). * Two Related Records: &nbsp;&nbsp;&nbsp;* Record B - A record with subfield g (for a specific item) &nbsp;&nbsp;&nbsp;* Record C - A record with no subfield g (show all related records) This issue was fixed. Now, regardless of the search term, if record “A” is included in the results list, the related items from record “C” are displayed in addition to the specific related item from record “B.'
    • March 2020 Resource Management SF: 00604094 URM-99939
      Searching for item descriptions caused an exception in Solr when the description contained a period and an asterisk and the solr_searching_language customer parameter was set. This has been fixed.
    • March 2020 Resource Management SF: 00741138 URM-120149
      Previously, there was an unexpected change in the behavior of the Add Members to Set Job initiated from a file containing a list of barcodes when the file contained invalid barcodes. The job report showed 'completed successfully' and the 'Total invalid' count did not match the count of rows in the error file. This issue was fixed.
    • March 2020 Resource Management SF: 00657091 00798760 00801243 00796066 00788772 00673579 00799350 URM-118880
      When the books input file from Springer had two ISBNs, the job would only search for one of the ISBNs, and some portfolios weren't found. The job now looks for both ISBNs to make sure that every relevant portfolio available is activated. Also, a fix was added to the Excel writing job so that the Excel file is available even for very large input files.
    • March 2020 Resource Management SF: 00713934 URM-119076
      Previously, there was an issue where electronic collections were disconnected from their services in the user interface. This issue was fixed.
    • March 2020 Resource Management SF: 00717752 URM-119736
      Previously, there was an issue with duplicates created as a result of the activation job. This issue was fixed.
    • March 2020 Resource Management SF: 00752585 00745865 00790351 00759343 00803550 URM-120619
      Previously, there was an issue with duplicates created as a result of the activation job. This issue was fixed. No duplication of any type is created as a result of the activation job. The activation job will activate at once (not partially and without duplication) the desired collection from the Community Zone.
    • March 2020 Resource Management SF: 00759090 URM-120789
      The publishing platform was not accurate with the number of rows/records per file. This issue was fixed.
    • March 2020 Resource Management SF: 00696353 URM-118602
      Previously, an Institution Zone record was linked to a Network Zone record with the 461 using the MMS ID of the Network Zone record; and the PLK field was built using the parent record in the Institution Zone which is not correct for Primo's retrieval of the child record in the Institution Zone. This issue was fixed.
    • March 2020 Resource Management SF: 00673395 00658396 URM-124471
      Previously, some items automatically fulfilled requests without going through remote storage when returned through the NCIP check-in from AWS. This issue was fixed. The scenarios have been expanded in which the correct behavior should take effect.
    • March 2020 Resource Management SF: 00708955 URM-114669
      Previously, the Aleph Bridge import job resulted with many skipped holdings and items that failed with a general error. This issue was fixed.
    • March 2020 Resource Management SF: 00600825 URM-114040
      Linking an Institution Zone bibliographic record to a Network Zone record (that is linked to the Community Zone) creates an Institution Zone bibliographic record that is linked to the Community Zone, and the Network Zone bibliographic record is linked to the Community Zone.
    • March 2020 Resource Management SF: 00744652 URM-121689
      Previously, using the Borrowing request > Add from external search function in the the Alma Korean interface did not return any results. However, the same query using the Alma English interface did provide results. This was fixed.
    • March 2020 Resource Management SF: 00653455 URM-16986
      When a network member did a repository search and the held by holdings had the fields 866/867/868 with subfield $$a and $$z, the $$z information did not appear under 'Summary Holdings' in the search results. This was fixed.
    • March 2020 Resource Management SF: 00654188 00510181 URM-112532
      Previously, text in angular brackets was not correctly displayed in Get It. This was fixed.
    • March 2020 Resource Management SF: 00699001 00603065 00523838 00584547 00627509 00793741 00575243 00562853 00583035 00728906 00650084 00583399 00610138 00585549 URM-93030
      Previously, when saving a holdings record sometimes the 852 field disappeared. This issue was fixed.
    • March 2020 Resource Management SF: 00576280 00638264 URM-118289
      In the Metadata Editor, after creating a new holdings for a bibliographic record on the left, replacing it with another bibliographic record on the right, and then creating another holdings using the hotkey Ctrl+Alt+H, two new duplicated holdings were created instead of one. This was fixed.
    • March 2020 Resource Management SF: 00724927 URM-118952
      Previously, the HanziToPinyin normalization task performed the wrong linking when the configuration option was set to not show the script code. This was fixed.
    • March 2020 Resource Management URM-12052
      The character mapping was updated for the new Chinese author number characters and corresponding codes.
    • March 2020 Resource Management SF: 00754495 URM-121050
      Previously, the pop-up assistance in Hebrew for the 260 and 264 fields did not appear in certain cases. This issue was fixed.
    • March 2020 Resource Management SF: 00745730 00659624 URM-109379
    • March 2020 Resource Management SF: 00668788 URM-119110
      In MARC21, subfield $$e is no longer part of the matching between bibliographic and authority records for fields 800, 810 in bibliographic records and for fields 100, 110, 400, and 410 in local authorities.
    • March 2020 Resource Management SF: 00741789 URM-120433
      Previously, when editing a record and using F3, deleted authority headings appeared. This issue was fixed. The deleted authority headings were removed.
    • March 2020 Resource Management SF: 00791189 00753671 00433424 00799709 00723729 00735697 00800317 00743323 00726722 00751756 00724396 00724235 00723804 00809557 SF:URM-116960 Previously, the local authority update job failed for a few days because of a dependent job that synchronized changes from the Community Zone. After determining that both jobs could run in parallel, the dependency between the jobs was removed.
    • March 2020 Resource Management SF: 00700596 URM-114136 For UNIMARC 7xx authority records containing subfield $$e, the subfield was duplicated when linking it to a bibliographic record. This was fixed.
    • March 2020 Resource Management SF: 00706100 URM-114518
      As a result of corrupted data, bibliographic headings were not updated. The issue was fixed by removing the corrupted authority headings.
    • March 2020 Resource Management SF: 00666607 URM-117384
      The BIBFRAME view of bibliographic records was missing links for local authority records. This was fixed.
    • March 2020 Resource Management SF: 00757187 00653367 00657820 00611415 URM-109853
      The data keeping policy was improved, and the display of manual issues was restricted to one year back. This solution should reduce the number of oops errors on the 'Manual Handling' page.
    • March 2020 Resource Management SF: 00741219 URM-121620
      In some cases, the EOD import job with the import profile fails and shows 'Failed in Commit after calling NZ.' This was fixed.
    • March 2020 Resource Management SF: 00809119 URM-124891
      Previously, the Publishing MODS to Primo failed if the Related records information enrichment option was selected in the publishing profile. This was fixed.
    • March 2020 Fulfillment SF: 00641086 00680411 00686405 00652613 00796319 URM-105079
      In some cases, when saving a rule on the Request Pickup Configuration page, an error was generated. This was fixed.
    • March 2020 Fulfillment SF: 00693233 00695620 00809863 URM-115695
      When scanning in a requested item from a different institution, the Print Slip action did not work when the fulfillment_network_unique_barcodes customer parameter was set to FULL. This was fixed.
    • March 2020 Fulfillment SF: 00721687 URM-118104
      Previously, when Alma responded to a patron information request (SIP 63) at a self-check machine, if the patron's city was blank, the response (SIP 64) included a null string in the patron's address. This was fixed.
    • March 2020 Fulfillment SF: 00647458 URM-121295
      In some cases, when a requested item was checked out to a patron other than the requester, the loan was not blocked. This was fixed.
    • March 2020 Fulfillment SF: 00728860 URM-121729
      On the Manage Patron Services page, the counter for the number of items renewed using the Renew All action was sometimes incorrect. This was fixed.
    • March 2020 Fulfillment SF: 00756362 00614301 URM-101497
      When requesting an ASRS remote storage item, sometimes the request appeared in Alma with a status of Request Communicated to Remote Storage, even though the communication with the ASRS server failed. Now, if the communication fails, Alma cancels the request with cancellation reason: Failed to communicate with remote storage.
    • March 2020 Fulfillment SF: 00806219 00754850 00634538 URM-102637
      Previously, if the Send Requests to Remote Storage Job failed after it processed the requests but before it exported the XML file to the FTP (e.g. as a result of server restart or FTP connection error), the requests were not exported but in Alma they appeared as if they were. This was fixed. Now, if the job fails, the requests will remain in Waiting for remote storage status, so that they will be handled again on the job's next run.
    • March 2020 Fulfillment SF: 00678803 00724446 URM-114535
      Previously, on the Pick From Shelf task list, marking an entry as missing did not work if the item was in a temporary location and the holding had more than one item. This was fixed.
    • March 2020 Fulfillment SF: 00711645 URM-115009
      In some cases, an item that was loaned remained on the Pick From Shelf list. This was fixed.
    • March 2020 Fulfillment SF: 00727734 URM-117545
      Previously, when scanning a barcode and request ID in the Scan In Interface, if multiple requests existed, the item was always attached to the first request in the queue. This was fixed.
    • March 2020 Fulfillment SF: 00804714 00804727 URM-124252
      Performance improvements were added to Get It for the fulfillment network configuration.
    • March 2020 Fulfillment - Resource Sharing SF: 00719048 URM-116009
      cancellation reason and note to partner limited to 4000 char only
    • March 2020 Fulfillment - Resource Sharing SF: 00709245 00731881 URM-117304
      In some case the Reactivate row action did not display in the Resource Sharing Borrowing task list. This was fixed.
    • March 2020 Fulfillment - Resource Sharing SF: 00731363 URM-118496
      In some cases the itemShipped message contained incorrect bibliographic data. This was fixed
    • March 2020 Fulfillment - Resource Sharing URM-12084
      In some cases the Volume, Chapter, Pages fields were not sent to RapidILL. This was fixed.
    • March 2020 Fulfillment - Resource Sharing SF: URM-124096
      In the Receive Items screen, entering a due date caused, in some cases, the item creation rule to unexpectedly run and change the location value that was manually chosen by the user. This was fixed. The location is now recalculated only in case both the item policy & location are the default values and were not changed manually.
    • March 2020 Fulfillment - Resource Sharing SF: 00648258 00684788 00789471 URM-110602
      Dynamic URL was not encoded properly. This was fixed.
    • February 2020 Acquisitions SF: 00708476 URM-114580
      In the In Process Items page, the Modified By column displayed the first operator that modified the record instead of the last operator. This was fixed.
    • February 2020 Acquisitions SF: 00674166 00733466 URM-113435
      In some cases when a PO Line was closed and reopened the PO Line's title was changed to the title of the previous PO Line handled.This was fixed.
    • February 2020 Acquisitions SF: 00790022 URM-121727
      In some cases, the PO Lines that were created from EOD ignored the purchasing review rules and continued the workflow. This was fixed.
    • February 2020 Acquisitions SF: 00680283 URM-109990
      The additional information was missing from invoice export XML when created from Physical - Standing Order order line. This was fixed
    • February 2020 Acquisitions SF: 00702085 URM-112971
      Total invoice lines amount did not display sum under invoice line detail. This was fixed.
    • February 2020 Acquisitions SF: 00685088 00769493 URM-115522
      When changing the price in the invoice line page the Redistribute line did not happen automatically and required the user to click it. This was fixed and now redistribute lines will happen automatically when changing the price.
    • February 2020 Acquisitions SF: URM-111201
      In case of combined search result, the inventory context was wrong. This was fixed.
    • February 2020 Acquisitions SF: 00626738 URM-101546
      E activation link from advanced search did not work. This was fixed and works as expected now from both searches (simple & advanced)
    • February 2020 Acquisitions SF: 00671578 00532041 URM-92711
      Selecting the trials link to a survey form led to an error. This was fixed.
    • February 2020 Acquisitions SF: 00747060 00793722 00731551 00787767 URM-118769
      Executing the data corrector caused the available for field to be empty. This was fixed and now the available for field gets the value depending on the owner.
    • February 2020 Acquisitions SF: 00759302 00746552 URM-119198
      Typo was corrected in the message displayed to user when adding a fund to a PO Line or Invoice line and there was an encumbered warning.
    • February 2020 Acquisitions SF: 00710513 00699403 URM-112149
      In Rollover Ledgers Job > Add job, When the Create Allocation From is changed from the default 'None' to anything else and then selecting 'Copy' in Action, the value in the field Create Allocation From returned to None. This was fixed.
    • February 2020 Acquisitions SF: 00533293 URM-90993
      When an Order was sent via EDI for Standing order type of PO Line the location was not added to the Order in EDI file. This was fixed.
    • February 2020 Acquisitions SF: 00702666 URM-113306
      The PO was stuck because of duplicate POs that were created in the EOD. This was fixed. For documentation: The input EOD file was invalid: There is no option to sent po number with two different libraries. If such situation is needed, they should send vendor invoice number but not PO number.
    • February 2020 Acquisitions SF: 00540508 URM-98729
      When selecting Acquisitions > Import > Load Usage data it took more than seven seconds for the page to load. This was fixed.
    • February 2020 Administration and Infrastructure SF: 00792366 URM-122503
      In the bulk fine waiving screen, typing anything other than numbers will be prevented.
    • February 2020 Administration and Infrastructure SF: 00526195 00683661 00594501 00593504 URM-115224
      Updating password from Primo without entering the old password would display a success message, but without actually updating the user password. The was fixed, an error message is now displayed.
    • February 2020 Administration and Infrastructure SF: 00659374 00758194 00717340 00750708 00799429 URM-115819
      In some cases, when searching for a user with a hyphen the user was not found. This was fixed.
    • February 2020 Administration and Infrastructure SF: 00715406 URM-116270
      Changed name display so that when configuration specifies both name and preferred name, both are displayed even if they are identical.
    • February 2020 Administration and Infrastructure SF: 00103990 URM-113468
      Checking the SMS Preferred in Primo my account was not validating the SMS number. This was fixed, whenever a blank SMS number is submitted an error message is displayed.
    • February 2020 Administration and Infrastructure SF: 00661018 URM-112374
      The Auto Complete search for users in Japanese environments did not return results when the last name contained spaces. This was fixed.
    • February 2020 Administration and Infrastructure SF: 00695423 URM-112453
      The external resources screen has special implementation and therefor the options to choose the number of results to display cannot be used. Issue was fixed by removing the option to set a different number of results than 20.
    • February 2020 Administration and Infrastructure SF: 00705746 00657295 00792211 URM-107639
      In Manage Items Returns, the pop-up message when returning an item to be reshelved to a temporary location was not translated. This was fixed.
    • February 2020 Administration and Infrastructure SF: 00735668 00643584 URM-119955
      The IdP Reset Password pages, when used with a language-code parameter, did not follow with the requested language to error-message pages. This was fixed.
    • February 2020 Administration and Infrastructure SF: 00702404 URM-116263
      The One-Time Logic using email pages, when used with a CSS skin, did not follow with the requested skin to a error-message pages and the success screen. This was fixed.
    • February 2020 Analytics SF: 00717661 URM-117761
      When creating a report in the E-Inventory subject area with fields from the Bibliographic Details dimension, if the the Originating System field is added, some of the results where Originating System is expected to be "Unknown" did not appear in the report. This was fixed.
    • February 2020 Analytics SF: 00642793 URM-120604
      The Transaction Type Pie chart on the Acquisitions dashboard could not be edited to display the remaining allocation regardless of status. This was fixed.
    • February 2020 Analytics SF: 00637768 URM-107177
      Subfolders were not displayed properly in the Analytics Object List, which prevented dashboards from being added to the list. This was fixed.
    • February 2020 API SF: 00648237 URM-117138
      The IdP Reset Password pages, when used with a CSS skin, didn't follow with the requested skin to the page where new password is requested. This was fixed.
    • February 2020 API SF: 00646813 00725471 00678614 URM-113883
      "The Update-User API failed when the user had 'Receiving Operator' role with the scope of the institution, but with a service-unit parameter in a scope of a library. This was fixed.
    • February 2020 API SF: 00714379 URM-115380
      The Create Set API didn't work when creating a logical set by library/locations. This was fixed.
    • February 2020 API SF: 00720665 URM-116272
      When updating a portfolio using an API the history tab showed that a 'change' was made to library even though this field was not touched. This was fixed.
    • February 2020 Fulfillment SF: 00705635 URM-114570
      Export Users job sometimes failed to upload XML file due to invalid characters. This was fixed, the invalid characters are removed before retrying to upload the file.
    • February 2020 Fulfillment SF: 00729923 00704493 00703731 00608577 URM-99010
      If an item's barcode was changed while the item was in a work order, the item was sometimes not found when searching for it by the new barcode on the Manage in Process Items page. This was fixed.
    • February 2020 Fulfillment SF: URM-104684
      When SMS was activated, if the Loans - Overdue and Lost Item job failed to send an SMS message because there is no preferred SMS number on the User Detail page, the job completion status was set to Completed with Errors. Now the SMS message is not sent, without causing the job status to be Complete with Errors. The SMS messages which were not sent will continue to be reported inside the job report as before.
    • February 2020 Fulfillment SF: 00744296 00735221 URM-118360
      Placing a request on a title with multiple items that belong to remote storage failed under a specific configuration. This was fixed.
    • February 2020 Fulfillment SF: 00733124 00769441 URM-119749
      Previously, if a library was removed from a lost loan profile, the locations list still remained saved on the profile, even though it was not displayed in the UI. Additionally, if a library and locations were selected, removing the location(s) from the profile did not work. Both issues are fixed.
    • February 2020 Fulfillment SF: 00756362 00614301 URM-101497
      When requesting an ASRS remote storage item, sometimes the request appeared in Alma with a status of Request Communicated to Remote Storage, even though the communication with the ASRS server failed. Now, if the communication fails, Alma cancels the request with cancellation reason: Failed to communicate with remote storage.
    • February 2020 Fulfillment SF: 00639641 URM-103102
      Previously, in some circumstances, when a user requested a title from primo with two holdings or more, a pickup location appeared in the drop-down list that was not applicable. This was fixed.
    • February 2020 Fulfillment/Collaborative Networks SF: 00696523 URM-112518
      In some cases the Rota Templates and Assignment Rules did not update from the Network. This was fixed by applying a data corrector.
    • February 2020 Fulfillment - Resource Sharing SF: 00688547 00684300 URM-111280
      In some cases, the locate process did not run for a partner and therefor left it in the rota, despite not having any items for the request. This was fixed. The Manual Locate Job now runs on all relevant partners.
    • February 2020 Fulfillment - Resource Sharing SF: 00659455 URM-113982
      Chapter author and chapter title are now determined by the content of SLNP message
    • February 2020 Resource Management SF: 00674416 URM-117232
      When running the 'Change Holding Information' job and the holdings did not match the normalization rule, the holdings, incorrectly, were changed anyway. This issue was fixed.
    • February 2020 Resource Management SF: 00705243 URM-119995
      The Locations filter on the List of Items page does not present the correct list of locations, per the user interface language being used (German). This issue was fixed.
    • February 2020 Resource Management SF: URM-120103
      In the Physical Item Editor, the locations and libraries were not translated. This was fixed.
    • February 2020 Resource Management SF: 00696284 00709644 00719581 00714169 00730541 URM-114389
      In the items list, the filters did not include all the values across pages, that was fixed.
    • February 2020 Resource Management SF: 00703769 URM-113819
      When a title had a deleted portfolio available for the institution and also an active portfolio available for a group, the title would sometimes appear in the main institutional export (instead of just the export for the group institutions). This has been corrected.
    • February 2020 Resource Management SF: 00716894 URM-115498
      Two portfolios connected to two different bibliographic records with the same ISBN / ISSN did not link properly to the Community Zone. This was fixed. The recommended workflow is to avoid creating bibliographic records with the same ISBN / ISSN.
    • February 2020 Resource Management SF: 00720954 00735159 00719431 00759325 00788382 URM-118036
      When the Springer 'Upload electronic holdings' job was run, the job was not able to download the file due to special characters in the name. This issue was fixed.
    • February 2020 Resource Management URM-100322 SF:
      Since there is no physical inventory maintained in the Community Zone or the Network Zone, the Community Zone and Network Zone search options (icons / tabs / radio buttons) were removed from the Alma repository search for the Physical titles and Physical items search options.
    • February 2020 Resource Management SF: 00721075 00718384 URM-116977
      The 'Publish your Local Holdings Records (LHRs) to OCLC' publishing job mistakenly took a bibliographic record 035 field value and added it to the holdings record 004 field when there was already a 004 field, thus creating a second 004 field. The standard dictates only one 004 field, and OCLC requires that the 004 value be the OCLC number. Set the 'fix_multiple_004_in_oclc_publishing' customer parameter to 'true' to address this issue.
    • February 2020 Resource Management SF: 00759564 00719909 URM-116624
      Previously, when running the 'Add Members to Set' job (Admin > Manage Jobs and Sets > Manage Sets > select Add Set > Itemized) and 1) the 'From File' option was selected from 'Add Contents from File to Set' section and 2) the file selected contained one or more invalid IDs that could not be found in Alma, the job report did not count the invalid IDs and showed the job as completed successfully. This was fixed. When invalid IDs are encountered in the selected file, they are now counted and reflected in the job report that is created. For more information, see 'Creating Itemized Sets' at <a href=""https://knowledge.exlibrisgroup.com/..._Itemized_Sets"">https://knowledge.exlibrisgroup.com/..._Itemized_Sets</a>.
    • February 2020 Resource Management SF: URM-116658
      When creating a logical set (Admin > Manage Jobs and Sets > Manage Sets > select Add Set > Logical) after completing a filtered repository search, the repository search filter appeared on the Repository Search page (wizard step 2) of creating a logical set. This issue was fixed. A refresh is now completed to avoid this issue.
    • February 2020 Resource Management SF: 00393209 URM-108103
      When an institution's authority linking strategy is based on ID and an authority search for 'bibliographical records matching this value” was performed, the authority ID prefix was ignored and returned irrelevant records. This issue was fixed.
    • February 2020 Resource Management SF: 00793673 URM-122231
      The Primo VE facets filter appeared as code, labels were missing. The Primo VE user interface was fixed.
    • February 2020 Resource Management SF: URM-119332
      In the scenario where 1) there are two network bibliographic records A (primary) and B (secondary), 2) a member institution had a local bibliographic record linked to the network record B, and 3) the local record B was related to a PO line AND the member institution performs 'Merge Records & Combine Inventory' for the two network bibliographic records A and B, record B was merged into A; and B was deleted. However, when B was deleted the PO lines previously associated with record B were not associated with record A. This was fixed.
    • February 2020 Resource Management SF: 00681621 URM-111057
      After selecting an item to edit through the 'Browse Shelf Listing' feature and then returning back to the MD Editor by selecting Cancel, Save or the Back arrow, the user is not directed back to the Browse Shelf Listing with the previous parameters settings. This was fixed.
    • February 2020 Resource Management SF: 00686125 00668558 00668457 URM-111851
      In some cases, when a member institution performed 'Merge & Combine' from the MD Editor on two network records, the 'primary' network record was 'locked by System' for one hour. This has been corrected.
    • February 2020 Resource Management SF: 00738891 URM-118759
      The following values that were not up-to-date were corrected/added to the UNIMARC bibliographic metadata profile, field 105, positions 4-7: m = dissertation or thesis (original) 7 = academic thesis below the doctoral level, including the masters v = dissertation or thesis (revised) w = religious text
    • February 2020 Resource Management SF: 00714086 URM-118826
      In some cases, when a member institution performed 'Merge & Combine' from the MD Editor on two network records, the 'primary' network record was 'locked by System' for one hour. This has been corrected.
    • February 2020 Resource Management SF: 00591893 URM-111681
      Brackets were missing in the SBN to UNIMARC converted record when a title was preceded by one-letter articles. This was fixed.
    • February 2020 Resource Management SF: 00742361 URM-118862
      Access to the Authority reference file using F3 was not working with Polish characters for certain fields such as the 373 field. This was fixed.
    • February 2020 Resource Management SF: 00529800 URM-90896
      For UNIMARC Browse Bibliographic Headings, some titles did not display properly. This was fixed. Subfield e is now added to the headings (only for display and sorting purposes, not for matching or linking with Authority records) created out of the bibliographic fields 200 (Title and Statement of Responsibility), 225 (Series), and 410 (Series - LINKING ENTRY). A full inventory re-indexing (including 'recreate bib headings') needs to be run for this fix to be fully functional.
    • February 2020 Resource Management SF: 00553890 URM-91582
      For UNIMARC Browse Bibliographic Headings, there were issues with the display and indexing of fields 225 and 410 > $$e. This was fixed. Subfield e is now added to the headings (only for display and sorting purposes, not for matching or linking with Authority records) created out of the bibliographic fields 200 (Title and Statement of Responsibility), 225 (Series), and 410 (Series - LINKING ENTRY). A full inventory re-indexing (including 'recreate bib headings') needs to be run for this fix to be fully functional.
    • February 2020 Resource Management SF: 00746271 URM-119170
      Two new scheduling options were added for the SUDOC central catalog integration job.
    • January 2020 Acquisitions SF: 00752082 00727349 00730262 00729330 00744537 00729810 URM-118053
      When receiving multiple journals on the Received Items List page, an error occurred. This was fixed.
    • January 2020 Acquisitions SF: 00747168 00507810 00527371 00620630 00664064 00638787 00622470 00579221 00648063 00684313 00650554 00657599 00678414 00599063 00653943 00662030 URM-98703
      When an electronic colleciton is linked with a PO Line, the E-Resource activation status was not correctly specified. This was fixed. Now, In electronic collections, if the resource has at least one active service and one active portfolio OR it links to unsuppressed bib that has a URL, it will be considered as active in the PO Lines List and in the Resource List (drawer).
    • January 2020 Acquisitions SF: 00612971 00701400 00706193 00587292 00701536 URM-100630
      In some cases, the PO status was stuck in Sent even though all PO Lines were closed or cancelled. This was fixed.
    • January 2020 Acquisitions SF: 00703816 00713459 00678527 00678592 00715117 URM-108812
      Performance enhancements were made for invoice processing.
    • January 2020 Acquisitions SF: 00651755 URM-109667
      When a credit invoice had a VAT amount, the VAT percent was set to a negative value. This was fixed.
    • January 2020 Acquisitions SF: 00709722 URM-115706
      If a fund had a negative value, when selecting the fund in the invoice line, the encumbered amount was ignored and the fund was not returned. This was fixed.
    • January 2020 Acquisitions SF: 00547688 URM-92389
      Alma failed to load the ONIX-PL file downloaded from the EDItEUR standard site. This was fixed.
    • January 2020 Acquisitions SF: 00663075 00664985 00661891 URM-108877
      When releasing a record from In Process Items, the notification listed the title of the first record on the list, not the records that were released. This was fixed.
    • January 2020 Acquisitions SF: 00662798 URM-110901
      Funds with diacritics could not be searched without the diacritic in a PO Line. This was fixed.
    • January 2020 Acquisitions SF: 00695621 URM-111622
      When editing an unassigned purchase request, the user could not change the currency for the Estimated Cost field. This was fixed.
    • January 2020 Acquisitions SF: 00652867 00658378 00658935 00661365 00666910 00669189 00670391 00671242 00673591 00678741 00679884 00682352 00683646 00690546 00691907 00696311 00699969 00703191 00710470 00719113 00723885 00724781 00725759 00728128 00729934 00730292 00734835 00740983 00742975 00743371 00746137 00747245 00747401 00751481 00769472 00791166 00791277 00792112 00792823 00793073 URM-107644
      Previously, PO lines were stuck in an Auto Packaging status because the PO line was assigned to the previous user. When the user selected Save and Continue on the PO Line details page, the PO line progressed in the workflow to Auto Packaging and a message was displayed, PO Line was updated and in status Auto Packaging. When clicking the PO line link in that message, the PO line was opened in edit mode and assigned to that user. This was fixed. Now, when the user clicks the PO line link, if the PO line is not editable, it is opened in view mode and therefore will not be assigned to this user.
    • January 2020 Administration and Infrastructure SF: 00510675 URM-53307
      When editing a user record where the address was mandatory, but not entered, the validation stated that the preferred email was not selected. This was fixed.
    • January 2020 Administration and Infrastructure SF: 00674580 00583762 URM-97042
      When accessing the User Details page without edit permission, the action buttons appeared but when selected, caused the page to freeze. The buttons were removed for users without edit permissions.
    • January 2020 Administration and Infrastructure SF: 00481959 URM-108458
      The Circulation Desk Operator - Limited role could not update or delete blocks, even though the Create Remove Blocks privilege was enabled. This was fixed.
    • January 2020 Administration and Infrastructure SF: 00600227 URM-114615
      When creating a new user through Manage Patron Services, the header of the User Information section wasn't translated to the active UI language. This was fixed.
    • January 2020 Administration and Infrastructure SF: 00736416 URM-118390
      The last name was not appearing correctly in most letter emails. This was fixed.
    • January 2020 Administration and Infrastructure SF: 00671738 URM-115768
      Under macOS Mojave 10.14.4, for users with the Circulation Desk Operator - Limited role, Alma displayed a blank page when adding a circulation desk parameter. This was fixed.
    • January 2020 Administration and Infrastructure SF: 00727579 00721405 00634501 00690185 URM-105279
      In the Physical Item Editor, in the upper Summary section, Process type and Status were not translated. This was fixed. Additionalally, when a physical item has a Process Type that is “not-in-place” (such as Patron digitization request, Acquisition technical services, and Transit For Reshelving), it is not translated in non-English interfaces. This was fixed for the search results list of Physical Items, the upper Summary section of the Physical Item Editor, and the List of Items page.
    • January 2020 Administration and Infrastructure SF: 00706221 URM-117634
      Email-based login to Alma and Primo included a confirmation that the email was sent, but it was only displayed in English. It is now translated according to the user's preferred language.
    • January 2020 Administration and Infrastructure SF: 00435157 URM-76369
      Slow upload times were noted in production. This was fixed.
    • January 2020 Analytics SF: 00753341 00788057 00756900 URM-120726
      The missing field 'Preferred Phone Number' was added back to the subject area.
    • January 2020 Analytics SF: 00206593 00659631 URM-57018
      In Analytics, data was not returned for roles in the Events subject area. This was fixed.
    • January 2020 Analytics SF: 00612626 URM-102466
      Adding the 'Event end date' field to Analytics reports in the Physical Item Historical Events subject area for transit events that do not have an end date caused the report to not display any data. This was fixed.
    • January 2020 Analytics SF: 00694317 URM-111867
      The Publication Date is now populated according to the following prioritization: MARC field 264 subfield c, if empty then MARC field 260 subfield c, if empty then MARC field 008 pos. 7-10.
    • January 2020 Analytics SF: 00706573 URM-117379
      A link on the Loan per Library tab of the Fulfillment Dashboard to the Items Loaned per Patron Group tab was broken. This was fixed.
    • January 2020 Analytics SF: 00717478 00705114 URM-119317
      When the value of the Return Date field in Analytics (Fines and Fees > Loan Details) was null because the loan is not returned, reports erroneously displayed '01/01/1'. This was fixed and now the field is empty.
    • January 2020 API SF: 00739973 URM-118817
      In the user-request REST API and Webhook XSD, the manual_description field was missing. The field was added and will be retrieved in GET requests.
    • January 2020 API SF: URM-89097
      When running the GET Bib API with expand=e_avail against a network and portfolios that exist in the network, the sub-fields $$0 and $$a were not retrieved. This was fixed.
    • January 2020 API SF: 00717237 URM-116271
      In some cases, updating portfolios via the API was changing the Activation Date by one day. This was fixed.
    • January 2020 API SF: 00692798 00741188 00727951 URM-118075
      The Create Portfolio API was not working for a bibliographic record if the bibliographic record had no existing portfolios linked to it. This was fixed.
    • January 2020 API SF: 00731954 URM-118702
      When a patron fine was paid using an API, the Created By and Accepted By fields did not have an indication in the fine/fee transaction list that the payment action was done via an API. This was fixed. Now, when the patron fine is paid using an API, the Accepted By field will contain exl_api.
    • January 2020 Fulfillment SF: 00671263 00668563 URM-108570
      Previously, multiple overdue blocks could be created for the same returned loan. This was fixed. Now, a single block should be created for each loan. The block should be created according to the updated return date, if it is different than the return date.
    • January 2020 Fulfillment SF: 00537240 URM-92708
      In some cases, when sending multiple checkout messages for the same user on a self-check machine, the loan limit could be exceeded. A performance improvement was implemented to address this issue.
    • January 2020 Fulfillment SF: URM-116754
      On the Held By Patron and On Shelf tabs of the Active Hold Shelf, clicking loan links caused an error. The loans are no longer clickable.
    • January 2020 Fulfillment SF: 00137820 00073829 00684133 00133442 00218631 00361884 00684052 00137916 00326538 URM-34516
      In some cases, the booking calendar had available slots appearing as not available and vice versa. This was fixed.
    • January 2020 Fulfillment SF: 00491212 00570186 URM-93605
      The Resource Sharing distribution job did not correctly handle partners that were deleted in the Network Zone and created again with the same code. The job also blocked deletion of partners that are connected to completed resource sharing requests regardless of the BorrowingRequestsInactiveFilters code table. This was fixed. The job now updates these partners as required and consults the BorrowingRequestsInactiveFilters tables for deletion.
    • January 2020 Fulfillment - Resource Sharing SF: 00629860 URM-101799
      A renewal request sent to an itemless library was not processed correctly. This was fixed.
    • January 2020 Fulfillment - Resource Sharing SF: 00693541 URM-114270
      Previously any recall operation initiated by fulfillment processes on an item in resource sharing would process the recall. This was fixed. The recall will not be allowed if the item is in resource sharing and the status is Returned by Partner.
    • January 2020 Fulfillment SF: 00530054 00661611 00712276 00715321 URM-90855
      The Test Access functionality in the portfolio editor was not working for URLs with non-latin alphabet characters. This has been fixed.
    • January 2020 Resource Management SF: 00663766 URM-111871
      Field 530 was not mapped correctly to the oai dc field when publishing a MARC record to the oai _dc format. This was fixed.
    • January 2020 Resource Management SF: 00700517 URM-117991
      Ex Libris fixed the customer data and deleted the additional portfolios.
    • January 2020 Resource Management SF: 00509995 URM-87631
      The wrong permission flag was removed from tar compression code.
    • January 2020 Resource Management SF: 00720896 URM-118152
      This was fixed by support with 18.10.
    • January 2020 Resource Management SF: URM-118155
      In Publishing to Primo, authority enrichment information was not published for UNIMARC records that used the working with ID strategy and had links to multiple authority headings per field. That was fixed.
    • January 2020 Resource Management SF: 00673395 00658396 URM-109622
      If an item came back from a resource sharing request to its remote storage by an NCIP check-in message, it would have automatically started the next resource sharing request instead of being put in place. This was fixed.
    • January 2020 Resource Management SF: 00679188 URM-111160
      Previously, when a remote storage item was checked in via an NCIP check-in message, Alma did not check if the item did indeed belong to remote storage, but, instead, automatically put it in place. This was fixed. Alma is now checking if the item belongs to the current remote storage.
    • January 2020 Resource Management SF: 00663701 00630971 00637626 00565091 URM-95584
      When viewing an in-transit item from search results where the To Circulation Desk is empty, then viewing a second item where the To Circulation Desk is not empty, and subsequently, returning to the first item, the first item shows the To Circulation Desk of the second item instead of remaining empty. This was fixed.
    • January 2020 Resource Management SF: 00653455 URM-16986
      When a network member did a repository search and the held by holdings had the fields 866/867/868 with subfield $$a and $$z, the $$z information did not appear under 'Summary Holdings' in the search results. This was fixed.
    • January 2020 Resource Management SF: URM-117907
      In Repository Search, a tooltip was added to the orders and requests links.
    • January 2020 Resource Management SF: URM-110590
      Browsing bibliographic headings for the local call number 09X did not bring the user to the correct place in the browse bibliographic headings list. This was due to a delimiter between subfields that was responsible for wrong sorting. This was fixed. Reindexing is required for this to be fully functional.
    • January 2020 Resource Management SF: 00576280 00638264 URM-102907
      When the MD Editor is open in split mode while editing a bibliographic record in one and a holdings record in the other, creating a new holdings record results in two holdings where one is related to the wrong bibliographic record. This issue was fixed with the exception of creating a new holdings record using the shortcut key ctrl+alt+h. The full fix will be handled in a later release.
    • January 2020 Resource Management SF: 00628384 URM-103859
      For a member institution, clicking on the record's link in the list of matches in the MD Editor displays the Community Zone icon instead of the Network Zone icon. This was fixed. In addition, when an Network Zone record already exists in the draft list, the record's link is now hidden for this record in the list of matches.
    • January 2020 Resource Management SF: 00721252 URM-117238
      The contribution of serial records to CALIS did not work. This was fixed.
    • January 2020 Resource Management SF: 00720432 URM-117535
      The Preferred Term Correction job removed subfields from the 651 field because of wrong matching. This was fixed.
    • January 2020 Resource Management SF: 00634901 URM-108924
      Subdivisions were duplicated in records with trailing punctuation (period). This was fixed.
    • January 2020 Resource Management SF: 00719942 00700533 URM-113778
      A new setting has been enabled that handles subfield u in the following manner: * Subfield u is ignored while browsing headings suggestions (F3) * Subfield u is kept after selecting the suggested heading * Subfield u is not part of the linking process * Subfield u is not part of the Preferred Term Correction process Reindexing needs to be run for this to be fully functional.
    • January 2020 Resource Management SF: 00702435 00639130 URM-116437
      The output file of the 'Duplicate Title Analysis' job included deleted bib records. This has been corrected.
    • January 2020 Resource Management SF: 00647258 00694008 00531194 00604766 00493144 00644802 URM-85353
      If the import finds at least one match, and the upon match method is 'DO NOT ADD,' then the import report did not display the matched records. This was fixed.
    • January 2020 Resource Management SF: 00691126 00618086 URM-102508
      After the import job completed successfully, no email report was sent for the import job. This issue was fixed.
    • January 2020 Resource Management SF: 00727936 00654643 00714134 URM-102645
      View Import on the Resolve Import Issues page led to an Oops error. This issue was fixed.
    • January 2020 Resource Management SF: 00630562 URM-103457
      When importing UNIMARC/CNMARC bibliographic records using the ISSN match method (exact subfield match), records that had position 6 of the LDR as 'l - Electronic Resources' and position 7 as 's - Serial' were not matched correctly by the ISSN. This was fixed.
    • January 2020 Resource Management SF: 00685475 URM-113391
      The crosswalk of OAI DC Format to MARC21 on the Repository profile was not supported. This issue was fixed.
    • January 2020 Resource Management SF: 00731980 00676139 URM-114704
      the indication rule was not applied for import profiles defined in a network member institution when the 'Use Network Zone' parameter was checked in the import profile. This has been fixed.
    • January 2020 Resource Management SF: 00693333 URM-115675
      Import with an Excel file that contains lines with one of their cells containing a space character was not processed correctly. This was fixed.
    • January 2020 Resource Management SF: 00706413 00734597 URM-113825
      When contributing a record to CALIS, subfields a and z of the 920 field were saved in the wrong order. This was fixed
    • January 2020 Resource Management URM-117613
      The manner in which Alma processes identifying records that need to be reviewed for change based on new or updated authority records has been modified for institutions that have implemented ID-based authority record linking. Now for institutions using the ID-based authority linking method when there are new or updated authority records, Alma uses an ID-based method for identifying bibliographic records that need to be checked for potential linking by the linking process. This ensures that the Authority Control Task List entries reflect more accurate and meaningful changes.
    • January 2020 Digital Resource Management SF: 00708419 URM-116885
      The universal viewer was not working for non-production environments in the EU region. This was fixed.
    • June 2020 Fulfillment - Course Reserves SF: 00661451 URM-126009
      The course code was not included in the file name when exporting lists to PDF in bulk. This was fixed.
    • June 2020 Fulfillment - Course Reserves SF: 00808391 URM-127332
      When changing the Material Type from Article to Electronic Article, changing the secondary type changed the fields in the citation's metadata section in the primary type. This was fixed.
    • June 2020 Fulfillment - Course Reserves SF: 00732979 URM-121988
      Copyrights for chapters were being approved when non-numeric characters were entered. This was fixed.
    • May 2020 Fulfillment - Course Reserves SF: 00828403 103039
      When editing a book chapter citation, duplicate Publication Date and Place of Publication fields appeared and displayed identical information in the Main section and More Item Details section. This was fixed.
    • March 2020 Fulfillment - Course Reserves SF: 00558998 103039
      The Course Loader job report did not show a deleted lists event (using the Delete operation). This was fixed.
    • March 2020 Fulfillment - Course Reserves
      The course loader job performance has been improved.
    • March 2020 Fulfillment - Course Reserves SF: 00557726 URM-94073
      In the Alma Citations brief display, the Pages, Chapter Author, and Chapter Title fields were hidden by default and have been added. This was fixed.
    • March 2020 Fulfillment - Course Reserves SF: 00573621 00699342 00706209 URM-113593
      The course loader file was processing duplicate files. This was fixed.
    • March 2020 Fulfillment - Course Reserves SF: 00711351 URM-119786
      Interface enhancements were made on the owner subscription letter.
    • March 2020 Fulfillment - Course Reserves SF: 00688241 00709144 00735529 URM-119959
      Copyright recalculation does not function after rollover. This was fixed.
    • March 2020 Fulfillment - Course Reserves SF: 00736258 URM-120057
      Submit button for digitization requests not functioning for a specific journal. This was fixed.
    • March 2020 Fulfillment - Course Reserves SF: 00797118 URM-122962
      Citation processing rules created purchase requests without fulfilling the rules. This was fixed.
    • February 2020 Fulfillment - Course Reserves SF: 00665112 URM-108823
      Analytics data does not include owners added using the set_instructors_as_owners flag. This was fixed.
    • January 2020 Fulfillment - Course Reserves SF: 00725347 00729516 URM-117768
      The resource locate was being triggered when no changes were made in the citation. This was fixed.
    • January 2020 Fulfillment - Course Reserves
      Previously, when the resource_locate_multiple_matches parameter was set to manually, and multiple results were matched, selecting Save and Run returned the user to the Edit Reading List. This was fixed. Now, the repository search page will appear, and the operator will be able to select the title.
    • January 2020 Fulfillment - Course Reserves SF: 00728534 00713135 URM-116302
      When selecting the All tab of a Reading List, an error was displayed. This was fixed.
    • January 2020 Fulfillment - Course Reserves SF: 00731299 00583061 URM-118224
      After September, the Number of Citations field counted only citations with usage. It was fixed and now it includes all citations. The Number of Citations now includes the number of citations in the reading list without any relation to the usage. The Activity Score field is impacted similarly as its calculation is based on the Number of Citations field.
    • January 2020 Fulfillment - Course Reserves SF: 00717468 URM-118226
      The Course Code field, which appears in the Course Reserves and Usage, has been increased to 255 characters.
    • Was this article helpful?