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

    Alma 2021 Release Notes

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

    Make the Most of August's Release

    Action Items

    Integration with Netpunkt - Danish libraries integrated with Netpunkt can use an improved integration with Alma by placing Alma’s Internal Identifier in the note field of the Netpunkt request form. This will enable Netpunkt to update Alma with relevant updates.

    The Increase of Analytics Export Size - We are happy to let you know that we have been working to increase the maximum size of exports from Alma Analytics, and it has been moved from 500k lines (in csv format) to 10 million rows.  You should now be able to create a single report to gather the data you need, and as needed, export it from Alma Analytics.

    Patron Waitlist Management for Controlled Digital Lending - A waitlist of patrons for accessing a controlled digital lending resource can be configured under Alma Configuration > Access Rights. Once the “concurrent users” policy is selected, a waitlist configuration section will be displayed, enabling to define factors such as grace period for accessing the resource and waitlist activity hours. Patrons will then be provided with a new waitlist registry page and provided with relevant details during the viewing session.

    Resource Sharing Directory - To add your institution to the Resource Sharing Directory, please contact Ex Libris if you would like to join a pod.

    Define a Specific Time Frame While Manually Harvesting R5 SUSHI Data - Do you use the option to manually retrieve SUSHI reports? Note that you can now specify the time period to be harvested.

    Upcoming Issues to Note

    Sandbox Refresh

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

    TLS Cryptographic Protocol Support 

    Read the following to avoid service disruptions.

    TLS is a cryptographic protocol that provides authentication and data encryption between different endpoints (for example, the user’s desktop and the application server). Various vulnerabilities (such as POODLE and DROWN) have been found in TLS versions 1.0 and 1.1 in recent years. 

    As announced in the latest security update, to avoid security vulnerabilities and to align with industry standards, Ex Libris will block TLS 1.0 and 1.1 traffic for Alma API in production environments and will support only TLS 1.2. The deprecation plan which was communicated will begin by October 2021 and will be concluded by May 2022:

    • Canada – October 17, 2021
    • APAC – February 20, 2022
    • Europe – March 10, 2022
    • America – May 15, 2022

    For practical steps to be taken, see  Ex Libris Higher Education Platform API - deprecation of TLS 1.0 and TLS 1.1.

    You can find additional information on TLS at:

    SAML Certificate Workflow Update

    Starting in August 2021, to accommodate the updated expiration policy of the certificate vendors, the signed certificate will be issued twice yearly.

    For example, the certificate made available in August 2021 will expire in June 2022 and the certificate made available in February 2022 will expire in December 2022. This means that institutions that wish to use the signed certificated must update it twice a year.

    Ex Libris highly recommends using the provided self-signed certificate to reduce the frequency of certificate updates.

    Starting with the October release, the Top Trending Books dashboard widget will be removed from the list of available dashboard widgets. The Top Trending Books dashboard widget is currently available for institutions that opted into sharing their anonymized data (Configuration menu > General > Data sharing Selection and development section). The deprecation of this dashboard widget is done due to the low adoption of institutions who opted into the "Selection and Collection Development" functionality and this is imperative in order to conduct analysis and provide reliable and effective data to be presented within the widget.

    September Release Sneak Preview

    The September 2021 is a maintenance release that will not contain any new features.

    Download a PDF of the Release Notes and Resolved Issues.

    Make the Most of July's Release

    Action Items

    Open the descriptions in the Genders code table for update - The list of gender value is now fully customizable. You can disable existing values, or add new values by changing the description and activating any of the added place holder categories. This will affect the list of gender options in the user form.

    Library input parameter to user registration rules - The User Registration Rules can receive a library input. This way, you can set up separate rules depending on the library at which the registration took place. For example, registering at a library desk in some libraries may be set up to trigger a fee and grant patron permissions at that library for a couple of months, while registering at a library desk in other libraries may be set up to not trigger a fee and grant patron permissions at that library for a full year.
    Push user records to ILLiad - If you use Alma’s capability to push borrower requests into ILLiad, you can now do that without having preloaded the user records in ILLiad. Your ILLiad partner record can be set up to push also the patron information into ILLiad in real time.

    Upcoming Issues to Note

    Sandbox Refresh

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

    SAML Certificate Workflow Update

    Starting in August 2021, to accommodate the updated expiration policy of the certificate vendors, the signed certificate will be issued twice yearly.

    For example, the certificate made available in August 2021 will expire in June 2022 and the certificate made available in February 2022 will expire in December 2022. This means that institutions that wish to use the signed certificated must update it twice a year.

    Ex Libris highly recommends using the provided self-signed certificate to reduce the frequency of certificate updates.

    Starting with the October release, the Top Trending Books dashboard widget will be removed from the list of available dashboard widgets. The Top Trending Books dashboard widget is currently available for institutions that opted into sharing their anonymized data (Configuration menu > General > Data sharing Selection and development section). The deprecation of this dashboard widget is done due to the low adoption of institutions who opted into the "Selection and Collection Development" functionality and this is imperative in order to conduct analysis and provide reliable and effective data to be presented within the widget.

    August Release Sneak Preview

    Click here to view August's sneak preview.

    Download a PDF of the Release Notes and Resolved Issues.

    Make the Most of June's Release

    Action Items

    'Type of Request' Indicator on Patron Request or Work Order - A new "Item is requested by the library" block preference can be used to activate alerts about the specific request type on the item when items are scanned in.

    New Reports Added to Consortia Folder - Some great new Consortia Analytics reports have been released for help with duplicate collection analysis as well as overlap analysis within a consortia. These can be used as is, or copied and modified for your particular need.

    New Dashboards Added to Alma Analytics - A new set of OTB dashboards is being released, which provides a comprehensive set of reports for all activities of a library. These will also be added as preconfigured analytics objects – if you want to change these settings you can do so after the release is deployed.

    Assigning Recommendations - This great new feature supports the ability to configure specific recommendations for specific staff users, and also to be able to assign them between the relevant users for handling.

    Upcoming Issues to Note

    SAML Certificate Workflow Update

    Starting in August 2021, to accommodate the updated expiration policy of the certificate vendors, the signed certificate will be issued twice yearly.

    For example, the certificate made available in August 2021 will expire in June 2022 and the certificate made available in February 2022 will expire in December 2022. This means that institutions that wish to use the signed certificated must update it twice a year.

    Ex Libris highly recommends using the provided self-signed certificate to reduce the frequency of certificate updates.

    July Release Sneak Preview

    Click here to view July's sneak preview.

    Download a PDF of the Release Notes and Resolved Issues.

    Make the Most of May's Release

    Action Items

    Generate Representation Labels from Templates - You now have the flexibility to generate bulk representation labels, based on a label template that could include constant strings or bibliographic details with an optional regular expression.

    Upcoming Issues to Note

    SAML Certificate Workflow Update

    Starting in August 2021, to accommodate the updated expiration policy of the certificate vendors, the signed certificate will be issued twice yearly.

    For example, the certificate made available in August 2021 will expire in June 2022 and the certificate made available in February 2022 will expire in December 2022. This means that institutions that wish to use the signed certificated must update it twice a year.

    Ex Libris highly recommends using the provided self-signed certificate to reduce the frequency of certificate updates.

    June Release Sneak Preview

    Click here to view June's sneak preview.

    As many of you already know, Alma development periodically needs to take a "back seat," and maintenance, cloud infrastructure, and other important tasks need to be handled in order to ensure that Alma meets the highest standards of performance and high availability. The April 2021 release is devoted to such tasks.

    We would also like to take this opportunity to update you on the following:

    Chat Support

    On February 14th, we were excited to roll out online chat support for Alma and Leganto in our European instances. And on March 15th we expanded this service to our North American Alma and Leganto customers. This is a gradual rollout, with chat support for all regions as our end vision.

    We have received over 100 chat sessions with a 100% satisfaction rate in the last week.

    In addition, we're happy to share with you some of the great feedback posted:

    • "The chat function is user friendly, quick and efficient. So is the representative who assisted."
    • "Quick reply and help, excellent service for simpler questions."
    • "Pleased to be able to get quick answers to small questions without having to open a case."

    User Experience

    Through 2019 and 2020 new UI concepts were introduced, in different areas of Alma. We will be implementing additional new UI concepts throughout 2021such as side-by-side display. For more information see Alma new UI concepts.

    With the April 2021 release, the New Metadata Editor reached an important milestone of providing full functionality by enabling the Rules management model. At this time, the New Metadata Editor became the default editor; we encourage all catalogers to use this new editor. Catalogers can still switch to the classic Metadata Editor if they come across issues that hinder their workflows. In these cases, please open a support case. Ex Libris is doing its best to address all critical issues before the new Metadata Editor becomes the only editor by June 2021 release.

    Analytics

    Look out for some important changes coming up regarding Alma Analytic dashboards in the May and June releases of Alma.

    In May, the following new dashboards will be available. 

    • Fulfillment - Loans Returns and Overdue
    • Acquisitions – Claims
    • Acquisitions – Fund

    These dashboards were made together with Ex Libris and a group of institutions who contributed their ideas and analytics knowledge to the project.  Each of the dashboards will have a default Analytics Object of type Dashboard.

    Additional dashboards with an Analytics Objects of type ‘Dashboard’ will be available as part of the June Release, enabling them to be used via a menu option from the Analytics menu in Alma.  All analytics objects can be customized by the institution.

    Cloud Apps

    Cloud Apps were released in the second half of last year. Already there are 24 apps released and available for use! This includes apps written by Ex Libris, by partners, and by members of the community.

    Apps have been installed thousands of times by hundreds of users. If you’re just getting started with Cloud Apps in your institution, check out the announcement blog and promotional video, the directory of currently available Cloud Apps, and instructions for enabling Cloud Apps for use in your institution.

    If you’re interested in developing an app, check out the Developer Network. This month the Australia/New Zealand User Group is sponsoring a hackathon to encourage the community to write apps that address the specific needs of their members. If you’re interested in sponsoring a hackathon in your region, we’re happy to help- reach out to us!

    This month’s Cloud App is the Interlibrary Add-on,  an app that helps to handle Borrowing Request activities more smoothly.

    clipboard_e070493f160be88c1a316755ce226264d.png

    Idea Exchange

    We have created a chart of completed ideas by subject area. As you’ll be able to see by the highest number of completed ideas, Fulfillment is still a very important area of a library’s activities. Analytics, Resource Sharing and Acquisitions are the next areas with the most completed ideas.  

    clipboard_e05bfa598ec253b383a409eb70dcd51b7.png

    Global Knowledge Delivery

    eLearning

    A re-designed Alma Essentials training kit was recently released as well as new modules for Rialto kit. We continuously update existing content and release new eLearning modules and courses, across all products, moving away from long tutorials towards micro learning, short and specific videos.

    Customer Education

    Primo VE: Become an Expert webinar - a 12-part webinar series is currently in progress, with over 4,500 registrants to date. You can sign up for future sessions or watch recordings here.

    Premium Services

    To support the evolving needs of libraries, Ex Libris offers an array of Premium Services for libraries that are in production with Ex Libris solutions. These services will help you to improve efficiency, deploy new features or services, and learn more about functionality.

    Learn more about our various offerings through the links above, or contact us for more information: Premium.Services@exlibrisgroup.com

    Alma Documentation Update 

    The Resource Management section of the Alma Documentation has been split into smaller sections and reorganized to make it clearer where information is, making it easier for you to find content when you need it.

    The new sections are:

    GuideMe 

    Recentlywe released new walkthroughs on CDI, SUSHI Account, Course Management, Activating an Electronic Collection and more, check them out. See full list and more information here. 

    May Release Sneak Preview

    Click here to view the May release sneak preview.

    Download a PDF of the Release Notes and Resolved Issues.

    Make the Most of March's Release

    Action Items

    Denied Note for Unregistered Users - Institutions can now add a secondary denied note for unregistered users, which will allow displaying a different message to logged out and logged in users who are denied access to a digital resource.

    Upcoming Issues to Note

    New GuideMe Workflows

    This month sees three new GuideMe walkthroughs:

    1. Avoid Duplicate Ebook Results in CDI
    2. Enable Collection for CDI Discovery Only
    3. Configure a SUSHI Account.

    See the GuideMe FAQ page for more information about all the GuideMe workflows. 

    SAML Certificate Workflow Update

    Starting in August 2021, to accommodate the updated expiration policy of the certificate vendors, the signed certificate will be issued twice yearly.

    For example, the certificate made available in August 2021 will expire in June 2022 and the certificate made available in February 2022 will expire in December 2022. This means that institutions that wish to use the signed certificated must update it twice a year.

    Ex Libris highly recommends using the provided self-signed certificate to reduce the frequency of certificate updates.

    Next Release Sneak Preview

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

    Download a PDF of the Release Notes and Resolved Issues.

    Make the Most of February's Release

    Action Items

    Identifier Based Locate - You can fine tune the resource sharing locate profiles to prefer identifier (such as ISBN) based locate and use other information (such as title) only if the borrowing request has no ISBN.

    Book chapter form - The Primo resource sharing request form can be enhanced to enable easier filling in of book chapter information. This is achieved by showing the chapter relevant fields (chapter/pages) only if the patron explicitly indicates that a book chapter is requested. The requested format will automatically be ‘digital’.
    Allow automation of branch requesting for RS serial requests - As resource sharing lenders, you can have Alma automatically create pickup request at branch libraries (for physical and for digital supply). When the requested resource is a serial or multi volume, you can now have Alma create a general hold/digitization request. This is in addition to the previously only option to automatically create a title level request. This would enable an automated branch requesting process for libraries that have cataloged their serial issues.

    Upcoming Issues to Note

    Sandbox Refresh

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

    SAML Certificate Workflow Update

    Starting in August 2021, to accommodate the updated expiration policy of the certificate vendors, the signed certificate will be issued twice yearly.

    For example, the certificate made available in August 2021 will expire in June 2022 and the certificate made available in February 2022 will expire in December 2022. This means that institutions that wish to use the signed certificated must update it twice a year.

    Ex Libris highly recommends using the provided self-signed certificate to reduce the frequency of certificate updates.

    As of February 1, 2021, Leganto will use the Copyright Clearance Center’s standard fee of $3.50 per order line item (citation), instead of the $0.45 discounted fee which is charged today. In the transition period, the calculation will be as follows: Any citation where the first download occurs before February 1st will retain the current $0.45 fee for the duration of the course. Citation that are not downloaded until after February 1st will include a fee of $3.50.
    For more information about the integration between Leganto and the CCC, see Clearing Copyrights Through the Copyright Clearance Center (CCC).

    Next Release Sneak Preview

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

    Download a PDF of the Release Notes and Resolved Issues.

    Make the Most of January's Release

    Action Items

    Receiving Digital Files for Borrowing Resource Sharing Requests - Two new options are included in this release for libraries that receive or ship digital files for fulfilling resource sharing requests:

    1. If you have received an attachment as a borrower, you can upload it to the borrowing requests task list and have Alma send an email with a link to the patron
    2. When both the borrower and lender are Alma institutions, the lender can trigger the borrower side to send an email directly to requesting patron, without requiring that the borrower exposes the patron’s email to the lender.
    Retry Rapid Requests - If you are using Rapid ILL in an integrated manner, you can now override Rapid self ownership blocks using a dedicated "Override local holding" action in the Alma task list.
    Improved Inventory Import - As part of the import profile, you can now define how to map the imported records to existing records in Alma.
    Additional Recent Entities Added - This release adds three key configuration entities (Code table, mapping table and integration profiles) to the Recent Entities slide out, enabling you to easily view recent changes made by you, and in a single click, navigate back to the specific table or profile you modified.

    Upcoming Issues to Note

    Sandbox Refresh

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

    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

    Completed

    NA06

    Completed

    NA07

    Completed

    NA91

    Completed

    EU00

    Completed

    EU01

    Completed

    EU02

    Completed

    EU03

    Completed

    EU04

    Completed

    AP01

    Completed

    CA01

    Completed

    CN01

    January 2021

    Change to the Community Zone collection used for SAGE for orders originating from OASIS/GOBI via 'Real Time' Orders

    In March release orders for SAGE resources coming into Alma via Real Time ordering  from OASIS/GOBI will look for the relevant resource under the following collection: SAGE Knowledge A-Z (collection ID 613790000000000598) and not in the collection which is being used now.

    In case you would like to move PO lines/License associated with resources under the previous SAGE collection to the new collection please use the " Move electronic portfolio information" job, more information can be found in Running Manual Jobs on Defined Sets.

    Alma Roadmap Highlights

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

    Next Release Sneak Preview

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

    Main Features

    'Invoice Due Date' Field Added to Invoice Editing Screen

    August 2021 Acquisitions URM-144930

    Alma has added a new field, "Invoice due date", to the Invoice editing screen. The Invoice due date is used mainly for ERP export purposes and does not affect the invoice progress within Alma.

    Once the invoice's status is "Ready to be paid" or "Waiting for payment", the invoice due date field is not editable (as the invoice was exported to the ERP already).

    The field is populated in two ways:

    • When an invoice is created manually.
    • When an invoice is created automatically via EDI. The date information is populated from the "DTM+13" field of the EDI file.

    An invoice due date can not be earlier than the "Invoice date" defined in the invoice.
    Additionally, the invoice date and invoice due date information is added to the invoice main list (to be used when searching for invoice and when using the invoice links from the Acquisitions menu).

    The "Invoice due date" field can also be updated (POST, GET, PUT) via API. 

    Invoice_Due_Date.png

    Invoice Due Date field 

    Define a Specific Time Frame While Manually Harvesting R5 SUSHI Data

    August 2021 Acquisitions idea exchange Idea ExchangeURM-134451

    In Alma, a new option is included enabling users to define a specific time frame while manually harvesting SUSHI data. This is only available for SUSHI Release 5 accounts. The existing "Harvest Now" function remains and will harvest usage from the past 12 months while the new "Custom Harvest" function presents users with a pop-up window allowing them to define the exact time frame for the harvest period. The "Custom Harvest" operation can run on the entire SUSHI account or on a specific report within the account. Users can define multiple harvest time frames.

    If the selected date range(s) contain months previously uploaded to Alma, these will get overridden.

    Harvest_Date_Range_SUSHI.png

    Harvest Due Date Range 

    Watch the Harvest SUSHI Data from a Specific Time Frame video (1:18 minutes).

    New SAML Certificate

    August 2021 Administration and InfrastructureURM-153999

    The current DigiCert SAML Certificate will expire on December 1st 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.

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

    Support 'Partial' Network Unique Item Barcodes in SIP2

    August  2021 Fulfillment URM-146135

    Alma now allows institutions to select whether to allow SIP2 transactions for items of other institutions in networks where barcodes are fully or partially unique (this option can be set by Ex Libris support). This is done by enabling/disabling the “Allow Fulfillment Network Items” option in the self-check integration profile. If self-check is configured to allow items from other institutions, the existing behavior for network items is maintained. Alma checks if there are duplicate barcodes in the network and if so the self-check transaction is refused and the item must be loaned at the desk. If self-check is configured not to allow items from other institutions, then only items of the local institution will be handled by SIP2.

    The new option appears only for institutions that are set up to allow fully or partially unique barcodes.

    Resource Sharing Integration - Netpunkt - OpenReceipt Enhancements

    August  2021 Fulfillment-Resource Sharing URM-152341

    Resource sharing integration with Netpunkt (a Danish ILL system)  was enhanced to update existing borrowing requests. Alma will identify the resource sharing borrowing request using Alma Internal Identifier.
    Resource sharing staff will need to include Alma’s Internal Identifier in the note field of the Netpunkt request form.

    Resource Sharing Integration - LIBRIS -Improved Import

    August  2021 Fulfillment-Resource Sharing URM-139793

    Alma has improved the workflow of how imports from LIBRIS (A Swedish ILL System) are performed. Previously, if an import request already existed or if the partner or patron of the request were unknown in Alma, the import process would not complete. The enhanced workflow now incorporates the following:

    • Alma now checks for an existing match on request IDs (External Identifier) with an active request. If there’s a match, then the rota of the matched request is updated with the rota information provided in the imported request.
    • If the partner record on the imported requests rota is not known to Alma, then the request will be imported and a note will be added to indicate that some partners were not identified in Alma.
    • If the requester one the imported record is not known to Alma, the request will be imported with a general configurable patron.
      The incoming patron information will be saved as a note.

    Resource Sharing Directory

    August  2021 Fulfillment-Resource Sharing URM-152086

    The Resource Sharing Directory is a global Community Zone based repository with up-to-date information about resource sharing libraries in Alma. Libraries can use this directory in order to create a resource sharing partner record and locate profile based on information that has  been contributed to the repository by the peer library itself. This greatly simplifies the process of creating resource  sharing partners, and reduces the chance of errors that  result in no communication between borrower and lender. Pulling a partner record from the community is described in Resource Sharing Partners.

    For the peer to peer process to work, the borrower must pull the lender’s partner record, and the lender must pull the borrower’s partner record.

    A library can contribute its own information to the repository. Please submit this form for Ex Libris to enable this for you. Once enabled, you can contribute your own resource sharing library information to the repository , see "Adding a member to RS Directory from existing RS library" for details.

    Support for Libraries Sorting by "Physically At" Location

    August 2021 Resource ManagementURM-1633

    To facilitate the work of Inventory Operators, who are interested first and foremost in seeing inventory within the library they work in, now the below functionalities within Alma support sorting by "Physically At" location of the user:

    To enable this new sorting, set the sort_library_by_relevance customer parameter to True (Configuration > Resources > General > Other Settings). When the parameter is set to False, the previous sorting order is used. See Configuring Other Settings (Resource Management).

    Metadata Editor Holdings 852 $b - Support for Libraries Sorting by User Location

    August 2021 Resource ManagementURM-124182

    When cataloging the holdings record and updating the 852 field in the Metadata Editor, now when you press Ctrl+Fthe "Library" dropdown "Sublocation or collection(b)" displays the available libraries in the following fashion:

    1. The library that is selected as your "Physically at" location.
      852 sublocation field my library on top.png
    2. Other libraries in the scope of your user roles that are assigned the PHYSICAL_INVENTORY_MANAGE privilege (for the roles assigned this privilege, see below). Note: If you have only one library in the scope of your user roles assigned the PHYSICAL_INVENTORY_MANAGE privilege, this library is selected automatically when editing 852 $b.

    If the holdings record already has a value in 852 $b (if the field was opened from a template), and the library is not in scope of your user roles assigned the PHYSICAL_INVENTORY_MANAGE privilege, Alma issues an error message and you need to select a library that is in the scope.error message if library is inherited from template.png

    Error message when a library inherited from template is not in scope of  your user roles assigned the PHYSICAL_INVENTORY_MANAGE privilege

    When cataloging without using CTRL+F, Alma now allows to modify the value of $b field only if both the existing library and the new library are in the scope of your PHYSICAL_INVENTORY_MANAGE privilege.

    The privilege PHYSICAL_INVENTORY_MANAGE is part of the below roles:

    • PHYSICAL_INVENTORY_OPERATOR
    • PHYSICAL_INVENTORY_OPERATOR_LIMITED
    • PURCHASE_MANAGER
    • PURCHASE_OPERATOR
    • REPOSITORY_MANAGER

    Physical Item Search - "Libraries" Facet Sorted by User Location

    August 2021 Resource Managementidea exchange Idea ExchangeURM-1633

    When doing a Physical Items search, the "Library" facets in the search results can now be ordered as follows:

    1. The library that is selected as your "Physically at" location.
    2. Other libraries in the scope of your user roles that are assigned the PHYSICAL_INVENTORY_MANAGE privilege.
    3. Other libraries, sorted alphabetically. 

    "Physical" Tab in Titles Search - Holdings Sorted by User Location

    August 2021 Resource ManagementURM-71606

    In the Physical tab that appears under each title, the holdings records can now be ordered as follows:

    1. Holdings records for the library selected as your "Physically at" location.
    2. Holdings records for the other libraries in the scope of your user roles that are assigned the PHYSICAL_INVENTORY_MANAGE privilege. 
    3. Holdings records in other libraries, sorted alphabetically. 

    holdings sorted by library.png

    Holdings records sorted by library, when the user's "Physically at" location is 'enew' location

    See Searching in Alma.

    Publishing Profile Information Added to Publishing Information Page

    August 2021 Resource Management URM-152062

    The Publishing Information page (Resources > Publishing > Publishing Information) displays the publishing information of specified identifier and chosen publishing profile. Now this page also displays general information of the selected publishing profile and enables the user to jump to the profile in order to edit it. 

    publishing information page pub profile info section.png

    See Publishing Information

    Additional Columns added to the "List of Holdings"

    August 2021 Resource ManagementURM-153037

    Three new columns were added to the List of Holdings:

    • Summary Holdings: field 866 $$a,x,z,9
    • Supplementary Material: field 867 $$a,x,z
    • Indexes: field 868 $$a,x,z

    The subfields are extracted according to the original cataloging order. Repeatable fields are separated by a semicolon. The new columns are hidden, to display these fields, select the open hidden columns icon.pngicon and select these columns from the list. 

    Additional columns in list of holdings.png

    August 2021 Resource Management

    Alma Link Resolver now supports incoming CDI OpenURLs with multiple ISBNs and eISBNs. Alma will use these ISBNs and eISBNs to match bibliographic records and return all relevant electronic services. 

    Support for Icelandic Special Characters

    August 2021 Resource Management URM-123945
    Alma now supports special Icelandic language diacritics for: repository search, user search, browse bibliographic headings, using F3, and sorting results.

    As part of the release of this functionality, re-indexing will be automatically triggered for the customers that use the Icelandic search settings.

    Until re-indexing completes, inconsistencies may appear.

    See Icelandic Characters, Browsing Bibliographic Headings and Configuring Institution Languages

    Alma Accessibility Improvements

    August 2021 Resource Management URM-152833

    The following improvements were done with the purpose of making Alma meet Level A and AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions:

    • Recent entities area - focus indicator were added to all elements:
      focus in recent entities list.png

    • The content of feedback messages is now exposed to screen reader users:
      Expose to screen reader users the feedback messages content.png

    Metadata Editor Accessibility Improvements

    July 2021 Resource Management
    • Keyboard navigation over the list of Records/Sets/Templates/Rules:
      • Use Tab to focus on the first element in the list for record, set, or folder. For templates and rules, Use Tab to focus on the first element in Private/ Shared/ Community lists.
      • Use Up and Down arrows to navigate across a list. It may be a top-level list (in Records tab), or a nested list in a set or folder.
      • Use Enter to open/close a set or folder.
      • Use Enter to open a record/ template/ rule.
      • Use Right arrow to dive into an open nested list of a set or folder.
      • Use Left arrow to zoom out of an item within nested list of a set or folder, and close it.
      • Use Space bar to dismiss tooltips of any item.
    • Tooltips in the Metadata Navigation lists now matches the level-AA behavior:
      • Use ESC to dismiss tooltips (with the exception of tooltips that are dismissed by Space bar).
      • Hover over tooltips with the mouse to view without dismissing.
      • Tooltips are dismissed automatically when the focus moves to the next element.

    Default Cataloging Level Applied to New Records Created by Metadata Import 

    August 2021 Resource ManagementURM-149538

    Now whenever a new record is created from the input file, the cataloger level of this record is the default cataloger level, or "00" level if no default is defined.

    It is recommended to set a default value in the "Cataloger Permission Level" configuration. See Cataloging Privileges for more information.

    See Configuring Cataloging

    August 2021 Digital Resource Managementidea exchange Idea ExchangeURM-144900

    Previously, copyright statements for digital representations were configured through the access rights functionality. This required separate access rights for each copyright statement that was associated with a representation. Now, in addition to the previous functionality, you can configure copyright statements directly on a representation, independently of the access rights.

    The copyright statement configured directly on the representation takes precedence over any configured through access rights.

    To support this feature, the following changes were made:

    • The Copyrights field was added when adding representations to a title:

      copyrights.png

      Copyrights
    • Copyright statements are now configured to be obtrusive per statement on the Configuring Copyright Statements – Digital page (Configuration > Fulfillment > Copyright Management > Copyrights Statements - Digital):
      • For boilerplate copyright statements, select Make Obtrusive. A check mark appears in the new Obtrusive column:

        boilerplate.png

        Make Obtrusive – Boilerplate Copyright Statements
      • For custom copyright statements, select the new Obtrusive checkbox when editing the statement:

        boilerplate - custom.png

        Make Obtrusive – Custom Copyright Statements
    • You can now run the Global Representation Changes job with Copyrights as an input or output parameter:

      global_rep_changes_parameters.png

      Global Representation Changes Parameters – Copyrights
    • You can now search for copyright statements that were configured independently of access rights.

      search_copyrights.png

      Search Copyrights

    Patron Waitlist Management for Controlled Digital Lending

    August 2021 Digital Resource Management URM-148010

    You can now configure a waitlist for patrons when applying concurrent users access rights to support controlled digital lending flows. When the access rights blocks a patron from accessing a digital resource because the limit of concurrent users is reached, the patron is given the opportunity to join a waitlist. When a slot opens, the patron is notified that the resource is now available.

    To support this new functionality, a new Waitlist Management section was added when configuring concurrent users access rights (Configuration > Fulfillment > Copyright Management > Access Rights):

    waitlist_management.png

    Waitlist Management

    From this section you can:

    • Select a grace period during which the patron must access the resource or lose the place in line
    • Limit the waitlist to specific hours outside which the functionality is first come, first serve

    When a waitlist is configured and the maximum number of concurrent users was reached, the following appears to the patron:

    waitlist_registry.png

    Waitlist Registry

    The patron selects Join the Waitlist to be notified when the resource is available.

    Alma sends emails to notify the patron when the patron joins the waitlist, when a resource becomes available, and when the grace period expires.

    After the patron receives access to the resource, the patron can display the time remaining in the session by selecting the hour glass icon and return the resource before the time available is over by selecting Return Early.

    return_early_and_display_time_remaining.png

    Display Time Remaining and Return Early

    For more information, see Configuring a Patron Waitlist.

    Watch the Patron Waitlist for Digital Lending video (4:38 minutes).

    August 2021 Digital Resource Managementidea exchange Idea ExchangeURM-151564

    You can now configure or remove the copyright symbol © that appears in the public note when selecting ViewIt and a copyright statement is associated with a representative:

    copyright_symbol.png

    Copyright Symbol

    To configure the copyright symbol, the following parameters were added:

    • For Primo at Configuration > Fulfillment > Discovery Interface Display Logic > Labels:

      copyright_icon_configuration.png

      Copyright Symbol Configuration – Primo
    • For Primo VE at Configuration > Discovery > Display Configuration > Labels > Viewit Labels:

      copyright_icon_configuration_primo_VE.png

      Copyright Symbol Configuration – Primo VE

    To remove the symbol, set the code table value to NOT_DEFINED.

    Create or Update a Proxy User Via API

    August  2021 API URM-49447

    Alma enables users to create or update a proxy user via API. Previously, the proxy segment for updating users was not supported. Now, when a customer wants to load a new user as a proxy, the user is created/updated with the "Proxy for" users in the XML.

    Recommendations for Jobs that Stopped Working

    August 2021 DARA URM-145088

    DARA now identifies if the Student Information System (SIS) job stopped working and recommends that you check the relevant job reports.

    job_failure.png

    Job Failure Recommendation

    There are three recommendations related to this development:

    • Job failure – if the SIS synchronization job fails 3 times in 10 days
    • No data processed – if no user/researcher was processed in the last 5 days
    • No job instance – if there is no job instance in the last 3 days
    The conditions listed for the recommendations above are configurable.

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

    Default Type For Disabled PO Line Types

    July 2021 Acquisitions URM-122865

    A new functionality will verify that the "PO Line Type" is active for orders created via API/purchase request. If a certain PO Line type is disabled, Alma will automatically look at the new "default" column and create the PO Line type according to it. These PO Lines will be added with an assertion (alert).

    This functionality can be configured in Configuration Menu > Acquisitions > Purchase Order > PO Line Types as follows:

    • Add a default type for the disabled PO Line type ("Default PO Line Type" column).

    Default POL type 1.png

    PO Line Types Mapping Table

    Selecting a "Default" value will affect the following workflows:

    • When an order is created via API, Alma will validate that the specified "PO Line Type" is actually enabled by the institution, If Yes, Alma will continue.
      • If the PO Line Type is not enabled but does have a "Default" type, Alma will add a new assertion to the PO Line that will state that the order's original "Type" is not enabled and the PO Line was created with the default "Type" value.
      • If the PO Line Type is not enabled and a default value was not selected in the "PO Line Types" table, Alma will add a new assertion to the PO Line stating that the order's original "type" is not enabled, and no "default" value was selected the PO Line was created with the original "type".
    • When an order is created via Purchase Request, currently the "type" for the PO Line which will be created once a purchase request is approved is determined based on the user selection within the Purchase Request form. If the institution would like approved purchase requests to create a PO Line type different from the default stated above, see Configuring default "types" for disabled PO Line types.

    Control "Interested User" Options For Automatically Created PO Lines

    July 2021 Acquisitions URM-38342idea exchange Idea Exchange

    An enhancement in the PO Line's "Interested Users" management area allows institutions to control whether to disable/enable the interested users options for PO Lines created via Purchase Request and EOD process. Additionally, a new job was created to provide institutions the ability to update the Interested users options on a set of PO Lines. Below is a short explanation for each option:

    1. When working on a purchase request, a new "Interested Users" field allows users to define the options that will pass to the PO Line which will be created once the purchase request is approved. 

    intersted user options.png

    Interested Users field

    For backwards compatibility (previously the first two options below were always selected by default) the parameters controlling these options are now set to 'True' by default. The default selection of options can be defined by the institution (Configuration Menu > Acquisitions > General > Other Settings). For this purpose, the following customer parameters were created: 

    Parameter The option it controls Default value of parameter
    po_line_hold_for_interested_users Hold Item True
    po_line_notify_for_interested_users_upon_cancelation Notify upon cancelation True 
    po_line_notify_for_interested_users_upon_receiving_activation Notify user upon receiving/activation False
    po_line_notify_for_interested_users_upon_renewal Notify upon renewal False
    1. PO Lines created via EOD process (new order import profile) has a new control over the interested users options for PO Lines created via this process.

    clipboard_e0c4e4b21dc80453188cf3d5353708cc6.png

    Interested users options for PO Lines
    1. A new job, "Update PO Lines Interested Users" located within the "Update PO Line" jobs area (Admin > Run A Job) provides institutions the ability to update the "Interested users" options on a set of PO Lines (the new Job does not handle closed and canceled PO Lines).

    clipboard_e800f5fd74b08ef067a23584fa65d12aa.png

    Update PO Lines Interested Users

    ​See Manually Creating a PO Line and Configuring Other Settings (Acquisitions).

    CDI New Information Field, Search Fields and Facets

    July 2021 Resource Management URM-142288, URM-147790, URM-147723, URM-144632, URM-144621

    A new field has been added in Alma: ‘CDI Last Market Update’. This field will indicate the 'last update date' for an electronic collection in CDI.

    Alma has incorporated new CDI related search fields that are available in the Advanced Search for Electronic collections.

    • CDI Activation required (This search field is visible for EasyActive customers only)
    • CDI Provider Coverage
    • CDI Type (Alma subscribes to only some titles in this collection)

    Support for Swedish and Norwegian Special Characters

    July 2021 Resource Management URM-123945idea exchange Idea Exchange

    The handling of Scandinavian characters was enhanced as follows:

    • Special characters cataloged in non-Scandinavian languages (such as French letters with accents), are now normalized during indexing. This means that a search for a term including these special characters now behaves as if the search was done without them. (However, the opposite does not happen: a search for a term without these special characters is not treated as if done with these special characters.)
    • Support for Swedish and Norwegian special diacritics in Browse Bibliographic and Authority Headings was added. 
    • Sorting of Swedish and Norwegian/Danish special characters in Staff Search & Browsing was added.

    As part of the release of this functionality, re-indexing will be automatically triggered for the customers that use the Swedish and Norwegian search settings.

    Until re-indexing completes, inconsistencies may appear

    See Scandinavian Characters.

    Alma Accessibility Improvements

    July 2021 Resource Management URM-151326, 142204, 81926

    The following improvements were done with the purpose of making Alma meet Level A and AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions:

    • Color contrast - the colors of low-contrast elements were changed to more prominent.
    • An indication for active state or hover was added.
    • 200% zoom with no content loss is now supported.
    • Increased text spacing with no content loss is now supported.
    • The loading blocker for screen reader users was exposed.
    • Recent entities – support for keyboard navigation in entities filter is now supported
    • Date picker – keyboard navigation and labels for screen reader users is now supported. To open the calendar, press Enter on the Calendar icon.
      date picker improvements.png

    Metadata Editor Accessibility Improvements

    July 2021 Resource ManagementURM-149529

    The following improvements were done with the purpose of making Alma meet Level A and AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions.

    • Menu actions - screen-reader related improvements
    • Navigation panel - keyboard navigation is now supported on the displayed registry tabs (using tab key) and on the collapsed registries list (open using Enter, navigate using up/down arrows, select with Enter)
      tab navigation mde.png
    • Panels of the Editing area - keyboard navigation between the two panels (in case of a split screen) and the Alerts area is now supported. Use tab/Shift +tab to move between the elements. 
    • Browse Bib Headings - support for tab navigation 
      browse bib heading tab navigation.png
    • "Open in Repository Search" is now accessible via tab navigation

    New Metadata Editor: Improved Display of Format Tabs 

    July 2021 Resource ManagementURM-149529

    In the Records area, the format tabs are now displayed in two rows instead of one--this enables you to see more formats, and removes the need to select the  icon when opening one of these tab. 

    In addition, the default order in which tabs are displayed is now the following: the sets, the bibliographic formats, the holdings, the authorities, and finally the DC formats (select to display them). 

    two rows of record formats.png

    Enhanced Ability to Filter a Set Using an Indication Rule

    July 2021 Resource ManagementURM-149521NERS NERS Enhancement (ID #6795)

    Filtering logical sets using indication rules can now be done faster and with less clicks, and each set now displays a link to the set it was filtered from or a link to its filtered sets (as appropriate for the set).  

    The button for saving a query that appears for all types of repository Title searches (All Titles, Physical Titles, Electronic Titles, Digital Titles), is now called "Save and Filter Query" (previously was called "Save Query"). This was done only on repository Title searches since filtering logical sets is possible only on these search types. 
    Save and Filter Query on all title repository searches.png

    Once you select this button, the Set Details page opens where you define the set to create from the search results. On this page, a new button "Save and Filter" allows you to initiate the process of saving a set that is to be filtered.
    Save and Filter on Set Details page.png

    Once you select this button, a new page opens where you can create the filtered set of that main set. The main set is created in the background in the meantime. Select "Filter This Set" to create an itemized set that consists of the filtering done on the main set according to the selected rule.

    When the new set is ready, it appears on the Set Details page of the main set; click on the link to open it. A similar section appears for the original set from which this set was created, listing all its filtered sets. The row actions list for the new set contains all the actions that can be achieved on this set, identically to the actions available from the Manage Sets page. 
    sets created by filtering this set.png

    See Filtering Sets

    Automatic Generation of Call Number Prefix and Suffix

    July 2021 Resource ManagementURM-144743

    The mechanism of generating call numbers and temporary call numbers for items and holding records was enhanced as follows:

    • You can now enter a new prefix on-the-fly when working with items and holding records. Alma generates the call number based on that prefix and saves the prefix in the list of prefixes for future use. This speeds up call number generation. 
    • You can now concatenate a suffix to the call number. 
    • To enable the method of call-number generation on-the-fly, contact Ex Libris staff. 
    • Suffix concatenation is disabled by default. Contact Ex Libris staff.

    Call numbers and temporary call numbers are generated on the fly as per the below:

    • Physical item's call number generation: The Physical Item Editor > Location Information tab allows you to update item-level information for physical items and generate the call number. If the prefix does not exist in Alma and you want to set it, enter the desired prefix for the sequence in the "Choose Prefix" field, and select GenerateThe system presents the following message: "An accession number sequence with the prefix <prefix> was selected and will be used to generate the call number upon save. The expected value is <expected value>." In addition, Alma saves this prefix for future use in the Accessions Numbers configuration table, see Configuring Accession Numbers
      generate item lelvel call number method 3.png

      See Updating Item-Level Information

    • Holding-level Call Number Generation: The 852 field $h allows you to update holdings-level information for items and generate the call number. If the prefix does not exist in Alma and you want to set it, enter the desired prefix  for the sequence in the 852 field $h, and then enter '?' (question mark), and (optionally) the suffix. Then select Generate Accession Numbers (in Record Actions menu) or press Ctrl+Shirt+A.
      852_field_prefix_creation with suff.png

      The system populates the 852 $h with the specified prefix + sequence (+ suffix). In addition, Alma saves the prefix for future use in the Accessions Numbers configuration table. 

      To change the accession number, delete the value in 852 $h. You are redirected to the Accession Configuration page, where you can select a different accession number. Clicking Select automatically returns you to the Metadata Editor and populates the 852 $h with the selected value.   

      • To apply the 'Accession Number' on holding level, the 'Physical Location' configuration for the Library+Location should be set with 'Accession Placement'. See Configuring Accession Numbers.
      • The 852 subfield that stores the generated number can be $h OR $j OR $p--the exact field is set at the Physical Location table > "Accession Placement" field. The above refers to 852$$h as the placement of the accession number; however, the same logic applies also when other placement ($j OR $p) is defined in the Physical Location table. 

      See Holding-level Call Number Generation.

    (URM-149538) Default Cataloging Level to Be Applied to New Records Created by Metadata Import 

    July 2021 Resource ManagementURM-149538

    This is an advanced notice for a future release. The below development is not being released in July 2021.

    In an upcoming release, Ex Libris will introduce the following new functionality for the Metadata Import: Whenever a new record is created from the input file, the cataloger level of this record will be the default cataloger level, or "00" level if no default is defined.

    It is recommended to set a default value in the "Cataloger Permission Level" code table.

    Download Digital Files in a Set

    July 2021 Digital Resource Management URM-147000idea exchange Idea Exchange

    You can now download the digital files of a digital title set into a zip file. To support this feature the new Download Files job is now available (Admin > Manage Jobs and Sets > Run a Job > Download Files.

    download_files.png

    Download Files

    After the job runs, you receive an email with a download link to download a zip file with the digital files.

    For more information, see Download Files.

    Watch the Download Files of a Digital Set video (1:31 minutes).

    Add/Renew Patron Role from Circulation Desk

    July 2021 Fulfillment URM-146771

    Alma now enables staff operators to easily add a patron role to a user, as well as view and update the patron role's expiration date. Previously, this functionality was only possible by User Managers and is now attainable by operators in the circulation desk. The new functionality performs the following:

    • Adds the new patron role either in the institution or the scope the desk operator is currently in (depending on the User Registration Rules).
    • Renewing a patron role is only allowed if the scope is at the "institution/specific library" which the operator is currently at.  

    This is possible by using the new "Add/Renew Role" button at the Manage Patron Services page.The button appears only in the user's Circulation Desk Operator role has a 'renew patron' privilege.

    In addition, the Expiration Alert Period that is defined in the User Registration Terms of Use will be used to warn (in the User Notes area of the Patron Services Workbench) about an expected expiry of the patron role in the current library or institution. This is in addition to the previous behavior where this parameter warned about an expected expiry of the user account.

    Add-Renew_Patron_Role_2_RN07.png

    Add/Renew Patron Role (Patron Services)

    Add Library Input Parameter to User Registration Rules

    July 2021 Fulfillment URM-138344

    User registration rules have been enhanced to support library-specific registration rules (to support different registration fees to different libraries). Previously, user registration rules could be used to add a patron role at the physical library. However, the rules are sensitive only to a user group as input. Therefore, different registration fees could not be automatically applied to the  same user when registering at different libraries. The new functionality supports different registration fees to different libraries.

    • If patron role is created using the Renew Role option (for example, when a loan is blocked due to missing patron role), then the user registration rules use the physical library of the loaned item as the scope and not that of the 'currently at'.
    • If patron role is created using the 'Register User' option, then the user registration rules use the scope of the 'currently at' library.

    Creating Fines/Fees at Library Level

    July 2021 Fulfillment URM-138348

    Alma now allows the option to have fines and fees related to a user to be created in relation to a specific library. Previously, manually assigned fees were  only attainable on an institution level or derived from the item barcode they are attached to. The new enhancement enables the following:

    • Ability to manually add a library-owned fine/fee.
    • Ability to add a library-owned fine/fee using API.

    Description Column Added to the Patron Services Workbench

    July 2021 Fulfillment idea exchange Idea ExchangeURM-145632

    A new 'Description' column can be added to the list of loan items in the Manage Patron Services page. The column shows the value of the physical item's 'Description' field.

    Description Column in Patron Services

    View Digitized Content in 'My Account' (Primo VE)

    July 2021 Fulfillment-Resource Sharing URM-148062

    Completed digitally received resource sharing requests will allow downloading the file from Primo VE and remain accessible in Primo VE as per the number of days that the library has configured to keep the file. This depends on the 'Document delivery files cleanup' job being active in the institution. For more information, see the Primo VE 2021 Release Notes.

    Quick Access to RapidILL Requests

    July 2021 Fulfillment-Resource Sharing URM-145615

    Alma now enables users to easily and quickly access RapidILL requests in the system by introducing new tasks showing unassigned resource sharing requests (borrowing and lending) attached to RapidILL partners. Previously, to view RapidILL requests, users had to access the task list. The newly added quick access tasks add benefit to RapidILL requests which require a quick turnaround for both lender and borrowing sides. 

    RapidILL_Requests_RN07.png

    RapidILL Requests in Borrowing and Lending Requests

    Convert 'Hold' to 'Resource Sharing' Requests for Personal Delivery

    July 2021 Fulfillment-Resource Sharing idea exchange Idea ExchangeURM-46550

    In Alma, institutions can now convert 'Hold' requests to 'Resource Sharing' requests if the pick-up location is personal delivery and the resource sharing library supports personal delivery. Whenever a convert action is triggered, either by a request expiry or as an online action, it will successfully convert a personal delivery request. Previously, Alma did not allow personal delivery requests to be converted to resource sharing requests.

    The conversion will only work if the resource sharing policy allows the same personal delivery (home/office) as the converted request.

    See: 'Automatically Converting a Hold Request to a Resource Sharing Request' for more information on converting hold to resource sharing requests.

    Push User Records to ILLiad

    July 2021 Fulfillment-Resource Sharing URM-148064

    Alma can now use ILLiad APIs to push user records to ILLiad (a resource sharing management system). The push will only occur if this is configured by the library and the user does not already exist in ILLiad. Before pushing a request to ILLiad, Alma will verify that the account exists and create a user account if not.

    The resource sharing partner record for ILLiad API was enhanced to allow configuring the following API values:

    • Search user in ILLiad using – the value which Alma will use to locate / create a user in ILLiad (user identifier or preferred email)
    • NVTGC -free string
    • Status - free string
    • NotificationPreferences - repeatable free text field with two comma separated values. The first will be sent as ActivityType and the second as NotificationType. For example - {RequestPickup,Email},{RequestOverdue,Email}.
    • Notification method - 'Electronic', 'Phone' or 'Mail'
    • Delivery Method - 'Hold for Pickup' or 'Mail to Address'
    • Loan Delivery Method - 'Hold for Pickup' or 'Mail to Address'
    • Electronic Delivery
    • Authtype - 'Default','ILLiad'

    ILLiaad_RN07.png

    Create user in ILLiad

    Alma will look up for the user in ILLiad. The value that will be used for the match will be from the above mentioned 'Search user in ILLiad' using mapping.

    The ILLIAD response will either provide details of their user record or will indicate a user cannot be found, in which case, Alma will  attempt to automatically create a user record in ILLiad.

    ‘Convert to Resource Sharing’ Option Available for ‘In Transit’ Requests

    July 2021 Fulfillment-Resource Sharing idea exchange Idea ExchangeURM-147573

    In Alma, the ‘Convert to resource sharing’ option is now available for ‘In Transit’ requests. Previously, this option was available only if the request was in "pick from shelf" or "not yet active".

    Customization of the Genders Code Table

    July 2021 Administration and Infrastructure URM-144743idea exchange Idea Exchange

    Institutions can now change the values of the list of user genders to conform with their local legislation. This can be done in the Genders table (Configuration > User Management > User Details > Genders). Once gender values have been defined, they can be assigned to users in the User Details page. 

    The Genders table contains four default genders: male, female, other and none. These values can be disabled and their description can be altered. In addition, the institution can define its own gender values in the "Additional" fields, up to total of 10 gender values in a list.

    Every change to the gender values will affect existing users to which this gender is assigned. 

    In a Network Zone, genders can be defined from the Network institution, in which case the gender values defined from the network are locked for editing by the member institutions.
    Genders table.png

    See User DetailsConfiguring User Genders.

    Watch the Configuring Genders in Alma video (1:28 minutes).

    Fund Management APIs - Full set of Management APIs

    July 2021 API URM-151579

    Alma now incorporates a full set of CRUD (Create, Read, Update and Delete) APIs for managing funds and ledgers. Previously, Fund APIs were limited to just GET services. The new set enables institutions to integrate financial systems and be able to create, modify and delete library ledger/fund structure as needed.

    Fund Management APIs:

    • Search and retrieve ledgers and funds
    • Search and View transactions for a fund
    • Create/Update/Delete Funds
    • Business functions: Allocate, Transfer

    Item API - Generate Description

    July 2021 API URM-148414

    Alma's user interface (UI) currently has a specific function to generate "item descriptions" when handling items received. This operation of generating an item description has now been extended to be performed via the API.

    Manage the Price Threshold and Amount Threshold for PO Lines and Invoices at the Library Level

    June 2021 Acquisitions URM-124285

    Alma has now enhanced the configuration of PO Line and Invoices price and amounts threshold to also be managed at the library level. The previous configuration was at the institution level only. This level is retained as the default option. If a value is configured on both the institution and on the library level, Alma will prefer (select) the PO Line/Invoice owning library definition (if it has been defined). For more information, see: Manage Price Threshold and Amount Threshold for PO Lines and Invoices at the Library Level.

    The existing customer parameters; assertion_over_po_line_price [POLine] and invoice_high_total_price [Invoice], will be removed and replaced with 2 new configuration tables: 

    1. PO Line Price Threshold configuration table (Configuration Menu > Acquisitions > Purchase Orders):
      • High -Level price allows institutions to define the threshold amount on a PO line/invoice which will trigger an alert for the PO line/invoice, for example, institutions may want to prevent orders (PO lines) created in the system automatically (API/EOD) from progressing in their workflow in case the order's amount is higher than 100 USD (or any other default currency the institution had defined) so the institution can configure  a High -Level price of 100 which will add an alert to any PO line created with an amount exceeding 100 USD.clipboard_e62b3f04e2c927927c6ef4568dc755ca3.png
    2. Invoice Amount Threshold configuration table (Configuration Menu > Acquisitions > Invoices):
      • Alma has now enhanced the configuration of High-Level price PO Line and Invoices to also be managed at the library level. Previous configuration of High-Level price was at the institution level only. The new configuration maintains that the institution level is the default High-Level price, but with an added option to add a High-Level price at the library level. In case there is a value configured on both the institution level and on the library level, Alma will check the PO Line/Invoice owning library, if there is an entry within the new configuration table for the owning library, Alma will use it, if there is no entry fir the specific library, Alma will use the value defined on the institution level.clipboard_e11310066be64efaef520aaee8a54dc58.png

    Existing Customer Parameters for Invoice and PO Line have been deprecated (assertion_over_po_line_price [POLine] and invoice_high_total_price [Invoice]) and are not functioning.

    • In case the institution already had a value customized within one of the Customer Parameters (Configuration Menu > Acquisitions > Other Settings table), this value will pass automatically to the new configuration tables. To update the values, go to the new configuration screens.
    • In case no value was customized by the institution, the default value (institution level) will be:
      • Invoice = 2,500
      • PO Line = 10,000

    Two New PO Line Types for Digital Inventory

    June 2021 Acquisitions URM-134355, URM-114083idea exchange Idea Exchange

    Alma now supports acquisition workflows for digital material that enables institutions to manage ordering and receiving of digital material. To enable this functionality, two new PO Line types were created:

    • Digital One Time (DIGITAL_OT)
    • Digital Continuous (DIGITAL_CO)

    Enable the new PO Line types for the functionality to work. By default, they are disabled.

    PO Line type "Digital" is created with no inventory (both One Time and Continuous), there is a need to associate a representation with the PO line. There are 2 ways to associate a representation with a PO line:

    1. From the PO Line editing page, there is an option associate a new representation. When selecting the +Add Representation action from the PO line's "Ordered Representation" section, the Representation editor screen will open for the creation of a new representation. Title, Library and PO Line number will be pre-populated in the representation when it is created via the PO Line, as they are inherited from the PO Line. The digital title will need to be associated with a collection and the representation must contain files. Once users create the representation and click Save, they will be redirected to the PO line and the representation will be attached to it. To complete the process, click on Save and Continue located on the top right corner of the PO line's editing page.

    clipboard_e19dd74c2826a66af6584ae7523e8fa95.png

    1. From a new/existing representation, to add a PO Line to a representation, the representation must be associated with an existing Title. Once the user edits the representation, adds a PO line and clicks SaveAlma will automatically attempt to push the PO line to the next step of the workflow.

    clipboard_e5392a90868a52d69690ca50fa961a27b.png

    After a Digital PO Line is created, the workflows differ for One Time and Continuous:

    • One Time PO Line: In review > Closed
    • Continuous PO Line: In review > Waiting for renewal OR Waiting for manual renewal

    To provide purchasing roles the ability to edit a representations from the PO Line, a new privilege is added: UPDATE_REPRESENTATION_FROM_ACQ.

    A PO Line can not be "Saved and continued" without a representation. If user attempts to "save and continue", the PO Line will prompt the user with a warning message that the information is missing.

    Watch the Two New PO Line Types for Digital Inventory video (2:50 minutes).

    Extended Availability for the Classic Metadata Editor

    June 2021 Resource ManagementURM-144745

    The availability of the Classic Metadata Editor was extended for users in production till October 2021 release. It will give more time to the users in production to test all changes that were done in the new Metadata Editor. Also this will allow more time for the users to be educated on and get used to the new Metadata Editor. 

    See Usability Improvements

    Improved Integration with SBN Italian Union Catalog

    SBN MARC Version Upgraded to 2.03

    June 2021 Resource Management URM-149269

    Alma now supports the SBN MARC format, version 2.03.

    To upgrade your system to this version, contact Ex Libris customer support. Note that upgrading to this version means that you will get different results when searching authority records of the Titoli Uniformi type: the uniform title term will be in 231/431/531 fields and not in 230/430/530 fields. 

    Merge Records In Central Catalog

    June 2021 Resource Management URM-140535

    Institutions working with the Italian Central Catalog SBN on level 4 now can can perform a fusione (merge) operation in SBN. This is available for both SBN bibliographic and authority (AU,MA,TU,UM,SO,CL) record types. To support this, a new option "Merge Records in Central Catalog" was added to the Metadata Editor (MD Editor > Editing Actions menu). Note that this option is available only for UNIMARC bibliographic and authority records. 

    If the records to be merged do not have a counterpart in SBN database, the operation does not take place, and you receive an error message. 

    merge records in central catalog option.png

    • The option is visible only if a Central Catalog integration profile for SBN is defined.
    • To perform a merge of records in SBN, the "Merge Records in Central Catalog" privilege must be selected for your user role. Currently the Catalog Manager role has this privilege enabled by default. Other roles must have enable this privilege. 

    For details, see Menu Bar of the Records AreaContribution of Redirection to SBN.

    Metadata Editor - Color Improvements

    June 2021 Resource Management URM-145831

    The color-coding on the Metadata Editor was made consistent across all tabs and registries. 

    The color-coding of the Metadata Editor now consistently indicates the following:

    Color Sample Description
    Dark Blue
     
    dark blue tab sample.png The records currently displayed in the Navigation Pane are from this tab.
    Light Blue
     
    light blue tab sample.png

    The record being edited in the Editing pane, and its pane is currently in focus (when the Editing pane is in split mode).

    If there is no light blue record, this means that the record being edited (marked in dark blue color) is the record currently focused as well as belongs to the tab currently displayed in the Navigation Pane.

    Grey 
     
    gray tab sample.png The record being edited in the Editing pane, but its pane is currently not in focus (when the Editing pane is in split mode).
    White white tab sample.png There are no opened records under this tab in the Editing pane, and it is not currently selected to display in the Navigation pane.

    Metadata Editor Accessibility Improvements

    June 2021 Resource Management URM-145831

    The following improvements were done with the purpose of making Alma meet Level A and AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions.

    • The filtering area of the Navigation panel is now accessible by keybord keys:
      filter and sort accessibility fixes June.png
      • To navigate within the Filter and Sort selection box by arrows
      • To select or clear a checkbox option, press the Space key.
        To select or clear a radio-button option, navigate with arrows. 
      • To apply your selection, press Tab to focus the "Apply" button, and press Enter to perform the action.. 
      • Tp close the Filter and Sort selection box, press Esc.  
      • To go back to the previously selected element, press Shift+Tab. 
      • Once you closed the  Filter and Sort selection box, press Tab to move to the other elements of the Navigation Panel. 
    • Now you move between registries in the Navigation panel using keyboard keys. The selected registry is highlighted in light gray color, so you can always know where the focus is. In addition, the name of the currently selected tab will now be read by the reader, so that you know what the selected tab is.  
    • Now the reader can read every section of the Browse Bibliographic Heading form. 

    Alma Accessibility Improvements

    June 2021 Resource Management URM-142200, URM-148201

    The following improvements were done with the purpose of making Alma meet Level A and AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions:

    Color Contrasts

    • Visual boundaries and colors of screen controls were adjusted to maintain 3:1 contrast ratio with its background.

    Lists 

    • "Search in List" button – Triggering operation by keyboard button (Enter), and discernible text with the explanation of the purpose of the button were added to the reader:
      Accessability_search in list button.png
    • Customize list – Group labels were added to the checkboxes list in the reader 
    • "Select All" checkbox and "Select Record" checkbox – A label for screen reader was added with explanation of the purpose of the checkboxes
    • "More Actions" button – The state of the button (collapsed or expanded) was exposed in the reader:
      Accessability_More Actions button.png
    • Drawers – The tabs were made accessible and the currently-chosen tab is exposed:
      Accessability_drawers.png
    • Pagination - adding accessible names to "Next", "Previous" and “Jump To” buttons and exposing which page is currently displayed.
    • "Results per page" – the selected amount of results to display is now exposed in the reader.

    Forms

    • Combo-box – attributes were added to explain to screen reader that there is a list with options in clicking 
      Accessability_Combobox.png
    • Checkboxes – Group labels were added to screen reader 
      Accessability_Checkboxes.png
    • An accessible name was added for the Back button: 
      Accessability_Back button.png
    • Chosen facets - Accessible names were added and keyboard navigation was added for the "Remove Facet" button: 
      Accessability_chosen facets.png

    Facets

    • The state of panel (collapsed or expanded) is now exposed and the buttons all have descriptive text.
    • Every facet group now has a correct count with the number of items in group.
    • The state of every facet group (collapsed or expanded) is now indicated:
      Accessability_focus order.png
    • Focus order – a shortcut was added when focusing on title for focus on facets and back to title.
    June 2021 Resource ManagementURM-144745

    This is an advanced notice for a future release. The described development is not being released in June 2021.

    In an upcoming release, Ex Libris will introduce new functionality that will enable limiting electronic resource management actions according to user role’s scope. Various staff user's actions such as editing, updating, deleting, activating, deactivating, etc., will be enabled/disabled based on the library scope of the user role (whether a specific library or institution level (across libraries)). This functionality will provide better control over staff activities across libraries.

    As part of this development, library ownership defined at the level of the collection will be inherited by all portfolios under the collection. This means that a portfolio cannot be owned by a different library than the library defined at the collection level. The release of this functionality will include the removal of any library defined at the portfolio level (unless there is no library defined at the electronic collection level).

    To know if your institution has cases in which the library at the level of the collection is different than the library at the level of the portfolios, Ex Libris recommends that you run the following report:​ "Ex Libris - Portfolios with portfolio library unit different than electronic collection library unit" in the folder: /shared/Community/Reports/Shared Reports/Reports/Inventory – Electronic. This will give you the option to review the library setup of the electronic resource in your institution, and allow you to do the data corrections necessary before the release of the new functionality.

    For Q&A regarding this functionality, see Q&A: Limiting Actions Related to Portfolios and E-collections According to User Role Scope.

    For a full description of the functionality, see Limiting Actions Related to Portfolios and E-collections According to User Role Scope.

    Additional Sorting and Filtering Abilities for Sets

    June 2021 Resource Management URM-148298idea exchange Idea Exchange

    The following enhancements were introduced on the Manage Sets page, Run a Job page, and on Publishing Profiles page > Select Set list:

    • Now you can sort the list of sets by any of the existing fields. This helps you easily locate sets, for example, if you sort by date, you can find the latest created sets. To sort, select the  icon in the heading of the column by which you would like to sort. Once a column displays sorted information, its icon changes to .
    • Now you can filter the list of sets by content origin (to display only sets that were created by the institution or in the Community Zone). To do so, use the "Content Origin" filter above the table. 

    Once you sorted or filtered the list, these sorting and filtering options are used in the next Alma sessions as well. 

    All Users Allowed to Manage Their Own Sets

    June 2021 Resource Management URM-101642

    All roles who can perform a repository search were now given the ability to do the following: 

    • Save a query in order to create a set,
    • Manage sets - have the link shown, and relevant options of set management open

    Saving a query

    • When performing a search in the repository, the Save Query option is now enabled for all users for any entity available in the search options.
      any user can select save query.png

    Adding a set

    • The user can now add sets, as long as the set belongs to the content types types that the user is allowed to work with according to the user's roles.

    Managing sets

    • The "Manage Sets" link is now open to all users
      manage sets open for all users.png
    • Manage Sets page - for sets created by the user, all of the actions are now enabled.
      For sets created by other users - the user can view and use the set (but not to edit the set).
      Users have all actions enabled on their sets.png

    For details, see Managing Search Queries and Sets

    Watch the All Users Allowed to Manage Their Own Sets video (1:05 minutes).

    General Publishing Profile - Option to Include Authority Headings

    June 2021 Resource Management URM-132484
    The General Publishing profile now supports the ability to enrich the published data with Authority headings. Any update to the selected authority headings triggers re-publishing of the data. The functionality of updating a record when preferred terms are updated will keep its current functionality.

    This is useful, for example, when the name 'Mark Twain' is embedded within a bib record and library would like to publish both 'Mark Twain' and the non-preferred term 'Samuel Clemens'.

    Institutions interested in this feature need to re-publish the data to apply the new policy.

    To support this development, the Authority Enrichment section was added to the General Publishing Profile. Here you can set up your authority enrichment scheme.

    Authority enrichment.png

    See Publishing and Inventory Enrichment (General Publishing)

    Courtesy Letter Indication for Block on Patron

    June 2021 Fulfillment URM-124746

    Alma's courtesy letter, which is sent to patrons when a loan due date is about to arrive, can include the reasons renewal of the loan is not possible. Previously, this included only blocks on the specific item. Following June release, it will also include an indication of blocks on patrons (such as too many overdue items or a manual block).

    'Type of request' indication on loan block pop-up

    June 2021 Fulfillment URM-138721

    A new block preference, “Item is requested by the library”, was added, to allow libraries to let operators override internal library requests, such as; move request, work order, etc. but not fulfillment requests, for instance; patron physical item request, resource sharing ship physically, etc., which are still controlled by the “Item is requested by another patron” block preference.

    Alma will also display the type of request blocking a loan, to give operators more information when deciding whether or not to override the block.

    Loan_Blocked.png

    'Notify Users' on Cancellation Requests for Staff Requests

    June 2021 Fulfillment idea exchange Idea ExchangeURM-150132

    Alma now sends cancelation notices to requesting staff via email when a move or work order request is canceled. Cancelling any non-patron request (such as work orders or move requests) with the 'Notify User' checkbox enabled will send the cancelation letter to the request creator, such as the operator who placed it.

    Ability to Change Alma Full Text Activation to CDI -Only Full Text Activation

    June 2021 Fulfillment-Resource Sharing URM-147072

    In cases where an electronic collection is active for full text you can now change it so it will only be active in CDI using the action  'Change to CDI-only full text activation'

    When using the option 'Change to CDI-only full text activation', the following will occur:

    • The collection will be activate for full text in CDI only.
    • In case of aggregator/selective collection:
      The full text service will be deactivated, and a confirmation pop-up message will be shown:
      "The service of this collection will be deactivated. The collection will be active for full text only in CDI, not in the Alma link resolver."
    • In case of database type of collection:
      The BIB record will be suppressed, and a confirmation pop-up message will be shown:
      "The collection will be deactivated. The BIB record will be suppressed. The collection will be active for full text only in CDI."

    User Details Subject Area Enhanced

    May 2021 Analytics URM-145599idea exchange Idea Exchange

    The User Details subject area has been enhanced with the following improvements:

    • You can now create reports with fields from different folders as is possible in other subject areas.
    • The User Measures dimension was added, which contains measure fields relating to the number of users.
    • The following fields were added under the User Details dimension:
      • Cataloger Level – the cataloger level of the patron
      • Patron Letters Opt In – the letters for which the patron has opted in
      • Patron Letters Opt Out – the letters for which the patron has opted out
      • Has Role Other Than Patron – indicates if the patron has a role other than Patron
      • Has Role Other Than Patron and Instructor – indicates if the patron has a role other than Patron and Instructor
      • Is Blocked – indicates if the patron is blocked
    • The Proxy For dimension was added, which contains fields that indicate for whom the patron is a proxy.
    • The names of the various Status, Type, and Note fields were expanded to include the dimension name to clarify which fields are intended.

    Enhancements to Scheduled Report Configuration

    June 2021 Analytics URM-146779/span>

    The following enhancements were added to the configuration for Scheduled Dashboard Alma Analytics Objects:

    • You can now produce scheduled reports in CSV format.
    • If you configure Alma to place the report on an FTP server, you can now have a timestamp included in the file name of the report. This prevents the file from being overwritten the next time the report is run.

    Enhancements to Scheduled Report Configuration.png

    Enhancements to Scheduled Report Configuration

    For more information, see Scheduling and Subscribing to Alma Analytics Reports.

    New Dashboards Added to Alma Analytics

    June 2021 Analytics URM-148167/span>

    The following new dashboards were added to Alma Analytics. For each dashboard, a new analytics object of type Dashboard was added. The dashboards are now available as links from the Analytics menu in Alma according to specific roles that you can configure:

    • Acquisitions Dashboard (Ex Libris)
    • Analytics Objects Dashboard (Ex Libris)
    • Analytics Usage Tracking Dashboard (Ex Libris)
    • API Usage Dashboard (Ex Libris)
    • Benchmark Analytics KPI Dashboard (Ex Libris)
    • Cost per Use for Electronic Inventory and COUNTER reports Dashboard (Ex Libris)
    • Cost per Use for Physical Inventory and loans Dashboard (Ex Libris)
    • E-Inventory Dashboard (Ex Libris)
    • Fines and Fees Dashboard (Ex Libris)
    • Physical Items Dashboard (Ex Libris)
    • Licenses Analysis Dashboard (Ex Libris)
    • Purchase Requests Dashboard (Ex Libris)
    • Overlap Analysis Dashboard (Ex Libris)
    • Usage via Alma Link Resolver Dashboard (Ex Libris)
    • Usage via COUNTER Reports - Release 4 Dashboard (Ex Libris)
    • Usage via COUNTER Reports - Release 5 Dashboard (Ex Libris)
    • Monthly Usage Data - Release 5 Dashboard (Ex Libris)
    • Vendor analysis - physical one time Dashboard (Ex Libris)
    • YoY (Year over Year) Dashboard (Ex Libris)

    New Reports Added to Consortia Folder

    June 2021 Analytics URM-148114/span>

    The following out-of-the-box reports were added to the Consortia folder. These reports can aid an institution in evaluating overlap as well as unique titles across the consortia:

    • Titles with inventory in only one institution based on field 035 subfield a with library and location – displays titles held by only one institution in the consortia. The analysis uses the field 035 subfield a as a basis for determining the uniqueness of the title. This report is designed to be run in the Network Zone.
    • Duplicate electronic collections in different member institutions linked to Community Zone – displays a list of electronic collections that were activated from the Community Zone from multiple member institutions. The electronic collections were not activated from the Network Zone using the Available For functionality and therefore cause many duplicate titles across the member institutions.
    • Duplicate titles by ISBN for NETWORK institution – displays duplicate titles by ISBN in a Network Zone institution and excludes titles linked to the Community Zone. This report is designed to be run in the Network Zone.
    • Duplicate titles by ISSN for NETWORK institution – displays duplicate titles by ISSN in a Network Zone institution and excludes titles linked to the Community Zone. This report is designed to be run in the Network Zone.
    • Duplicate titles by Title Author Combined and Normalized for NETWORK institution – displays duplicate titles by the field Title Author Combined and Normalized in a Network Zone institution and excludes titles linked to the Community Zone. This report is designed to be run in the Network Zone.
    • Duplicate titles by 035a for network institution – displays a list of titles that exist in the Network Zone institution and are duplicate titles. The records are determined to be duplicates based on the 035 field subfield a.

    Enable Easy Rollover of IDP Certificate

    June 2021 Administration and Infrastructure URM-117149

    When a SAML IDP changes their certificate (for security reasons), the certificate needs to be updated on the integration profile. If the certificate is not updated at the same time on both systems, this can cause downtime, since Alma does not trust the response from the IDP  that was signed with the "wrong" certificate.

    Now Alma allows holding two certificates simultaneously, and tries to authenticate using both certificates. This allows the institution to add the new certificate ahead of time, without removing the old certificate until after the IDP has made the switch.

    To support this, a new set of fields was added on the SAML intergration profile that enables uploading the second certificate. In addition, now the information describing each certificate (thumbprint, expiry date and upload date) are displayed for easy recognition of each certificate. 

    SAML integration profile second certificate.png

    See SAML-Based Single Sign-On/Sign-Off.

    Assigning Recommendations

    June 2021 DARA URM-148003

    You can now assign recommendations to a specific user. This can be done both for a specific recommendation and for all the recommendations of a type. This can be useful in the following ways:

    • Administrators can assign individual recommendations to be handled by a specific user in the library.
    • Users can assign a recommendation to themselves and prevent it from being displayed to other users.
    • A user that handle all of the recommendations of a specific type can have all those recommendations automatically assigned to that user only.

    To support this feature, the following enhancements were implemented:

    • A new Assign To option was added to the Actions menu for recommendations:

      assign_to_option.png

      Assign To

      After selecting this option, a drop-down list is displayed from which you can select a user to which to assign the recommendation.

      assign_to_dropdown.png

      Assign To Drop-Down List
      Only users with roles configured to view the recommendation are available in the drop-down list.

      You can also add a note.

    • After assigning a recommendation to a user, the assignment is indicated in the information of the recommendation:

      assigned_to.png

      Assigned To Information
    • You can filter recommendations to display only recommendations assigned to you, unassigned recommendations, or all recommendations:

      assigned_to_filter.png

      Assigned To Filter
    • Users with the new Recommendation Manager role can view recommendations assigned to others:

      assigned_to_others.png

      Assigned To Others
    • You can assign recommendation types to a specific user. This allows only that user to view all the recommendations of that type. To support this feature, a new Assign To field is available when configuring DARA (Configuration > General > General Configuration > DARA Recommendations):

      assign_to_recommendation_type.png

      Assign To - Recommendation Type
      Only users with roles configured to view the recommendation type are available in the drop-down list.
    Watch the Assigning DARA Recommendations video (1:36 minutes).

    4th and 5th reporting codes added to acquisitions entities  

    May 2021 AcquisitionsURM-124287
    Two new reporting codes have been added to the Purchase Order Line editing screen; 4th and 5th reporting codes. The additions include the following in Alma:
    • These new options within the PO line, Invoice line and Fund transaction screens (4th and 5th reporting codes).
    • Two new menu links in Alma configuration menu (4th and 5th reporting codes).
    • The names of the fields in the Alma UI have been modified and are now called "1st reporting code, 2nd reporting code, 3rd reporting code, 4th reporting code and 5th reporting code".
    • There is a new dedicated section for the reporting codes in the POL.
    • Only the UI labels have changed. The tags for API and EOD remain the same.
    Watch the Additional Reporting Codes in PO Lines video (1:53 minutes).

    Receiving workbench incorporates sticky filters

    May 2021 Acquisitions  idea exchange Idea Exchange URM-113263

    Alma's receiving workbench (Manage items screen) now incorporates sticky filters. These sticky filters (Sort Routine, Receiving Status and Location) enable users to easily re-access these workspaces when either a user leaves the screen and returns after a short while or logs in again to Alma. The filters remember the selections made by users so that they don't have to be re-defined when re-accessing the system.

    The Filter "Location" will be sticky only if there are items with the same location as previously selected. If a POL, which was opened, does not have items which match the value in the "Location" filter, the filter will automatically move to "All".

    If a "Sort Routine" is selected by the user and then deleted by the system administrator, the user who will login to the receiving workbench will not see the Sort Routine name listed. The user will need to select a new sort routine.

    Changing Holdings or Relinking Item is Possible Only in User Role Scope

    May 2021 Resource Management URM-148034

    Now when changing holdings for an item or relinking item to a bibliographic record, the target library must be within the scope of the user role. This prevents moving item or changing holdings for an item, if a new holding is not in user scope. When attempting one of these actions and the target library is not in scope, the user receives an error message "You are not allowed to move items to the selected holdings library" and the action is aborted. 

    user not allowed to move items to another library.png

    This functionality is disabled by default. To enable it, contact Customer Support. 

    See Moving Items Between Holdings and Deleting Holdings Records and Moving Holdings Between Bibliographic Records (Relinking).

    'Suppress from Discovery' is Available for Unsaved Records

    May 2021 Resource Management URM-89709

    The 'Suppress from Discovery' option is now available in the Record Actions menu of the Metadata Editor for new records before they are saved. This allows you to suppress from discovery new bibliographic records while creating them in the Metadata Editor. In addition, now you can use the new keyboard shortcut Alt+Shift+S to suppress records. 

    Discovery and Research Rules in the Rules Area

    May 2021 Resource Management URM-105811

    Now the Discovery Display rules (rules that control the display of information from Alma in Primo VE) and Research rules are easily accessible and easily distinguishable in the Metadata Editor. To create these rules, when clicking New, now users can select Normalization (Discovery) (appears only if Primo VE is defined in the system) or Normalization (Research) (appears only when Esploro is defined in the system). 

    creating discovery rules.png

    Each rule that you create has an appropriate badge (for example, "Normalization (Discovery)"), and appears in a dedicated tab (bearing the same name as the badge). 

    Heading Information in Metadata Editor and Repository Search

    May 2021 Resource ManagementURM-144783

    The ability to search for bibliographic records that are related to a specific heading was improved as follows:

    • In the Metadata Editor: When you search for bibliographic records related to a heading by Browse Bibliographic Headings > View, now you can open the results that display in the Bibliographic Records tab in the repository search. To do that, select the new option Open in Repository Search.
      Once the results are in the repository search, you can create a set that would include all these results, and work with the set as usual. This significantly improves the workflow for browsing bibliographic headings. 
      heading_information_search_MDE.png
    • A new option Heading Information was added to the Advanced Search. This option allows searching for bibliographic records related to a specific heading in the same way as by using Browse Bibliographic Headings in the Metadata Editor.
      heading information advanced search.png

    See Browsing Bibliographic Headings and Performing an Advanced Search

    Information Loss Prevented when Changing Item Location by Moving the Last Item to a New Holdings

    May 2021 Resource Management URM-29290

    When a holdings record holds only a single item, and you move this item to a different location, now the item remains associated to the same holdings record, and only its details are modified. Previously a new holdings record would be generated, and the information related to the previous holdings record, such as versions, notes, etc., would be lost. Now this information loss is prevented. 

    To notify users that there have been recent changes to the holdings record, an indication now appears in the History tab of the Physical Item Editor that states "There have been Holdings changes in the past 6 months". This indication appears when any type of change in the holdings took place, not only when the location has changed. Click the Holdings changes button to view the history of item changes. 

    Holdings changes in last 6 months.png

    Note that this behavior only takes place for a holdings record with a single item. When the holdings record has several items and you want to move some of these items, the existing functionality remains - a new holdings record is created and all the selected items are moved to that holdings record.  

    See Updating Item-Level Information.

    Field 060 Added to Search Index 'National Library of Medicine Call Number' 

    May 2021 Resource Management URM-39331

    MARC 21/KORMARC field 060 $$a,b was added to the index "NLM (National Library of Medicine)-Type Call Number". This in addition to MARC 21 field 096 $$a,z, which continues to be available for this index. Now searchers retrieving records from NLM can find records by using "NLM-type Call Number" index based on both fields 060 and 096.

    Full inventory indexing must be run for this development to take effect. 

    Metadata Editor Accessibility Improvements

    May 2021 Resource Management URM-73033

    The following improvements were done with the purpose of making Alma meet Level A and AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions.

    On the search result panel in the Metadata Editor (for example, Browse Shelf Listing panel), the users can use the mouse to navigate between the records and pages. However, some users might find the repetitive use of the mouse problematic. Now, these users can navigate the results list by using the keyboard's keys.

    You can navigate as follows:

    • Use Tab/Shift +Tab to navigate from the fields panel to the results panel.
    • Use Tab/Shift +Tab to navigate the different results panel tabs.
    • Use Tab/Shift +Tab to browse next and previous pages. Press Enter to open the desired page. 
    • Use Tab/Shift +Tab to navigate between results in the panels. Press Enter to open the desired result. 
    • Use the Enter to open the ellipsis button, and use the up/down arrows to move between the options. To close the options, press Esc/Tab (focus on the next button) or Shift +Tab (focus on the previous button).

    opening elipsys options with tab.png

    In addition, more accessibility improvements were made to improve the ability of screen readers to correctly convey the state of elements to the reader, on Browse Bib Heading panel, in the Editing panel and in the Filter and Sorting panel.  

    Alma Accessibility Improvements

    May 2021 Resource Management URM-142181

    The following improvements were done with the purpose of making Alma meet Level A and AA of the W3C Web Content Accessibility Guidelines (WCAG 2.1) and Section 508 of the US Rehabilitation Act for features and functions:

    • Form fields – A label was added for the "X" button.
      Page sections now have group labels.
    • Record List View – In internal search the labels of the search box and the search icon are now accessible by keyboard.
      The Sort Routing action is now accessible by keyboard:
      sort routine accessability improv.png
      The Expand action is now accessible by keyboard, and you can open and close the list using keyboard keys, see the selection there (if any), and remove or change it:
      Expand option.png
    • Floating Messages – the floating messages are now accessible by keyboard navigation. You can press on the icon to open the message and to navigate to the Collapse and Close buttons with keyboard keys. In addition, now the message indicates if there is a list of comments in the message or a single comment.
      floating message accessability improvements.png

    Holding Search - Additional Indexes

    May 2021 Resource Management URM-142153

    Additional indexes were added to holdings search. This allows you to conduct a more refined search for physical title and physical items. All these indexes are part of Advanced search only.
    searching encoding level within holdings.png

    New indexes 

    Index name

    Taken from

    Possible Values

    Show in Part of Keywords
    Encoding level  LDR pos17

    1 - Holdings level 1
    2 - Holdings level 2
    3 - Holdings level 3
    4 - Holdings level 4
    5 - Holdings level 4 with piece designation
    m - Mixed level
    u - Unknown
    z - Other level

    Advanced no
    Type of record LDR pos06 u - Unknown
    v - Multipart item holdings
    x - Single-part item holdings
    y - Serial item holdings
    Advanced no
    Receipt, acquisition, or access status 008 pos06

    0 - Unknown
    1 - Other receipt or acquisition status
    2 - Received and complete or ceased
    3 - On order
    4 - Currently received
    5 - Not currently received
    6 - External access

    Advanced no
    Method of acquisition 008 pos07

    c - Cooperative or consortial purchase
    d - Deposit
    e - Exchange
    f - Free
    g - Gift
    l - Legal deposit
    m - Membership
    n - Non-library purchase
    p - Purchase
    q - Lease
    u - Unknown
    z - Other method of acquisition

    Advanced no
    Completeness 008 pos16

    0 - Other
    1 - Complete
    2 - Incomplete
    3 - Scattered
    4 - Not applicable

    Advanced no
    Creation date (physical holdings) HOL creation date date field Advanced no
    Modification date (physical holdings) HOL modification date date field Advanced no
    URL method 856 $2 text simple and advanced no
    URL materials specified 856 $3 text simple and advanced no
    URL access status 856 $7 text simple and advanced no

    Pattern first level of enumeration

    853 $a text simple and advanced no
    Pattern second level of enumeration 853 $b text simple and advanced no
    Pattern third level of enumeration 853 $c text simple and advanced no
    Pattern fourth level of enumeration 853 $d text simple and advanced no

    Pattern fifth level of enumeration (NR)

    853 $e text simple and advanced no
    Pattern sixth level of enumeration (NR) 853 $f text simple and advanced no
    Pattern frequency 853 $w text simple and advanced no

    Textual holdings

    866 $a

    867 $a

    868 $a

    text simple and advanced no
    Linkage Number 014 $a text simple and advanced yes
    Control Number (Holdings) 001 text simple and advanced yes
    Other System Number (035a) 035 $a text simple and advanced yes
    Other System Number (035z) 035 $z text simple and advanced yes
    Other System Number (035a+z) 035 $$a,z text simple and advanced yes
    OCLC Control Number (035a) 035 $a (OCLC prefix) text simple and advanced yes
    OCLC Control Number (035z) 035 $z (OCLC prefix) text simple and advanced yes
    OCLC Control Number (035a+z) 035 $$a,z (OCLC prefix) text simple and advanced yes
    Action note note 583 $$x,z text simple and advanced yes

    Action Note Authorization

    583 $f text simple and advanced yes

    URL

    856 $u text simple and advanced yes
    URL non public note 856 $x text simple and advanced yes
    URL link text 856 $y text simple and advanced yes
    URL public note 856 $z text simple and advanced yes
    Textual holdings nonpublic note

    866 $x

    867 $x

    868 $x

    text simple and advanced yes
    Textual holdings public note

    866 $z

    867 $z

    868 $z

    text simple and advanced yes

    Full inventory indexing must be run for this development to take effect. 

    See Search Indexes.

    Overlap Analysis Tool - Support for Sites with Distributed Electronic Resources

    May 2021 Resource Management URM-140755

    Sites who manage distributed electronic resources using the 'Available For' group setting can now use the Overlap and Collection Analysis tool for collection development analysis. Using the Overlap and Collection Analysis tool it is possible to analyze the overlap of electronic resources for specific library/campus according to the 'Available For' group settings. 

    See Working with Overlap and Collection Analysis and Overlap and Collection Analysis Job Reports.

    This feature is not activated by default. Please contact Ex Libris support in order to enable it.

    Semi-Annual Re-indexing

    May 2021 Resource Management URM-128820
    During May, 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 May semi-annual re-indexing. See the list below.
    • Holding Search - Additional Indexes. See here
    • Field 060 added to search index 'National Library of Medicine Call Number'. See here
    • Support for Czech Alphabet. See here.
    • Extended Lookup for Authority UNIMARC Classification. See here

    Solution for Institutions with 'Active for Search' restricted collections

    May 2021 Resource Management 

    URM-142654

    Alma now allows institutions to use the search activation function for collections that require a subscription for search (for example, A&I databases). Such collections are marked on Alma as 'CDI search rights: Subscription'. Previously, it was only possible to activate these collections in Alma in the same way you activate a full text collection (or use the ‘CDI only full text: Yes’ setting) to indicate the institution had a subscription and the collection would become searchable in CDI. This was not intuitive and led to a lot of confusion, not least because such collections do not usually contain any full text. With this release, both types of activations are now possible. No changes are needed for collections that you already activated, and you can continue to fully activate these types of collections. Additionally, activation for search in CDI is now also possible and has the same effect as the full activation: both types of activations will ensure the collections will be discoverable in CDI.

    This change is relevant for Fully Flexible setting customers only.

    Generate Representation Labels from Templates

    May 2021 Digital Resource Management idea exchange Idea Exchange URM-134626

    You can now add labels to representations based on a template that you configure. The labels can be fixed text or based on a field from the bibliographic record with an optional regular expression. Labels can be added to representations individually or in bulk using a job. In addition, a job can be used to remove the labels from representations in bulk.

    You configure the representation templates from the Representation Label Template Setup Editor (Configuration > Resources > General > Representation Label Templates). To create a template for representation labels, create a parameter with an entity type equal to None.

    entity_type_none.png

    Entity Type - None

    The following fields are displayed.

    representation_label_output_parameters.png

    Representation Label Output Parameters

    Enter information in the fields to determine the text of the label. For more information, see Configuring Representation Label Templates for General Representations.

    You can add the labels defined in the templates to representations:

    • To a single representation:

      The Auto-Generate Label button now appears for all representations.

      auto_generate_label.png

      Auto-Generate Label

      Select the button to add a label to the representation according to the template you configured.

    • To a set of representations:

      Create the set of representations to which you want to add the labels. Configure the Global Representation Changes job to run on the set.

      global_representation_changes.png

      Global Representation Changes

    From the Label row, select Generate.

    To remove labels from the set, from the Label row, select Empty.

    For more information, see Global Representation Changes.

    Suppress Bibliographic Records Without Active Inventory

    May 2021 Digital Resource Management URM-105189/span>idea exchange Idea ExchangeURM-105189

    You can now configure the Global Representation Changes job to suppress bibliographic records that have no active inventory after the job is run. To configure this feature, select the Suppress bib without active inventory option when selecting Inactive from the Label row.

    suppress_bib_without_active_inventory.png

    Suppress Bib Without Active Inventory

    For more information, see Global Representation Changes.

    Additionally, when manually setting an individual representation to Inactive, if there are no other active representations on the bibliographic record, a pop-up appears asking if you want to suppress the record.

    suppress_bib_record_confirmation.png

    Handling Bibliographic Record Without Active Inventory - Confirmation

    In addition, a parameter was added to the Update Representation Rest API to suppress bibliographic records without active representations.

    Support ability to Waive All/Large lists of Fines/Fees in User Record (Fines and Fees tab)

    May 2021 Fulfillment URM-75227

    Alma now enables user to select fines and fees across the full paginated fees list (among multiple pages) and waive them. A 'Waive All' option is added to the Fines\Fees tab. Previously, users could only waive selected fines and fees on a currently displayed page. 

    For more information, see Managing User Fines and Fees.

    The new ability to select fines and fees across the full paginated fees list (i.e. selecting from different pages) implies that any personalization a user may have previously done for the fees' list columns will have to be redone following this release.

     

    It is not possible to waive more than 100 selected fees in one action.

    Watch the Waive All the Fines and Fees of a Patron video (1:13 minutes).

    Search user records by phone number

    May 2021 Fulfillment   URM-142433

    In Alma, phone numbers are now a searchable user field. Phone numbers can now be entered in the simple or the advanced  search to find users. Previously, this was not a supported search user field in Alma.

    Since phone numbers are encrypted upon save, a phone search will be an exact match search (e.g. if country code is entered in the phone number it should be used when searching), on numeric values only (any non-numeric values, e.g. hyphens, spaces or brackets, will not affect the search).

    Sort user list by User Group Code and Expiration/Purge Date

    May 2021 Fulfillment   idea exchange Idea ExchangeURM-140301

    Alma now enables the User List to be sorted by User Group Code, Purge Date  and Expiration Date. When using the advanced search, a set can be created to include multiple user groups. These groups or the expiry/purge date can now be sorted. The purge date column is hidden by default and can be added to the displayed columns.

    Pop-up message when scanning in an item with a request note

    May 2021 Fulfillmentidea exchange Idea ExchangeURM-138658

    A new 'Requester Note' message has been added to the Scan In Messages Configuration screen. By default, this message is enabled and will appear as a 'Pop-Up'. The message will be displayed when an item that is scanned in has a 'Requester Note' associated to it.

    Watch the Requester Note Appears Upon Scanning In an Item video (1:39 minutes).

    Enhanced export when sending requests to remote storage

    May 2021 Fulfillment URM-141730, URM-141732

    The integration profile for exporting requests to remote storage was enhanced in the following ways:

    1. Privacy enhancement: For integration types XML and XML/NCIP (regardless of system type), a new configuration, "Include patron info in physical item requests", now allows libraries to have patron information in the exported XML for physical requests.

    For digital requests, patron information is controlled by an existing configuration (‘Handles digitization requests locally' in the remote storage). In the past, this affected physical requests as well - this was fixed, and digital requests handling will no longer affect physical requests. Libraries that wish to include patron information in physical requests will need to enable the new checkbox in the integration profile.

    It is our recommendation that libraries that choose to export patron information will use an encrypted sFTP connection (see FTPing encrypted files to Alma using PGP).

    1. XML file changes: For integration types XML and XML/NCIP (for system "BIBSYS" and "XML" only), the following information is added to the exported file:
      • Request note
      • Title (exists today for manual description requests only, will be added for all request types)
      • Author
      • ISSN/ISBN
      • Place & date of publication
      • When patron information is exported, it will now include requester's preferred address
    2. Request itemization enhancement: A new "itemize remote storage requests" option was added to the remote storage integration profile (export request section). This allows libraries to choose if remote storage requests are itemized upon export (as today) or when waiting for export to remote storage.
      For more information, see Requests to Remote Storage Facilities.
    3. The label "System (for EXL purposes...)" is modified to "System" – as the remote storage system may impact the XML file format for integration types XML and XML/NCIP.

    Locate status added to the audit trail of borrowing and lending Resource Sharing requests

    May 2021 Fulfillment-Resource Sharing URM-142219

    Locate status has been added to the audit trail of borrowing and lending RS requests. This allows librarians to see when locate status changed between "Locate not run", "Resource located" and "Locate failed". This change in the 'locate status' is reported in the request history.

    Prefer electronic format in lender locate

    May 2021 Fulfillment-Resource Sharing URM-141640

    Alma can be configured to show preference to electronic format articles in the lender side locate process. If a requested article is found in electronic format then that resource will be considered the only option for the lender. Other potential physical options are considered only if no electronic resources are found.This behavior is activated by the new "Prefer Uresolver locate results" switch that can be switched on at the Lending Setup section of the resource sharing library. Note that electronic resources are considered a match only if their coverage matches the details of the request.This affects both the automatic and the manual locate process on the lender side.

    For more information, see Configuring Parameters of a Resource Sharing Library.

    Combined Search - Support For Electronic Collections of Type Database

    May 2021 Collaborative Networks URM-141679

    Electronic collection of type 'Database' (electronic collection with no portfolios) managed in the Network Zone for all members or for specific members (using an 'Available For' group) will now be included in the Institution Zone's combined search for the relevant member. 
    Using combined search results provides consortia members quick access to electronic resources that are managed for them in the Network Zone.

    combined search - support electronic collections with no portfolios.png

    This functionality is supported for institutions where combined search is enabled. Contact Customer Support to enable combining Institution and Network Zone search results. For details, see Combining Institution and Network Zone Search Results

    New Acquisitions and Fulfillment Dashboards

    May 2021 Analytics URM-146004

    The following new out-of-the-box dashboards were added to Alma Analytics. For each dashboard, a new analytics object of type Dashboard was added. The dashboards are now available as links from the Analytics menu in Alma according to the following roles:

    • Acquisitions – Claims Dashboard (Ex Libris)
      and
    • Acquisitions – Fund Reports (Ex Libris):
      • Acquisitions Administrator
      • Fiscal Period Manager
      • Fund Manager
      • Invoice Manager
      • Invoice Operator
      • Invoice Operator Extended
      • Ledger Manager
      • Purchasing Manager
      • Purchasing Operator
      • Purchasing Operator Extended
      • Receiving Operator
      • Receiving Operator Limited
      • Vendor Account Manager
      • Vendor Manager
    • Fulfillment Loans Returns and Overdue Dashboard (Ex Libris):
      • Circulation Desk Manager
      • Circulation Desk Operator
      • Fulfillment Administrator
      • Fulfillment Services Manager
      • Fulfillment Services Operator

    The old Acquisitions – Claims dashboard is now marked to be deprecated and will be removed for the June release.

    Improved Letter XML Examples

    May 2021 Administration and Infrastructure URM-142450 idea exchange Idea ExchangeURM-142450

    When configuring letters, users can make use of out-of-the-box XML examples. These examples were now enriched to provide more detail that can help uses to customize the letters. To view these examples, open the DefaultLetter.xml file that is located in the Letter Examples tab of the Letters Configuration page for the desired letter. 

    Letter_Examples tab.png

    Testing Authentication on SAML Integration Profile

    May 2021 Administration and Infrastructure URM-146296

    Alma supports the SAML 2.0 Web Browser SSO profile. This enables Alma to exchange authentication and authorization information, allowing a user to sign in or out of an external system and be automatically signed in or out of Alma, or vice versa. For the details of configuring this profile, see SAML-Based Single Sign-On/Sign-Off

    The Save And Test button has been added to the log-in integration profiles (SAML, CAS, LDAP and social log-in profiles). This removes the need to log out from Alma and log in again, and if the authentication fails, provides a clear indication of what went wrong. 

    Currently, this is available for the SAML integration only. In the upcoming releases, this will be supported on all authentication integrations.

    See Testing Authentication on SAML Integration Profile.

    Download Staff Login Report via API

    May 2021 API URM-145346

    Previously in Alma, creating a login report required a staff member to login, produce and download the Excel spreadsheet, and convert it to CSV. Alma now enables institutions (via API) to retrieve staff login data via a new API and further execute processes as they desire, e.g. export it to a CSV file. For more information on creating the report via the API, click here and scroll to section labeled Staff Login Report.

    Fund Management APIs

    May 2021 API URM-145081

    Alma enables institutions to create a richer integration with their finance systems with updated capabilities of retrieving funds and associated transactions. The Fund Management APIs have added the following two capabilities:

    • Search and Retrieve Ledgers and Funds
    • Search and View Transactions for a fund

    For more information, see Fund Management APIs.

    API for running Import profile on a single BIB record

    May 2021 API URM-123393

    Alma introduces a new API designed for running Import profiles on a single BIB record. The new API, labeled "Importing a single record" will execute the following:

    • Receive an import profile ID as a parameter
    • Receive a BIB record as payload
    • Run the import profile on the BIB and return the resulting BIB record:
      • If no match found - a new record is created.
      • If match found - the matched record is used.

    This will be done in a similar way to the existing "Import a single record" option in Alma: In order to run the API you will need to have a defined import profile. The API will import a bibliographic record only – not inventory records.

     

    This API is intended for individual record imports. Bulk imports should be performed via the MD Import functionality.

    New fields added to the REST Item APIs

    May 2021 API URM-104745

    A number of existing item fields in Alma (previously not supported by API) have now been added and are supported in the REST Item APIs. Listed below are the added item fields:

    • Issue date (get, put, post)
    • work_order, process_at (currently will be added only to GET and will not be supported in PUT/POST)
    • temporary location source (get, put, post)
    • break indicator (get, post, put)
    • pattern type (get, post, put)
    • linking number (get, post, put)
    • type of unit (get only)

    Chat with Support

    March 2021 Administration and Infrastructure URM-146018

    Staff users who have been assigned chat permissions can now chat with our Support team regarding the following types of Alma and Leganto issues directly from within the Alma management interface:

    • Simple how-to questions and configurations
    • Behavior and general inquiries
    • Known issues

    PVE_ChatLink_NewLayout.png

    Chat Icon in Alma's Persistent Menu

    This functionality is disabled by default. Only staff users who have been assigned the Chat with Support role will be permitted to open a Chat session with our Support team. For more configuration information, see Managing User Roles.

    For more details, see Online Chat Support and Chat Support Availability.

    Beginning on March 1, 2021, Chat will be available for Alma and Leganto customers who are in production in the European region. For production customers in the North American region, Chat will become available a couple of weeks later. Chat will not be available for customers in implementation.

    PO Line Infrastructure Upgrade

    March 2021 Acquisitions URM-136168
    In upcoming releases, technical upgrades to the PO Line infrastructure will take place, which will not result in any functional changes.

    New Option To Replace Resource Associated With An Electronic PO Line

    March 2021 Acquisitions URM-140777
    When editing an electronic PO line (Collection/Portfolio) users now have the option to detach the existing resource from the PO line and replace with another electronic resource associated with the Institution Zone, Community Zone or the Network Zone. Additionally, an indication to which "Zone" the resource is associated with, was added to the Ordered items table with the color coding Alma uses to indicate whether the resource is "Available" or "Not Available".



    Utilizing the "Replace Resource" function will prevent the users from the need to delete a PO line in case it was associated with the wrong electronic resource. Institutions who are part of a Network Zone and their Electronic resources are managed by the Network Zone (but their purchases are handled locally) will be able to:

    • Create a local PO line associated with an electronic resource.
    • Send the order to the vendor.
    • Once the resource is available for them, ask the Network institution to enable the electronic resource in the Network Zone and have it "Available for" them.
    • Use the new function to replace the resource associated with the PO line with the Network Zone resource made available for them.

    In case the PO line doesn't have a license and the Network Zone resource has a license - the Network Zone license will be associated with the POL. In case the PO line has a license and the Network Zone resource has a license as well - the Network Zone license will not be associated with the POL.

    This operation is available for any resource type of type "Electronic" and the resource type for the replaced resource must be with the same "Type". For example: if the source resource is "Electronic Portfolio", only "Electronic Portfolio" can be selected as the new resource.

     

    In case the resource replaced is associated with a different bibliographic record, the POL will be associated with this new bibliographic record and the user will be prompted with a pop-up asking whether to keep the detached resource or delete it. In case the user selected to delete the electronic resource and the bibliographic record for that resource has no other inventory associated to it, the a pop-up will also present the user with the options to handle this bibliographic record (depending on the settings done for pol_handle_bib_record_without_inventory.

    Read more about this parameter here.

    Multiple runs per day for PO packaging and EDI jobs

    March 2021 Acquisitions URM-140017

    In order to improve communication between Alma and vendors, additional scheduling options were added to the PO packaging job so that PO lines can be packed automatically to a PO several times a day and ready to be sent to the vendor. For institutions using EDI to communicate orders with their vendors, institutions now can have the EDI job run a few times a day. This will result in orders being sent to vendors closer to the time the orders were actually created in Alma. The 2 new scheduling options for both jobs are "Every 2 hours" and "Every 4 hours".

     "PO Line package" job which handles purchase order lines that are not marked for manual packaging was added with two more scheduling options in addition to the existing job scheduling options (located in Configuration > Acquisitions > Job configuration):

    Read more about PO packaging job.

    "EDI" job runs to communicate with vendors configured to work with EDI. Two more scheduling options were added in addition to the existing job scheduling options to allow the communication to run multiple times per day (located in Vendor > EDI information > Input job parameter):

    Read more about EDI job scheduling.

    New "Survey Language" field in the trial surveys editor

    March 2021 Acquisitions URM-64646

    In order to allow Survey composers the ability to send a survey form in a dedicated language (other than English), institutions utilizing the Trials functionality in Alma now have a new field "Survey Language" which was added to the survey editing form ("form configuration" section), this new field supports selecting the language in which the survey is sent to the user (up until today users which received the survey had the option to view it only in English). 
    When creating a new trial or editing an existing trial, the default language in this field will be the institution's default language. 

    Text for questions that are composed by the creator of the survey should match the language selected in the new "Survey Language" field.

    Read more about Managing Trials in Alma.

    Watch the Compose a Trial Survey in a Selected Language video (0:53 seconds).

    New Metadata Editor

    New Metadata Editor Layout Turned On as Default for All Users

    March 2021 Resource ManagementURM-145427

    Continuing the rollout of the new Metadata Editor, starting from this release, the new Metadata Editor opens up for all Alma users as the default.

    Users can switch back and forth between the new and the original Metadata Editors.

    To switch:
    • to the new Metadata Editor, select new MDE button.jpg on the right-hand side of the top toolbar of the Editor.
    • back to the original Metadata Editor, select  Old Editor on the right-hand side of the top toolbar of the Editor.

    Ex Libris recommends that all relevant users become familiar with the new Metadata Editor prior to it becoming exclusive use, which is planned to take place with the deployment of the June 2021 release.

    Rules Management in Metadata Editor

    March 2021 Resource ManagementURM-98936

    Ex Libris continues the rollout of the new Metadata Editor. In the current release, the Rules Management core functionality was introduced (the functionality available in the original Metadata Editor plus new features). 

    See New Metadata Editor Functionality.

    Rules Right-click Menu

    March 2021 Resource ManagementURM-132883

    You can now perform actions in the Rules area from the right-click menu in the new Metadata Editor. See below for the list of right-click actions:

    Rules right-click Menu
    Action Available for Description
    Edit Private rules,
    Shared non-default rules
    Select to edit the rule (not available for out-of-the-box (default) rules and Community Zone rules). 
    View All rules Select to view the rule in cases when you cannot edit it.
    Duplicate  All rules Select to duplicate the rule to modify the copy and create another rule based on this rule. 
    Contribute to CZ All rules Select to contribute this rule to Community Zone (if you have this capability).
    The contributed rule appears both in the Shared folder and in the Community Zone folder. 
    Properties All rules Select to view and modify the rule properties, such as its name.
    Delete  Institution rules,
    CZ rules contributed by your institution
    Select to delete the rule (available for local rules and rules in the Community Zone that were contributed by your institution).
    Test external records Institution rules Select to save and test the rule in Primo-VE. For details, see Testing Normalization Rules for External Data Sources.

    Message to Users Opting-out from New Metadata Editor

    March 2021 Resource ManagementURM-140860

    Starting from the March release, only users with the below roles can opt-out from the new Metadata Editor and work in the classic Metadata Editor:

    • CATALOGER
    • CATALOGER_EXTENDED
    • CATALOG_ADMINISTRATOR
    • CATALOG_MANAGER
    • PHYSICAL_INVENTORY_OPERATOR (users with this role can switch back to the class Metadata Editor only if they have a cataloger role as well)
    • PURCHASE_MANAGER
    • PURCHASE_OPERATOR
    • REPOSITORY_MANAGER

    Users who haven't opted-out or did not switch to the new Metadata Editor yet, will get a message with a link to opting-in and a warning that the classing Metadata Editor is only available till June 2021.

    See Usability Improvements.

    Enhanced Message Display

    March 2021 Resource ManagementURM-142406

    The display of messages in the new Metadata Editor was enhanced. Notification messages that appear in a specific context (related to records, rules, etc.), now appear in the relevant panel of the Metadata Editor:  
    message in context 1.png

    Opening New Holdings from the Add Inventory Menu

    March 2021 Resource ManagementURM-143706idea exchange Idea Exchange

    The ability to add new holdings was added under the Add Inventory menu (in addition to the existing ability to add them under the New menu). This makes it more intuitive for operators to create new holdings.

    The same Holdings section that appears in the New menu now also appears in the Add Inventory menu. You can choose which template to use for creating the holdings in the same way as it is done in the New menu. 

    add new holdings under add inventory.png

    See Add Inventory Menu.

    Watch the Add New Holdings from the Add Inventory Menu video (0:47 seconds).

    Accessibility Improvements in the New Metadata Editor

    March 2021 Resource ManagementURM-142176

    The below improvements were done with the purpose of making the new Metadata Editor compliant with the Americans with Disabilities Act (ADA). The improvements include:

    • Ability to close the Navigation panel using keyboard, when it is opened in hover above the Metadata Editor. To close it, press Escape. Note that if a tooltip is opened in the Navigation panel, you have to press Escape twice - the first closes the tooltip, the second closes the Navigation panel. 
      navigation panel on hover.png
    • You can now navigate up and down within the lists of items in the Navigation panel using the keyboard. 
    • You can now open the Alerts panel and navigate within it using the keyboard. 
    • Unique IDs were added to Html elements of each record/template/rule in the Navigation Panel and within the Editing area.
    • The page title was set to "Metadata Editor" for screen readers.

    Editing Tasks from Authority Control Task List in the Metadata Editor

    March 2021 Resource ManagementURM-123960

    Now when you review tasks in the Authority Control Task List, you can edit the relevant record directly in the Metadata Editor. To support this, a new type of set "Authority Controlled Task List" was created under Sets in the Records area. To open records in the Metadata Editor, select the desired records in the Authority Control Task List and select Edit in the row list actions, or Edit Selected above the list.  

    Managing Brief Levels in Record Header

    March 2021 Resource Management URM-134130

    The brief level indication now appears in the record header for all MARC bibliographic formats.

    brief level in new MDE.png

    See Working with Brief Record Levels.

    Side-by-side Editing of Primary and Searched/Browsed Records

    March 2021 Resource Management URM-140990

    Now you can view the searched/browsed record alongside your primary bibliographic record, whether on the right of the primary record, or on the left. This allows you full flexibility in how you want to display the records, while also providing easy navigation back to the search form to refine your search if needed.

    See Working with Search Resources in the MD Editor.

    Use Existing Bibliographic Record when Creating a PO Line via "New Order" Import Profile

    March 2021 Resource Management URM-142153

    Continuing the enhancements to the "New Order" import profile (see Associate a PO Line Created via the Import Profile to an Existing Portfolio), now you can use the existing matched bibliographic record without modifying it, and associate the newly created resource and PO line under this matched bibliographic record. In case a matching resource is also found under the bibliographic record (see Associate a PO Line Created via the Import Profile to an Existing Portfolio), only a PO line will be created.

    To support this, a new radio button "Use Existing Record" was added to the Match Profile tab of the Import Profile (New Order profile only). When this radio button is selected, Alma does not update the bibliographic record and and only creates the resource and the PO line.

    Community Zone Update Task List Improvements

    March 2021 Resource ManagementURM-141433idea exchange Idea Exchange

    The Community Zone Update Task List is used to display all changes that were made to to your Community Zone activated electronic resources as a result of Community Zone updates. The Community Zone was enhanced to enable faster and more efficient access to the data included in it. This includes new access points, information fields, actions, as well as more filters and sorting abilities. All the new features apply to both the Review and All tabs. 
    enhancements to cz updates task list.png

    Enriched Title Display
    The Title of the portfolio is now identical to the way the portfolio's Title is displayed in the Service editor Portfolios list.

    Enhancements to Columns
    All new columns are hidden by default. 

    • Submit Date (enhanced column) - now displays date and time of the change. When portfolios are added or deleted, this helps you know which came first from the task list, thus letting you know if content was removed without being re-added. The date and time formats are defined by customer parameters system_date_format and system_time_format.
    • Resource ID (new column) - displays the local ID of the resource (portfolio ID / electronic Service ID / Electronic Collection ID), depending on the resource level of the selected Report Type.
    • Resource Type (new column) - displays Electronic Portfolio / Electronic Service / Electronic Collection to let you know the resource level of every entry.
    • Is Free (new column) - displays the electronic collection/electronic service's 'Is Free' parameter value (if the override is populated, displays the override value). For every Collection/Service, state Yes/No, and for Portfolio states the portfolio's Service's 'Is Free' value (inherited).
    • Collection Type (new column)  - displays the electronic collection's type: Selective package / Aggregator package / Database.
    • Collection content type (new column) - displays the electronic collection type: Book Package / Journal Package / Mixed Package / Abstract & Index Package / Web Service / Database.
    • Library (new column) - displays the library of the resource. If the library is inherited from the e.collection, displays "<Library_Name> (e.collection)".
    • Orders (new column) - displays the number of the resource's PO Lines. The number is a link, select it to view the relevant PO Lines. Select Back to return to the Community Zone Update Task List.
    • Local Information (enhanced column) - previously appeared only on the Review tab. Now it was added to the All tab as well.

    Enhancements to Row Actions

    • Edit Electronic Portfolio / Electronic Service / Electronic Collection - Select to open the resource in its editor (if you have the required permissions).
      If you do not have editing permissions to the resource, you will be able to view the resources but not edit them.
      This option is not available for deleted resources. 
      To return to the Community Zone Update Task List after editing/viewing the resource, select the new "Review CZ Updates" button that appears at the top of the resource (see below for details).
    • Report To ExLibris - Select to send a report for Ex Libris, in case of any issue. 

    Enhancements to Reports

    • Portfolio deleted from non auto-active electronic service - The report 'Portfolio deleted from non auto-active package' was renamed to 'Portfolio deleted from non auto-active electronic service'This is because an electronic collection may have more than one electronic service, with one service set to auto-active and the other to non auto-active, so the portfolio inherits its auto-active status from the electronic service, not the electronic collection.
    • Portfolio deleted from auto-active electronic service - This report was available previously in the All tab. Now is is available on both tabs. The report lists the portfolios deleted from electronic services that are defined as "Activate new portfolios associated with service automatically" = Yes.

    New Filters 
    New filters were added:

    • Electronic Service - Include the values All / Auto-Active / Non Auto-Active. This filter displays only entries of the Service level. This filter has no corresponding column.
    • Resource Type - Includes the values All / Electronic Portfolio / Electronic Service / Electronic Collection. If any of the resource types is not displayed in the table, the filter does not provide the option to filter by it.
    • Has Order - Include the values All / Yes / No. If any of the resource types is not displayed in the table, the filter does not provide the option to filter by it.
    • Is Free - Include the values All / Yes / No on the electronic service and electronic collection levels only.
    • Has Local Information - Includes the values All / Yes / No
    • Library - Includes the available libraries of the institution.
    • Collection content type - Include the values All / Book Package / Journal Package / Mixed Package / Abstract & Index Package / Web Service / Database. If any of the resource types is not displayed in the table, the filter does not provide the option to filter by it. 
    • Collection Type - Include the values All / Selective package / Aggregator package / Database. If any of the resource types is not displayed in the table, the filter does not provide the option to filter by it.

    New Search Options
    New search options were added to enable searching for a specific identifier, MMS ID, and Resource ID.

    Default Time Range Modified
    The table's time range now defaults to the last 30 days.

    New Sorting Options
    The table now supports the ability to sort from additional column headers:

    • Identifier
    • Resource Type
    • Is Free
    • Package Type
    • Collection Type
    • Library
    • Orders

    New Selection Counter and Ability to Clear Selection
    On the Review tab, a selection counter was added. The counter supports multi-page selection. Also, an action Clear selection was added, to enable easily clearing of the selected rows across pages.

    See Working with the Community Zone Updates Task List.

    New Access Points to the Community Zone Update Task List from Electronic Resource Editors

    March 2021 Resource Management

    New access points were added to the electronic resource editors (Electronic Collection Editor / Service Editor / Portfolio Editor) that enable navigating from the editors to the Community Zone Update Task List page. The access point is the button "Review CZ Updates (X)", where "X" indicates the number of CZ updates available in the Review tab of the Community Zone Update Task List for that resource.
    Review CZ update button.png

    This button appears for resources linked to the Community Zone, including portfolios that were linked to CZ in the past and got localized due to portfolio deletion from the CZ. This button appears only for users with Repository Manager role (regardless if the role's scope is library-level or institution-level).

    See Accessing the Community Zone Update Task List from Electronic Resource Editors

    User Interface Improvements in Accession Number Generation Configuration 

    March 2021 Resource Management URM-143863

    The user-interface that supports the generation of call numbers and temporary call numbers for items was enhanced to enable you to work quicker with a large number of call numbers:

    • Pagination and search were added to the Accession Configuration page (Configuration Menu > Resources > General > Accession Number) and to the Accessions Number list that opens when generating a call number from the Metadata Editor. 
    • In the Accession Configuration page, saving is now automatic, which means all data that you enter is saved without the need to select the Save button (which was removed from this page.)
      Accession configuration new table.png

    See Configuring Accession Numbers

    Accessibility Improvements

    March 2021 Resource Management URM-142176

    The following improvements were done with the purpose of making Alma compliant with the Americans with Disabilities Act (ADA):

    • Recently used options in dropdown lists are now labeled with a recently-used indication. 
      accessability_issues_march_1.png
    • The Clear button in the search bar is now accessible by keyboard navigation and is labeled. 
      accessability_issues_march_2.png
    • The Selection History button in pickup fields is now a label and complies with the screen reader expectations. 
      Selection History button.png
    • The Search bar input field now displays an explanation of what to do in the field.
    • All options in dropdown lists are now enabled to keyboard navigation, the screen reader reads the correct number of options.
    • Input fields in the Advanced search were labeled appropriately.
    • Group fields in the Advanced search are now marked as a group. 
    • When multiple buttons exist in the Advanced search, each now has its own label. 
      accessability_issues_march_4.png

    Denied Note for Unregistered Users

    March 2021 Digital Resource Management URM-138800

    When defining access rights for digital objects, you can now configure a separate Denied Note for unregistered users. This allows you to have one note configured to inform unregistered users of the need to log in and a separate note for logged in users to inform them of additional conditions required for viewing the resource. To support this development, a new Denied Note (override for unregistered users) field was added to the Access Rights Policy page.

    access_rights_policy.png

    Denied Note (override for unregistered users)

    Enter the note in this field that you want to appear when access is denied for unregistered users. If no note is configured, the note configured in the Denied Note field is displayed.

    For more information, see Access Rights Policies for Digital Objects.

    PDF.js Viewer now Available to Display PDFs

    March 2021 Digital Resource Management URM-120743

    Alma now uses the PDF.js viewer when displaying PDFs to provide a rich tool set of viewing capabilities.

    Enhanced request cancelation after “date needed by” has passed

    March 2021 Fulfillment  idea exchange Idea Exchange URM-23558

    The "Date needed by" field (also known as “Not Needed After”), which can be populated by the patron, was taken into account only in the "pick from shelf" workflow step, cancelling the request when the date was in the past without sending a cancel notification (since the patrons indicated tthat hey are no longer interested).

    Following this development, this behavior will be applied in other workflow steps in the request lifecycle:

    • Queued requests that are not yet active but are past their date needed by will now be canceled by the "Request - handle last expiration STEP" (to avoid recalling items to fulfill requests that are no longer relevant).
    • When an item is scanned in, if the "date needed by" of the request had passed, the request will be canceled.
    • When an item is placed on the hold shelf, if the date needed by is earlier than the regular hold shelf expiry, the hold shelf expiration date will be populated by the date needed by (so that the request will not remain on the hold shelf after the patron is no longer interested).

    A new cancelation reason, “date needed by has passed”, was added for requests that were canceled because the date needed by indicated by the patron was reached before the item could be placed on the hold shelf.

    Requests in transit will not be canceled when their date needed by is past, as the transit step needs to be completed. The cancelation will happen when the item is scanned in at the destination.

     

    If a library is not interested in working with Date Needed By, it can hide the "notNeedAfter" field from the patron’s request form. See: Customizing Primo Request Forms, Configuring Request Forms for Primo VE or Configuring the Request Forms for Alma-Summon.

     

    If date needed by is enabled on RS requests, the requests will also be affected. Customers who wish to prevent automatic cancellation of requests that are no longer required by patrons can remove the field from the request form.

    Refresh "linked accounts" when using Primo VE My Account

    March 2021 FulfillmentURM-143769

    In Primo VE, when a Fulfillment Network patron uses the Primo VE My Account to view activity in another Alma institution, their linked account in that Alma institution is now refreshed using the user record at the patron's home institution. Refreshing the account allows an up to date assessment of the patron's eligibility to renew loans (e.g. if the patron is blocked).

    Temporary renew of a Resource Sharing loan

    March 2021 Fulfillment-Resource SharingURM-131560 NERS NERS Enhancement (ID #6962)

    In Alma, when asking a lender to renew a RS loan that is about to become overdue, it is now possible to have the loan due date extended by a configurable short period (up to 9 days after the request renew date). This will prevent the loan from becoming overdue and accruing fines while the lender is contacted to arrange a renewal and new due date. Once the renewal has been confirmed with the lender, the loan and the borrowing request will be renewed to the agreed upon due date (using the existing workflow). The option is activated by selecting the new 'Extend due date when renew requested'   checkbox and populating the new ''Extend due date by (days)' field on the resource sharing library configuration page.

    Borrowing and lending request lists to display create and update time

    March 2021 Fulfillment-Resource Sharing idea exchange Idea ExchangeURM-124170

    In Alma, the borrowing and lending resource sharing requests lists will now display the time as well as the date in the create and update date. This feature will enable institutions to sort borrowing and lending requests by date and time, to help libraries that want to handle digitization requests quickly and efficiently. The time display will depend on the institution’s system_time_format customer parameter.

    Recall process for SLNP requests

    March 2021 Fulfillment-Resource SharingURM-75741

    A lender using Simple Library Network Protocol (SLNP) can now recall items by sending a recall email to the email address configured in the SLNP partner of the borrower. When recall is allowed in the partner’s workflow and triggered by the operator or an incoming request, the Lending Recall Email Letter email is sent to the borrowing library and the lending request is considered recalled.

    Primo VE Blank Request DOI/PMID Lookup Options

    March 2021 Fulfillment — Resource Sharing URM-126299

    It is now possible to add ‘Auto Fill’ buttons to the DOI and the PMID fields of the article request form. When clicked, Alma uses the value in the DOI or PMID fields to search for the article information and auto-completes the remaining form fields (such as article name and pages) based on these identifiers.

    Blank_Request_Form.png

    Activate this feature by enabling the new ‘DOI Auto Fill’ and ‘PMID Auto Fill’ fields on the Discovery > GetIt Configuration > Resource Sharing Request configuration form.

    Additional Chapter and Article Information in Primo VE My Account Requests Lists

    March 2021 Fulfillment — Resource Sharing URM-141075

    Resource sharing requests listed in Primo VE’s My Account requests lists are now richer with more information describing the requests’ publication date, pages, and name of the journal.

    My_Account_Requests_Lists.jpg

    Book chapter requests include their chapter title, author, and number in addition to the requested pages. The fields only display if they are populated.

    New System Events Subject Area

    March 2021 Analytics URM-142900

    The new System Events subject area is intended to replace the current Events subject area. The current Events subject area reports on a very large number of events, some of them redundant or not used, which makes it very difficult to produce effective reports on events that run in a reasonable amount of time. The new System Events subject area includes only a select number of events so that reports can be run quickly and efficiently. For a period of time, both subject areas will be available to allow customers to adjust to the new System Events subject area.

    The following events are available in the System Events subject area:

    • Events that are used in reports that the institution created and ran at least once in the past year.
    • Events in out-of-the-box reports under Alma/shared/events/reports
    • Events related to the creation, deletion, and update of invoice lines and invoices 

    For more information, see System Events.

    Borrowing and Lending Request Time in Hours and Minutes

    March 2021 Analytics URM-141733

    Previously, it was only possible to calculate borrowing and lending request time in terms of days. The following fields were added that enable you to create reports that calculate the borrowing and lending request time in hours and minutes:

    • In Borrowing Requests > Borrowing Request Details:
      • Hours of Request for Partner
      • Hours of Request to Material Arrival
      • Hours of Request Sent to Material Arrival
      • Hours of Request Sent to Non-Fulfilled
      • Hours of Arrival to Patron Loan
      • Hours of Patron Check-In to Return
      • Minutes of Request for Partner
      • Minutes of Request to Material Arrival
      • Minutes of Request Sent to Material Arrival
      • Minutes of Request Sent to Non-Fulfilled
      • Minutes of Arrival to Patron Loan
      • Minutes of Patron Check-In to Return
    • In Lending Requests > Lending Request Details:
      • Hours of Request
      • Hours of Request Created to Material Sent
      • Hours of Material Sent to Return
      • Minutes of Request
      • Minutes of Request Created to Material Sent
      • Minutes of Material Sent to Return

    Support Discontinued for Internet Explorer

    March 2021 Administration and Infrastructure

    Starting from the March 2021 release, Alma no longer supports the Internet Explorer browser, including no longer fixing potential display and performance issues on IE.

    Enhancements to Letters Configuration Table

    March 2021 Administration and Infrastructure URM-130472

    The Letters Configuration code table was enhanced to enable you to find the desired letter quicker:

    • You can now search for letters by name.
    • Pagination enables you to jump between pages.
    • Filters enable you to see a subset of relevant letters:
      • Enabled: To see letters you enabled during implementation and need to configure.
      • Channel: To filter letters by email, SMS or Webhook.
      • Patron Facing: To easily disable patron-facing letters if you do not want to send them out to patrons.
      • Customized: To see only letters that were customized or were not customized. 

    enhanced letter configuration table .png

    See Configuring Letters.

    Watch the Enhancements to Letters Configuration Table video (1:03 minutes).

    Importing Code Table UILeganto Labels

    March 2021 Administration and Infrastructure URM-137898

    Now you can import the UILeganto Labels code table. This enables you to update the Leganto labels elsewhere and then import all of them into Alma. Note that the number of rows in the imported table must be identical to the number of rows in the table in Alma. 

    It is advised that you export the existing Alma table (select ), make your changes and import it back to Alma. 

    Import UILeganto Labels.png

    Support for Campus Name Translation

    March 2021 Administration and Infrastructure URM-19144idea exchange Idea Exchange

    Now you can translate Campus names (Configuration > General > Libraries > Define Campuses) to the languages defined in your system. The translated campus names subsequently appear in Alma and in Primo VE, for example in the pickup locations list, in Get It Request Form, and more, if you choose to display Primo VE in the interface language to which campus names were translated. This is an important ability for multilingual Primo VE sites.
    campus language selection.png

    See Configuring the Institution and Its Libraries.

    Watch the Support for Campus Name Translation video (0:54 seconds).

    New Alma Layout - Exclusive Use

    March 2021 Administration and Infrastructure URM-143811

    Finalizing the rollout of the new Alma layout, the new layout is now exclusively available for Alma users. Users can no longer switch back and forth between the new and the old Alma layouts. For instructions on working with the new layout, see The Alma User Interface

    To switch back to the old Alma layout in case of specific needs, please contact Ex Libris customer support. 

    Physical Inventory Viewer Privileges Added to All Relevant Roles

    March 2021 Administration and InfrastructureURM-126672

    Now all staff users can view all inventory (physical, electronic and digital), across the entire institution, regardless of the user role's scope. Users who do not have the permissions to edit the inventory can only view it. 

    To limit the ability to view holdings and items in your institution only to certain roles, contact Ex Libris customer support. 

    See Managing User Roles.

    The Licenses API was enhanced to support retrieving additional types of Licenses

    March 2021 APIURM-128869

    It is now possible in Alma for the GET licenses API to retrieve a list of negotiations and amendments. Previously the GET licenses API returned a list of licenses of type='LICENSE' only and not negotiations or amendments. 

    The following newly added parameter 'types" are used to retrieve the license types:

    • type=ALL (will return both licenses & negotiations)
    • type=NEGOTIATION (only negotiation)
    • type=LICENSE (only licenses)
    • type=ADDENDUM (only amendments)

    Amendments can also be retrieved using GET /almaws/v1/acq/licenses/{license_code}/amendments ).

    Negotiation type licenses are only available in a Network Zone (NZ).

    The Electronic Portfolio API now supports the "Public access model" field

    March 2021 APIURM-124860

    Users now have the ability to use 'GET/PUT/POST' API for Electronic portfolios in order to create/update the Public access model field in portfolios. Previously, the API for electronic portfolios did not include information/update ability to the Public access model field which is found within the Acquisition tab of the Electronic Portfolio Editor. 

    Valid values for the Public access model field can be found in the "Code" column of the "Access Model" table located in Alma->Configuration->Acquisitions->Licenses -> Access Model.

    The access model code can be edited by the user. When using the create/update API, in case the access model code in the API does not match a code in Alma, this will not prevent the creation of the POL.

    Enhanced Library Calendar

    March 2021 FulfillmentURM-140592

    The availability calendar in booking requests was enhanced to also reflect the times when the library is closed. If a pickup location is selected before checking the availability calendar, the calendar will show when the library is closed, in addition to when no item is available for booking. This will help patrons to better understand when an item is available for booking. The closed times and the unavailable times will differ in color, and new customizable labels were added to specify in writing the time and nature of closed/unavailable windows in order to improve the availability calendar’s accessibility. 

    As part of the May release, the “Check Availability” label’s OTB value will change to inform patrons that in order to see the library's opening hours, they should first select a pickup location. As this is a patron-facing change, it will not be reflected in existing environment – libraries that wish to implement it will need to configure this label. For more information on customizing labels, see: Modifying Display Labels or Configuring Display Labels for Primo VE.

    Associate a PO Line Created via the Import Profile to an Existing Portfolio

    February 2021 AcquisitionsURM-138280

    When a PO line is created via the "New order" import profile, Alma can now locate and use existing inventory and associate the newly created PO line to it. Once matching inventory is found, a PO line is created and associated to that inventory item, instead of creating a new resource for each order.

    To support this, a new checkbox "Locate Existing Resource" was added to the "New Order" import profile > PO Line Information tab. This checkbox is only visible for electronic type of inventory (import types Electronic/Mix).

    PO Line Infrastructure Upgrade

    February 2021 AcquisitionsURM-136168
    In upcoming releases, technical upgrades to the PO Line infrastructure will take place, which will not result in any functional changes.

    View Invoice when Editing a PO Line

    February 2021 Acquisitions idea exchange Idea Exchange  NERS NERS Enhancement (ID #7049) URM-130717

    Now, when editing PO lines, and accessing the Invoice Lines tab, the invoice numbers on invoice lines are clickable and linkable to the invoice. The invoice opens in a view mode. Note that only users with roles that allow viewing/editing invoices can view the invoice via this link. Click "Back" from the invoice page to be directed back to the location from which you clicked the invoice line.

    This was done in the following locations:

    • On invoice lines in the Purchase Order Line Details page > Invoice Line tab 
      invoice number clickable on the PO line.png
    • On the Invoice Line Details page > Summary pane was made clickable and linkable to the invoice as well. 
      invoice line number with link.png
    Watch the View Invoice when Editing a PO Line video (0:40 seconds).

    See Orders Associated with Requests When Receiving Multiple Orders  

    February 2021 AcquisitionsURM-117968

    In the Receive page, when receiving one or more PO lines from the main receiving screen, the existing pop-up message (which indicated that one of the orders has a user request associated with the order) was enhanced to present the users with a clear indication of the PO line that is associated with a user request:

    confirm message receiving items with requests on them.png

    This enhanced message can be disabled from the Manage Acquisitions Alerts configuration page. Another message, which was also added to the "Receiving Alerts" section, is the confirmation message that appears when receiving items from the Receiving > Manage Items page (item that has a request associated to it). 

    receiving alerts section in manage acquisitions alerts.png

    See Managing Acquisitions Alerts

    Assign Holding Records to Another Cataloger by Scope

    February 2021 Resource Management URM-141045

    Now when assigning a holding record to another cataloger using the Assign Record to Another Cataloger dialog, you can only assign it to users who have the privilege to work with holdings in the scope of the record (Physical Inventory Manage privilege). 

    For details on the scope of holdings records, see the following presentation: Holdings record management on the library level.

    See Navigating the MD Editor Page.

    Reload Record from the SBN Central Catalog

    February 2021 Resource Management URM-141128

    The following enhancements were done in the SBN Integration profile:

    • Ability to select the desired merge routine when contributing records to SBN - A checkbox "Use this Merge Routine in Contribution" was added to the Contribution Configuration section of the SBN Integration Profile. This determines how the SBN record will be merged with the existing one when contributing a record to SBN:
      • When this checkbox is selected, then the merge routine for copy cataloging is used during contribution as well.
      • When this checkbox is clear, then the merge routine defined in the repository import profile that is configured on the Integration profile is used in contribution.
    • Preferred Record when Reloading from SBN in MD Editor- A checkbox "Preferred Record when Reloading from SBN in MD Editor" was added to the Bibliographic Alignment Configuration section of the SBN Integration Profile. This allows you to select which is primary record during reloading from SBN ('SBN' is the default option).

    use this merge routine in contribution - SBN.png

    See Integrating the SBN Italian Union Catalogue

    Merge and Combine Process

    February 2021 Resource Management URM-106363

    The Merge Records and Combine Inventory tool was added under Resource Management > Advanced ToolsThe Merge Records and Combine Inventory tool allows you to handle duplicate titles by merging them and combining their inventory.

    Merge and Combine inventory tool.png

    The duplicate records to be merged are taken from the report file (.csv) of your Duplicate Title Analysis job (see Using Duplicate Title Analysis). 

    See Using Merge Records and Combine Inventory and Using Duplicate Title Analysis.

    Additional Fields for Inventory Import

    February 2021 Resource Management idea exchange Idea Exchange URM-41382

    Additional fields were added to the Import Profile page > Inventory Operations tab for physical inventory. You can map item-level information from these fields in the input file, or indicate a value to be placed in the imported records. 

    new fields of import details for physical inventory.png

    See Creating/Editing an Import Profile: Inventory Information

    Watch the Additional Fields for Inventory Import video (1:32 minutes).

    Support for Cataloger Level in Authorities (New MDE)

    February 2021 Resource Management URM-138263

    Now the Cataloger Level is displayed in the new Metadata Editor for authorities. For this to display, you need to have cataloging levels configured for your institution (see Configuring Cataloging Levels for Contribution to Externally Managed Authorities).

    When Cataloger Level is displayed in the Metadata Editor, and your cataloging level is lower than the authority record you are trying to edit, a message is displayed providing you insight as to why you cannot edit the record. 

    authority catalog level.png

    This functionality is available only in the new Metadata Editor layout.

    See Assigning Cataloging Levels Upon Save and New Metadata Editor Functionality.

    Support for Czech Alphabet

    February 2021 Resource Management URM-136366
    Alma now supports special Czech language characters for staff searches in the following areas: repository search, user search, purchase and fulfillment requests, and deposits. It also applies to browse bibliographic headings, using F3, and sorting results. If you are interested in this capability, contact Ex Libris Support to configure this for your institution.

    To apply the above changes for Bibliographic/Authority/Inventory data, the following indexing jobs must be run for Czech institutions:

    • Full Indexing Job
    • Full Inventory Indexing Job

    A more detailed explanation of this process can be found here.

    See Czech Characters and Configuring Institution Languages

    Accurate Partial Linking Indication

    February 2021 Resource ManagementURM-142942

    In some cases, the MDE showed a partial linking icon  instead of the full linking icon . During the February release, Ex Libris will run a data correction job that will fix the data, to align the data with the actual link in all these cases.

    New Alma Hot Key

    February 2021 Resource Management URM-133922

    The following hot key was added to Alma, to allow you to work faster. 

    • Alt+M - Press to toggle the Metadata Editor open/closed.

    See Global Alma Hot Keys.

    Shared MD Import Profiles in the Community Zone are Now Published to the Developer Network

    February 2021 Resource Management URM-48516

    To help users share Metadata Import profiles in the Community Zone, Ex Libris now publishes the list of shared Metadata import profiles in the Developer Network: https://developers.exlibrisgroup.com/alma/integrations/sharedmdimpprof/.

    This is the same list that can be viewed from Import Profiles page > Community tab. Publishing this list in the Developer Network enables both Alma users and others who cannot log in to Alma to see the sharing that is done within the system. The list updates automatically whenever new MD Import profiles are shared in the Community Zone. 

    See Sharing Import Profiles in the Community Zone.

    New Metadata Editor - Accessibility Improvements

    February 2021 Resource ManagementURM-140976

    The improvements were done in the new MDEditor with the purpose of making it compliant with the Americans with Disabilities Act (ADA). The improvements include addition of labels and tooltips where they were missing, and in the the ability of screen readers to convey the state of elements to the reader. This was done in the following areas of the MDEditor:

    • Tabs:
      tab button labels.png
    • Filter and sort:
      filter and sort accessibility fixes.png
    • Buttons on the Navigation panel header:
      nov pane header accessibility fixes.png
    • Item list (records/templates/rules)
    • Record validation

    Fulfillment Administrator Role Support for Library-Level Scoping

    February 2021 Fulfillment URM-101627

    The Fulfillment Administrator role can now be scoped to a specific library within an institution. This affects the Alma links that are accessible to the user with this role. To support this feature, you can now select a library from the Scope drop-down list when configuring the Fulfillment Administrator role for a user:

    user_role_details.png

    Scope Drop-Down List

    For a user whose role is scoped to a specific library:

    • In the Fulfillment menu:
      • The following links are not visible:
        • Distribute Fulfillment Network Configuration (only for network institutions)
        • Distribute Resource Sharing Network Configuration (only for network institutions)
        • Resend Printouts/Emails
        • Loans Overdue Notification Status Update
        • View Overdue and Lost Loan Jobs
      • The following links remain visible:
        • Create Fines and Fees Report ( The Received by Library drop-down list and the Fine Owner drop-down list are not limited to libraries in the role's scope)
        • Create Fulfillment Sets
        • Citation Alternate Suggestions
      • Pages that currently enable library level management remain visible.
    • In the Fulfillment configuration menu:
      • The Configuring drop-down list displays the library for which the configuration links are displayed.
      • If the user has another role besides the Fulfillment Administrator role that allows access to all of the Fulfillment links (for example, the General Admin role), all the menu options appear.

    For more information on User Roles, see Managing User Roles.

    Limit Loan Renewal Time Frame

    February 2021 Fulfillment URM-109366

    You can now limit the time period during which a user can renew a loan to a specific number of days before the loan is due. You do this with the new Time frame when loan renewal is allowed policy type.

    limit_renewal_time_frame.png

    Limit Loan Renewal Time Frame

    When selecting a Value Type of Other, the Days before due date field appears. Enter the number of days before the loan is due that you want users to be able to renew the loan.

    The limit applies as well to any automatic renewal configurations.

    For more information on Fulfillment policies, see Adding Fulfillment Policies.

    Limit Courtesy Notifications for Daily Renewal Attempt to Once Per Loan

    February 2021 Fulfillment URM-109366

    A new Handle loans option, Daily within range without repeating notification, was added to the Send Courtesy Notices and Handle Loan Renewals Fulfillment job:

    daily_within_range.png

    Daily Within Range Without Repeating Notification
    It allows the job to run multiple times if the loan cannot be automatically renewed, but only sends one courtesy notification to the patron.
    If the due date is changed after the courtesy notice is sent, this function is reset and an additional notification may be sent for the loan.

    For more information on configuring fulfillment jobs, see Configuring Fulfillment Jobs.

    Identifier Based Locate

    February 2021 Fulfillment-Resource Sharing URM-138275

    You can configure Alma’s locate by fields from both the borrower side (Configuration > Fulfillment > Resource Sharing > Locate Profiles) and the Lender side (Configuration > Fulfillment > Library Management > Library Details) to find a matching record by matching one of the selected identifier fields. The new Locate only if all fields match option was added to allow this.

    locate_only_if_all_fields_match_borrowing_side.png

    Locate Only if All Fields Match

    If set to Yes, the existing behavior of successful locate only when all selected fields match is maintained. If set to No, then:

    • If the request has identifiers (such as ISBN, OCLC number or LCCN), locate is successful if any of the selected identifier fields finds a match. Other fields such as Title and Author are not used for the match.
    • If no identifier fields exist on the request, locate is only successful if all of the other selected fields match.
    Customers already using the locate by fields functionality have the Yes option selected by default to maintain their current behavior.

    For more information concerning Resource Sharing Locate by Fields, for the borrowing library side, see Adding Locate Profiles and for the lending library side, see Configuring Parameters of a Resource Sharing Library.

    New Checkbox to Display Chapter Fields in Primo VE Request Form

    February 2021 Fulfillment-Resource Sharing URM-139694

    A new checkbox appears at the top of the Primo VE book request form that allows you to indicate that you only need a specific chapter or pages. Selecting this checkbox displays fields for requesting book chapters (Chapter and Pages). In this way you can display these fields only when they are relevant.

    primo_specific_chapter_or_pages.png

    Chapter Fields Checkbox

    To configure the checkbox to appear, select a checkbox next to the new Specific Chapter or Pages option from the Resource Sharing Form Customization page (Configuration > Discovery > GetIt Configuration > Resource Sharing Request). If the Specific Chapter or Pages option is not selected, there is no change in the behavior of the request form, and the chapter fields always appear if activated for the book request form.

    specific_chapter_or_pages.png

    Specific Chapter or Pages

    For more information, see Primo Book Chapter Request.

    Allow automation of branch requesting for RS serial requests

    February 2021 Fulfillment-Resource SharingURM-129616

    The process for automatically creating an internal ship physically/digitally request for a serial/multi volume resource was enhanced. Before, when the lending request was for a serial/multi volume resource, Alma supported either mediating the request or have a title level request created automatically. A new option was added which will automatically create requests with a manual description containing the relevant metadata from the lending request (if exists), providing the librarian picking the item from the shelf with information to help select the required volume/issue.

    This can be done by setting the values of the rs_auto_request_lending_with_serials and rs_auto_request_lending_with_volume_issue parameters to 'general'.

    SIP2 Certificate Updated to SHA-256

    February 2021 Administration and InfrastructureURM-137087

    In order to provide improved security and integrate with the latest versions of Stunnel, the certificate used to integrate between Alma and Stunnel was updated to the SHA-256 standard.   If you would like to upgrade to the latest Stunnel version, you can now download a new certificate from Alma which is compatible with this version.

    Stunnel is software used as a proxy between self-check machines and Alma (for details, see  Stunnel). It is configured to listen on a defined port (e.g. 5003) over TCP/IP and routes the request to Alma port 6443 over SSL using a pem file used as key&cert download from the Self-check integration profile. 

    See Self-check - Stunnel.

    Accessibility Improvements

    February 2021 Administration and InfrastructureURM-140976

    The following improvements were done with the purpose of making it compliant with the Americans with Disabilities Act (ADA):

    • In the Summary section (that appears above the page when viewing on small-sized window):
      • "More Info" button is now available by keyboard
      • More Info popup (after clicking) is now available by keyboard
      • The "Close" button of the More Info popup is now available by keyboard
      • The user card that opens from the More Info popup is now available by keyboard
      • "Collapse" button now indicates the real meaning and the expanded/collapsed state of the section.
        accessibility - summary section.png
    • In the Summary panel (that appears to the right of the page when viewing on normal-size window):
      • "More info" button is now available by keyboard, and describes the real meaning and the current state of section (expanded/collapsed).
      • "Collapse" button now indicates the real meaning and the expanded/collapsed of the section.
        accessibility - summary panel.png
    • Correct contrast was added to dropdown hover:
      contrast on dropdown hover.png

    Enhanced Code Table API

    February 2021 APIidea exchange Idea Exchange
    The Code Table API now privies support for updating code-tables, in addition to the existing ability to retrieve this configuration entity. In addition, the GET-Code-Table API now supports the parameter "scope" that can receive as a value a particular library within the institution. Thus supports the ability to retrieve tables that are specific to a library. See  Developer Network.URM-82356

    PO Line Infrastructure Upgrade

    January 2021 AcquisitionsURM-135408
    In the upcoming releases, there will be technical upgrades to the PO line infrastructure but will not result in any functional changes

    PO Line confirmation messages to include the owning library

    January 2021 Acquisitions URM-122327

    In Alma, the existing pop-up message for the "Create PO Line" workflow was enhanced to notify users to which library the existing PO line is associated and with which library the existing item is associated with (when creating a physical PO line).

    RN02.png

    Additionally, these 2 alerts was added to the 'Manage Acquisitions alert' configuration screen (Configuration Menu -> Acquisitions > Manage acquisitions alerts) so that institutions can set it not to appear:

    clipboard_e93936367415217cf0b33145623cf02ae.png

    Control Availability Status of Electronic Resources created via Real Time Ordering

    January 2021 Acquisitions URM-137953

    A new customer parameter (acq_activate_portfolio_from_API) was added to enable institutions to decide if electronic resource orders created via Real Time Ordering will create the Community Zone (CZ) linked portfolio as 'available' or as 'not-available'. 

    RN01.png

    In case the parameter is set to 'true', institutions are no longer required to go via the E-Activation task list in order to make the resource available as it is created as such when the order enters into Alma.

    The Out of the Box (OTB) value for this parameter is set to "False" and will create the e-resource via the Real Time order process as "Not Available" to modify the parameter go to Configuration menu -> Acquisitions -> Other settings -> acq_activate_portfolio_from_API (set this to 'true' for portfolios to be created as 'Available').

    Additional collections for activating OASIS 'Real Time' Ordered Portfolios from the Community Zone

    January 2021 Acquisitions URM-139825

    Five new collections were added to the 'Real time Order' workflow of activation of Community Zone resources for orders originating from OASIS.

    The collections are:

    Provider Name Collection Name Collection ID
    Brill Online Brill Online Books 613170000000000148
    De Gruyter  De Gruyter eBooks Complete 611000000000002268
    IGI Global Online  IGI Global InfoSci-Books 611000000000002255
    JSTOR JSTOR Books 613170000000000272
    Oxford Scholarly Editions Online Oxford Scholarly Editions Online 613840000000000106
    Project MUSE Project MUSE - EBA All Single Title Collection 615410000000000517

    See OASIS vendors list for full list of Community Zone collections which supports this functionality.

    Email Notification from CDI Publishing Profile

    January 2021 Resource ManagementURM-132951

    The Alma Publish Electronic Records to Central Discovery Index job now has an Email Notification button for users to opt in to automated emails updated when publishing runs.

    New Holdings Management Privilege

    January 2021 Resource Management
    The privilege PHYSICAL_INVENTORY_MANAGE was added to ensure that unauthorized users cannot change existing holdings. Users with CATALOGING privileges only are no longer able to create and edit holdings. Only users with the privilege PHYSICAL_INVENTORY_MANAGE can create and edit holdings by scope.   URM-137391

    To make sure that holdings management is only done by authorized users, the following changes were made to Alma roles:

    • New privilege PHYSICAL_INVENTORY_MANAGE is now part of the following roles:
      • PHYSICAL_INVENTORY_OPERATOR
      • PHYSICAL_INVENTORY_OPERATOR_LIMITED
      • PURCHASE_MANAGER
      • PURCHASE_OPERATOR
      • REPOSITORY_MANAGER
    • Users with PHYSICAL_INVENTORY_DELETE role can delete a holdings record. 
    • Users with CATALOGING privileges only will no longer be able to manage holdings. They will need to be given a role that has the PHYSICAL_INVENTORY_MANAGE/DELETE privilege.

    Users without CATALOGING privileges cannot open and work in the Metadata Editor in its classic layout. They can only work in the new MDE layout.

    See Metadata Editor and Navigating the MD Editor Page, Working with Holdings Records, Searching in Alma, Viewing Read-Only Records in the Simple Record View Page.

    New Metadata Editor

    Enhancements to the New Metadata Editor Layout

    January 2021 Resource ManagementURM-138297

    The following changes were made:

    • The three functional areas of the MDEditor - Records, Templates and Rules - are now located on the Navigation pane as tabs, and not as a dropdown, for better visibility and quicker access. 
    • Under each functional area, the tabs of the new MDEditor are now located in the Navigation pane. This frees valuable real estate on the MDEditor that can be used for cataloging work. The new compact design allows quick access for users who work with few record types, while still providing full access for users who work with many record types. 
      Each tab represents a different type of records (Sets, DC, MARC21, UMIMARC and the other formats, Holdings, Authorities formats). To open records of a certain record family, click the tab. The tab changes its color to blue (see Holdings in the screenshot below) to indicate that its records are currently displayed in the Navigation pane. To view other record types, select the  arrow, and select the desired type of records from the list.   

    New layout of the MDE header.png

    See Draft RecordsMetadata EditorRecords.

    Template Management in Metadata Editor

    January 2021 Resource ManagementURM-98935

    Ex Libris continues the rollout of the new Metadata Editor. In the current release, the Template Management core functionality was introduced (the functionality available in the original Metadata Editor plus new features). Rule management will be rolled out in the upcoming releases (see Rollout Plan), giving users enough time to adjust to the changes.

    Alma users can switch back and forth between the Records and Templates areas in new and the original Metadata Editors.

    To switch:
    • to the new Metadata Editor, select new MDE button.jpg on the left-hand side of the top toolbar of the Editor.
    • back to the original Metadata Editor, select  Old Editor on the left-hand side of the top toolbar of the Editor.

    Ex Libris recommends that all relevant users start familiarizing themselves with the new Metadata Editor prior to its Go-Live, which is planned to take place with the deployment of January 2021 release.

    See New Metadata Editor Functionality.

    Watch the Manage Record Templates video (2:26 minutes).

    Side-by-side Editing of Primary and Searched/Browsed Records

    January 2021 Resource ManagementURM-135440

    Now you can view the searched/browsed record alongside you primary bibliographic record. This allows you to compare your bibliographic record with the searched record, while also providing easy navigation back to the search form to refine your search, if needed.

    When you have a bibliographic record open in the MDEditor, and you trigger Search External Resources, the search form opens in the right pane. Search Results cover the search panel with the option Back to Results that allows you to go back to refine your search. When selecting View on one of the results, the viewed record now covers the left pane, with an option to go back to results. The bibliographic record that you had open in the right pane appears again, allowing you to compare both.

    search results alongside edited record.png

    See Working with Search Resources in the MD Editor.

    Improved Inventory Import

    January 2021 Resource ManagementURM-134878

    As part of the import profile, you can define how to map the imported records to existing records in Alma (if there are such). This is done on the Inventory Information tab of the Import Profile page (Resources > Import > Manage Import Profiles or Acquisitions > Import > Manage Import Profiles).

    The following changes were made to the Inventory Information tab: 

    • For physical inventory, you can now map the inventory information in the input file either from a single field or from different fields.
    • The tab was redesigned to display information clearer.

    See Managing Import Profiles.

    Search Index Operators for Local Call Numbers

    January 2021 Resource ManagementURM-132398

    Search operators were added to the local call numbers index. 

    range operators for local call numbers.png

    Community Zone Updates - Remove Bibliographic Records With No Inventory

    January 2021 Resource ManagementURM-140080

    Up till now, when a Community Zone portfolio was updated to relink to a different bibliographic record, the Community Zone Update process updated the Institution Zone portfolio to point to the new bibliographic record, but the old bibliographic record remained in the Institution Zone even if it no longer had inventory.Starting from this release, if the bibliographic record does not have any inventory, the Community Zone Update process removes it.

    Community Zone Task now includes a dedicated report type for this type of Community Zone updates, "Portfolio bibliographic record updated". This report type shows the MMS ID of the deleted bibliographic record and MMS ID of the new bibliographic record to which the portfolio was relinked.

    New Alma Hot Key

    January 2021 Resource ManagementURM-140981

    The following hot key was added to Alma:

    • Ctrl+Alt+C - Press to toggle the Configuration menu open/closed. When pressing to close the Configuration menu, you are taken to the Alma homepage.

    See Global Alma Hot Keys.

    Collection of Type ‘Search Rights in CDI: Subscription’ Require Activation 

    January 2021 Resource Management

    Collections that are defined as ‘Search Rights in CDI: Subscription’ can only be activated for search in CDI if your institution subscribes to the collection

    As of this release CDI Fully Flexible customers can indicate that they have subscription for these type of collections by activating the collections in Alma or by setting them up as 'Full text in CDI Only; it will no longer be possible to  'Activate for Search in CDI' 
    example:

    clipboard_e757140cf1255941d497745949d5ca2ad.png

    January 2021 Digital Resource Management URM-138801

    Several enhancements were implemented for configuring Digital Copyright statements:

    • Digital copyright statements were separated from the general copyright declarations and now has its own page: Copyright Statements - Digital.
    • The out-of-the-box set of boilerplate copyright statements now includes all Creative Commons licenses, Rightsstatements, and US Code. These statements are view-only and are available in the Boilerplate section of the page.
    • A new Custom section is available on the Copyright Statements - Digital page where you can add an unlimited number of custom made copyright statements.

    copyright_statements_digital.png

    Copyright Statements - Digital

    For more information, see Configuring Copyright Statements – Digital.

    New circulation desk configuration to control the appearance of the 'Override return Date and Time' field in the 'Return Items' page

    January 2021 Fulfillment

    Institutions now have the ability to configure that the circulation desk does not display the Override return date and time field in the 'Return Items' page.Previously, this field was displayed at all times and scenarios for user roles where this was enabled, because the field was not associated to any circulation desk configuration. Institutions now have control and can limit the appearance of the field.

    To set this configuration, go to the relevant location in the 'Configuring' dropdown menu on the top of the configuration menu then go to Fulfillment->Circulation Desks-> Add/Edit the relevant desk and see the 'Supports overriding return date' field (enabled by default):

    clipboard_ed63b091f4248037c6fed3d7a3a45990d.png

    Automated Resource Sharing Request Digitization Process

    January 2021 Fulfillment-Resource SharingURM-135772

    Alma now allows the resource sharing request digitization process to be automatic even when there are multiple branch library level digitization departments. Previously, the process of creating a request could work if there was only one digitization department at the institution. If there were branch library digitization departments then the digitization requests needed to be created manually by the resource sharing staff and manually assigned to the relevant branch library.

    To enable this functionality go to the Configuration menu->Fulfillment->General->Other settings, customize the 'rs_default_digitization_department' parameter and set its value to 'prefer_local':

    clipboard_e3eb387774ed3ce8a77967248b66dcce0.png

    The new configuration is currently not supported for AFN requests. If your consortium is working with AFN, a specific digitization department needs to be used.

    Alma to Alma - Send digitized content directly to patron

    January 2021 Fulfillment-Resource SharingURM-139507

    In Alma ISO resource sharing, digitized content provided as a link by the lender can now be sent to patrons without the email address of the patron being shared with the lender. The shipped digitally message from the lender triggers the borrower side to send an email to the patron with a link that requires authentication on the borrower side, which then directs the patron to the document the lender uploaded. Before, this process required sharing the patron email with the lender by setting the partner to support ADD address, which raised a privacy concern for libraries. The email with the link to the digitized content is now sent regardless of the ADD address configuration. The customer parameter borrower_document_delivery_send_automatically (on the borrower side) determines whether the document delivery email is sent automatically to the patron when resource is shipped by the lender, or will be sent manually by the librarian on the borrower side using new 'View File' and 'Send File to Patron' row actions in the borrowing request task list.

    Send digitized content to patron - Upload file

    January 2021 Fulfillment-Resource Sharingidea exchange Idea ExchangeURM-109783

    Library staff is now able to upload a file to a borrowing resource sharing request in Alma and have Alma send the document delivery email with a controlled link to the file. When a non-Alma library sends a digital file to an Alma library the file has to be sent as an attachment to an email. Before, forwarding this email to the patron had to be done using tools outside of Alma. Librarians can now use Alma to send patrons uniformed emails and not different emails depending on how the file was obtained,  using new 'Upload File' and 'Send File to Patron' row actions in the borrowing request task list 

    Retry Rapid request

    January 2021 Fulfillment-Resource SharingURM-131551

    In Alma, when a borrowing request is sent to Rapid using the API, the operator is now notified by Alma that Rapid found a local match for the request. The operator is then given an option to override this and send the request to Rapid anyway. If the request is sent to Rapid and rejected because of a local match then the request is assigned the new 'Local Holding' status. This allows to easily identify automatic send attempts to Rapid that were rejected because of local holdings. The new "Override local holding" action allows to override the Rapid rejection.

    Allow automation of branch requesting for RS serial requests

    January 2021 Fulfillment-Resource SharingURM-129616

    This feature has been deactivated and will appear in the February release.

    The process for automatically creating an internal ship physically/digitally request for a serial/multi volume resource was enhanced. Before, when the lending request was for a serial/multi volume resource, Alma supported either mediating the request or have a title level request created automatically. A new option was added which will automatically create requests with a manual description containing the relevant metadata from the lending request (if exists), providing the librarian picking the item from the shelf with information to help select the required volume/issue.

    This can be done by setting the values of the rs_auto_request_lending_with_serials and rs_auto_request_lending_with_volume_issue parameters to 'general'.

    New Alma Layout - Hurry to Opt In for a Better Working Experience

    January 2021 Resource ManagementURM-140830

    The rollout of the new Alma layout continues, and the new layout is already the default for thousands of Alma users. 

    Ex Libris recommends that all users opt-in to gain experience with the new layout. Starting from March 2021, it will no longer be possible to use the old layout. 

    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 and opt-in instructions, see Layout Improvements.

    Consortia CDI Inheritance

    January 2021 Collaborative NetworksURM-130742

    The CDI inheritance indication has been added to the Network tab making it visible and easy to understand whether the institution inherits the collection CDI setup from the Network Zone (NZ) or not. CDI inherited collections will be presented in the combined search results and the Network Zone tab with the specific CDI related setup present in a new dedicated CDI drawer.

    RN03.png

    clipboard_eabc5b575135b69d8efc5986adbf51813.png

    The example above shows that the collection 'Scholars Portal Books: Springer-Religion and Philosophy 2017' was activated in Alma for 'Alma Academy' but the Network decided not to mark its content as Full Text Available in CDI.

    The CDI drawer will indicate the following information (when relevant):

    • Available for: Contains the Alma full text activation.
    • Do not show as full text in CDI even if active in Alma: Lists all member institutions / campuses for which ' Do not show as full text in CDI even if active in Alma' is selected.
    • CDI only full text activation: Lists all member institutions / campuses with FT in CDI only activation. 
    • CDI search activation: Lists all member institutions / campuses with CDI search activation.

    The CDI drawer will also be displayed for institutions with distributed management of electronic resources. In this case, it will present the CDI setup for the relevant "Available For Groups".

    Re-assign MMS Records in Network Shared Catalog

    January 2021 Collaborative Networks URM-139514

    The Assign Record to Another Cataloger action in the Metadata Editor now provides the ability to assign Bibliographic and Authority Network Zone records to a cataloger from another institution within the network. 

    This functionality is available only in the new Metadata Editor. 

    The new functionality is available only when the new customer parameter enable_nz_record_assignment in NZ environment is set to True (Configuration Menu > Resources > General > Other Settings). This parameter is available only for the Network Zone, since the network sets this policy for all its member. Stand-alone institutions and NZ members do not have access to this parameter.

    See Assigning a Network Zone Cataloging Record to a Cataloger of Another InstitutionContributing to the Community Zone – Bibliographic Records and Configuring Other Settings (Resource Management).

    New Alma Analytics Dashboard for Analytics Objects

    January 2021 Analytics URM-134426

    A new Alma Analytics dashboard is now available for the Analytics Objects subject area. It contains the following reports that display information concerning the Analytics Objects of your institution:

    • Customized objects with at least one user
    • Customized objects with no users
    • Number of objects created per user
    • Objects breakdown by type
    • Objects created in the last year (last 365 days)
    • Top 5 most popular scheduled reports and widgets

    For more information, see Out-of-the-Box Reports.

    Configuration Change Tracking in Code and Mapping Tables

    January 2021 Administration and InfrastructureURM-132217

    Now you can see the history of changes made by your staff to code and mapping tables (but not the full details of the change). This helps you know what configuration changes were made, and by whom, for audit purposes.

    The decision of whether to store these events and the period during which they are kept is controlled by the institution. The customer parameter code_and_mapping_table_log_retention_period (Configuration Menu > General > General Configuration > Other Settings) controls the duration of days for which this data is stored. The default is 0 (data is not stored), and you can change it to any number of days. 

    When the parameter value is higher than 0, Alma now supports storing events when changes are made to the Code or mapping tables. Events include the user that made the change, the table where the change was made, and the action (new row, row update, row deletion). You can then run a report of these events via Alma Analytics. 

    See Configuring Other Settings.

    Support for Authentication Forcing in OpenID Authentication

    January 2021 Administration and InfrastructureURM-131362

    Now the OIDC (OpenID Connect) authentication of Alma supports authentication forcing when Alma authenticates users via OIDC. If you want to force authentication when Alma authenticates users via OIDC, select the "Force Authentication" checkbox in the Actions tab of the OpeinID Connect integration profile.

    force authenticaiton on OIDC integration profile.png

    See OpenID Connect.

    Additional Recent Entities Added

    January 2021 Administration and InfrastructureURM-123260,123259,123259

    Actions performed on the following pages are now listed on the Recent Entities pane:

    • Mapping tables
    • Code tables
    • Integration Profiles

    New entities on the Recent Entities pane.png

    This provides quick access to the entities you updated recently, without having to go through the entire list of tables or integration profiles. For more information, see Recent Entities List.

    January 2021 APIURM-72715

    In Alma, it is now possible to manage itemized sets of vendors via the API.

    For further details, click here

    The Items API was enhanced to include a new option for Sorting by Expected Receive Date

    January 2021 APIURM-132320

    The Get-Items API now supports sorting by the expected received date. When working with continuous orders and prediction patterns, this enables fetching the items that should be received next and helps to identify items that should be claimed.

    Attach Citations Manually to a Specific Bibliographic Record

    August 2021 Fulfillment - Course Reserves URM-149886

    You can now manually attach a citation to a specific bibliographic record. Use the Manual Locate action to manually select or change which record the citation is attached to.

    manual_locate.png

    Manual Locate

    The Manual Locate action is always available, regardless of if a citation is located.

    Search for the bibliographic record you want to attach the citation to, then select the relevant bibliographic record from the search results.

    If the citation selected is already associated with an MMS ID, the following confirmation message appears:

    ConfirmationMessage.png

    Manual Locate — Confirmation Message

    If you select Confirm, the citation is detached from its current MMS ID and attached to the new MMS ID.

    Alert for Duplicate Purchase Orders

    August 2021 Fulfillment - Course Reserves URM-149887

    You now see an alert before submitting a duplicate purchase request from a citation. When selecting Citation > Purchase Request, if an unapproved purchase request already exists with the same MMS ID, the following message appears:

    DuplicateConfirmation.png

    Duplicate Purchase Request — Confirmation Message

    Upon selecting Confirm, the purchase request form opens.

    Upon selecting Cancel, you are returned to the previous screen.

    Run Course Loader in Report Mode

    July 2021 Fulfillment - Course Reserves URM-107170
    You can now run the Course Loader (Configuration > General > External Systems > Integration Profiles) in Report Mode by selecting Run in Report Mode from the Actions tab. The report mode creates a report as if the Course Loader had run, detailing the records that would have been processed and a list of anticipated issues, warnings, or errors. This report enables the library to clean up the file as needed before running the job, to ensure the Course Loader runs successfully.
    Report_Mode.png
    Leganto Course Loader Actions

    Update Citation Type in Bulk

    July 2021 Fulfillment - Course Reserves URM-139271

    Alma now includes the option to update the citation type using the Reading List Citation Update task (Admin > Run a Job). Note the following exceptions
    • book chapter, article, and electronic article cannot be updated in bulk as they require an additional title 
    • citations associated with a copyright request or license type-CLA cannot be updated in bulk

    Updating the type using the Reading List Citation Update task will not trigger a resource locate or change in the citation status.

    For more information, see Running Manual Jobs on Defined Sets.

    Citation_Type.png
    Citation type
    June 2021 Fulfillment - Course Reserves URM-146581 URM-146582 URM-147839
    For Norwegian customers, Leganto now supports the ability to request Extended Right Clearance from Bolk. When an Extended Right Clearance is required, the Copyright Status updates to Declined and the Bolk Status updates to Rejected.
    ExtendRightClearance.png
    Extend Right Clearance status
    Use the Extend Right Clearance action to submit your request to Bolk. The Copyright Status updates to Waiting for Approval and the Bolk Status updates to Ordered.
    BolkStatus2.png
    Bolk status
    Use the Update Bolk Status action from the citation menu to track your Bolk status. Currently, tracking your status is a manual process, but this will be replaced in the next release with an automatic daily job to update the status.
    UpdateBolkStatus.png
    Update Bolk Status

    When the Bolk status changes to Approved, the user sees a price per page and required fee in order to make the material available to students. The Copyright Status at this stage maintains the status of Waiting for Approval.

    Two new actions display in the citation menu:

    • Accept Bolk Right Clearance — you agree to the terms of use. The material will be available for students. The Copyright Status updates to Approved.
    • Reject Bolk Right Clearance — you do not agree to terms of use. The Copyright Status updates to Declined and the material will not be available for students. You can then update the Bolk request.

    AcceptRejectRightsClearance.png

    Bolk Right Clearance
    In order to better follow Bolk Right Clearance requests, two new alerts were added to the citation:
    • Bolk Right Clearance Approved
    • Bolk Right Clearance Rejected

    These alerts were also added to the user task list:

    UserTask.png
    User tasks
    You now have the option to update excerpt requests, respond to limitations on additional requests, and lock curriculums. See Integrating with Bolk for more information.
    After a request is submitted, you now have the option to update a Bolk request as long as the course is not locked.
    UpdateBolkStatus.png
    Update Bolk Request
    When selecting Update Bolk Request, a dialog box displays to enter the required page range.
    AdditionalBolkRequest.png
    Bolk request
    Selecting this action opens a window to enter your required page range. The default page ranges are pre-populated according to the page ranges required by the instructor.

    When a second request is submitted containing the same ISBN as a previous request, the initial request is resubmitted to Bolk as well. Upon submitting a second request, a dialog box displays informing you that an approved request already exists:

    Confirmation.png

    Confirmation Message

    Upon selecting Confirm, you are prompted to enter the pages you are requesting and reconfirm that all requests related to this ISBN are resubmitted.

    Upon selecting Lock Bolk request from a course, Leganto checks whether there are any outstanding requests still awaiting processing. If there are any outstanding requests, the following message is displayed:

    LockedCourse.png

    Locked message
    March 2021 Fulfillment - Course Reserves SF: 00895060 00895525 URM-141486
    You can now add or remove courses from reading lists with citations that have an approved copyright. The recalculation will be done overnight.
    The process of adding or removing courses from reading lists can be done individually or in bulk from the Reading Lists Task List. (See Adding and Removing Courses from a Reading List). When doing so, if a copyright on the list is already approved, it will be recalculated.
    • You cannot remove an association in bulk if a copyright on the list is approved.
    • To remove a course from the list, there must be another course already attached to the list.
    An overnight job will run to recalculate the copyright on any lists in which the course association was changed during that day. The job report can be seen via the scheduled job.
    If a copyright's start date is in the past when the recalculation is done, the Date Available To of the existing copyright will be changed to the date of the course association, and a new copyright request created. If the end date on the request has already been reached, no additional action is taken. If the start date has not yet arrived, the date of the course is added to the copyright. If there are two or more courses, the earliest start date and the latest end date of all the courses will be used.
    If the recalculation causes the copyright status to change to Not Approved, the citation status will change to Ready for Processing. If the copyright is approved, the citation status is taken from the citation_copyright_approved parameter.
    If the copyright status was previously approved and it changes to Not Approved, an Approved copyright changed alert is added to the citation.
    Copyright alert.png
    Copyright Alert

    This does not apply to lists with a License Type of Bolk, CLA, or CCC.

    Option to Attach Files to Citations Automatically as Part of the Digitization Workflow

    March 2021 Fulfillment - Course Reserves URM-130011
    Alma will now attempt to automatically add the file to the citation at the completion of the digitization workflow, in addition to the existing notification email that is sent to the library staff that manages the list.
    The handling of the file(s) is as follows:

    If the citation has no file and only one file was digitized:

    • The digitized file is added to the citation associated with the request.
    • The existing email is sent with a notification that the digitized file was added to the citation.

    If citation has no file and multiple files were digitized:

    • The digitized files are not attached to the citation.
    • The existing email is sent with a notification that the digitized files were not added to the citation because the digitization request contains multiple files.

    If citation has already a file:

    • The digitized file is not attached to the citation.
    • The existing email is sent with a notification that the digitized file was not added to the citation because the citation has an existing file.

    If file could not be uploaded (in instances such as a communications error):

    • An email is sent with a notification that the file was not added to the citation due to a general error.

    The citations can be tracked using the following facets:

    • Citation Digitization Request Completed
    • Citation has a new file
    Notification Item Letter.png
    Notification Item Letter
    The Ful Digitization Notification Item Letter contains the following new fields:

    File_not_uploaded_file_exists

    The digitized file was not uploaded because another file is already attached to the citation.

    File_uploaded

    The digitized file was uploaded to the citation.

    File_not_uploaded_multiple_files

    Because the digitization request contains multiple files, they could not be automatically uploaded to the citation.

    File_not_uploaded_general_error

    Due to a general error, the file could not be uploaded to the citation.

    For more information about the letter, see Configuring Alma Letters.

    Recalculate Copyrights of Multiple Citations (Job)

    February 2021 Fulfillment - Course Reserves SF: 00889528 URM-139484
    You can now recalculate the copyright rules in bulk for a set of citations. To do so, select the Bulk Citation Copyright Recalculate job from Fulfillment > Advanced Tools. The job will not recalculate the following types of citations:
    • Citations that are not associated with a copyright request.
    • Citations that have a copyright request in the past (the copyright has ended).
    • Citations that have a License Type of Bolk, CLA or CCC.
    URM-139484.png
    Bulk Citation Copyright Recalculate Job

    Automatically Calculate Total Chapter Count

    January 2021 Fulfillment - Course Reserves URM-139606
    In the Copyright Attributes tab of a Reading List Citation, the Total Chapters Count is now automatically calculated from the Required Chapters field. The calculation is performed only if Required Chapters contains numbers, Roman numerals, '-' or ','. You can override the automatically calculated value by typing over the number.

    DCS Create Courses

    January 2021 Fulfillment - Course Reserves SF: 00842179 URM-112062
    The UK CLA Digital Content Store (DCS) now includes support for adding courses. If a copyright request is created in Alma/Leganto and the course does not exist in DCS, then the course is automatically created in DCS using the Submit Course API.

    Additional Enhancements

    • August 2021 Resource Management SF: 00877677 URM-139422
      All instances in the Alma UI that refer to "Full text active in CDI only" have been changed to "CDI-only full text activation".
    • August 2021 Analytics URM-151780
      The date filter fields in Alma Analytics (such as the Fulfillment Due Date Filter) can now be filtered according to the Older than 7 Days filter. Select this option from the New Filter pop-up to apply this filter:

      older_than_7_days.png

      Older than 7 Days
    • August 2021 Analytics URM-88987
      The Uniform Resource Identifier Exists field was added to the Bibliographic Details folder for all subject areas for which it exists. It indicates if 856 subfield u contains data.
    • August 2021 Analytics URM-148218
      The Chapter Number field was added to Borrowing Requests > Borrowing Request Details.
    • August 2021 Analytics URM-139696
      When calculating the cost-per use (E-Inventory > Cost Usage), matching is now done using the ISBN Valid and ISSN Valid fields.
    • August 2021 Analytics URM-152968
      The following reports were added to the Consortia folder:
      • Number of fully processed COUNTER files per institution in current calendar year
      • Number of fully processed COUNTER files per institution in previous calendar year
    • August 2021 Analytics URM-153110
      Alma now supports the display and export to CSV format of 10 million rows.
    • August 2021 Analytics URM-152823 URM-154624
      Several security enhancements were implemented when viewing reports in Alma Analytics:
      • Previously, it was possible to alter the URL of an accessible report to view a report that should be blocked. This is no longer possible.
      • Linked reports that open in a new window are a security risk and are no longer supported. If you have any such reports, you must change them to be either Embedded in Section or Link – Within the Dashboard:
        1. From the Compound View of the relevant report, select the Properties icon:

          properties_icon.png

          Properties Icon
        2. From the Display Results drop-down menu, select either Embedded in Section or Link – Within the Dashboard:

          display_results.png

          Display Results
    • August 2021 Fulfillment - Course Reserves SF: 00808972 URM-130012idea exchange Idea Exchange
      When copying a citation with a public note, the note is copied in the following scenarios:
      • Duplicating a list
      • Copying a citation
    • July 2021 Digital Resource Management URM-147560
      The display of the Alma Viewer in landscape mode for mobile devices was improved.
    • July 2021 Analytics URM-88987
      The following fields were added to the E-Inventory subject area:
      • No. of Portfolio (In Repository Contributed to CZ) – the number of portfolios in the repository contributed to the Community Zone
      • Portfolio Contributed to CZ – indicates if portfolios were contributed to the Community Zone
      • No. of Electronic Collections (In Repository Contributed to CZ) – the number of electronic collections in the repository contributed to the Community Zone
      • Electronic Collection Contributed To CZ – indicates if electronic collections were contributed to the Community Zone
    • July 2021 Analytics URM-143885
      The Num of Locate Failed Requests field was added to Lending Requests > Lending Request Details and Borrowing Requests > Borrowing Request Details. It indicates the number of failed locate requests.
    • July 2021 Analytics URM-143885
      The following fields were added to User dimensions located in subject areas besides the Users subject area:
      • Cataloger Level
      • Has Role other than Patron
      • Has Role other than Patron and Instructor
      • Is Blocked
      • Patron Letters Opt In
      • Patron Letters Opt Out

      These fields were added to:

      • Borrowing Requests > Requester
      • Course Reserves > Librarian
      • E-Inventory > Cost Usage POL Approver
      • E-Inventory > Electronic Collection PO Line Approver
      • E-Inventory > Portfolio PO Line Approver
      • Fines and Fees > User Details
      • Fulfillment > Borrower Details
      • Funds Expenditure > PO Line Approver
      • Leganto Student Usage > Student Details
      • Physical Items > PO Line Approver
      • Purchase Requests > Purchase Request Approver
      • Purchase Requests > Purchase Request Assigned To
      • Purchase Requests > Purchase Request Creator
      • Purchase Requests > Purchase Request Modified By
      • Purchase Requests > Purchase Request Requester
      • Requests > Requester
    • July 2021 Analytics URM-96443
      On the Alma Analytics Object page (Analytics > Analytics Objects > Analytics Objects List), the Analytics Folder and Name fields are now on their own lines which gives these fields additional space to display values.
    • July 2021 Analytics URM-151339 URM-151349
      The following three new tabs were added to the Consortia Network dashboard:
      • Logins in last 30 days – the number of logins in the last 30 days
      • Logins in last 365 days – the number of logins in the last 365 days
      • Bibliographic records – the number of active (not deleted) bibliographic records per institution in consortia

      The Logins to Alma per institution tab was removed.

    • July 2021 Analytics URM-147302
      Reports created with the Institution Name field that was filtered to a specific institution now run faster. Reports that were created before this enhancement require the filter to be reapplied to benefit from this enhancement. An indication that the report is now benefiting from the improved speed is that in the filter text under the report, the institution code is displayed and not the institution name.

      institution_name_filtered.png

      Filtered Institution Field
    • June 2021 Analytics URM-147495
      The Operator Identifier 1 and Operator Identifier 2 fields were added to Fines and Fees > Staff Operator Details. They allow you to enrich the user details exported to Analytics with additional identifiers.
    • June 2021 Analytics URM-138607
      Two additional reporting code fields (#4-5) were added for reporting codes and reporting code descriptions to the PO line dimension for all subject areas in which it appears. The names of the fields were also changed, so that the reporting code fields are as follows:
      • Reporting Code - 1st
      • Reporting Code - 2nd
      • Reporting Code - 3rd
      • Reporting Code - 4th
      • Reporting Code - 5th
      • Reporting Code Description - 1st
      • Reporting Code Description - 2nd
      • Reporting Code Description - 3rd
      • Reporting Code Description - 4th
      • Reporting Code Description - 5th
    • June 2021 Analytics SF: 00720550 00844304 URM-137250
      The DC License and DC Rights fields were added to the Bibliographic Details dimension for all subject areas in which it appears. These fields contain the license and rights information from Dublin Core bibliographic records.
    • June 2021 Analytics URM-146037
      The following Acquisitions reports were removed:
      • Non-Serial Issues Claims Report (Items without material type issue and expected receiving date greater than seven days that have not been received)

        It was replaced by: POLs with Items which should have arrived in the last 2 years and have not - all material types

      • Serial Issues Claims Report (Items with material type issue and expected receiving date greater than seven days that have not been received)

        It was replaced by: Report name: POLs with Items which should have arrived in the last 2 years and have not - material type journal

    • June 2021 Analytics URM-148164
      The following improvements were made in the Physical Items dashboard:
      • An indication of the total number of items was added to the Item Count by Library and Location tab and to the Item Process Type tab.
      • In the Inventory > Physical Items dashboard, the Physical Items > Num of Items field was renamed to Num of Items (Deleted + In Repository).
    • June 2021 Analytics URM-148163
      In the Fulfillment > Fines and Fees Dashboard for the User Cash Transactions and Library - Type Transactions tabs, when there are no results, the message displayed is now: No Transactions meet the criteria specified in the filters.
    • June 2021 Analytics URM-149603
      The TR_J1 - Unique Title Requests field was removed from the Usage Data Details - Release dimension in the Usage Data subject area. This field was removed because it was erroneously added when COUNTER Release 5 was added to Alma and Alma Analytics.
    • May 2021 Acquisitions SF: 00922507
      When Alma harvests usage reports from a vendor's URL, not all vendors know to accept the 2 date formats which are sent via the URL. Alma was enhanced to inter-operate error codes that are sent from the vendor, send another request with 1 date format and add an additional request (if needed) with another date format.
    • May 2021 Fulfillment URM-98676
      Alma's search for partner records has been enhanced. Previously, the records were only searchable by name and code. The enhancement now allows other elements to be searched, i.e. partner symbol, email address (from parameters tab) and customer code (for AFN).
    • May 2021 Fulfillment
      An enhancement to the current export capabilities in Alma has been made. The existing export job will now include the following:
      • Request comment
      • Bib metadata - description, author, title and year
      • User data (requester ID, full name and preferred address)
    • May 2021 Analytics URM-140468
      Out-of-the-box reports are now available for the System Events subject area that was released in March. These reports were taken from the old Events subject area.
    • May 2021 Analytics URM-146014
      The new Invoice Related Events report was added to the System Events folder.
    • May 2021 Analytics URM-144695
      The Invoice-Internal copy Ind field was added to Funds Expenditure > Invoice Line. It indicates if an internal copy of the invoice exists.
    • May 2021 Analytics URM-147304
      The User Record Type field (Users > User Details) now indicates if the user is a Contact user.
    • May 2021 Analytics URM-145419
      The following folders were renamed for improved clarity:
      • Usage Data Details was renamed to Usage Data Details – Release 4
      • Usage Data Details – JR5 was renamed to JR5 Usage (Release 4)
    • May 2021 Analytics URM-145640
      Tool tips were added to the following fields in E-Inventory > Cost Usage fields to indicate the source of the data: 
      E-Inventory Field From Usage Data Field
      E-Inventory > Cost Usage Measures > Usage DR Usage Data > Usage Data Details - Release 5 > DR - Unique Title Requests
      E-Inventory > Cost Usage Measures > Usage TR_B1 Usage Data > Usage Data Details - Release 5 > TR_B1 - Unique Title Requests
      E-Inventory > Cost Usage Measures > Usage TR_J1 Usage Data > Usage Data Details - Release 5 > TR_J1 - Unique Item Requests
    • May 2021 Analytics URM-146036
      The following Acquisitions reports will be removed for the June release:
      • Non-Serial Issues Claims Report (Items without material type issue and expected receiving date greater than seven days that have not been received)

        It will be replaced by: POLs with Items which should have arrived in the last 2 years and have not - all material types

      • Serial Issues Claims Report (Items with material type issue and expected receiving date greater than seven days that have not been received)

        It will be replaced by: Report name: POLs with Items which should have arrived in the last 2 years and have not - material type journal

    • March 2021 Resource Management URM-141433
      A new advanced search index 'Electronic Collection Content Type' was added on the Electronic Collection level. It enables you to search for electronic collections of a specific type.
    • March 2021 Digital Resource Management URM-125510
      Quick Access for Primo VE is now available for mobile devices. For more information, see Configuring the Quick Access Service.
    • March 2021 Digital Resource Management URM-144511
      The IIIF infrastructure was upgraded for better performance in displaying high resolution images with all of the Alma viewers.
    • March 2021 Analytics URM-144434
      The procedure for deleting an object from the community folder was changed. You now enter DeleteObject in the Description field in the Properties of the object. For more information, see Deleting a Folder, File, or other Object from the Community Folder.
    • March 2021 Analytics URM-140895
      The Num of Rapid Local Override field was added to Borrowing Requests > Borrowing Request Details > Partner Level Requests. It indicates the number of times librarians overrode the RapidIILL block for borrowing requests when the borrowing library has the requested item locally.
    • March 2021 Analytics URM-142547
      In the Titles Level Overlap Analysis dashboard, the explanatory text was moved to the right of the fields for better readability in the following tabs:
      • Overlap any inventory
      • Only P
      • Only E

      Additionally, the explanatory text was added to the Overlap P and P tab.

    • March 2021 API
      The "GET" PO-line API was enhanced to include information regarding the ID of the portfolio associated with the PO line.
    • March 2021 API
      The Alma UI and API have been updated to clearly indicate "Process_ID". Previously, there were instances that "Process_ID" was referred to as "Job_ID" and "Instance_ID". This has been rectified to all instances to refer to "Process_ID".

    • February 2021 Resource Management URM-140976
      Various issues related to accessibility in the Metadata Editor were treated, with the purpose of making the MDE compliant with the Americans with Disabilities Act (ADA).
    • February 2021 Fulfillment-Resource Sharing idea exchange Idea Exchange URM-112144
      The Automatically Print Slip option in the resource sharing receiving interface was enhanced. This option is used when printing the Resource Sharing Receive Slip Letter when receiving a physical item. It now retains the last value you selected for this option.
    • February 2021 Analytics URM-138124
      The following fields were added to the Fulfillment subject area:
      • The Loans (Not In House) from Resource Sharing Borrowing Request field was added to the Loan dimension. It indicates the number of not in house loans that came from a resource sharing borrowing request.
      • The Is Resource Sharing Borrowing Request Loan field was added to the Loan details dimension. It indicates if the loan was initiated by a resource sharing borrowing request.
    • February 2021 Analytics URM-139428
      The Active for Fulltext In CDI field in E-Inventory > Electronic Collection was renamed to CDI-only full text activation to be consistent with the naming style of the other CDI fields.
    • February 2021 Analytics URM-141963
      The In CDI field in E-Inventory > Electronic Collection was renamed to CDI - Available for CDI search activation to better explain the purpose of the field.
    • January 2021 Acquisitions URM-135752
      The summary section in the 'Fund and Ledger' screen was moved to be positioned at the top of the page.
    • January 2021 Digital Resource Management URM-131617
      The Share focused file checkbox that allows you to share a URL with the viewer focused to a specific file is displayed only when there are multiple files in the representation.
    • January 2021 Digital Resource Management URM-134930
      In the new Alma Viewer, you can now collapse the Descriptive Information pane for a larger file display in the center pane.
    • January 2021 Analytics URM-137922
      The Label and Label History (deleted labels) fields were added to Borrowing Requests > Borrowing Request Details and Lending Request > Lending Request Details.
      These fields are relevant for customers with Rapido.
    • January 2021 Analytics URM-140149
      The Duplicate Titles by 035a for network institution out-of-the-box report was added to the /shared/Alma/Consortia/Reports folder. It retrieves duplicate titles by field 035 subfield a in a Network Zone institution and excludes titles linked to the Community Zone. This report is designed to be run in the Network Zone.
    • January 2021 Analytics URM-139031
      The new YoY (Year over Year) out-of-the-box dashboard was added to Alma Analytics. It contains the following reports that display changes to data in one period from one year to the next.
      • API executions YoY
      • COUNTER usage Books R4 YoY
      • COUNTER usage Books R5 YoY
      • COUNTER usage Journals R4 YoY
      • COUNTER usage Journals R5 YoY
      • Expenditure for Electronic Format
      • Expenditure for Physical Format
      • Leganto Student Usage Events YoY
      • Loans YoY
      • Patron Physical Item Requests YoY
    • January 2021 Analytics URM-126999 URM-136233
      The Proquest Purchase Model field was added to E-Inventory > Portfolio. It contains information for both single institutions and multi-institution implementations. Possible vales are:
      • Subscription
      • DDA
      • Owned
    • January 2021 Analytics URM-125171
      The following fields were added to Usage Data > Usage Data Details - Release 5 to display information for IR R5 COUNTER reports:
      • IR - Total Item Requests
      • IR - Unique Item Requests
      • IR - Total Item Investigations
      • IR - Unique Item Investigations
      • IR - No License
      • IR - Limit Exceeded
      • IR_A1 - Unique Item Requests
      • IR_A1 - Total Item Requests
      • IR_M1 - Total Item Requests
    • January 2021 Analytics URM-139319
      The Has Active Items (to be deprecated) field (Physical Items > Holding Details) was removed.
    • August 2021 Fulfillment - Course Reserves SF: 00924743 URM-152506
      The Leganto List Library Notes and the Leganto List Library Notes Last Update fields were added to Course Reserves > Reading List. They indicate the reading list library notes and the date that the notes were last updated.
    • August 2021 Fulfillment - Course Reserves URM-151990
      If the reading list has no citation, the Librarian > First Name and Librarian > Last Name fields now contain the librarian name. However, if there is no reading list, the value of these fields is unassigned. In this case, the Librarian > User ID field is also unassigned.
    • July 2021 Fulfillment - Course ReservesURM-152351
      A new event was added to the DCS synchronize job report to include copyrights whose statuses remain unchanged.
    • June 2021 Fulfillment - Course Reserves
      The following DSC system tags can be used when creating a rule to auto-generate a purchase request (Configuration > Fulfillment > Courses > Citation Processing Rules):
      • Digitisation Approved
      • Digitisation Rejected
      • Digitisation Removed
      • Digitisation Sent
      • Digitisation In Progress
        DigitisationRequests.png

        Digitisation
    • April 2021 Fulfillment - Course Reserves URM-148969
      You can now control whether there will be an option to automatically attach files to a citation in a digitization request. When the auto_attach_digitization_to_citation parameter is set to true (Configuration Menu > Fulfillment > General > Other Settings), the option is available. When set to false, the option is unavailable. See Configuring Other Settings (Fulfillment)
    • February 2021 Fulfillment - Course Reserves URM-143162
      You can now create a set of courses by uploading a file that contains the course IDs. For more information, see Creating Itemized Sets.
    • January 2021 Fulfillment - Course Reserves SF: 00855648 URM-136134
      When a user is added as an instructor to a course in Alma, the instructor role is added if it was not already present for the user. The role expiration date is calculated based on the instructor_role_expiration_months parameter (Fulfillment > General > Other Settings). 

    Resolved Issues

    • July 2021 Release Update Acquisitions SF: 00967612 00970977 00970987 00970989 00971104 00971108 00971110 00971211 00971233 00971237 00971400URM-155228
      Purchase requests were missing from the Manage Purchase Requests page. This was fixed.
    • July 2021 Release Update Resource Management SF: 00971334 URM-155521
      The Customize View settings were not working for the Electronic Collection display in the Repository Search. This was fixed.
    • July 2021 Release Update Resource Management 
      In the Accession configuration mapping table, certain values disappeared. This was fixed.
    • July 2021 Release Update Resource Management SF: 00967920 00967963 00969460 00969832 00971059 00971074 00971225 00971389 00971405 00971410 00971422 00971443 URM-155968
      Words containing "aa" and "ä" were not searchable. This was fixed.
    • July 2021 Release Update Fulfillment SF: 00960945 00964042 URM-154257
      Comments added to an AFN request in Primo are were visible to the lender. This was fixed.
    • July 2021 Release Update Fulfillment - Resource Sharing URM-154239
      When an item was received with an item policy, the policy was not used. This was fixed.
    • July 2021 Release Update Fulfillment - Resource Sharing SF: 00966805 00968674 URM-155857
      When borrowing requests were submitted for titles with multi-volumes, "locate of lending request" failed because Volume and Barcode were missing. This was fixed.
    • June 2021 Release Update Resource Management SF: 00951262 00954778URM-152868
      When items were scanned and assigned to the "Main Library," the process status stayed as "Transit". This was fixed.
    • June 2021 Release Update Resource Management SF: 00948650 00951262 00953962 00954778URM-152670
      Moving items to a temporary location left the item connected to a deleted holding. This has been fixed. This was fixed.
    • June 2021 Release Update Resource Management SF: 00961926URM-154079
      Available items sometimes returned the message: "The Item has no requestable inventory". This was fixed.
    • June 2021 Release Update Resource Management SF: 00962673URM-150924
      New Metadata Editor: For GND records in the community, the cataloger level value always remained at 2. This was fixed.
    • June 2021 Release Update Resource Management SF: 00962405 00962761URM-154170
      New Metadata Editor: When adding a new field in the new Metadata Editor, the field width changed, and fields jumped while editing. This was fixed.
    • June 2021 Release Update Resource Management SF: 00962261 00962719 00963122URM-154335
      New Metadata Editor: When opening the new Metadata Editor from Configuration > Discovery > Normalization rules for External Data sources, it did not load. This was fixed.
    • June 2021 Release Update Resource Management SF: 00962673 00962683 00963525URM-154259
      The CatLevel in Authority records was set automatically to catalogers CatLevel. This was fixed.
    • June 2021 Release Update Resource Management SF: 00920248 00950781URM-146920
      The update from Central Catalog job took more than 10 days to finish. This was fixed.
    • May 2021 Release Update Acquisitions SF: 00952423 00952428 00952452URM-152039
      Adding the Sort Routine to the user preferences caused the fetch from it to fail when the sort routine's name had a comma in it. This was fixed.
    • May 2021 Release Update Fulfillment - Resource Sharing SF: 00951885URM-151894
      Shipping a digital item via 'Ship item' without an attached file generated an error. This was fixed.
    • May 2021 Release Update Resource Management SF: 00952426 00952547URM-152103
      The Allocate button disappeared from the Item editor in the May release. This was fixed.
    • May 2021 Release Update Resource Management SF: 00941842URM-150206
      In some instances, corrupted XMLs were created by the general Publishing job. This was fixed.
    • May 2021 Release Update Resource Management SF: 00951895URM-151895
      When Show Directional Characters was enabled, it wasn't possible to highlight text in the New Metadata Editor using the arrow keys. This was fixed.
    • May 2021 Release Update Resource Management
      Updates were made to ensure the new Metadata Editor is not from the cache when deploying the new NG version.
    • May 2021 Release Update Resource Management SF: 00942008URM-150113
      Bib Records with MARC_6XXNAME heading were returned when browsing for Names (without MARC21 600/610/611). This was fixed.
    • May 2021 Release Update Administration and Infrastructure SF: 00952137 00952621 00952643 00952666URM-151974
      Unable to create itemized set from a list of OCLC numbers. This was fixed.
    • May 2021 Release Update Administration and Infrastructure SF: 00924518URM-148563
      The access rights for concurrent users were not reset after a user logged out. This was fixed.
    • May 2021 Release Update Administration and Infrastructure SF: 00909405URM-149939
      Some users were blocked from accessing links to digital files in the View It. This was fixed.
    • March 2021 Release Update Acquisitions SF: 00918081URM-145923
      An error message was received when sending a PO. This was fixed.
    • March 2021 Release Update Acquisitions SF: 00932591 00933369 00934045 00933284 00933495 00932431 00930859 00930813 00933242 00932844 00930609 00927386 00931489 00932461 00932759 00932399 00931110 00933130 00933638 00932483 00933395 00930687 00932720 URM-147706
      There were some issues with the Update PO Lines jobs and sets in Solr. This was fixed.
    • March 2021 Release Update Resource Management SF: 00903532 00933914URM-148718
      Call Number Range integer qualifiers were not working. This was fixed.
    • March 2021 Release Update Resource Management SF: 00923930 00934220URM-148159
      Publishing to Primo finished with the status “Completed with Errors” every time with Publishing Error “Failed to retrieve holdings for mmsids”. This was fixed.
    • March 2021 Release Update Resource Management SF: 00861689 00907589 URM-142983
      SBN integration - The update of a Uniform title in SBN was producing an error "Authority was contributed but failed on non-preferred fields". This was fixed.
    • March 2021 Release Update Fulfillment SF: 00924347URM-148955
      Previously, sorting the list of loans, using any of the column fields (i.e. Title, Loan Status), did not work. This was fixed.
    • March 2021 Release Update Fulfillment SF: 00907725 00926353URM-148461
      Downloading files created following a digitization request was not possible when the authentication was based on 'Social Login' or 'Login via Email' and the user had only the Patron role. It is now supported. This was fixed.
    • March 2021 Release Update Administration and Infrastructure SF: 00934832URM-148369
      The duplicate row button in Advanced Search for users was not working properly. This was fixed.
    • March 2021 Release Update Administration and Infrastructure SF: 00934351 00934580 00934776URM-148872
      Itemizing logical user sets created sets that did not return any members. This was fixed.
    • February 2021 Release Update Resource Management SF: 00924032URM-146915
      The Export Urls job was failing. This was fixed.
    • February 2021 Release Update Resource Management SF: 00890776URM-144971
      Linked Data (publishing and APIs) is now enriched with URIs pointing to the National Library of Israel Authority base.
    • February 2021 Release Update Fulfillment SF: 00924811URM-147047
      The drop-down list of the libraries in the advanced search for physical items/titles is now sorted alphabetically.
    • January 2021 Release Update APIURM-143393
      Create request API now supports manual description with holdings.
    • January 2021 Release Update Resource Management URM-143098
      General publishing using Authority Enrichment did not publish non-preferred fields from CZ records when publishing IZ records that were linked to NZ records. This was fixed.
    • January 2021 Release Update Resource Management SF: 00914603 URM-144864
      All the jobs in the Bridge caused errors. This was fixed.
    • January 2021 Release Update Resource Management SF: 00914444 00914499 00914514 00914526 00914530 00914594 URM-144803
      The Accession Numbers in the old Metadata Editor were not displaying or being created correctly. This was fixed.
    • January 2021 Release Update Resource Management SF: 00897901 URM-141040
      EOD Import jobs failed but Inventory and PO Lines were created successfully. This was fixed.
    • January 2021 Release Update Administration and Infrastructure URM-141423
      Several UNIMARC classification enhancements were implemented due to incorrect functionality. This was fixed.
    • January 2021 Release Update Administration and Infrastructure SF: 00893421 URM-140615
      In UNIMARC, the commas were taken into consideration when linking bib headings to authority. This was fixed.
    • August 2021 Acquisitions SF: 00757262 00816764 URM-122654
      Query to Requester, Letter not attached to User Record. This was fixed.
    • August 2021 Acquisitions SF: 847138 URM-135196
      The title for Purchase request was taken from the DC record. Now if the bibliographic record exists, the title will be taken from the display section where it contains the full title.
    • August 2021 Acquisitions SF: 00921373 URM-146016
      The creation date and modification date were exported in String format. This was fixed to be exported in date format.
    • August 2021 Acquisitions SF: 00898120 URM-146955
      The recalculate encumbrance job didn‘t update the dis-encumbrance in some cases. This was fixed.
    • August 2021 Acquisitions SF: 00961351 URM-153951
      There was a typo in the description of the Trail Letter (Acquistions Department). This was fixed.
    • August 2021 Acquisitions SF: 963493 URM-154758
      CZ/NZ/IZ Icons in PO Line details was not visible. This was fixed.
    • August 2021 Acquisitions SF: 00914419 URM-148224
      Error message was added to Mashup labels code table for translation.
    • August 2021 Acquisitions SF: 00847557 URM-132488
      When PO Line is not fully funded, trying to renew it will display an error message. This was fixed
    • August 2021 Acquisitions SF: 885071 URM-142881
      E-Activation Task created upon sending order that was imported via EOD where New Order import profile has ‘Do not create electronic activation task‘ checkbox ticked. This was fixed.
    • August 2021 Acquisitions SF: 00926026 URM-149463
      When creating Purchase Request for a user with status = DELETED (It is possible if the user is selected from the recently used records) Alma will display an error message ‘Requester is not found...‘. This was fixed.
    • August 2021 Acquisitions SF: 819267 URM-127874
      In invoice list, when sorting the list by Vendor, some of the records disappeared. This was fixed.
    • August 2021 Acquisitions SF: 00903503 00903069 00961311
      Claims Facets are incorrectly reset once a change is made to a PO Line. This was fixed.
    • August 2021 Acquisitions SF: 00788203 URM-121659
      Cancelling PDA program will deactivate the import profiles and the scheduled jobs for them. This was fixed.
    • August 2021 Acquisitions SF: 00936673 00883444 00855819 00944379 00835020 00915789 00945587 00880988 00922269 00918660 00915560 00926293 00948276 00912595 00918645 00931781 00922641 00959236 00913740 00910070 00896168 00905854 00917777 00919706 00962671
      Sushi Harvesting job not harvesting automatically. This was fixed.
    • August 2021 Acquisitions SF: 00943927 00949099
      DARA‘s ‘High Request Load‘ recommendation is now available also for ‘Purchase request operator‘ and ‘Purchase request manager‘.
    • August 2021 Administration and Infrastructure SF: 00942230 URM-152413
      An error was encountered when trying to access Rota Templates. This happens after the Scope column was selected for sort. This was fixed, the sort for Scope was removed since it is not supported.
    • August 2021 Administration and Infrastructure SF: 00954749 URM-153995
      Searching users by phone number used to return inaccurate results due to indexing issue with SIS process. This was fixed.
    • August 2021 Administration and Infrastructure SF: 00856445 URM-132844
      Some document files were not displayed in the New Alma viewer. This was fixed.
    • August 2021 Administration and Infrastructure SF: 00960668 00942290 00936452 00955194 00948784
      The full display of a brief record appeared empty in the Quick Access view. This was fixed.
    • August 2021 Administration and Infrastructure SF: 00946747 00938681
      When signing out from the Deposit link, users were redirected incorrectly to an irrelevant URL. This was fixed.
    • August 2021 Administration and Infrastructure SF: 00957528 00939388
      When Primo VE customers accessed the deposit direct link, they would be directed to the Deposit UI with the AlmaGeneralView vid. This was fixed.
    • August 2021 Administration and Infrastructure SF: 00909122 URM-147895
      The Arabic semicolon broke the linking to the authority record. This was fixed.
    • August 2021 Administration and Infrastructure SF: 00965610 00965810
      Previously, the volume metadata for book chapter requests did not transfer from RapidILL to Alma. This was fixed.
    • August 2021 Analytics SF: 00871250 00952308 00889875 00663631 00700798 00795218 00930143 00921271 00954964
      The Item Policy field (Physical Items > Physical Item Details) displayed a value of UNKNOWN instead of the correct value. This was fixed.
    • August 2021 Analytics SF: 00913246 00910503
      The Electronic Material Type field (E-Inventory > Portfolio) is not updated with information from Alma. This was fixed.
    • August 2021 API SF: 00908709 URM-145131
      Customer cannot perform two subsequent returns. This was fixed.
    • August 2021 API SF: 00934710 URM-149565
      The Update Electronic Service API, when in Group-Settings ‘Proxy enabled‘ is ‘Resource Default‘, the API failed and deleted the Group-Setting. This was fixed.
    • August 2021 API SF: 00920172 URM-151421
      The Get-Lending-Requests API when used with the ‘lang‘ parameter, returned no results. This was fixed.
    • August 2021 Fulfillment SF: 00928852 00929028
      Previously, when items are available in different locations within the same library and multiple requests are placed, in Pick from shelf list, the requests are assigned to only one item location. This was fixed.
    • August 2021 Fulfillment SF: 00941694 00935908 00949545 00942260
      The library filter of manage in process items page for non acquisition departments was wrong. This was fixed.
    • August 2021 Fulfillment SF: 00945162 URM-153046
      Previously, comments containing quotation marks did not save. This was fixed.
    • August 2021 Fulfillment SF: 00875781 URM-146674
      Performance issues with the library deletion process. This was fixed.
    • August 2021 Fulfillment SF: 00936491 00934042
      Previously, request was created with status ‘FAIL_TO_MATCH_ITEM‘ due to simultaneous access to the same record/item. Now, recalculation brings these requests back to the track.
    • August 2021 Fulfillment SF: 00964907 URM-154753
      Cancellation notices cannot be sent to requesting staff via email when a work order request is cancelled. Now, the Notify Users checkbox in the cancel requests popup is displayed for all request types.
    • August 2021 Fulfillment - Resource Sharing SF: 00945291 00936973
      Resource Sharing Shipping Slip Letter was missing the item information for a lending request with multiple barcodes. This was fixed.
    • August 2021 Fulfillment - Resource Sharing SF: 00942076 URM-153269
      Resource Sharing Lending Requests Task List: When opening the Physical Drawer, the ‘Items of Related Records‘ link is displayed, but when clicking it, an error message is displayed and there are no results. This has been corrected, now the ‘Items of Related Records‘ link is not displayed.
    • August 2021 Fulfillment - Resource Sharing SF: 00943501 URM-153369
      A search in Borrowing/Lending task lists with phrase ‘pattern‘ would fail because it is a reserved word in the indexer. This was fixed.
    • August 2021 Resource Management SF: 00873634 URM-138527
      Changing the date range for Reminders and then clicking Enter, resulted in returning to the previous page. This was fixed.
    • August 2021 Resource Management SF: 00951020 URM-152706
      Holdings Management: When relinking holding with over 1000 items, the relink operation failed. This was fixed.
    • August 2021 Resource Management SF: 00696528 URM-152840
      Analytics: Physical Items fields ‘Public Note‘ and ‘Fulfillment Note‘ were limited to 400 characters. They are now expanded to 4,000 characters.
    • August 2021 Resource Management SF: 00928196 URM-153050
      Physical Item Editor: When editing a physical item and changing its process type, the save fails for items belonging to a holdings record having more than 1,000 items. This was fixed.
    • August 2021 Resource Management SF: 00961583 URM-154073
      Repository Search: Selecting over 1000 items in the Physical Items search and performing 'Run A Job' operation caused an error. This was fixed.
    • August 2021 Resource Management SF: 00880241 00900514 00875863
      When activating portfolio only PO Lines when the status is ‘sent‘, are moved to the next status.
    • August 2021 Resource Management SF: 953266 URM-149076
      Finding a Network Zone record with portfolio using the ‘combined search‘ results in an error when clicking on Electronic tab > View. This was fixed.
    • August 2021 Resource Management SF: 931059 URM-149594
      The definition ‘Display closely related records holdings‘ did not work when location sorting was enabled. This was fixed.
    • August 2021 Resource Management SF: 00922805 URM-149763
      Group setting embargoes appeared as 'Available' instead of 'Not Available' in some contexts because the operator variable wasn‘t set correctly. This was fixed.
    • August 2021 Resource Management SF: 00935765 URM-154061
      In staff search results (Electronic results, Collection results, Portfolio results), the ISBN field was taken from 776 in some cases. This was fixed.
    • August 2021 Resource Management SF: 00950957 URM-151873
      Some jp2 files in Jpx format failed to process and display in Alma. This was fixed.
    • August 2021 Resource Management SF: 952056 URM-152216
      Full-text generation failed for some files. This was fixed.
    • August 2021 Resource Management SF: 00939228 URM-152430
      When adding a representation to a digital title and selecting a Library or Access Rights from the Recent list, the selections were not retained. This was fixed.
    • August 2021 Resource Management SF: 955586 URM-152498
      Some docx files did not display in the new and classic Alma viewer. This was fixed.
    • August 2021 Resource Management SF: 00584628 00894287
      Publishing Information: for sporadic records, publishing history could not be created. This was fixed.
    • August 2021 Resource Management SF: 00902359 URM-146066
      Sometimes a published bibliographic field was not enriched with authority data, when the bibliographic and authority field have the same tag. This has been fixed.
    • August 2021 Resource Management SF: 00951418 URM-152121
      General Publishing job report: There was a discrepancy between the total for Records Processed and the number of records displayed in the report counters section. This was fixed.
    • August 2021 Resource Management SF: 00927442 URM-149717
      Repository Search: The Language facet showed code rather than description for ISO 639-1 language. This was fixed.
    • August 2021 Resource Management SF: 00854277 URM-135236
      Search result on ‘Tag Suppressed (Title)‘ and ‘Tag Sync External Catalog‘ give incorrect results. This was fixed.
    • August 2021 Resource Management SF: 00883681 URM-151734
      Repository Search: The series information is displayed in reversed order If the record has more than 1,490 fields. This was fixed.
    • August 2021 Resource Management SF: 00928870 URM-148052
      The GetIt took a very long time to load the list of items when the user was signed in if the record was a serial title that had many items with the same description. This was fixed.
    • August 2021 Resource Management SF: 00939839 00931783 00814507 00888964
      Bx recommendation services weren‘t filtered by date coverage in Primo VE. This was fixed.
    • August 2021 Resource Management SF: 00868686 URM-141157
      Home and work addresses weren‘t shown in user requests list as a pickup location in My Account. This was fixed.
    • August 2021 Resource Management SF: 00871595 00943256 00935752 00851226 00932229
      Item level general electronic services weren‘t filtered by display logic rules. This was fixed.
    • August 2021 Resource Management SF: 00911593 URM-147004
      Local field labels appeared as codes in basic pre-filters search. This was fixed.
    • August 2021 Resource Management SF: 00954143 URM-152919
      ‘CNMARC: 200.f,g‘ is not mapped to creator facet. This issue was resolved by adding missing drools for facet_creator_contrib for CNMARC.
    • August 2021 Resource Management SF: 00960944 00960946
      Navigation and display issues in Define Thumbnail Link configuration table. This was fixed.
    • August 2021 Resource Management SF: 00828327 URM-131993
      CDI Tab tooltips in Alma Electronic Collection Editor are unclear and do not match the actual available settings. This was fixed.
    • August 2021 Resource Management SF: 00857279 URM-135548
      Primo Central publishing profile has been removed, but the job continues to run. This was fixed.
    • August 2021 Resource Management SF: 00860418 URM-138785
      The CDI tab of a collection did not properly read breaks without the CDI Inventory Operator role for Local Notes. This was fixed.
    • August 2021 Resource Management SF: 00869392 URM-149738
      The Electronic Collection CDI tab Local Notes field did not auto expand to show all content for CDI Inventory Operators. This was fixed.
    • August 2021 Resource Management SF: 00900087 URM-141961
      New Metadata Editor: When editing a record with a long title, the tooltip in the record list and the tooltip on the record‘s header in editing mode were too long and caused display issues. This was fixed.
    • August 2021 Resource Management SF: 00943272 00940493 00947209 00953413 00930468 00952889 00941060 00946009 00961829 00952437
      New Metadata Editor: The community zone records were missing the local field icon. This was fixed.
    • August 2021 Resource Management SF: 00937119 00935257
      New Metadata Editor: ‘Copy to Catalog‘ operation was not available when viewing a Community Zone record. This was fixed.
    • August 2021 Resource Management SF: 00944498 URM-150452
      New Metadata Editor: After performing SBN search and Copy & Overlay operation, the search panel remains (when it shouldn‘t), and the left collapsed record remains when it should disappear. This was fixed.
    • August 2021 Resource Management SF: 00951858 URM-151859
      Metadata Configuration > Marc21 Bibliographic: Sporadically, the page is loaded for several minutes, then opened with an empty list. The was fixed.
    • August 2021 Resource Management SF: 00958283 00952483 00934455
      New Metadata Editor: Duplicating a Normalization Rule after save creates a rule with the previous content. This was fixed.
    • August 2021 Resource Management SF: 00955762 URM-152796
      New Metadata Editor: “Browse Bibliographic Headings” is opened unexpectedly when editing a Bib record linked to authority > click binoculars > select bibliographic records tab > click any title > then “Back to Results” > “Browse Bibliographic Headings”. This was fixed.
    • August 2021 Resource Management SF: 00929118 URM-147887
      New Metadata Editor: When editing a data field that contains Hebrew/Arabic characters, the cursor was not displayed well. This was fixed.
    • August 2021 Resource Management SF: 00949923 URM-154761
      New Metadata Editor: The ‘Open form editor‘ for UNIMARC fixed-length fields is not available from the data-field menu. The was fixed.
    • August 2021 Resource Management SF: 00929653 URM-149968
      Metadata Editor: Save of faulty rule resulted in a long and non-responsive error message. The issue was fixed by using the expansion/collapse mechanism of messages - a general error title is displayed - and by clicking it the full list of errors can be opened.
    • August 2021 Resource Management SF: 00953810 URM-153807
      New Metadata Editor: For consortia members institutions PrimoVE is not defined for them, while is defined in their NZ, the rules tab is empty. This was fixed.
    • August 2021 Resource Management SF: 00862825 URM-134106
      Authority Management: When a customer has configured parameter 6xx_0_names_vocabulary to a certain vocabulary and has configured the authority priority, the 6xx bib heading is linked to the first authority priority vocabulary instead of the vocabulary defined in the 6xx_0_names_vocabulary parameter. The was fixed.
    • August 2021 Resource Management SF: 920645 URM-154915
      Authority Management: Metadata Editor - Partial linking: After manual linking via F3 of a heading containing subdivisions, the half-binocular icon is not displayed after saving the record. The was fixed.
    • August 2021 Resource Management SF: 00959058 URM-154638
      An error could occur when the SBN record contained a 510 or 517 UNIMARC field, which could prevent displaying ‘Search Resources‘ results or importing the record from SBN. This was fixed.
    • August 2021 Resource Management SF: 00949761 URM-152870
      When running jobs of a Digital import profile that uses OAI import protocol, it was not possible to download files of imported records from the report. This was fixed.
    • August 2021 Resource Management SF: 896585 URM-145417
      SBN integration: There was an incorrect behavior of the date‘ s representing (in tags 100 and 210) which ended in a dot. This was fixed.
    • August 2021 Resource Management SF: 00911894 URM-147279
      ‘Held By My Institution‘ failed due to a null suppressed tag. This was fixed.
    • August 2021 Resource Management SF: 00942535 URM-150069
      Modified the SBN Alignment job default to ‘update‘ operation when <oggettoVariato> element in the response from SBN is missing the tipoModifica attribute.
    • August 2021 Resource Management SF: 960681 URM-153974
      When editing NZ records linked to the Aleph central catalog in the IZ, some but not all local extensions in the IZ record could be deleted. This was fixed.
    • July 2021 Acquisitions SF: 00900736 00367719 URM-68587
      When creating PO Line, the list of Acquisition Methods are not sorted and does not reflect the order list in Code table. This was fixed.
    • July 2021 Acquisitions SF: 00796250 00711237 00794740 00854784 00935320 00923964 00946720 00922044 00827911 00800644 00919984 URM-125283
      Claim was triggered twice automatically for the same PO-Line with one item. This was fixed.
    • July 2021 Acquisitions SF: 00854138 URM-132739
      When using the 'Invoice Service' API with Op=Rejected, the Invoice would get stuck in 'In-Review' status. This was fixed.
    • July 2021 Acquisitions SF: 00944768 URM-150746
      Creating an Invoice from PO with hundreds of POLs generates an Oops error. This was fixed.
    • July 2021 Acquisitions SF: 00943760 URM-151948
      Warning and suggestion given not to delete a vendor, but simultaneously vendor is deleted. This was fixed.
    • July 2021 Acquisitions SF: 00868116 00865167 00878278 00941275 00858821 URM-134221
      The Public Access Model field in ViewIt was not showing translations for languages other than English. This was fixed.
    • July 2021 Acquisitions SF: 00868204 URM-136024
      Relink of previously cancelled PO line gave an error. This was fixed.
    • July 2021 Acquisitions SF: 00959759 00943032 00957654 00958093 00958051 00958058 00958931 00958914 URM-145602
      There was a problem with the 'Status' facet in SOLR. This was fixed.
    • July 2021 Acquisitions SF: 00845140 URM-137723
      PO Line's resource is 'not active' when resource is 'active'. This was fixed.
    • July 2021 Acquisitions SF: 00851960 URM-133120
      Running 'Update PO Line information - Advanced' changed the PO Line owner if the field was selected and then the task parameter was unchecked. This was fixed.
    • July 2021 Acquisitions SF: 00931920 URM-148542
      When trying to export PO Lines that have a slash ("/") in their name, Alma tries to create the file with the PO Line number in the file name. This causes the export process to fail. This has been resolved by replacing the slash with "-" for the file name of the export.
    • July 2021 Administration and Infrastructure SF: 00808430 URM-136242
      Updating the password from Primo VE without entering the old password used to display a success message without actually updating the user password. This was fixed and an error message is now displayed.
    • July 2021 Administration and Infrastructure SF: 00886503 00723941 00938182 00833885 00939745 00912870 00721952 00666833 URM-141524
      When trying to add or delete a service unit from a receiving operator, an error message was displayed. This was fixed.
    • July 2021 Administration and Infrastructure SF: 00920283 00808876 URM-139638
      Alma continued to send emails to BCC address after BCC was disabled in letters. This was fixed. CC and BCC labels work now in any letter where they existed (previously worked only for some), and are turned on/off according to their 'enabled' status.
    • July 2021 Administration and Infrastructure SF: 00884328 URM-141066
      The Job Event Details page in some cases displayed an unexpected title. This was fixed.
    • July 2021 Administration and Infrastructure SF: 00910041 URM-147894
      Monitor Requests & Item Processes page: Active requests were not visible in the German interface. This was fixed.
    • July 2021 Administration and Infrastructure SF: 00938771 URM-149791
      Some image files were not displayed properly in the Alma Viewer in low resolution screens such as with laptops. This was fixed.
    • July 2021 Administration and Infrastructure SF: 00941975 URM-150137
      A PDF did not open with the correct page number in the Alma Viewer when pdf.js was enabled. This was fixed.
    • July 2021 Analytics SF: 00919852 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 2021 Analytics SF: 00895798 00933448 00920440 00901848 URM-141445
      The Analytics report for DARA for the Identical system control number displayed an error when run in the Network Zone. This was fixed.
    • July 2021 Analytics SF: 00934006 URM-149712
      Electronic Collections that no longer have CDI information in Alma, still have this data showing in Alma Analytics. This was fixed.
    • July 2021 Analytics SF: 00918108 URM-151641
      When a renewal was done through Primo VE and not a circulation desk, analytics reports created with fields from Fulfillment > Renewal Circulation Desk did not display loan data properly. This was fixed.
    • July 2021 Analytics SF: 00923724 URM-151929
      The out-of-the-box report for SCONUL '4.1 Total unique loans with prompt by loan date (does not include in-house loans)' did not work properly. This was fixed.
    • July 2021 Analytics SF: 00953265 URM-152867
      The Event Date and Time field (System Events > Event Date) was not working properly. This was fixed.
    • July 2021 API SF: 00923160 URM-146735
      API GET request for holdings does not include the correct suppressed status if the holdings are suppressed on location level. This was fixed.
    • July 2021 API SF: 00889205 URM-146766
      The 'Update Item information' API was changing the 'Due Back By' date back by 1 day in some cases. This was fixed.
    • July 2021 API SF: 00940833 URM-151842
      When creating a user by API, the 'Created By' field in the contact information was populated with the default value of 'System'. This was fixed and it now has exl_api
    • July 2021 Fulfillment SF: 00909429 URM-144932
      Request_note not displaying complete note in automatic printing of Fulfillment Resource Request Slip Letter. This was fixed.
    • July 2021 Fulfillment SF: 00936299 00914803 00909681 URM-145020
      An end of term event that was configured at the institution level and indicates it was inherited by the library would not allow the library to select the event as a due date. This was fixed.
    • July 2021 Fulfillment SF: 00944817 URM-150561
      Library selected from configuration menu changes when using quick link created for 'Opening Hours'. This was fixed.
    • July 2021 Fulfillment SF: 00937292 URM-152851
      The Create Physical Item Work Orders job sometimes created requests even though the work order type/department did not support the item's library. These invalid requests caused errors when trying to handle the requests or edit the requested items. This was fixed.
    • July 2021 Fulfillment SF: 00933017 URM-149237
      Ampersands inside parse parameters were encoded before being written to the database even when the parse parameters came from the link value and when the parse parameter was not a URL. This was fixed.
    • July 2021 Fulfillment - Course Reserves SF: 00899257 URM-150130
      If the customer parameter course_restricted_bib_data_will_be_deleted was set to true, records that were marked as course restricted were sometimes not republished to primo after the course became inactive. This was fixed.
    • July 2021 Fulfillment – Resource Sharing SF: 00915116 00931453 URM-146831
      Whenever a lending request got rejected and a new one was created with the same External identifier (wrong behavior), the ship operation will fail to find the relevant request and the shipping interface page would lose some details as a result. This was fixed.
    • July 2021 Fulfillment – Resource Sharing SF: 00934172 00940126 URM-149074
      When a date needed by is added to a borrowing request (either from discovery or from Alma), it now appears in the borrowing request details even after the request was cancelled.
    • July 2021 Fulfillment – Resource Sharing SF: 00888187 URM-149422
      Primo's ILL request form did not translate the values in Level of Service list. This was fixed.
    • July 2021 Fulfillment – Resource Sharing SF: 00943624 00940200 URM-150322
      In case of blocked Primo's Blank ILL request, the error message 'Resource sharing request service is not available' wasn't displayed. This was fixed.
    • July 2021 Fulfillment – Resource Sharing SF: 00924832 URM-150539
      When sending an ISO Request message to the lender, the 'Publication Date' was not sent for customers using registryId UNIMARC. This was fixed.
    • July 2021 Fulfillment – Resource Sharing SF: 00929537 URM-151471
      The 'Send Overdue Message' to Resource Sharing Borrowing Partner job did not send the messages to partners of profile type ISO18626. This was fixed.
    • July 2021 Resource Management SF: 923897 URM-149582
      "If an e-resource had an Available For setting for an Inventory Network Group that was a non-Alma institution, the AF settings showed as blank in the Network search. This was fixed.
    • July 2021 Resource Management SF: 00921919 URM-148021
      In some cases the Create Physical Item Work Orders job created bad requests. These bad requests caused errors when trying to update the requested items. The job was fixed.
    • July 2021 Resource Management SF: 00934052 00953100 00947354 URM-149993
      When the customer parameter 'include_subfields_delimiter_in_analytics' was set to 'true', subfield $$9 was not extracted from Holdings fields (specified in the 'Holding Local Parameters for Reports' code table) to create fields local_param_1 to local_param_10 in the inventory_holding Analytics table. This was fixed.
    • July 2021 Resource Management SF: 00880386 00909951 00939649 URM-145742
      In some cases, when the title of the selected entity included special characters, its was displayed wrong. This was fixed.
    • July 2021 Resource Management SF: 00916090 URM-147985
      An error message 'The field description is mandatory, please enter the required data.” was displayed when creating PO Line from local portfolio. This was fixed. PO-Line creation was enabled in case of 'standalone' portfolio via portfolio list in All titles search result.
    • July 2021 Resource Management SF: 00903193 URM-149172
      Due to a gap between SFX and Alma, in some specific cases, OpenURL was returned with available services. This was fixed.
    • July 2021 Resource Management SF: 00918989 URM-149856
      The job 'Synchronize Changes from CZ' failed in some cases for some customers. This was fixed.
    • July 2021 Resource Management SF: 00899507 00899121 URM-150365
      The new fields PORTFOLIO_MODIFICATION_DATE and PORTFOLIO_CREATE_DATE created by Alma are now being used by Analytics.
    • July 2021 Resource Management SF: 00936366 URM-152093
      ETask Task status was not updated according to the selection of the customer. This was fixed.
    • July 2021 Resource Management SF: 00957184 00950030 00960244 00953865 00952236 00954849 00951296 00951658 URM-152864
      Vendor was sending a KBART File which Alma could not process due to the KBART file being incorrectly formatted. The parsing of KBART file by the AutoHoldings job was improved, so that there is a lesser chance of the job failing due to incorrect/corrupt fields in the vendor's KBART File.
    • July 2021 Resource Management SF: 00769625 00943176 URM-122501
      Clicking the 'Download EAD' button on a Top Level Collection did not work for collections with more than 1000 branches. This was fixed.
    • July 2021 Resource Management SF: 00938795 00951890 URM-152010
      A Collection that was linked to deposit profile that was already deleted could not be deleted. This was fixed.
    • July 2021 Resource Management SF: 00938120 URM-152171
      Collection Name and Description were not consistently translated. This was fixed.
    • July 2021 Resource Management SF: 00923768 00933207 URM-149652
      The Merge and Combine job did not check that Preferred record was not deleted. This was fixed. The job now makes sure that the primary record in each group from the input file is not deleted. If it is, the status of the group in the output file will be 'skipped', and the 'message' column will contain the following text: 'Primary record is deleted'. This fix is relevant also for Merge and Combine jobs done by the MD Import.
    • July 2021 Resource Management SF: 00583574 00744692 00504861 URM-90783
      Special Danish character written format (OE) was not searchable in Manage Patron Services’ automatic dropdown list, i.e. &#xF8; was searchable, but oe was not.
    • July 2021 Resource Management SF: 00906327 URM-145571
      The Country of Publication index was searchable by code only. This was fixed. The 'Country of publication' index was improved to suggest a list of countries' names. This will be deployed gradually, with the semi-annual indexing starting on the May release.
    • July 2021 Resource Management SF: 00927122 URM-150820
      Disconnection issues occurred in the middle of working in Alma. This was fixed
    • July 2021 Resource Management SF: 00868325 00915716 00889742 00937416 00889093 URM-136143
      Previewing records that failed to load for import data to Primo VE job threw a Java exception. This was fixed.
    • July 2021 Resource Management SF: 00859382 URM-139909
      Default material type for purchase requests wasn't changed according to the configuration screen. This was fixed.
    • July 2021 Resource Management SF: 00867286 00914567 URM-143198
      Custom CNAME permalinks were not resolving. This was fixed.
    • July 2021 Resource Management SF: 00907764 URM-143432
      Dublin Core record templates did not work when the dc:identifier had values with less than 18 characters. This was fixed.
    • July 2021 Resource Management SF: 00920532 URM-145926
      Primo VE: 'Search Inside' was missing when permalink was not for the English user interface. This was fixed.
    • July 2021 Resource Management SF: 00923728 00934733 00891635 00944985 00928363 00934427 URM-147702
      Digitization requests were created without a requester. This was fixed.
    • July 2021 Resource Management SF: 00923624 00927495 00927931 00950814 00944979 00936538 URM-148422
      Primo VE: Libraries and location facets occasionally were not translated. This was fixed.
    • July 2021 Resource Management SF: 00943029
      URM-150122The Links section was displayed although there were no links to display. This was fixed. 
    • July 2021 Resource Management SF: 00945385 URM-152180
      Primo VE: SAML authentication was not working for *.com.cn URL. This was fixed.
    • July 2021 Resource Management SF: 00887440 URM-138996
      MARC21 controlled field 008 holds the Place of publication in position 15-17 = 3 values. But the drop-down menu contains also the list of discontinued codes, identified by a hyphen preceding the first letter in the code string and 3 letters. When choosing this type of code and then open the field form editor again, this dropdown is empty. This was fixed - the hyphen removed from the discontinued codes with a hyphen and 3 letters, and '(old code)' added to the description of the code.
    • July 2021 Resource Management SF: 00941824 00926032 00932383 00929533 URM-136012
      New Metadata Editor: After opening the 'Field Information' pane, when clicking the editing pane of this field, the field became locked for editing. This was fixed.
    • July 2021 Resource Management SF: 00879570 00935615 URM-137739
      New Metadata Editor: When pressing F8 on an existing record, a new filed was added, but also a dropdown for the controlled vocabulary of the field in focus was displayed. This was fixed, and now the controlled vocabulary does not appear.
    • July 2021 Resource Management SF: 00903774 00907876 URM-142941
      New Metadata Editor: The cursor was thrown to the end of a field when the subfield delimiter was inserted in the middle of an existing Hebrew text line. This was fixed.
    • July 2021 Resource Management SF: 00950258 00899518 URM-143605
      New Metadata Editor: 'Go to' link popup for 856 remained on screen after removing the field. This was fixed.
    • July 2021 Resource Management SF: 00931596 00899170 00944137 00915630 URM-146975
      New Metadata Editor: On smaller screen resolutions, the 'Old Editor' Button sometimes was hidden. This was fixed.
    • July 2021 Resource Management SF: 00942108 00886923 URM-147415
      New Metadata Editor: Search Resources panel did not close after import. This was fixed.
    • July 2021 Resource Management SF: 00893239 00878145 00954155 00918532 00889118 00899065 00948517 00963558 URM-148545
      New Metadata Editor: After the user collapsed a record that was already saved, the Draft icon appeared for this record. This was fixed.
    • July 2021 Resource Management SF: 00934569 URM-149180
      New Metadata Editor: Ctrl+S removed directional characters. This was fixed.
    • July 2021 Resource Management SF: 00937212 00932552 00935222 URM-149188
      New Metadata Editor: In some cases, when opening a record for the first time, the performance was slow. This was improved.
    • July 2021 Resource Management SF: 00929957 URM-149644
      New Metadata Editor: For Network Zone records, users could not add more than one field by using F8. This was fixed.
    • July 2021 Resource Management SF: 00943642 URM-150357
      New Metadata Editor: Changing Cataloger Level suggestion was not sticky while editing the Record. This was fixed.
    • July 2021 Resource Management SF: 00952488 URM-152161
      Metadata Editor: Normalization Rule's 'Preview' action and the Indication Rule's 'Try It' action could not be used if the tested record was modified without saving. This was fixed.
    • July 2021 Resource Management SF: 00948986 URM-152457
      New Metadata Editor: Editing Actions > Add Alternate Graphic Representation menu item did not have a shortcut Alt+F1, instead pressing Alt+F1added alternate field. The was fixed.
    • July 2021 Resource Management SF: 00937623 URM-151568
      When editing a Community Zone record, for the 650 field second indicator 7, F3 was not returning results. This was fixed.
    • July 2021 Resource Management SF: 00867598 URM-139479
      SBN integration: there was an incorrect label for Fingerprint search and a missing filter option for filed 140. This was fixed.
    • July 2021 Resource Management SF: 00915919 00888285 URM-142924
      Added functionality to the SBN contribution code to check if the record in Alma has no originating system version. If there is no originating system version, the contribution is preceded by a call to retrieve the version from SBN before contributing. The fix requires setting the customer parameter temp_enable_sbn_null_version_fix to true (default value).
    • July 2021 Resource Management SF: 00941937 00948006 00952831 00956010 URM-152134
      The "Help for this page" link worked incorrectly for the new Metadata Editor (navigated to general Alma Help pages). This was fixed.
    • July 2021 Resource Management SF: 00922887 URM-149788
      Resources > Advanced Tools: The "Merge Records and Combine Inventory" link is now available only to users who have one of the following roles: Catalog Manager, Catalog Administrator, General System Administrator.
    • July 2021 Digital Resource Management SF: 00905167 URM-145516
      Sometimes in Primo, a digital service such as the Alma Viewer did not recognize a signed in user and displayed an access denied message. This was fixed.
    • July 2021 Digital Resource Management SF: 00933181 00959298 00952518 00951960 URM-150013
      Generation of digital file thumbnails timed out before it could finish. This was fixed.
    • July 2021 Digital Resource Management SF: 00943034 00891800 URM-150128
      Importing digital files larger than 5GB failed. This was fixed.
    • July 2021 Digital Resource Management SF: 00949818 URM-152113
      When opening the Alma Viewer configuration page, an error message appeared. This was fixed.
    • July 2021 Digital Resource Management SF: 00949903 URM-152658
      On the page that appears when selecting Add Representation for a digital title, the Upload option is selected, but the ability to upload files is grayed out. This was fixed.
    • July 2021 Digital Resource Management SF: 00920266 URM-152713
      When selecting the 'Group Representation Delivery Services by' option for View It (Configuration > Fulfillment > Discovery Interface Display Logic > Other Settings), it was not possible to change the Alma Viewer label. This was fixed.
    • June 2021 Analytics SF: 00892520 URM-141500
      When creating reports on physical item requests, sometimes the report was empty. This was fixed.
    • June 2021 Analytics SF: 00927515 URM-149445
      When running reports with a Material Type Description of 'Undefined', no results were displayed. This was fixed.
    • June 2021 Analytics SF: 00920187 URM-150641
      Fields from the Physical Items dimension were visible in the Purchase subject area. This was fixed.
    • June 2021 Analytics SF: 00700466 URM-148308
      Clicks to Bx recommendations were not counted in Analytics reports in the Link Resolver subject area after Direct Linking became active in Primo. This was fixed.
    • June 2021 Acquisitions SF: 00861383 URM-134737
      Library field was empty for Print book - Standing order in PO Line list Standing Order drawer. This was fixed.
    • June 2021 Acquisitions SF: 00921897 URM-147941
      When attempting to approve and order a purchase that links to a Deleted Bibliographic record - an oops error was displayed. This was fixed and now when the Purchase request is approved, a proper error message is displayed.
    • June 2021 Acquisitions SF: 00880216 00565025 00557072 URM-93346
      'ERP Number' field is not indexed by any existing index in the 'Order lines'. This was fixed by adding the ERP number to the order lines search.
    • June 2021 Acquisitions SF: 00922811 00889862 URM-140586
      If the PO Line is in status Auto Packaging and the resource is activated through E-Activation task list, the notification to the interested user was not sent. This was fixed.
    • June 2021 Acquisitions SF: 00882585 00805405 00891636 00895324 00891320 00836304 00800393 00891272 URM-124436
      Sushi Harvesting failed when created with an empty report. This was fixed.
    • June 2021 Acquisitions SF: 00913259 URM-149438
      Events subject area of Alma Analytics created reports where Acquisition Work Order was inaccurately associated with SUSHI Jobs. This was fixed.
    • June 2021 Acquisitions SF: 00904716 URM-149438
      EDI file names are not assigned unique names which can cause the file names to be overwritten. This was fixed. This fix handles Standard naming convention only.
    • June 2021 API SF: 00905645 URM-147075
      Returning of items was not possible when RFID was connected. This was fixed.
    • June 2021 API SF: 00835518 URM-129147
      Get PO-Line API returned inaccurate sum per fund in some cases. This was fixed.
    • June 2021 API SF: 00919349 URM-148948
      REST API Usage in Analytics wasn't up to date in some cases. This was fixed.
    • June 2021 Cloud Apps SF: 00930552 URM-148537
      Few fields (library, po_line, counter_platform, free & license) in the Update-collection API didn't support empty input. This was fixed.
    • June 2021 Fulfillment SF: 00681243 URM-111420
      If an item is still found in Acquisitions > Post Receiving Processing > Receiving Department Items but its Acquisition technical services request doesn't exist, the item can be loaned to patrons. When clicking on 'Done' for such an item in the Receiving Department Items list, the item status changes from loan to transit though the item stays on loan to the patron. This was fixed.
    • June 2021 Fulfillment SF: 00887339 URM-145798
      In specific scenarios, the barcode switched after several scan-in operations. This was fixed.
    • June 2021 Fulfillment SF: 00915251 URM-146956
      Accessing the Request Task Names at the Network, will now have the button for Save and Distribute.
    • June 2021 Fulfillment SF: 00928775 URM-147789
      The Request Queue screen was sometimes empty if the requested title had multiple holdings with an identical library, location and call number values. This was fixed.
    • June 2021 Fulfillment SF: 00913079 URM-149048
      Unable to send borrowing request a second time to once active partner after Remove and Recalculate Rota. This was fixed, conditionally that the Rota Assignment Rules actually changed the Rota.
    • June 2021 Fulfillment SF: 00935829 00928529 URM-149144
      Fixed the typo in Advanced Configuration Policy 'Is Requestable for Physical Resource Sharing'
    • June 2021 Fulfillment SF: 00813692 URM-150082
      When the interface language is traditional Chinese and the preferred language for the user is English, 'shortened_due_date' notifications are not being translated. This was fixed.
    • June 2021 Fulfillment SF: 00792155 URM-122378
      The delayed Place on Hold Shelf letters was previously attached by System. This was fixed and this will now be written on the operator who made the triggering operation.
    • June 2021 Fulfillment SF: 00909522 URM-148170
      When clicking Done in Item in the department when the PO Line has Interested users, an error was displayed. This was fixed
    • June 2021 Fulfillment SF: 00915832 URM-150012
      From now on, every time the approval requests list is opened from the task list widget, previous search conditions and filters will not take effect and the whole list will be loaded.
    • June 2021 Fulfillment SF: 00950922 URM-151809
      Availability calculation did not work for reading rooms. This is now fixed.
    • June 2021 Fulfillment - Resource Sharing SF: 00798500 00657835 URM-113568
      Lending requests with the following statuses are now able to perform check in action from UI:
      - Overdue
      - Recalled
      - Damaged
      - Lost
      - Lost and fee communicated
    • June 2021 Fulfillment - Resource Sharing SF: 00898321 URM-147114
      When a borrowing request for a non-physical format was received in a different format as physical, the return row action was not visible so it was not possible to return it. This was fixed.
    • June 2021 Fulfillment - Resource Sharing SF: 00791076 URM-147114
      Start Page and End Page are now mapped to the Pagination ISO field between partners when 'Pages' field is empty in borrowing requests.
    • June 2021 Resource Management SF: 00912602 URM-149154
      Items Creation Policy has been added to the Update Inventory profile by mistake. This was fixed.
    • June 2021 Resource Management SF: 00570510 00925192 00883455 URM-94316
      Add Physical item > Holdings Type = Existing: 1) If the selected record held only locations out of the user's physical inventory role scope, an OOPS message popped up. 2) If the selected record held both scoped and unscoped locations, the location dropdown was not populated with the allowed locations. These issues were fixed.
    • June 2021 Resource Management SF: 00911896 00902000 URM-143629
      In some cases, an incorrect number of related holdings records was displayed in the results of a 'Physical Titles' search. This was corrected.
    • June 2021 Resource Management SF: 00915917 URM-144275
      When Resources > Add Physical Item > Choose Holdings Type > Existing, the Physical Material Type customized definitions were not taken into consideration: not active entries appeared; for non-English interfaces, the translated values did not appear. This was fixed.
    • June 2021 Resource Management SF: 00926074 URM-149766
      Holdings record could not be deleted when the holdings list was filtered. This was fixed.
    • June 2021 Resource Management SF: 934292 URM-145163
      Indexing problems with Proquest DDA integration profile set-up. This was fixed by deploying the Handle Bibs With No MD Representation SP Job.
    • June 2021 Resource Management SF: 00921421 URM-149956
      OpenURL was empty in the Link Resolver Usage. This was fixed.
    • June 2021 Resource Management SF: 00806754 00901610 URM-128299
      Directional characters were added automatically by the system and published, preventing the exact phrase to be found in Primo. This was fixed.
    • June 2021 Resource Management SF: 00895129 URM-144704
      The CP 'Cataloging_level_user_preferences' was not effective to record the last selected Cataloger Level between network and local records. This was fixed.
    • June 2021 Resource Management SF: 00914895 00916249 URM-144978
      Profiles for Contribute Record to Central Catalog were missing when opening the record directly in new Metadata Editor. This was fixed
    • June 2021 Resource Management SF: 00854512 00798909 00911883 00928358 URM-123421
      New Metadata Editor: When the user pressing F3 and clicking on 'Headings from bibliographic records' tab for the searching, the response time is slow. This was fixed.
    • June 2021 Resource Management SF: 00926033 00947296 URM-144661
      New Metadata Editor: Many users experienced slowness in the new MDE the first time it was opened. There was no clear indication of when the loading was complete, so users got used to pressing buttons over and over until 'it started working'. To give a clear sense of the loading time, we added a loading blocker until the MDE completes loading the first time.
    • June 2021 Resource Management SF: 00949955 00939703 00913318 URM-145214
      New Metadata Editor: Pushed records not showed Local Extensions fields when pushed from Network Zone search. This was fixed.
    • June 2021 Resource Management SF: 00918427 URM-145725
      New Metadata Editor: Adding a record to the editing list for linked Authority records did not cause the record to be added to the Navigation list. This was fixed.
    • June 2021 Resource Management SF: 00934153 00934184 00918605 00926130 URM-147517
      New Metadata Editor: Shared templates could be modified by any cataloger, not only by 'Cataloger Extended'. This was fixed.
    • June 2021 Resource Management SF: 00940763 00927154 00942837 URM-148712
      New Metadata Editor: View Related Data / Add Inventory / Order menus were unavailable when the record was opened in View mode, when edited by another cataloger. This was fixed.
    • June 2021 Resource Management SF: 00934511 URM-148880
      New Metadata Editor: An internal error occurred when automatically reloading a record from the Central Catalog. This was fixed.
    • June 2021 Resource Management SF: 00919056 00942590 00935037 00924664 00942038 URM-149162
      New Metadata Editor: In the German environment, the cataloger level on GND authorities was not displayed at all. This was fixed.
    • June 2021 Resource Management SF: 00923181 00934036 URM-149163
      New Metadata Editor: After enabling network authority templates (that this network authority vocabulary managed only local) in the 'Template display configuration' screen, the authority templates were not available in the 'New' menu. This was fixed.
    • June 2021 Resource Management SF: 00926030 URM-149306
      New Metadata Editor: When opening two records, and clicking 'Field Information' on one of the records, the second record moved to the left, but the title of the record belonged to the second record. This was fixed.
    • June 2021 Resource Management SF: 00936734 00930982 URM-149337
      New Metadata Editor: In some cases, when editing a Network Zone record, the record opened in the Metadata Editor with missing information in the record's header and did not appear in the records list. This was fixed.
    • June 2021 Resource Management SF: 00937360 00952384 00956008 00935505 00955321 URM-149399
      New Metadata Editor: When a record was opened on the left pane and a rule on the right pane, and the user clicked Preview the rule > back > Made changes > clicking the 'Save' button, nothing happened. This was fixed.
    • June 2021 Resource Management SF: 00949152 00942725 00956089 00940930 00940624 00945177 00937983 00937085 00945742 00944300 00933231 00934137 00934932 00957777 URM-149409
      New Metadata Editor: When the records list was unpinned, and there were two presenters in Split mode when clicking on action that collapsed the left presenter, the right presenter extended to the right side. The was fixed.
    • June 2021 Resource Management SF: 00944389 00926542 URM-149436
      New Metadata Editor: When opening a record and clicking the 'i' icon, modification appeared to be by the current user at the time of opening the record. This was fixed.
    • June 2021 Resource Management SF: 00937112 URM-149848
      New Metadata Editor: After closing the right editing pane in split mode, the focus remained on the registry list of the record that was closed instead of moving to the registry list of the record that remained open in the Navigation pane. This was fixed.
    • June 2021 Resource Management SF: 00953449 URM-152230
      New Metadata Editor: It was unable to duplicate CZ Authorities. This was fixed.
    • June 2021 Resource Management SF: 00930913 00854790 URM-133810
      New Metadata Editor: 'Push selected records to Metadata Editor' did not consider locking time. This was fixed.
    • June 2021 Resource Management SF: 00943710 00942268 URM-141134
      New Metadata Editor: The Order button did not work for a specific record (that contained ':' character). This was fixed.
    • June 2021 Resource Management SF: 00920239 00919043 00939486 00907495 URM-142889
      New Metadata Editor: Templates with ':' in the text were wrongly parsed, and failed record creation from the template. This was fixed
    • June 2021 Resource Management SF: 00928965 00939485 00919106 00907500 URM-143639
      New Metadata Editor: Community templates that were enabled via the Templates display configuration did not appear in the 'New' menu after log out. This was fixed.
    • June 2021 Resource Management SF: 00912542 00923265 URM-149532
      After selecting 'Copy to Catalog' from a Community Zone record, the 'Search Resources' option was still grayed out. This was fixed
    • June 2021 Resource Management SF: 00904630 00886025 00943926 URM-137158
      New Metadata Editor: User could not add a local extension or inventory to Network Zone record with a higher cataloging level. This was fixed.
    • June 2021 Resource Management SF: 00890003 00940854 URM-140136
      New Metadata Editor: Community Zone and Network Zone records did not show the Suppressed icon. This was fixed.
    • June 2021 Resource Management SF: 00929118 URM-147887
      New Metadata Editor: When editing a data field that contained Hebrew/Arabic characters, the cursor was not displayed well. This was fixed.
    • June 2021 Resource Management SF: 00927543 URM-149685
      For NLI authorities, when external authority equals 50 and user cataloger level equals 20 in the external authorities mapping table, we got an error while trying to save the authority. This was fixed.
    • June 2021 Resource Management SF: 00947283 00916325 URM-146597
      New Metadata Editor: When a record was created from a template that contained a field 990 $$9 local, the local indication was not displayed. This was fixed.
    • June 2021 Resource Management SF: 00952454 URM-152148
      The user couldn't create an NZ auth record from the shared NZ template. this was fixed
    • June 2021 Resource Management SF: 00826608 URM-127992
      It was not possible to delete an authority record. This was fixed.
    • June 2021 Resource Management SF: 00893019 URM-142329
      New Metadata Editor: In the Editing Records menu, the 'Reload Record From Central Catalog' option was mistakenly disabled for authority records. This was fixed.
    • June 2021 Resource Management SF: 00904877 URM-142549
      When localizing SBN authority records of type Titoli uniformi (Uniform titles) and Titoli uniformi musica (Uniform music titles), the localization data returned from SBN was not added to the Alma record. This was fixed.
    • June 2021 Resource Management SF: 00947638 00861689 00907589 URM-142983
      SBN integration - The update of an Uniform title in SBN was producing an error 'Authority was contributed but failed on non-preferred fields'. This was fixed. If CATALOGER_LEVEL field does not exist (is null) in HFRUSER, the livello is taken from 980 field.
    • June 2021 Resource Management SF: 00911821 URM-148251
      Due to technical issues, some NZ publishing jobs completed with errors. This was fixed.
    • June 2021 Resource Management SF: 00928101 URM-149153
      Export Bibliographic Records job- When large sets were selected for the job, an error message was sometimes obtained on the 'Enter Task Parameters' screen. This was fixed.
    • June 2021 Resource Management SF: 00928103 URM-149589
      Change Physical Items job ignored condition for changing temporary location information. This was fixed.
    • June 2021 Resource Management SF: 00917105 URM-147419
      When going back from the Items list to search results, the list appeared from the first entry, not from the entry from which you opened the items list. This was fixed.
    • June 2021 Resource Management SF: 00927442 URM-149717
      Alma language facet showed code rather than description for ISO 639-1 language for Maori. This was fixed.
    • June 2021 Resource Management SF: 00921894 00926699 URM-149759
      New Alma Layout: When using Advanced Search immediately after sign-in and using “Enter” on the keyboard, it resulted in an empty screen. The results appeared only after performing a Simple Search, then the Advanced Search again. This was fixed.
    • June 2021 Resource Management SF: 00885542 URM-141625
      For some related items, Get It did not show that the related item was available. This was fixed. Matching related holdings and items by filters in bib record field 773$g (MARC21/KORMARC) or 461$v / 463$v (Unimarc/CNMARC): the bib filters are now checked against item data, only if the filter exists (there is a value in $g) AND there is data in the corresponding item field. Examples: Year filter - $g yr: 2015 - is checked only if an item has a value in the 'Chronology I' field; Volume filter - $g no: 1 ==> non-empty 'Enumeration A' field, or barcode; Issue Number filter - $g iss: 4 ==> non-empty 'Enumeration B' field; Part filter - $g pt: 5 ==> non-empty 'Enumeration C' field; Pages filter - $g p: 10-20 ==> non-empty 'Pages' field. Notes: (1) Filters are taken into account only when the customer parameter 'display_specific_related_items' is set to 'true'. (2) If no specific match is found according to the defined filters, no filtering can be done despite the customer parameter.
    • June 2021 Resource Management SF: 00751264 00931323 URM-126495
      Primo VE: Pickup location of other institution was missing under My Account > Requests. This was fixed.
    • June 2021 Resource Management SF: 00719307 00937156 URM-131866
      Renewal rejection status was not translated when renewing selected or all loans. This was fixed.
    • June 2021 Resource Management SF: 00908444 00858857 00902088 00837461 00905807 00792784 URM-134499
      Duplicate items appeared in PrimoVE Collection Discovery. This was fixed.
    • June 2021 Resource Management SF: 00723486 URM-138676
      Primo VE: the user interface prevented semi-colon to be displayed in the Brief Record Display. This was fixed.
    • June 2021 Resource Management SF: 00859382 URM-139909
      Default material type for purchase requests wasn't changed according to the configuration screen. This was fixed.
    • June 2021 Resource Management SF: 00907254 URM-143516
      Full view details links occasionally referred to browse search. This was fixed.
    • June 2021 Resource Management SF: 00788605 URM-143771
      Primo VE>My Library Card: Overdue icon did not appear unless overdue records were on the list. This was fixed. If there is no alert in the response's loans, the system checks if the user has any overdue or due loans and according to that, it will be marked if it has an alert or not.
    • June 2021 Resource Management SF: 00891196 URM-144390
      Full Record Display - Get it - Borrow and Scan buttons did not have meaningful alternative text labels. This was fixed.
    • June 2021 Resource Management SF: 00918224 URM-146680
      NA91: Links from Alma to Primo Studio did not work. This was fixed.
    • June 2021 Resource Management SF: 00699854 00709884 URM-147545
      Accessibility: navigating Advanced Search with screen reader was confusing. This was fixed.
    • June 2021 Resource Management SF: 00708854 URM-147711
      Only 245 $$a $$b of the Request Title were shown in Primo > My Requests - PrimoVE. This was fixed.
    • June 2021 Resource Management SF: 00865162 00890338 00936863 URM-143371
      A new portfolio was added to the Community Zone, yet the portfolio was not linked to the electronic collection in the Institution Zone. This was fixed. This was fixed. If a portfolio is marked as deleted and then revived and marked as an update, while the portfolio is not activated in IZ, the portfolio will be localized.
    • June 2021 Digital Resource Management SF: 00883572 URM-148557
      Thumbnails and URL links did not appear in Primo for digital titles. This was fixed.
    • June 2021 Digital Resource Management SF: 00930300 00924748 URM-149383
      Digital repository and digital import profiles for Digital Commons were not able to harvest qualified DC. This was fixed.
    • June 2021 Digital Resource Management SF: 00924501 URM-150050
      The Export Handles job did not run on a MODS record. This was fixed.
    • June 2021 Digital Resource Management SF: 00934038 00945534 URM-149446
      New Metadata Editor: Alma Search Options Show only Collections After Linking Bib to Collection, Searching Shows we Remain in the 'Add Collection' Wizard. This was fixed.
    • June 2021 Administration and Infrastructure SF: 00936152 00881202 00939395 URM-141794
      New Metadata Editor: After a record was copied to Catalog in the right-side editor, the Merge and Combine menu was still grayed out. This was fixed.
    • June 2021 Administration and Infrastructure SF: 00942244 00908755 00928027 00953983 00940670 00937275 00936131 00935019 00908781 00933889 URM-143272
      New Metadata Editor: in Expand from Template, long template names are cut off. This was fixed by expanding the popup.
    • June 2021 Administration and Infrastructure SF: 00923628 URM-147507
      Advanced search for Statistical Note with a wildcard led to an empty page. This was fixed.
    • June 2021 Administration and Infrastructure SF: 00914399 URM-145315
      Itemized set creation from file: wrong format record at the input file caused the 'Add members to set' job to fail, without a clear indication about the wrong input. This was fixed; the wrong line will be indicated.
    • June 2021 Administration and Infrastructure SF: 00924518 URM-148563
      The access rights for concurrent users are not reset after a user logs out. This was fixed.
    • June 2021 Administration and Infrastructure SF: 00952048 00880425 URM-140982
      Previously, the Fines and Fees Report used the code from 'Workbench Payment Method'. Now the code uses the customized description from this table.
    • June 2021 Administration and Infrastructure SF: 00896831 00923094 URM-142361
      When a user that is defined as a requester of a Purchase Request is about to be deleted, an error message will now be displayed, 'The user is a requester of a purchase request and cannot be deleted'
    • June 2021 Administration and Infrastructure SF: 00909405 URM-149939
      Users are erroneously blocked from accessing links to digital files from the View It link. This was fixed.
    • May 2021 Acquisitions SF: 00711710 00912097 00897014 00744723 URM-119759
      The fund sum was calculated incorrectly when a discount was issued. This was fixed.
    • May 2021 Acquisitions SF: 00822860 00886965 URM-127538
      Resolved all errors that occurred during Network Zone record import when a Purchase Order was created with the customer parameter central_record_management = ENFORCE_NETWORK.
    • May 2021 Acquisitions SF: 00886172 URM-140939
      The OCLC Record Manager could not login to Alma if either the password or the institution code was shorter than 10 digits. This was fixed.
    • May 2021 Acquisitions SF: 00937976 00907331 00901294 00903410 00924058 00902453 00917207 00918145 00934322 00922500 00919193 00929176 00916696 00916900 00936170 00945025 00890474 00930744 00938045 00888675 00898818 00894997 00916738 00922362 00930802 00910841 00869615 00890390 00936306 00916697 00940440 00887889 00897309 00929108 00934475 00937347 00919842 00944351 00923465 00940831 00916016 00894552 00925020 00909082 00939768 00935659 00927833 URM-144911
      When users open a PO Line in View Mode and click the 'Edit' button, the PO Line is assigned to them no matter the PO Line status. When the user leaves the page without saving, the PO Line remains assigned to them without any possibility to release this assignment. This issue was fixed. Now only when the PO Line is in an assignable task list (i.e. InReview or Deferred) it will be assigned to this user.
    • May 2021 Acquisitions SF: 00905535 00896787 URM-146662
      'Query to requester' will be sent from the Email that is defined in the Letter configuration as the 'From Address'. If this is not defined or disabled, the logged in user's email will be used.
    • May 2021 Acquisitions SF: 00845021 00798482 00720149 00934417 URM-116236
      An issue occurred when all attached POLs are closed or cancelled, but the PO status is 'Sent'. This occurred when closing the last PO Line of a PO where at least one of the PO Lines is cancelled. This was fixed.
    • May 2021 Acquisitions SF: 00930308 00932320 URM-148529
      The search list from SOLR did not sort alphabetically. This was fixed.
    • May 2021 Acquisitions SF: 00895222 URM-142723
      Fund with 'no limits' cannot be added. This was fixed.
    • May 2021 Acquisitions SF: 00634314 00631919 URM-102268
      The default display status of received items in PO lines was 'Not Received'. This was fixed.
    • May 2021 Acquisitions SF: 00660809 URM-116080
      In a department with multiple printers, Alma always printed to the default printer instead of to the selected printer when using the Print Slip action in the Manage In Process Items page and when using the Print Interested Users List action in the Receive New Material page. This was fixed and now the correct printer is used.
    • May 2021 Acquisitions SF: 00831505 URM-134324
      Scanning an item belonging to a PO Line in Acquisitions did not set the PO Line to be in Receiving Workbench. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00834284 URM-129694
      When the pick up location is not at the item owner, the Hold Shelf Letter is sent without considering the Hold Shelf Delay. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00916717 URM-145573
      Patron Active Balance was, on occasion, inaccurate due to active fines with currency 'null'. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00915783 URM-145829
      When viewing fines and fees, if the list's sort order was by the Fine/Fee type column but the column contained values that were disabled in the Fine/Fee code table, an Oops error appeared and the list failed to load. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00329994 00345289 00355215 00504169 00798265 URM-66414
      The label for user ID in the User Details page was incorrectly displaying 'Primary Identifier' and not ID. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00925095 00869431 00375335 00793490 00619207 00548039 URM-68960
      The report events for the SIS job were showing 'succeeded to update users' and 'Succeeded to create users' with severity as 'Error'. This was fixed, the severity is now 'Information'.
    • May 2021 Administration and Infrastructure SF: 00805686 URM-125254
      Deleting a user identifier prevented a user from being indexed, but searching for the deleted identifier kept returning the user. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00817490 URM-126163
      Creating new Job Categories failed to save the category when an ampersand was used in their description. This was fixed by forcing the new Job Categories descriptions to be created without an ampersand.
    • May 2021 Administration and Infrastructure SF: 00854858 URM-133915
      User Manager Role was allowed to edit a library's contact info even though the General System Administrator Role was 'Read only'. This was fixed to consider only General System Administrator role for that matter.
    • May 2021 Administration and Infrastructure SF: 00881938 URM-141818
      Before the fix, the 'Add from Profiles' option in Analytics objects did not appear with the Analytics Administrator role. After the fix, The 'Add from Profiles' option in Analytics objects does appears for Analytics Administrator.
    • May 2021 Administration and Infrastructure SF: 00905553 URM-144910
      Occasionally when sorting, itemized sets of Users had issues moving between pages in the members list.
    • May 2021 Administration and Infrastructure SF: 00902871 URM-145133
      Refreshing a Linked User would set the current time and date to the Creation Date of the refreshed user. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00910453 URM-147028
      Occasionally, importing a large Excel file into a mapping table failed. This was fixed so that when there are more than 20 lines, the import phase is skipped.
    • May 2021 Administration and Infrastructure SF: 00889450 URM-139299
      The 'Copy' bubble did not properly copy backslashes. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00898037 URM-143530
      New Alma Layout: Offers autocompleted from incorrect search indexes. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00917055 00915833 00936201 00914743 URM-145160
      New shortcut Ctrl+Alt+C that opens the configuration menu was overlapping with the old shortcut to clear item returns. This was fixed. New shortcuts are triggered only if there are no old shortcuts.
    • May 2021 Administration and Infrastructure SF: 00938456 URM-149729
      New Alma layout: User details were not printed when printing out the Manage Patron Services page. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00904099 URM-144421
      In the Hold Shelf letter, the system notes were not translated for some languages. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00729272 URM-119785
      The Scheduled Jobs Status widget did not display the correct date. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00907804 URM-144548
      DARA Library Filter did not consider the Category Filter in some cases. This was fixed.
    • May 2021 Administration and Infrastructure SF: 00867416 URM-147222
      There was an inconsistent panel closure, with only Advanced Search requiring a direct click on the button. This is fixed.
    • May 2021 Analytics SF: 00896296 URM-145952
      There was a problem with deleting subscribers. To correct this, a new code table was created to be used by customers to configure subscribers.
    • May 2021 Analytics SF: 00909753 URM-147865
      There was an error when using PO Line Creation Date fields with PO Line Creation Date Filter (field). This has been fixed.
    • May 2021 Analytics SF: 00919386 URM-148383
      The aggregation rule for the MMS ID field was changed from Count Distinct to Sum and now returns correct results.
    • May 2021 API SF: 00825563 URM-129350
      The GET-Request API was missing an 'Additional Request ID'. This field (additional_id) has now been added.
    • May 2021 API SF: 00878633 URM-140911
      Using REST API to suppress an Institution Zone (IZ) record did not suppress them from the PrimoVE index of the Network Zone (NZ). This was fixed.
    • May 2021 API SF: 00897991 URM-143335
      When using the Update-Bib API to modify local fields on an Institution Zone (IZ) Bib linked to the Network Zone (NZ), the local fields were not indexed. This was fixed.
    • May 2021 API SF: 00921289 URM-146497
      The GET Invoice Lines API returned inaccurate amounts caused by rounding. This was fixed.
    • May 2021 API SF: 00913049 URM-147271
      When calling Get Job Instances in API for General Publishing in the Network Zone, the section “Counters” was empty. This was fixed.
    • May 2021 API SF: 00873063 URM-141935
      Create User API didn't validate statistic_category against the "User Statistical Categories" code-table. This was fixed.
    • May 2021 Fulfillment SF: 00918549 URM-146908
      Occasionally, items that went through a resource sharing process, the Due Date Reminders job did not process some loans due to redundant milliseconds in the loan's due dates. This was fixed by avoiding the milliseconds in the due dates.
    • May 2021 Fulfillment SF: 00921881 URM-147442
      An error occurred when returning an item with a work order that was set to 'Do not pick from shelf'. This was fixed.
    • May 2021 Fulfillment SF: 00618917 URM-106273
      The expired requests that were automatically cancelled by the Requests - Handle Expiration Step job did not incorporate a cancellation reason. This was fixed and now the cancellation reason for these requests is 'Request expired'.
    • May 2021 Fulfillment SF: 00665576 00871063 URM-109865
      Items with quotation marks in the item description field are not requestable via Primo. This was fixed.
    • May 2021 Fulfillment SF: 00857705 00889397 00896036 URM-137174
      The row action Print Slip in the Pickup from Shelf screen did not work as expected when there were multiple requests behind a single list entry. This was fixed.
    • May 2021 Fulfillment SF: 00917461 URM-147226
      Purchase Request form field length is extremely short and does not expand to make visible pre-filled or added metadata. This was resolved by changing the Requester note for PRIMO to be a text area.
    • May 2021 Fulfillment SF: 00941900 00942622 00944836 URM-150021
      Fulfillment network requests displayed incorrect values for the Held Since/Process Date fields. These fields were incorrectly filled with the values from the Held Until/Expiration Date fields. This was fixed.
    • May 2021 Fulfillment - Resource Sharing SF: 00902421 URM-41234
      The locate process search for an article author resulted in a locate failure. This was fixed, the author will not be part of the locate for article title.
    • May 2021 Fulfillment - Resource Sharing SF: 00910843 URM-144285
      A lending request received via ISO18626 with no publicationType in the message was created as an 'Article' by default. This was fixed, the default type for ISO18626 now is 'Book', either by sending '<publicationType>Book</publicationType>' or not sending the publicationType.
    • May 2021 Fulfillment - Resource Sharing SF: 00820765 URM-146191
      When a 'Ship Physically' request or a 'Move' request was created for a title with a single item the request was created on the item-level instead of on the title-level. As a result, if a new item was added to the title, the request was still attached to the old item even if the old item was not available. This was fixed.
    • May 2021 Fulfillment - Resource Sharing SF: 00902040 URM-141547
      Item call numbers should be added in the 'Signatur' field of SLNP shipped messages. If the item call number does not exist, the call number is taken from the holding.
    • May 2021 Resource Management SF: 00897491 URM-144931
      Inventory Network Groups with a comma in the name are not supported; an error message will now appear and prevent groups with commas in the name from being saved.
    • May 2021 Resource Management SF: 00864280 URM-134625
      It was not possible to save certain holdings records with Items/Holds linked to a specific bibliographic record. This was fixed.
    • May 2021 Resource Management SF: 00886083 URM-139871
      The 'Item Policy' drop-down list in the Physical Item Editor was not translated (i.e. all entries were only in English) in non-English interfaces. This was fixed. In addition, the list is now alphabetically sorted.
    • May 2021 Resource Management SF: 00939058 00934357 00932055 00910844 URM-147999
      New Metadata Editor: Selecting Relink to another bib from Physical Items list > Add holding > Add new holding > Minimize the new Metadata screen brought the user back to Physical Items list. This was fixed.
    • May 2021 Resource Management SF: 00897506 00900660 URM-141028
      In Export jobs, deleted records were processed and appeared in the report. This was fixed.
    • May 2021 Resource Management SF: 00937257 URM-150318
      User with Purchasing Operator / Purchasing Manager could not get the ability to dismiss all in CUTL page. This was fixed.
    • May 2021 Resource Management SF: 00922189 URM-146670
      Publishing platform job: Delivery URL did not use CNAME in URL. This was fixed.
    • May 2021 Resource Management SF: 00914396 URM-147414Publishing to Primo > Headings enrichment = yes > Multilingual authority > “lat” is published in $$9 (not as expected). This was fixed.
      To have a clear indication of the type of information that is published in each sub-field, the following will be done:
      The headings information (A descriptive value mapped in "Add Authority enrichment"- Value in Subfield '9') will be published in $$9 (as today).
      The language information will be published to Primo in $$L
    • May 2021 Resource Management SF: 00906774 URM-147961
      Network Publishing - Records with physical inventory and inactive representations showed 'online availability' in Primo if published from the NZ. This was fixed.
    • May 2021 Resource Management SF: 00840536 URM-133576
      The order of the list of collections in the Collection Editor was not alphanumerical. This was fixed.
    • May 2021 Resource Management SF: 00899156 URM-143969
      When running a normalization process on a set of records that contained a data issue, this cause the job to fail. This was fixed.
    • May 2021 Resource Management SF: 00918557 URM-145957
      Add Members to Set for Physical titles job was failing if the file contained OCLC numbers and identifiers starting with 'ocl'. This was fixed.
    • May 2021 Resource Management SF: 00881949 URM-138320
      When calling Alma via SRU/OAI in Dublin Core, dc:contributor and dc:creator subfields $$d and $$0 were attached to the name ($$a) without any space or subfield delimiter. This was fixed. A delimiter was added between subfields.
    • May 2021 Resource Management SF: 00705346 00795077 URM-114862
      General electronic services that use the rft.mms_id parameter in their URL template used the wrong MMS ID on dedupped records. This was fixed.
    • May 2021 Resource Management SF: 00712873 URM-118380
      The Local Fields Test dialog for normalization rules for search and facets did not work. This was fixed.
    • May 2021 Resource Management SF: 00843627 00756319 00755746 URM-123304
      Reordering the Open Access service did not work. This was fixed.
    • May 2021 Resource Management SF: 00896391 URM-141768
      Searching with a special character that is replaced in char conversion to empty (?-u3007, ?-u3005) caused an error and no results. This was fixed.
    • May 2021 Resource Management SF: 00758045 URM-142854
      Accessibility WCAG 2.0: Some skip links were not working with VoiceOver + Safari. This was fixed.
    • May 2021 Resource Management SF: 00915044 00895195 URM-142906
      Deleted Springer Auto Holdings eBooks were still appearing in Primo. This was fixed.
    • May 2021 Resource Management SF: 00904746 URM-143360
      CZ records appeared with NZ icon in CZ search in consortia members with DNZ. This was fixed. The NZ icon is now hidden in this case.
    • May 2021 Resource Management SF: 00910383 00919461 URM-143366
      Pickup location defaulting to patron home institution did not work in Primo VE. This was fixed. The 'ful_network_default_pickup_inst' business logic was implemented when getting the request form (title and item level). If the CP is 'local', the item owner will be the default institution. If the CP is 'patron', the patron source institution will be the default institution. In all other cases (including 'blank') the field will be blank.
    • May 2021 Resource Management SF: 00886544 URM-146542
      Primo VE: Availability information was missing, delivery failed for records in Everything scope due to delivery ID request/response mismatch. This was fixed.
    • May 2021 Resource Management SF: 00754741 URM-146959
      The condition of 008(21) for Journals was not lowercase. This was fixed. The condition was changed to lowercase (008(21) <> l|m|d|w).
    • May 2021 Resource Management SF: 00921715 URM-147157
      Primo VE - SLSP - there were some typos in discovery OTB labels. This was fixed.
    • May 2021 Resource Management SF: 00521993 00897379 URM-127481
      When a record created by the system ('Ex Libris') is updated by a user, the value in 'created by' changes to this user. This was fixed.
    • May 2021 Resource Management SF: 00868820 00918474 00934279 URM-136728
      New Metadata Editor: The 'Add Holdings' button was not working for a user with a lower cataloger level than the record's in a specific scenario. This was fixed.
    • May 2021 Resource Management SF: 00928237 URM-137063
      New Metadata Editor: Insert Directional Characters (RTL) - the text moved left, but the cursor stayed right. This was fixed.
    • May 2021 Resource Management SF: 00878099 URM-137838
      New Metadata Editor: 'Modified By' info for Community Zone records displayed user username and the institution code, instead of displaying only the institution code. This was fixed.
    • May 2021 Resource Management SF: 00915219 00879196 URM-139131
      New Metadata Editor: 'Error while validating data with profile' appeared after adding a portfolio to an Network Zone/Community Zone-linked record. This was fixed.
    • May 2021 Resource Management SF: 00881119 00885375 00882482 00888623 URM-139843
      New Metadata Editor: The new local record created from the 'Copy to Catalog' action retained Cataloger Level from the network record. This was fixed. The local record will get the minimum Cataloger Level value '00', which will allow the staff catalogers to work on the record.
    • May 2021 Resource Management SF: 00898199 00935704 URM-141941
      New Metadata Editor: Duplicate record menu option was erroneously available for Community Zone records. This was fixed. Now the menu does not include the Duplicate record option. &nbsp;
    • May 2021 Resource Management SF: 00933831 00938140 00936752 00914923 URM-142302
      New Metadata Editor: the 'Add Local Extension' option was missing in single institution for Community Zone records. This was fixed.
    • May 2021 Resource Management SF: 00903774 00907876 URM-142941
      New Metadata Editor: The cursor was thrown to the end of a field when subfield delimiter was inserted in the middle of an existing Hebrew text line. This was fixed.
    • May 2021 Resource Management SF: 00893034 URM-144822
      New Metadata Editor: When searching external resources, Search Resources > SBN > “Header information not defined for this presenter” appeared in the results pane. This was fixed.
    • May 2021 Resource Management SF: 00915392 URM-145176
      New Metadata Editor: Records list > information popup upon hover on a record: the title was center-aligned to both margins. This was fixed.
    • May 2021 Resource Management SF: 00793741 URM-146748
      New Metadata Editor: Editing an holding record with 853 field and using the MARC21 Expand Holding By 863/4/5 Task in some cases caused the Save Record action to fail. This was fixed.
    • May 2021 Resource Management SF: 00917416 URM-147236
      New Metadata Editor: In some institutions, when entering the new Metadata Editor from the Alma menu, sometimes the 'Old Editor' button did not appear in an accessible place. This was fixed.
    • May 2021 Resource Management SF: 00934825 00905790 00929647 URM-136182
      New Metadata Editor: The shortcut for 'Add Alternate Graphic Representation' (Alt F1) and all its submenus (Alt F2, Alt F3, Alt F5. Alt F6) did not work. Also, the label description of the menu (Alt F1) was missing. This was fixed.
    • May 2021 Resource Management SF: 00910847 URM-147118
      New Metadata Editor: when entering or changing the location information in the holding tab 852 $$b, the field seemed to reload every change. This was fixed.
    • May 2021 Resource Management SF: 00919541 00934557 URM-147089
      New Metadata Editor: when creating GND record from the right-click action 'New Record From Template', the record was not created on the correct level (Community Zone). This was fixed.
    • May 2021 Resource Management SF: 00940760 00499589 00917364 URM-88916
      Editing a MARC 21 bib record in the MD editor with $$j in x11 (111 611 711 811) field broke the link to the authority. The was fixed. Broken links will be fixed gradually with the May semi-annual indexing.
    • May 2021 Resource Management SF: 00901321 URM-143343
      MARC bib records didn't use the 1st indicator for tag 130 for the non-filing characters of UNIFORM TITLE. This was fixed. This will be deployed gradually, with the semi-annual indexing starting on the May release.
    • May 2021 Resource Management SF: 00912205 URM-144898
      For 830 Bib Fields, the headings links behaves exactly as in 6XX regarding subdivisions – incorrectly, because 830 does not have subdivisions. Subfield $x in 830 should behave as $v. The issue was fixed. For already existing records, the links will be fixed by the semi-annual indexing, which starts in May.
    • May 2021 Resource Management SF: 00915918 URM-119441
      GND records with a higher cataloging level can be pushed to the MD Editor by users with lower cataloging permissions.. This was fixed. Now user's cataloger level is compared against the record's cataloger level before pushing record to new MD Editor.
    • May 2021 Resource Management SF: 00867145 URM-136607
      The field 312 was not being converted to the NoteLegame field in SBNMARC and was not being sent to SBN. This was fixed.
    • May 2021 Resource Management SF: 00890091 URM-142914
      The field 311 was not being converted to the NoteLegame field in SBNMARC and was not being sent to SBN. This was fixed
    • May 2021 Resource Management SF: 00861689 00907589 URM-142983
      SBN integration - The update of an Uniform title in SBN was producing an error 'Authority was contributed but failed on non-preferred fields'. This was fixed. If CATALOGER_LEVEL field does not exists (is null) in HFRUSER, the livello is taken from 980 field.
    • May 2021 Resource Management SF: 00905342 URM-143927
      When managing location information in an SBN record, the merge rules from the SBN import profile were applied on the record. This was fixed. Bow When managing location information in an SBN record, only the 899 fields in the Alma record in updated, and no merge operation is executed.
    • May 2021 Digital Resource Management SF: 00851461 URM-133925
      The advanced search for digital files by file size did not work properly. This was fixed.
    • May 2021 Digital Resource Management SF: 00896287 URM-143818
      Searching for digital files with some search parameters resulted in an error. This was fixed.
    • May 2021 Digital Resource Management SF: 00916128 URM-146230
      The new Alma Viewer allowed copying from protected PDFs. This was fixed.
    • May 2021 Digital Resource Management SF: 00924845 URM-147245
      The MD import of MODS records failed in certain situations. This was fixed.
    • May 2021 Digital Resource Management SF: 00926774 URM-147492
      After the premium sandbox was refreshed, representations were not accessible. This was fixed.
    • May 2021 Digital Resource Management SF: 00937268 URM-149959
      When direct linking was enabled for digital services, the mashup ViewIt did not work properly for remote representation services. This was fixed.
    • April 2021 Resource Management SF: 00935058 URM-149159
      Staff search resulted in an Internal error in the French and German interface. This was fixed.
    • March 2021 Acquisitions SF: 00906472 URM-144834
      Update PO lines information job did not change the access model on the portfolio. This was fixed.
    • March 2021 Acquisitions SF: 00868295 00364446 URM-143871
      The task list widget located on Alma's Dashboard presents the user with a count on how many PO lines "In Review" are assigned/unassigned. The count presented next to each task now takes into account the user's role scope. In case the user's scope is not institutional and is associated with a specific library or libraries, the count in the task list will include only PO lines "In Review" that are owned by the libraries associated with the user's role scope.
    • March 2021 Acquisitions SF: 00364446 00868295 URM-72143
      The task 'Order Lines - review - unassigned' counts the number of unassigned order lines of the whole institution, instead of counting only the ones of the library in the user role scope. This was fixed."
    • March 2021 Acquisitions SF: 00788013 URM-123168
      In Alma, searching for (Order lines> Receiving notes> ???) does not retrieve any results. This issue is resolved by the move to SOLR.
    • March 2021 Acquisitions SF: 00887981 00507810 00794470 URM-125260
      Additional order with PO Line Type 'License Upgrade' did not close after the invoice is handled. This was fixed.
    • March 2021 Acquisitions SF: 00899232 URM-144656
      Creating an invoice from file failed on 'Thread Timeout' for large Excel files. This page was removed from the 'Thread Timeout' mechanism.
    • March 2021 Acquisitions SF: 00702904 URM-118805
      Attempting to delete a fund from summary fund displayed an error. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00704276 URM-113978
      Changing User Role from active to inactive, and vice versa, will be reflected on the Status Date of the user from now on.
    • March 2021 Administration and Infrastructure SF: 00755396 URM-120944
      User History used to have issues parsing User Notes changes, with regards to Pop up notes information. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00906039 00908904 00867187 00881322 00906725 00869782 URM-135597
      Time zone gap affected searching dates in users records. This was fixed by considering time zone offset into querying.
    • March 2021 Administration and Infrastructure SF: 00910453 URM-143970
      Importing records into a large mapping-table, such as Statistical Categories/Types, took very long causing the import to fail occasionally. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00506714 URM-90849
      In the View Files Details page of the Import Job, file names were truncated even when there was enough space in the column. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00887416 URM-138841
      New Layout: Patron Services - font weight of the right summary panel was different from the small-screen summary section. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00900091 URM-142297
      New Alma layout - User brief detail pop-up jumped and was cut off under Resource Request Monitoring. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00900614 URM-143226
      New Alma layout - Users that switched to the new UI were switched back to the old UI. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00920618 00912862 00909580 00870390 00922063 URM-143355
      New Alma layout: Long current location was not showing. This was changed to display cut names with 3 dots.
    • March 2021 Administration and Infrastructure SF: 00903423 URM-143647
      New Alma layout - User Card was covered by the right-hand side menu of the new layout. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00911162 URM-144658
      Sometimes not all the menus appeared in the configuration menu. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00891429 URM-145598
      New Alma layout - Trying to View Fine/Fee Receipt redirected to Homepage instead of Showing Receipt. This was fixed and the receipt now opens in new tab.
    • March 2021 Administration and Infrastructure SF: 00823191 URM-126891
      Users were unable to scroll past page one in iPad & iPhone Safari. This was fixed.
    • March 2021 Administration and Infrastructure SF: 00926492 URM-147407
      "Synchronize Changes from CZ" job was failing from 12.2.2021 onwards. This was fixed. The records will stay in 'PENDING' status in the cz_harvesting_log until the installation of Alma March release.
    • March 2021 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.
    • March 2021 Analytics SF: 00914679 00914687 URM-144854
      The shared institutional folder was missing for the institution, which caused an error when attempting to create an analytics object. This was fixed and the shared institution folder was added."
    • March 2021 API SF: 00822896 URM-127325
      'GET Bib API' when used to retrieve a Network-Zone record with the members' holdings did not retrieve them when PrimoVE was active. This was fixed.
    • March 2021 API SF: 00894458 URM-141466
      Retrieve Item API does not retrieve the permanent call number if the item is in a temporary location. The 'GET-Item API' now has a new field; [permanent_call_number], which holds the call number from the Holdings records the item relates to, even when in a temporary location."
    • March 2021 API SF: 00907944 URM-143350
      When the 'Get-item-by-barcode API' was used with the lang (language) parameter, the redirect did not work well. This was fixed.
    • March 2021 API SF: 00909390 URM-144694
      Update 'PO-Line API' failed when used with JSON payload and 'null' Library. This was fixed.
    • March 2021 API SF: 00889393 URM-145307
      Refresh User API failed when Birth Date or Purge Date were set to false in the 'Linked Account Shared Fields' Mapping Table. This was fixed.
    • March 2021 API SF: 00906954 URM-145450
      Retrieve all items for Bib record via API using the offset parameter retrieved the 1 item twice in subsequent requests. This was fixed.
    • March 2021 Digital Resource Management SF: 00892064 URM-144983
      Lengthy note text did not display properly in the description panel of the New Alma Viewer. The text would display with a horizontal scroll bar instead of fitting within the panel. This was fixed.
    • March 2021 Fulfillment SF: 00862489 00885081 URM-135270
      Records that had a publication date but not another date field resulted in the copyright rules calculation being incorrect. This was fixed.
    • March 2021 Fulfillment SF: 00863069 URM-142432
      When the Closed Library Due Date Management policy was set to 'Move to next open day (same hour)' or 'Move to previous open day (same hour)', the Fulfillment Configuration Utility displayed a wrong loan due date time if the due date fell on a closed day. This was fixed."
    • March 2021 Fulfillment SF: 00710582 00450138 00427397 00897572 00428296 00901044 00550228 URM-76291
      In the job report of a few detailed sections, the last character of the last barcode was truncated. This was fixed.
    • March 2021 Fulfillment SF: 00871339 00914212 00880895 00886568 00871297 00883938 00909389 00868465 00889681 00884590 URM-136157
      Multi-item titles with many title-level requests resulted in slow loading for loans/returns. This was fixed by implementing performance improvements for scanning in requested items.
    • March 2021 Fulfillment SF: 00892542 URM-139657
      Adding information to the job report: “Loans - Overdue and Lost Item” failed to handle an item when a comma as a decimal separator was used in the Replacement cost. This was fixed.
    • March 2021 Fulfillment SF: 00872391 URM-140711
      Personal delivery requests for blocked patrons were not removed from 'Pick From Shelf' after scan-in. This was fixed.
    • March 2021 Fulfillment SF: 00899192 URM-141167
      The number of requests under the item list in specific cases was incorrect. This was fixed.
    • March 2021 Fulfillment SF: 00911783 URM-143193
      The Overdue and Lost Loan Profile filtered the loans by the User Group at the time of the loan. This was fixed, and now the Overdue and Lost Loan Profiles filter the loans by the current User Group of the user.
    • March 2021 Fulfillment - Resource Sharing SF: 00898436 URM-142223
      Journal title was lost when converting Patron Digitization Request for an article to a Resource Sharing Request. This was fixed by placing the journal title in the matching field of the borrowing request.
    • March 2021 Fulfillment - Resource Sharing SF: 00888430 URM-143193
      The GES self ownership calculation ignored holding suppression. This was fixed. Items under suppressed holdings are now considered 'not available'.
    • March 2021 Resource Management SF: 00790058 URM-126107
      The GetIt tab displayed a filter for year volume and description when there was only one item, because the holdings record has an 866 subfield x. This was fixed.
    • March 2021 Resource Management SF: 00915555 URM-128238
      Primo VE GetIt was creating linked accounts from the logged-in institution, even if patrons were handled centrally in the Network Zone. Now, if patrons are managed centrally in NZ Primo VE Get It will create a user by copying the record from NZ, and not by creating a linked account from another IZ.
    • March 2021 Resource Management SF: 00886563 URM-143249
      Shelf report returned incorrect results in specific cases. This was fixed.
    • March 2021 Resource Management SF: 00891902 URM-144503
      While saving items with an empty barcode field OR barcode field that contained only space characters, the mechanism of generating barcode was not triggered. This was fixed.
    • March 2021 Resource Management SF: 00859471 00863221 URM-135637
      'Link to community' functionality deleted the 'Public access model'. This was fixed, will be available after the SP job for fixing the data will run.
    • March 2021 Resource Management SF: 00860401 00883140 URM-139573
      An encoding issue led to incorrect target URL for portfolios using parse params, where the parser was not Bulk::BULK and the parse param included a URL with a '&'. A fix was created, currently controlled by a customer parameter (temp_encode_amps_for_test_access). This customer parameter is set to false in the OTB and will be set to true and then removed altogether within the next few months.
    • March 2021 Resource Management SF: 00895108 URM-140172
      Portfolios with the same bib were not updated correctly. This was fixed.
    • March 2021 Resource Management SF: 00887725 00912880 URM-144698
      'Localize/Activate portfolios from CZ' was not working using the Chinese UI. This was fixed.
    • March 2021 Resource Management SF: 00914014 URM-144699
      Publisher and place of publication did not map as expected in portfolio loader. This was fixed.
    • March 2021 Resource Management SF: 00909677 00902594 URM-142892
      There were duplicate records in the publishing file for ZDB holdings. This was fixed.
    • March 2021 Resource Management SF: 00891926 URM-144665
      RSS Publishing: some details were written to the RSS file even if there were no published items. This was fixed.
    • March 2021 Resource Management SF: 00899227 URM-112673
      The collections list and the collections facet displayed the default language collection name and not the translation in the current institution language. This was fixed.
    • March 2021 Resource Management SF: 00902103 00923602 URM-142551
      Running the portfolio loader with the 'Add local portfolio' option selected created duplicate local portfolios when there was a large number of titles in the input file. A fix was created, currently controlled by a customer parameter (temp_skip_create_local_portfolios). This customer parameter is set to false in the OTB and will be set to true and then removed altogether within the next few months.
    • March 2021 Resource Management SF: 00812510 URM-134034
      Some ISO 20775 holdings responses violated the schema by not having at least one holding entry. This was fixed. When the record has no holding items, the return XML will not include the holdings tag(<holdings>).
    • March 2021 Resource Management SF: 00919082 URM-145912
      Configuring campuses and labels with a colon inside were breaking the Getit request form. This was fixed.
    • March 2021 Resource Management SF: 00893915 URM-142826
      When clicking on 'Online Access' from the search results in Primo, the ViewIt was opened and the viewer was attempting to open as a popup and was blocked. This was fixed. Direct linking logic for digital services was changed (and is now aligned to logic that works for electronic services). If direct linking is enabled for digital services - then the single/first digital service link is now directed automatically from the mashup, instead of opening a new tab.
    • March 2021 Resource Management SF: 00708854 URM-115643
      Only 245 $$a $$b of the Loaned Title are Shown in Primo > My Loans. This was fixed. The logic of patron circ action loan title is now aligned with Alma logic.
    • March 2021 Resource Management SF: 00829279 00905314 00848394 00877959 00896613 00838386 00829305 00870835 00836431 URM-130238
      For CZ items, there was an issue with the resource type based on index (database). This was fixed.
    • March 2021 Resource Management SF: 00837668 URM-132133
      Article OpenURL from vendor led to an ebook instead of the Primo services page. This was fixed.
    • March 2021 Resource Management SF: 00855591 00664935 URM-133255
      The ILL form Start page and End page were not populated as expected. This was fixed.
    • March 2021 Resource Management SF: 00797662 00830557 00887593 URM-136820
      Collection features displayed in Primo VE although the collection was suppressed in Alma. This was fixed.
    • March 2021 Resource Management SF: 00870241 URM-137186
      Location map code was missing from OTB and had no label. This was fixed. also, a tooltip was added to the button.
    • March 2021 Resource Management SF: 00884222 00871125 00910178 URM-137762
      Primo VE: Loan type dropdown was locked and the patron could not choose the loan period for the request. This was fixed. For title level requests, an empty option is added to the drop-down regardless of the CP (temp_getit_add_empty_default_option_to_request_attributes), but for item level requests an empty option is added, and this is controlled by a customer parameter.
    • March 2021 Resource Management SF: 00794498 URM-139202
      Primo VE: 'Dublin Core tag' selection ignored the 'Encoding Schema'.
    • March 2021 Resource Management SF: 00884291 URM-138353
      'Only on cross consortia searches' option for physical inventory inclusion for other members did not work. This was fixed.
    • March 2021 Resource Management SF: 00878657 00894599 00915806 00899511 00909458 URM-138356
      The order of fields configured in the Resource Sharing Form Customization was not reflected as expected. This was fixed.
    • March 2021 Resource Management SF: 00888898 URM-139168
      Errors were encountered during federation passive sign-out. This was fixed.
    • March 2021 Resource Management SF: 00911744 URM-140934
      Fixed a bug where manual registration for fulfillment network members didn't work.
    • March 2021 Resource Management SF: 00883587 00893730 URM-141469
      Link Resolver did not return Unpaywall links in the View-It of a Services Page if generated by Primo Citation Linker or Google Scholar. This was fixed.
    • March 2021 Resource Management SF: 00900895 00898470 URM-141538
      Resource sharing requests were not displayed in Primo VE. This was fixed.
    • March 2021 Resource Management SF: 00864018 URM-142358
      An improper search, which passed in CDI (and not in Solr), in the Blended tab, resulted in no facets. This was fixed.
    • March 2021 Resource Management SF: 00719733 URM-142850
      The 'opens in a new window' icon was not shown in the availability line in some cases and the text was not added to the tooltip. This was fixed.
    • March 2021 Resource Management SF: 00793848 URM-142852
      Some regions in the user account area did not comply with accessibility demands. This was fixed.
    • March 2021 Resource Management SF: 00861480 URM-143669
      Primo VE brief search results were not highlighted correctly. This was fixed.
    • March 2021 Resource Management SF: 00902407 URM-143388
      Alma - CDI Publishing job completed with errors. This was fixed.
    • March 2021 Resource Management SF: 00871404 URM-143499
      Electronic collection 'CDI search activation' field update filter showed incorrect information. This was fixed.
    • March 2021 Resource Management SF: 00902049 00854780 URM-133809
      New Metadata Editor: Pushing records to MDE caused a jump back to first results page. This was fixed.
    • March 2021 Resource Management SF: 00856950 URM-133949
      New Metadata Editor: 1. 'Filter List' tooltip was modified to 'Filter and Sort list' 2. The abbreviations 'Asc' and 'Desc' are written out in full (as in the translations).
    • March 2021 Resource Management SF: 00863437 URM-135031
      New Metadata Editor: In some cases, after starting the 'merge and combine' process, while waiting for the load to end, an error message appeared. This was fixed.
    • March 2021 Resource Management SF: 00881055 URM-137401
      New Metadata Editor: Delete option for CZ authority did not appear when a contributor had an extended role. This was fixed.
    • March 2021 Resource Management SF: 00894429 00886025 00925679 URM-140156
      When opening records that have a higher cataloger level via the 'Edit' button in the search results of record view, an external process was changing the original record. This was fixed.
    • March 2021 Resource Management SF: 00851829 URM-140417
      New Metadata Editor: In Google Chrome a black border was displayed around the fields. This border was overlying diacritics and made it impossible to distinguish them. This was fixed.
    • March 2021 Resource Management SF: 00895526 URM-141081
      New Metadata Editor: The language scripts for 'Alternate Graphic Representation' were not loaded in time and all relevant menu items did not display. This was fixed.
    • March 2021 Resource Management SF: 00879192 URM-141313
      New Metadata Editor: wrong behavior of the checkboxes in Authority Control Task List. This was fixed.
    • March 2021 Resource Management SF: 00898094 00884085 00894231 URM-141472
      New Metadata Editor: performing the ordering operation on a record did not release the record from the Metadata Editor. This was fixed.
    • March 2021 Resource Management SF: 00905923 00896907 URM-142979
      New Metadata Editor: F3 heading control did not work after using the 'Enhance The Record' tool or the 'Expand from Template' tool. Also, the binoculars icons for the linked headings disappeared. The issue was fixed.
    • March 2021 Resource Management SF: 00910235 URM-144939
      New Metadata Editor: Editing fixed fields via form > Edit > Exit form > the change was displayed only after clicking on the field. The issue was fixed.
    • March 2021 Resource Management SF: 00917761 00895003 URM-133826
      New Metadata Editor: Menu item 'Release Records of Another Cataloger' was added under 'Record actions' menu. When no record is opened, this item is active and visible.
    • March 2021 Resource Management SF: 00857085 URM-133111
      New Metadata Editor: when the user changed the description field under any rule properties, the change was not updated. The issue was fixed for the new Metadata Editor only.
    • March 2021 Resource Management SF: 00886849 00904210 00903372 00894940 00904093 URM-142954
      New Metadata Editor: Browse Bib Headings - some headings with browse_type = MARC_6XXNAME were not found under Subjects+6XX heading type. This was fixed.
    • March 2021 Resource Management SF: 00898314 URM-142532
      Metadata Import - Test Connection gave a success message even when the connection failed. This was fixed.
    • March 2021 Resource Management SF: 00883312 URM-140851
      Merge and Combined failed with an error message. This was fixed.
    • March 2021 Resource Management SF: 00898881 00899054 00898573 00897765 00898374 00902724 00897790 00898493 00900748 00899139 00898418 00897762 URM-140881
      In certain situations, the old Metadata Editor was not loading in Firefox. This was fixed.
    • March 2021 Resource Management SF: 00880820 URM-140964
      Resource Types 'Atlas - Physical' and 'Atlas - Electronic' was not supported for Serials (LDR pos 7 = s). This was fixed. The Resource Type for existing records will be recalculated during the semi-annual indexing planned for May.
    • March 2021 Resource Management SF: 00898957 00756587 URM-144354
      When you had a record with some ISSN fields (022, 775) and one of them was wrong, there was a warning message. When you clicked on this warning message, the first field was highlighted, although the wrong ISSN was in another field. The issue was fixed for ISSN and for the following other types: IAN, ISBN, ISMN, OtherStandardNumber, UPC.
    • March 2021 Resource Management SF: 00884938 URM-141023
      'Single match' in the import profile was not copied when copying the profile. This was fixed.
    • March 2021 Resource Management SF: 00904908 00907133 URM-145386
      Import job finished with 'File failed in Loading' error due to file extraction issue. This was fixed.
    • March 2021 Resource Management SF: 00841694 URM-130969
      SBN search view labels were changed.
    • March 2021 Resource Management SF: 00907589, 00861689 URM-142983
      SBN integration - The update of an Uniform title in SBN was producing an error "Authority was contributed but failed on non-preferred fields". This was fixed.
    • March 2021 Resource Management SF: 00860415 URM-143889
      A permissions error was received when viewing the CDI tab without an Electronic Inventory Operator Role or CDI Inventory Operator Role. This was fixed.
    • March 2021 Resource Management SF: 00841776 00859484 URM-132580
      Display Logic Rules aimed at hiding a specific service if any other service existed did not work. This was fixed.
    • February 2021 Acquisitions SF: 00863294 00895860 URM-136166
      Deleting a fund (other than the first fund) of a PO line with multiple funds causes a different fund to be deleted. This was fixed.
    • February 2021 Acquisitions SF: 00861831 URM-137086
      Sometimes multiple PO lines were autopackaged to one PO, although this was not configured. This was fixed.
    • February 2021 Acquisitions SF: 00883257 URM-141458
      The Access Model field was not visible for the Computer File type of PO Line, even though it is an electronic type. This was fixed.
    • February 2021 Acquisitions SF: 00907967 URM-143346
      A typo appeared in the confirmation message displayed when rejecting purchase requests. This was fixed.
    • February 2021 Acquisitions SF: 00886618 URM-142442
      When a purchase request for a new bibliographic record was matched to an existing record, the existing record was suppressed even though it had physical inventory. This was fixed.
    • February 2021 Acquisitions SF: 00533293 URM-132265
      The LOC (location) segment in the EDI order message for 'Print Book - Standing Order' for PO lines that had more than one item linking to them was not generated. This was fixed and now the LOC segment is displayed one per item.
    • February 2021 Acquisitions SF: 00860547
      Items in the In Process List disappear intermittently. The items are marked 'Done' and made available without the operator marking them done. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00861098 URM-133850
      When logging out of the New Alma Viewer, the file was still displayed in the viewer. This was fixed, and now 'Access Denied' is displayed after logging out.
    • February 2021 Administration and Infrastructure SF: 00890324 00914184 URM-139832
      Previously, Patrons loans repeat on the second page of results in the Network Activity tab, now it was fixed
    • February 2021 Administration and Infrastructure SF: 00904685 URM-143012
      The waive reasons in the User's Fines and Fees tab were always displayed in English, instead of the interface language. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00394245 00212343 URM-59039
      The Back button for the 'You do not have permission to access the requested page, please contact the system administrator for more information' error message did not work. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00895051 URM-140706
      User history did not include when a user block was added with an expiry date and the user block was deleted by the “Users - Remove Blocks” job. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00895671 00890756 URM-141275
      Institutions not using SIS could not update users with an API if they had been toggled from internal user to external user, due to the SIS_temp value placed in their external_id. This was fixed, and now the SIS_temp value does not block users from being updated with an API.
    • February 2021 Administration and Infrastructure SF: 00878502 URM-140151
      Article title was cut off in catalog record. Full title appears in search results and URL. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00894341 URM-140598
      The Public Access Model was not showing in the ViewIt. This was fixed. Public Access Model was added to the short context service list and the related context service list in ViewIt.
    • February 2021 Administration and Infrastructure SF: 00876914 URM-137166
      F3 and PTC are adding a non-Arabic comma (U+002C) to the bib record. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00790765 URM-125932
      Some images URLs did not work in user details. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00813692 00799792 00849283 URM-127312
      Shortened_due_date notifications were not being translated. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00872873 URM-140530
      ILL EMAIL TO USER could not be disabled. This was fixed. Sending general email to users will consider from now on 'ILL EMAIL TO USER' letter status
    • February 2021 Administration and Infrastructure SF: 00866926 URM-135821
      Previously, letter examples of 'Pz System Job Letter' were mixed into the letter examples of 'System Job Letter'. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00903100 00910509 00903035 URM-143832
      Configuring Ex Libris Secure FTP services from sandboxes did not work from some of the regions (outside of North America). This was fixed.
    • February 2021 Administration and Infrastructure SF: 00870391 00899904 URM-139834
      New Alma layout: On larger monitors or higher zoom levels, entered search terms may be obscured by the chosen search fields. This was fixed by adding a tooltip to fields and breaking the line inside the combo-box.
    • February 2021 Administration and Infrastructure SF: 00896297 URM-140770
      New Alma layout: After several searches, selecting a previous search opened the wrong search. This was fixed. Note: this is fixed only for new searches. Old searches with corrupted data still appear until the news will remove them
    • February 2021 Administration and Infrastructure SF: 00878750 URM-141321
      New Alma layout: The Copy function did not appear for Generate Tracking ID. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00899573 URM-142285
      New Alma Layout: Alma Display Density set to big font size led to the current location not showing. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00909559 URM-143263
      User Interface does not load if 'en' is disabled in 'Institution Languages' mapping table. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00895968 URM-143391
      Sometimes the first opening of Alma was very slow. The load time was improved.
    • February 2021 Administration and Infrastructure SF: 00910868 URM-143681
      New Alma layout: Recent pages widget gives connection error for a specific user. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00879518 URM-137720
      The description pane in Alma viewer was sometimes cut at the end - so you could see the last line partially. This was fixed.
    • February 2021 Administration and Infrastructure SF: 00898833 00907096 00905049 00911171 00890451 URM-139541
      There was an issue calculating the correct number of roles. This issue also effected pagination in the roles list. The way number of roles is retrieved was updated and the issue is now resolved.
    • February 2021 Analytics SF: 00890836 URM-142876
      The 'is equal' operator did not work for the Invoice - Approval field (Funds Expenditure > Invoice Line). This was fixed.
    • February 2021 Analytics SF: 00865446 URM-138732
      A report to identify the number of Loans, Renewals, and Returns for a certain library during a time period sometimes returns incorrect values. This was fixed.
    • February 2021 Analytics SF: 00892470 URM-140319
      Sort is not working properly for null values. This was fixed.
    • February 2021 Analytics SF: 00901499 URM-142575
      Combined reports were not working. This was fixed.
    • February 2021 Analytics SF: 00879950 URM-143138
      The Available for Group Members field (E-Inventory > Portfolio) was not populated when a cumulative field, such as No. of Portfolios (in Repository), was added to the report. This was fixed.
    • February 2021 API SF: 00878156 URM-137308
      When Webhook Integration Profile was configured to send JOB_END events in JSON format, some events had null values when processing Alma's internal jobs. To fix it, from now on, Alma's internal jobs will not be sent by Webhooks.
    • February 2021 API SF: 00888252 URM-141617
      Webhooks did not work for item updates when users ran the Update Holdings job. This was fixed.
    • February 2021 Fulfillment SF: 00874163 00862255 URM-134247
      If a patron created a personal delivery request but came to pick up the item instead of waiting for the item to be delivered to him, when the item was loaned to the patron who requested it, the loan was incorrectly recalled. This was fixed. Now the loan will not get recalled in this case.
    • February 2021 Fulfillment SF: 00866649 URM-136402
      The booking request row was removed from the Request Configuration mapping table.
    • February 2021 Fulfillment SF: 00880755 URM-139463
      The Work Order edit page now supports diacritics in the Name and Description fields.
    • February 2021 Fulfillment SF: 00800639 00900731 URM-142799
      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 details of the items within the list. This was fixed.
    • February 2021 Fulfillment SF: 00895051 URM-143466
      "When the Remove User Blocks job removed a block from a patron, it did not write a user history entry. This was fixed. If multiple blocks were removed, multiple history entries are recorded.
    • February 2021 Fulfillment SF: 00713110 URM-115220
      A performance improvement was added for the GetIt page.
    • February 2021 Fulfillment SF: 00583695 00799450 00608163 00869491 00863413 URM-97671
      When cancelling a request from the Scan In Interface, the cancellation reasons did not appear on the Cancel Request pop-up window. This was fixed.
    • February 2021 Fulfillment SF: 00881249 URM-140568
      On the Manage In Process Items page, sorting by in digitization departments did not work. This was fixed.
    • February 2021 Fulfillment SF: 00728356 URM-121667
      When an OpenURL request from Primo had no identifier, the genre was dissertation, and the source was Ebscohost, the genre was overwritten as unknown. This was fixed.
    • February 2021 Fulfillment SF: 00874200 URM-137569
      Previously, the Bulk Fine Waiving Job changed items in place to a Process Type of Lost and Paid. This was fixed. Now, when a loan comes from ILS_IMPORT_LOAN and has a return date, the process type is not changed to lost and paid but the appropriate fine of the loan is waived.
    • February 2021 Fulfillment SF: 00905509 00909065URM-142992
      Saving predicted item records became unresponsive for daily newspapers. This was fixed.
    • February 2021 Fulfillment URM-143831
      Downloading files created following a digitization request was not possible when the authentication was based on 'Login via Email'. It is now supported.
    • February 2021 Fulfillment - Resource Sharing SF: 00876528 URM-137702
      In some cases, local hold requests that were converted to AFN Resource Sharing Requests were paused in 'Ready to be sent' status due to missing IE in the locate process and were not sent to the partner. This was fixed.
    • February 2021 Fulfillment - Resource Sharing SF: 00889646 00889411 URM-139554
      'Convert to resource sharing request' action did not work fine for General Digitization request. This was fixed.
    • February 2021 Resource Management SF: 00805965 URM-129692
      Three missing resource types have been added to the Bibliographic Resource Type code table: 'Map - Microfiche', 'Map - Microfilm', and 'Map - Microopaque'. This enables Analytics to display the correct resource type for bibliographic records whose resource type is one of these.
    • February 2021 Resource Management SF: 00696528 URM-141734
      Analytics: the fields Public Note and Non-public note were extended to 4000 char.
    • February 2021 Resource Management SF: 00817006 00839465 00845500 00816831 00733823 URM-121863
      In CZ scope, search results for electronic collection displayed black house and 'Service is Not Available' message, when the service was available in the IZ. This was fixed.
    • February 2021 Resource Management SF: 00908388 00890294 00866622 00840479 00861928 URM-132697
      Parser parameters were not flattened as showed in the user interface. This was fixed.
    • February 2021 Resource Management SF: 00850610 URM-139733
      'Static URL' and 'Static URL (Override)' fields in electronic portfolio replaced '&' with '%26'. This was fixed.
    • February 2021 Resource Management SF: 00897506 00900660 URM-141028
      In Export jobs, deleted portfolios was were processed and appeared in the report. This was fixed.
    • February 2021 Resource Management SF: 00850217 URM-131764
      Fulltext was not extracted from a txt file. This was fixed.
    • February 2021 Resource Management SF: 00861520 URM-136432
      In the New Alma Viewer, the forward arrow did not work when viewing a digital PDF file. This was fixed.
    • February 2021 Resource Management SF: 00893553 URM-141372
      In the New Alma Viewer, the contents of MARC field 542 $f appeared in both the Copyrights and Notes fields. This was fixed so that now it appears only in the Copyrights field.
    • February 2021 Resource Management SF: 00900677 URM-143552
      The OAI Marc21 format was not available for the YouTube remote repository. This was fixed and it is now available.
    • February 2021 Resource Management SF: 00751804 URM-143619
      When publishing to Primo, publishing the fulltext service URL link into AVD subfield h did not work properly. This was fixed.
    • February 2021 Resource Management SF: 00887794 URM-142399
      Digital Inventory and Collection drawers were not displayed properly in All titles/ Digital titles in staff search result in case of improper data. This was fixed.
    • February 2021 Resource Management SF: 00873657 00894367 00900499 00905389 URM-140243
      Google Scholar publishing was running successfully and the institution was in the registration file, but Google was not harvesting the holdings. This was fixed. Access to NA91 DC from Google Scholar is now permitted.
    • February 2021 Resource Management SF: 00882370 URM-141074
      Publishing to Libraries Australia: in some cases, suppressed records were shown as deleted in the job's report, but they were not added to the output file of deleted records. This was fixed.
    • February 2021 Resource Management SF: 00904138 URM-141980
      MARC publishing profile allowed selecting XSL indication rules. This was fixed.
    • February 2021 Resource Management SF: 00891530 URM-142542
      Holdings availability was not displayed well in a specific configuration in classic Primo. This was fixed.
    • February 2021 Resource Management SF: 00895982 URM-143508
      Location codes were displaying in the RSS feeds despite the 'Display Location Name' option selected in the publishing profile. The was fixed.
    • February 2021 Resource Management SF: 00896253 URM-141376
      'Suppressed from CDI' collections appeared as deleted every run. This was fixed.
    • February 2021 Resource Management SF: 00886474 URM-139137
      A HTML tags was not closed in the output of Export URLs job. This was fixed.
    • February 2021 Resource Management SF: 00846681 00843157 00823943 00831843 00118238 URM-40982
      "In Electronic Collection search results, the “Available” facet was not counted correctly. This was fixed. For the fix to take effect, full inventory indexing is needed; therefore, this fix will apply in July 2021 (after the semi-annual indexing will be finished).
    • February 2021 Resource Management SF: 00850223 URM-133806
      Error in advanced search if the Options field was empty. This was fixed.
    • February 2021 Resource Management SF: 00881934 URM-141061
      In the Repository Search, item availability remained green even when no items were available. This was fixed.
    • February 2021 Resource Management SF: 00912042 00916458 00915439 URM-145068
      Clicking Other Details in search results automatically navigated to the top of the page. This was fixed.
    • February 2021 Resource Management SF: 00888709 00898819 URM-139296
      When a newly created user attempted to search external resources, the search would fail to execute without any error message. This was fixed.
    • February 2021 Resource Management SF: 00872544 URM-139478
      New Alma layout: Advanced Search dropped the first letter typed when searching for search indexes. This was fixed.
    • February 2021 Resource Management SF: 00884681 URM-138734
      SRU > searchRetrieve > blanks in pos. 0-4 of LDR (hash characters in Alma that are changed to blanks in SRU) are not correctly removed. This was fixed.
    • February 2021 Resource Management SF: 00857440 URM-136476
      Place code had 'xx' value for place code in Analytics although it had a correct value in Alma. This was fixed.
    • February 2021 Resource Management SF: 00884294 00899773 URM-139578
      New Metadata Editor: when the user viewed versions for a record and the number of version was greater than 7, scrolling to the last one was not possible. This was fixed.
    • February 2021 Resource Management SF: 00875776 URM-140696
      When adding a new field to a record and using Tab to navigate from indicators to field, the cursor was placed before the subfield delimiter, instead of skipping to after the subfield. This was fixed.
    • February 2021 Resource Management SF: 00897749 00902896 00897375 00905793 URM-140904
      New Metadata Editor: When editing a record in Firefox, the cursor overlapped characters or appeared at the end of a line with space before it. This was fixed.
    • February 2021 Resource Management SF: 00895714 00897104 URM-141271
      The Authority Control Task List disappeared after coming back from the new Metadata Editor. This was fixed.
    • February 2021 Resource Management SF: 00878300 00901559 00902634 URM-142546
      In the Metadata Editor, the View Related Data is corrupted after page 17 for a record with many relations. In some cases, incorrect amounts of related records were shown behind the host record's 'related records' link. This was fixed. In addition, up to 500 records are displayed when clicking on the Related Records number in the Repository search.
    • February 2021 Resource Management SF: 00902533 00910409 URM-141709
      New Metadata Editor: quick link menu not visible when doing actions in the new Metadata Editor. This was fixed.
    • February 2021 Resource Management SF: 00906465 URM-142688
      New Metadata Editor: when fonts were customized in Firefox, the icons were not displayed. The issue was fixed.
    • February 2021 Resource Management SF: 00895869 00899229 00896439 URM-140846
      New Metadata Editor: Users working in the new Metadata Editor were experiencing slow response and performance. This was fixed.
    • February 2021 Resource Management SF: 00889187 URM-139295
      In the Metadata Editor, template properties: User for 'Last updated by' was not updating. This was fixed.
    • February 2021 Resource Management SF: 00895642 00897892 00900165 00906401 URM-142246
      In the Metadata Editor, a partial linking indication appeared for full linking authorized fields, in some cases. This was fixed. The data will be fixed gradually during the February release by the system job 'Update Heading Partially Linked Info'.
    • February 2021 Resource Management SF: 00873528 URM-138471
      OAI Publishing MARC 500 and 260 tags to DC mapping was wrong. The 500 and 260 fields publishing was fixed to fit loc xsl.
    • February 2021 Resource Management SF: 00900616 00822981 URM-128455
      When saving an uncontributed SBN authority record in Alma, an authority heading was created with local originating system and id, and the authority heading was not removed when the authority record was contributed to SBN and a new authority heading was created. This was fixed. There may be a need for a data correction job to remove the 'orphaned' authority headings. Alternatively, they might be removed by re-indexing of authorities, if the existing authority headings are dropped.
    • February 2021 Resource Management SF: 00859815 URM-133823
      SBN: Authority alignment - several defects in handling of authority alignment results were fixed.
    • February 2021 Resource Management SF: 00899709 URM-141126
      When using 'Align Record Version with Central Catalog', the Alma record's fields were merged with the current SBN record's content, instead of only updating the Alma record's originating system version with the value from SBN. This was fixed. Alma now updates the record's originating system version without modifying record's fields or subfields.
    • February 2021 Resource Management SF: 00891438URM-143613
      In some cases, certain records that were updated by import from Sudoc were not published. This was fixed. 
    • January 2021 Acquisitions SF: 00843700 URM-132294
      When two interested users for a POL; one that has 'notify upon cancellation' and the other does not have this ticked, both users got the 'InterestedIn letter' after the cancellation of a POL. Now, only users with 'notify upon cancellation' get the letter upon cancellation. &nbsp;
    • January 2021 Acquisitions SF: 00871456 00751354 URM-135144
      When opening an unassigned tab of a purchase request, an error was displayed. This was fixed.
    • January 2021 Acquisitions SF: 00849674 URM-136708
      The Approved Format field in the Subject Area of Purchase Request was not populated when the purchase request was approved. This was fixed.
    • January 2021 Acquisitions SF: 00868116 00865167 00878278 00858821 URM-134221
      The Public Access Model field in ViewIt was not showing translations for languages other than English. This was fixed.
    • January 2021 Acquisitions SF: 00870518 00743020 URM-122870
      If more than one interested users were in the PO Line, the cancellation letter was sent multiple times (the number of emails per user was the number of the interested users). This was fixed,
    • January 2021 Acquisitions SF: 00788013 URM-123168
      This issue is resolved by the move to SOLR. SOLR search will be turned on to ALL customers in January 2021 release.
    • January 2021 Acquisitions SF: 00890369 URM-139910
      A 'Receiving note' was allowed to be added to an electronic PO Line via API. This enabled electronic resources to have 'Receiving notes' that cannot be seen or removed from Alma UI. This was fixed and the 'Receiving note' will only be added to Physical PO lines.
    • January 2021 Acquisitions SF: 00890295 00876774 00886289 URM-140608
      When relink holdings for a bib with POL, sometimes POL loses the bib description and becomes 'Missing Description'. This was fixed.
    • January 2021 Acquisitions SF: 00665548 URM-107561
      The ERP export using the Profile Invoice Payment job was taking too long to run. This was fixed.
    • January 2021 Acquisitions SF: 00668443 00733177 00668423 URM-108031
      Selecting 'Use prorata' makes Additional Charge invoice lines (99991 - 99994) disappear but their transactions remain when editing an existing invoice with Fund and Transaction. This was fixed and now when saving this change, the transactions are deleted.
    • January 2021 Acquisitions SF: 00729119 URM-123069
      When details of a license negotiation is set for a year that has more than 365 days (e.g. such as a leap year where there is 29 days in February), the license is considered as multi year by mistake and so the 'Price per year' is visible instead of Price. This was fixed.
    • January 2021 Acquisitions SF: 00583614 00887108 00569199 00692954 00609840 00578402 00708071 URM-95494
      In Electronic Activation task list when the user is in the tab 'Assigned to Others' and sorts the list by assigned to when navigating to the 'Unassigned' tab, an error message is displayed. This was fixed.
    • January 2021 Acquisitions SF: 00898267 URM-141530
      Clicking 'Done' in an electronic activation task for PO Lines with Interested users caused an error. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00858858 URM-139602
      When exporting a Fines and Fees Report, the exported file was generated in *.xls format and not *.xlsx. This has been fixed so that when the parameter 'export_xlsx_fines_fees_report' is enabled, the generated report file will be in *,xlsx format. When the parameter is disabled, *.xls format is generated.
    • January 2021 Administration and Infrastructure SF: 00809874 URM-129354
      Using the 'Forgot password - reset by email' flow did not work when there were two users in Alma with the same email address, even if one of the users was deleted. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00882824 URM-139961
      User Management Profile includes API roles that are irrelevant. These are now removed.
    • January 2021 Administration and Infrastructure SF: 00805971 00711764 00791173 URM-116637
      Error in 'Change Vendor in Order' job. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00850785 URM-138147
      When printing multiple slips from the Lending Resource Sharing Task List, only one slip printed. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00893768 URM-139989
      New Alma viewer using SAML patron authentication was not working as expected: user name was not displayed after login. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00876486 URM-140631
      Redundant 'Assign To' Letter was removed.
    • January 2021 Administration and Infrastructure SF: 00895541 URM-140348
      New Alma Layout: In non-English user interface, the 'Chat with Support' box was cut at the bottom. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00632715 URM-102051
      The Summary panel information popup got cut off sometimes. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00878215 00872145 00872081 00866925 URM-135167
      New Alma UI: 'Last updated from Community Zone' was missing from the Help menu. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00879056 URM-138407
      New MDEditor: new MDE was stuck in half screen mode. This was fixed
    • January 2021 Administration and Infrastructure SF: 00891717 URM-140051
      When adding subscribers to an Analytics report, you could add a user from pickup only once. In the next times, the search was not closed after selection. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00894240 URM-140157
      Summary panel information popup cut off in Loan Audit Trail. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00888153 00888161 URM-141124
      New Alma layout: using the web browser's Back button led to not would inadvertent execution of an operation again. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00875954 URM-141367
      In the New Layout, printers were sometimes forgotten after logging out and then logging back in. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00902118 URM-141656
      New Alma layout: Missing advanced search option in Manage Patron Services menu. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00899195 URM-141642
      In Alma Viewer, quick access mode, the video was too big and the control buttons were hidden. This was fixed.
    • January 2021 Administration and Infrastructure SF: 00867767 URM-141554
      The Link to Primo Studio for configuring Deposit UI didn't include 'Create Deposit' button. This was fixed.
    • January 2021 Analytics SF: 00860255 00880771 00861463 00862902 00871324 00859068 00869974 URM-135088
      Primo Analytics Widgets were not selectable in the 'Manage Widgets' function on the Alma homepage. This was fixed.
    • January 2021 Analytics SF: 00899763 00864592 00896095 00896915 URM-136264
      Data Visualization projects could not be saved to a shared folder. This was fixed.
    • January 2021 Analytics SF: 00881323 URM-139002
      An unexpected error occurred when the 'Holding Lifecycle' and 'Fund Information' attributes were used together. This was fixed.
    • January 2021 Analytics SF: 00894932 URM-140642
      In the Titles subject area of Analytics, the field 'Material Type code' was missing under the 'Bibliographic Details' folder. This was fixed.
    • January 2021 API SF: 00895019 00856980 URM-133109
      In some cases, using the update, 'User API' caused errors regarding a role's scope. This was fixed.
    • January 2021 API SF: 00887681 URM-140133
      Using the REST API to create a borrowing resource sharing request with “Requested Format: Digital” and “Requested Pickup Location: Personal Delivery: Work Address” didn't work. This was fixed.
    • January 2021 API SF: 00902402 URM-141690
      Updating 3M's RFID tags from within Alma wasn't possible for some tag-formats. It is now possible to configure specific Tag Format value in the RFID Integration Profile.
    • January 2021 Fulfillment SF: 00866057 00793104 URM-128188
      Auto-renewing loans for a patron record with an expiry date would send the patron a courtesy notification. The 'Notifications - Send Courtesy Notices and Handle Loan Renewals' Job Report marked these loans as 'loans not renewed' with the error message: 'The due date is already set to the renewed due date.' This has been fixed so that the Auto-Renewal job takes into consideration the current date and calculates if the library is open and if the patron's record doesn't expire before the new due date.
    • January 2021 Fulfillment SF: 00791477 00692174 URM-128313
      Very poor response times when using Fulfillment. To compensate, performance improvements have been implemented for loan item actions.
    • January 2021 Fulfillment SF: 00830987 00874018 00875133 URM-129720
      Performance improvements were done in the request recalculation process. This will improve the performance of circulation actions that trigger request recalculation such as loan/return/scan in, especially in cases where the scanned title has many items and many requests.
    • January 2021 Fulfillment SF: 00862489 00885081 URM-135270
      Previously, when a record had a publication date but not another date field - the copyright rules calculation was incorrect. This was fixed.
    • January 2021 Fulfillment SF: 00868459 URM-135820
      In a fulfillment network, if Reshelve without Transit rules were configured, the rules were sometimes incorrectly applied also in case of out-of-institution transit. As a result sometimes an error appeared when returning an item at another institution and no transit slip was printed. Now the Reshelve without Transit rules are only applied for inside institution transit and have no effect on out-of-institution transit.
    • January 2021 Fulfillment SF: 00876402 URM-141787
      In a fulfillment network, when scanning in an item from another institution to place it on the hold shelf, the printing of the slip failed if the item had a pop-up note or was magnetic. This was fixed.
    • January 2021 Fulfillment SF: 00845329 URM-130927
      Previously, a user with the Physical Inventory Operator role with a specific scope could edit physical inventory of a different library when accessing it from the Loans tab on the Manage Patron Services when clicking the item barcode. This was fixed.
    • January 2021 Fulfillment SF: 00900308 URM-141504
      Previously the Circulation DESK code field only accepted 10 characters. It is now possible to type code for circulation desks up to 20 characters.
    • January 2021 Fulfillment SF: 00825928 URM-129064
      Previously, Auto-renewals job renewed loans by one day more than usual (new due date was 8 days ahead instead of 7 days) for specific timezones due to moving to Daylight Saving Time. This is now fixed
    • January 2021 Fulfillment SF: 00817017 URM-126976
      The user note at the patron workbench for items on hold shelf counter was refined to filter out booking requests which were placed on hold shelf and their end time has expired. Requests tab indicator was fixed as well to omit these requests.
    • January 2021 Fulfillment SF: 00862302 URM-133943
      When printing Ful Resource Request Slip Letter in Non-English UI, the request type appears in English on the letter even though all other elements of the letter are in the correct language. The request type in the request slip letter is now translated.
    • January 2021 Fulfillment SF: 00883360 00892041 00880576 00892299 00884671 00881902 00886461 URM-138773
      If the On Shelf Request policy was set to 'No requesting from available holdings', local hold requests were incorrectly canceled when a shipped item was returned from a lending request. This is now fixed.
    • January 2021 Fulfillment SF: 00878425 URM-138910
      Remote Storage XML was missing locationCode for Full Chapter Digitization Requests. A new field was added in the exported XML for remote storage digitization requests. The field will now include the digitization department code.
    • January 2021 Fulfillment SF: 00894925 00860240 00890621 00889065 00864011 00758417 00866450 00870917 00867553 00888927 00881095 00863803 00876935 00879015 00885049 00871073 00860027 00880958 00853649 00884038 00886291 00876619 00876032 00852748 00897685 00881145 00828417 00876352 00868748 00891990 URM-138249
      An encoding issue with the '&' character separating two parse params for portfolios caused linking not to work with portfolios that had two or more parse params. This was fixed.
    • January 2021 Fulfillment SF: 00822239 URM-131360
      When the Activate/Deactivate Courses job activated a course, it automatically unsuppressed any suppressed bib records in the associated reading lists. Now the job will unsuppress the bib records of the activated courses only if the bib records are marked as course restricted. In addition, in the job's report, the list of unsuppressed records was sometimes incorrect. This was fixed.
    • January 2021 Fulfillment - Resource Sharing SF: 00870034 URM-135932
      When using the Get It resource sharing form in Chrome browser, if the user tried to enter an alternative mailing address for home delivery, the fields to enter this new address did not initially appear and the user had to toggle delivery methods back and forth for the fields to appear. This was fixed. The relevant fields now appear automatically when selecting the alternative address option.
    • January 2021 Fulfillment - Resource Sharing SF: 00868303 URM-136930
      The Resource Sharing Partner parameter 'Send ReturnInfo' did not update in IZ on the distribute job from the NZ. This was fixed.
    • January 2021 Fulfillment - Resource Sharing SF: 00903352 URM-142378
      Previously, when rejecting some lending requests, the staff received an Oops error message. This was fixed.
    • January 2021 Fulfillment - Resource Sharing SF: 00894754 URM-141368
      The locate process for the Lending Request fails if author initials are included in the request. This was fixed, the author initials will be sent in ISO protocol only when no author exists in the request.
    • January 2021 Resource Management SF: 00897326 URM-140704
      The field 'Code for RFID' in Organization Unit Details stopped allowing alpha-numeric values. This was fixed.
    • January 2021 Resource Management SF: 00874647 URM-137505
      Mashup uresolver: add HTML class tag surrounded the viewer service element
    • January 2021 Resource Management SF: 00890776 00890955 URM-139426
      Publishing with Linked Data enrichment: Authority URIs did not appear for fields with $$u and $$e. This was fixed.
    • January 2021 Resource Management SF: 00769625 URM-122501
      Clicking the 'Download EAD' button on a Top Level Collection did not work for collections with more than 1000 branches. This was fixed.
    • January 2021 Resource Management SF: 00892354 URM-140780
      Thumbnail Size Validation in Collection editor was incorrect - it limited uploading thumbnail image even if it was less than 100kb. This was fixed.
    • January 2021 Resource Management SF: 00899972 URM-141265
      Withdraw items job ran slowly. This was fixed.
    • January 2021 Resource Management SF: 00713586 00699791 URM-114341
      When setting the display fields to view interested users in PO Line list, the field was not added to the PO Line list. This was fixed.
    • January 2021 Resource Management SF: 00865972 URM-138649
      New layout > Search results > Expand drop-down > Expand All/Collapse All/All were not translated. This was fixed
    • January 2021 Resource Management SF: 00879360 URM-139215
      In brief record view, parallel fields were not displayed in Network Zone, only in Institution Zone. This was fixed.
    • January 2021 Resource Management SF: 00875552 URM-139298
      In some cases, sorting of physical item search results according to call number (ascending or descending) did not work properly. This was fixed.
    • January 2021 Resource Management SF: 00885716 URM-140019
      New Alma UI: Advanced search was not available for Add title search in Collection Editor. This was fixed.
    • January 2021 Resource Management SF: 00871029 URM-138241
      In the related records page (repository search results --> one of the records --> 'Other details' link --> click the number near the 'Related Records' text), the blue downward arrow near the 'Record Number' field, displayed when the record has more than one record number, did not work, i.e. the rest of the record numbers were not displayed. This was fixed.
    • January 2021 Resource Management SF: 00866968 00876882 00862829 00878185 00873803 URM-137199
      When creating an itemized set from Analytics and adding an Analytics report from the 'Recent reports' folder, this resulted in an error. This was fixed.
    • January 2021 Resource Management SF: 00881949 URM-138320
      When calling Alma via SRU in Dublin Core, dc:contributor and dc:creator subfields $$d and $$0 are attached to the name ($$a) without any space or subfield delimiter. This was fixed. A delimiter was added between subfields.
    • January 2021 Resource Management SF: 00821160 URM-136393
      When a title had both physical and electronical resources, the Digitization option appeared in GetIt even when the user was not signed in. This was fixed. Now the Digitization option appears only if the user is signed in.
    • January 2021 Resource Management SF: 00797736 00821047 00662204 URM-120256
      Non filing words were not removed from prima search sort title for UNIMARC records. This was fixed. Now UNIMARC records behave like MARC21 re non-filing behavior. Note that it works according to the non-filing standard (removing the no. of ind2 of characters from the beginning of the field) and requires: 1.recalculate operational 2.Index
    • January 2021 Resource Management SF: 00890408 URM-139291
      Primo VE - Year was not exported to Mendeley. This was fixed.
    • January 2021 Resource Management SF: 00885449 URM-140950
      In RIS format, the TY was not always displayed first. This was fixed. New mappings of risType were added: ElectronicBooks / book, PrintBooks / book.
    • January 2021 Resource Management SF: 00904213 URM-142193
      Primo VE: Getit dropdown did not reflect the Alma description. This was fixed.
    • January 2021 Resource Management SF: 00885001 URM-141464
      The 'We subscribe to only some titles in this collection' configuration field disappeared on and off in the CDI tab of an electronic collection. This was fixed.
    • January 2021 Resource Management SF: 00809186 URM-125008
      In UNIMARC when you created a new record using a template with a mandatory subfield, ignored it and left it blank, the expected message came up, but the saving was not blocked. This was fixed.
    • January 2021 Resource Management SF: 00843695 URM-131790
      In the old Metadata Editor, it is possible to click once on one of the dropdown menus and hover over the other menus to see all the menu options. This is now possible in the New Metadata Editor.
    • January 2021 Resource Management SF: 00888317 00885498 00885438 URM-132759
      Minimizing MDE after creating a new item/portfolio resulted in going back to the item/portfolio form, which could not be used. This was fixed. After minimizing, the users are taken back to the last page of Alma they visited before entering MDE.
    • January 2021 Resource Management SF: 00876915 00903652 URM-138952
      New MDE: When the focus was on 'View Inventory' pane, clicking on an action did not trigger the loading popup. This was fixed.
    • January 2021 Resource Management SF: 00508216 00882017 URM-139150
      A user without any Cataloger role was able to edit Holdings records. This was fixed.
    • January 2021 Resource Management SF: 00896503 URM-139172
      New MDE: when using F3 > 'Headings from bib records', the first row is selected and matched.
    • January 2021 Resource Management SF: 00882599 URM-139617
      New MDE: Searching in external resources after importing a record resulted in an error. This was fixed..
    • January 2021 Resource Management SF: 00881119 00882482 00888623 URM-139843
      When a network member institution disconnected a linked record from the network by using the File > 'Copy to catalog' option in the Metadata Editor, the Cataloger Level from the network record was retained. This was fixed. The Cataloger Level of the disconnected record (now local) is set to the default level as defined by the member institution.
    • January 2021 Resource Management SF: 00895621 00895616 00895561 00895637 00896485 00895620 00896428 URM-140423
      Search resources were not working with Aleph central catalog search. This was fixed.
    • January 2021 Resource Management SF: 00883312 URM-140851
      Merge and Combined failed with an error message. This was fixed.
    • January 2021 Resource Management SF: 00899996 URM-141147
      New MDE > Editing record > Search Resources > Search Cataloging Profile was displayed doubled; the edited record disappeared. This was fixed.
    • January 2021 Resource Management SF: 00895492 00883306 URM-138268
      New MDE: the profiles for 'Contribute Record to Central Catalog' menu option were missing. This was fixed. A sub-menu with the database names was added to 'Contribute to Central Catalog' in case of multiple DB names in CALIS profile.
    • January 2021 Resource Management SF: 00820991 00819134 00810395 00713297 00698811 00683610 URM-125108
      Deleted local authority record were still available in MDE using F3. This was fixed. A new data corrector was added to delete the ghost authority headings.
    • January 2021 Resource Management SF: 00848485 URM-132968
      MeSH authoritiy records were not linked to the bib record on save or through the 'Authorities - Link BIB Headings' job. This was fixed. Note that re-indexing or re-saving of bibliographic records that reference MESH or Jurivoc authority headings in $$0 is required to correct the heading ids.
    • January 2021 Resource Management SF: 00848492 URM-132973
      When multiple name authority priorities were set (customer parameter authority_names), classification field 084 was handled as a names heading field instead of a classification heading field. This was fixed. Re-indexing or re-saving of the bibliographic records referencing RVK authorities in the 084 field is required.
    • January 2021 Resource Management SF: 00851797 URM-133686
      Authorities subject $$2 value was ignored upon linking field to heading, for the magnifier (see linked authority record) action. This was fixed.
    • January 2021 Resource Management SF: 00863432 URM-134539
      Authority Record View Versions list displayed the second 1XX field instead of the first. This was fixed.
    • January 2021 Resource Management SF: 00875720 URM-136883
      In cases where the same originating system id existed for both GND and IDREF authority records, the bib record was linked to a GND authority even when it was supposed to be linked to IDREF. This was fixed.
    • January 2021 Resource Management SF: 00881512 URM-141115
      During import of UNIMARC records, the fields 304, 305, 307 were not converted to MARC21 500 fields. This was fixed.
    • January 2021 Resource Management SF: 00865355 URM-141332
      In MD Import, the sorting of the 'Submitted On' column was wrong. This was fixed.
    • January 2021 Resource Management SF: 00908579 URM-143098
      General publishing using Authority Enrichment did not publish non-preferred fields from CZ records when publishing IZ records that were linked to NZ records. This was fixed.
    • June 2021 Fulfillment – Course Reserves SF: 00917148URM-146475
      Exporting PDFs was failing in some cases. This was fixed.
    • January 2021 Fulfillment – Course Reserves SF: 00887698 URM-139607
      In the course loader job, a more accurate error message appears instead of 'Failed records'.
    • January 2021 Fulfillment – Course Reserves SF: 00848125 URM-140024
      Bibliographic details were overwriting citation details for non-repository citations. This was fixed.
    • Was this article helpful?