Alma 2023 Release Notes
- Last updated
- Save as PDF
Upcoming Issues to Note
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Upcoming Issues to Note
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Upcoming Issues to Note
Updated Documentation for Analytics Tables
As part of an ongoing project and in alignment with the Analytics Community of Practice, Ex Libris is currently enriching the documentation of several analytics field tables each month with additional information. This initiative aims to assist and support users in comprehending how our Alma data is presented within the realm of Analytics fields. For this month, the following tables within the Funds Expenditure subject area have been updated:
Upcoming Issues to Note
Change to Monthly Release Notes Distribution
Beginning in November, we will discontinue creating and distributing PDF versions of our release notes. This decision reflects our ongoing efforts to streamline our processes and focus on more efficient information sharing. While we will no longer provide PDFs, you can still access all the latest updates, enhancements, and resolved issues through our online platform.
We understand the significance of staying informed about our product developments. We are committed to ensuring that this transition does not impact the quality and accessibility of our information.
We appreciate your understanding and continued support as we improve our release notes distribution. If you have any questions or concerns, please don't hesitate to contact our dedicated support team.
Rollout of the New Layout for the PO Lines Task List
As of August 2023, the next-generation Alma UI design is available for the PO Lines task list. Individual users can opt-in to the new task-list layout to experience the functional enhancements and the new User Experience.
For a general overview of the new PO Lines task list, see New Unified PO Line Task List. See also Searching for PO Lines - New Layout; Managing PO Lines - New Layout.
For more information about the rollout plan, see Rollout Plan.
Upcoming Issues to Note
New Cookie Banner
As part of our commitment to transparency and privacy protection, we are gradually introducing a new feature in Alma and all our higher-education back-office products that requests user consent for the use of cookies. Your daily activities and Alma functionality will remain unaffected regardless of your cookie preferences.
Why is this change being made?
As part of Clarivate’s policy, we prioritize user privacy and aim to provide a secure and transparent user experience. By implementing this change, we align our products with company-wide policies and comply with regulations such as the General Data Protection Regulation (GDPR) and regional requirements. This ensures that your personal information is handled carefully and respectfully.
When will the change be implemented?
The new cookie banner will be rolled out gradually during August Release and will take a few weeks to complete.
How will the change be implemented?
Over the next few weeks, a OneTrust banner will be gradually rolled out and displayed at the beginning of each session when using Alma and other back-office solutions. This banner will request your consent to use cookies in our products.
Once you consent, the OneTrust banner will no longer be displayed during subsequent sessions, offering a streamlined user experience. We believe that by allowing you to control your cookie preferences, we enhance transparency and enable you to make choices that align with your privacy preferences.
What actions do you need to take?
During your initial login, after the feature is deployed, you will have the option to either accept or reject cookies. Should you wish to update your preferences at any time, you can do so on the new Cookies Settings page within the user preferences area.
We value your privacy and strive to provide a secure environment for your data. Should you have any questions or concerns regarding this update, contact our support team.
Sandbox Refresh
As a reminder, premium sandboxes will be updated in August according to Alma's premium sandbox refresh policy.
Upcoming Issues to Note
Gradual Rollout for the New Unified PO Line List
In the August release, users can independently opt in to a New Unified PO line list. The new interface holds multiple enhancements, new ways to interact with the PO line management list, search results, and editing of PO lines. These changes will require users to adapt to a new user experience and may require institutions to update their internal training. To make this process as smooth as possible, a dedicated page was created summarizing the enhancements and advantages of the new interface, and this is in addition to the gradual rollout process, which will be available for users working with PO lines. The design and validation of the new interface were made available thanks to the Alma community, led by the UX focus group actively participating as early adopters and working with the new interface for over a year.
The New Unified PO line task list will have many benefits, including:
- Information about all PO lines is presented in a single task list that can include PO lines in all workflow stages and assigned to any user.
- A multiple-facet selection will support a more flexible tool for creating a work set by including PO lines that meet multiple criteria of the same facet in one work set.
- “Assignment” as a facet.
- A new "side-by-side" layout option enables users to view a list of PO lines on one side of the window and detailed information regarding the selected PO line on the other side. The information in the Details pane is editable so that users do not have to navigate to a special PO line editing screen to perform basic tasks.
- It will be possible to add labels to a PO line and to be able to facet or search PO lines by these labels. This brings efficiencies to the PO line processing workflow by enabling on-the-fly tagging orders with workflow-related indications.
- “Single page” application to save extra navigation needs.
- Alma pages related to the currently selected PO line can be opened in a slide-out panel on top of the PO line page, enabling users to view and work on them while keeping the PO line in the background so that they don't lose their place in the PO-line list. For example, a user working on a PO line can view and modify the information about the item itself in a sliding panel.
- New advanced search will give users an easier way of building complex nested queries with a modern and accessible UI. It will utilize a new query builder, allowing the creation of nested logical conditions of 'And' and 'Or.'
See this short video for a preview of the new interface.
Note:
- The current user interface will remain available and easily accessible to allow gradual acclimation if needed.
Alma Known Issues Removed
URM-193167URM-192538Ex Libris has decided to remove our current Alma known issues system, which was inadequate in meeting our service standards. We apologize for any inconvenience caused.
Our teams are actively discussing alternative options to provide you with a better customer experience.
Upcoming Issues to Note
New SAML Certificate
The current DigiCert SAML Certificate will expire on June 8th. If your institution uses this certificate, Ex Libris recommends that you consult with the IT dept. in your institution, and if required, replace the certificate for Alma and/or Primo VE. If replacing the certificate, this must be done in coordination with your IDP. For more information, see Replacing a Signed Certificate.
If your institution uses ADFS, Ex Libris highly recommends that you replace the certificate to avoid any complications.
No immediate action is needed. Replacing the certificate can be done at any time until its expiry on June 8th.
Upcoming Issues to Note
New SAML Certificate
The current DigiCert SAML Certificate will expire on June 8th. If your institution uses this certificate, Ex Libris recommends that you consult with the IT dept. in your institution, and if required, replace the certificate for Alma and/or Primo VE. If replacing the certificate, this must be done in coordination with your IDP. For more information, see Replacing a Signed Certificate.
If your institution uses ADFS, Ex Libris highly recommends that you replace the certificate to avoid any complications.
No immediate action is needed. Replacing the certificate can be done at any time until its expiry on June 8th.
Upcoming Issues to Note
New SAML Certificate
The current DigiCert SAML Certificate will expire on June 8th. If your institution uses this certificate, Ex Libris recommends that you consult with the IT dept. in your institution, and if required, replace the certificate for Alma and/or Primo VE. If replacing the certificate, this must be done in coordination with your IDP. For more information, see Replacing a Signed Certificate.
If your institution uses ADFS, Ex Libris highly recommends that you replace the certificate to avoid any complications.
No immediate action is needed. Replacing the certificate can be done at any time until its expiry on June 8th.
Upcoming Issues to Note
Sandbox Refresh
As a reminder, premium sandboxes will be updated in February according to Alma's premium sandbox refresh policy.
Alma Roadmap Highlights
The next version of the Alma Roadmap Highlights document is available here.
Upcoming Issues to Note
Sandbox Refresh
As a reminder, premium sandboxes will be updated in February according to Alma's premium sandbox refresh policy.
Alma Roadmap Highlights
The next version of the Alma Roadmap Highlights document will be published in January 2023.
Next Release Sneak Preview
Select February 2023 Sneak Preview to view the next release sneak preview.
Main Features
Removing Alma URI for MARC Records Published as BIBFRAME
When publishing MARC records that are converted to BIBFRAME format, you have the option to decide whether to include an Alma URI in the record. This choice can be made by toggling the checkbox within the publishing profile.
If the intention is to republish records as BIBFRAME to Alma through third-party linked data editors, it's recommended to publish the records without an Alma URI.
On the other hand, if the aim is to provide records to a third party, it's important to include the Alma URI. This ensures the information can be effectively connected back to Alma.
For more information, see Creating a General Publishing Profile.
Concurrent API Request Threshold Increase
The concurrent API requests threshold was increased. Previously, it enabled 25 requests per second. Now, it combines two measurements: enabling 50 requests per second and a maximum of 1500 requests per minute. The change from 25 per second to a maximum of 1500 per minute might sound similar at first, but actually, this enables more fluent support for unplanned peaks.
Ex Libris monitors our servers' log files and will approach customers who are still hitting the threshold limit following the update, and offer guidance on how this can be avoided.
For more information, see API Governance Thresholds in the Developers Network.
New Digital Adoption Tool
Starting in the November 2023 release, Ex Libris is gradually deploying Pendo, a new digital adoption tool, across Alma and other components of our higher-education back-office suite.
- Pendo is a Digital Adoption tool used by SAAS (Software as a Service) software companies to identify usage trends and to provide users with an optimized user experience. It provides information on user trends and behavioral analytics to help improve the user experience.
- The implementation of Digital Adoption on the HEP (Higher Education Platform) is designed with our business partners to ensure that no personal data is passed through to Pendo.
- As part of our ongoing effort to improve the user experience, Digital Adoption helps us identify complex workflows where users might be struggling. This gives us the input needed to improve or simplify these workflows. During 2024, we will add a new walkthrough, which provides in-app guidance. In the future, there might be additional capabilities such as in-app help, messaging, user feedback, and more.
- For more information about Pendo, see the FAQ.
Deployment and Configuration
The digital adoption is functional only for users where:
-
Pendo is operating based on their country and institution’s policy.
-
The Digital Adoption configuration is turned ON (see screen capture below).
-
The user accepted functional and targeting cookies.
The digital adoption tool is gradually implemented at the following instances based on country policy:
-
Nov 7th – APAC (excluding China)
-
Nov 12th – NA
-
Nov 19th – EU start
-
Nov 26th – EU end
Administrator users of institutions where Pendo is configured may activate/deactivate the digital adoption activity at their institution by setting up the Digital Adoption page: Configuration Menu > General > General Configuration > Digital Adoption.
For more information about data collection, data privacy, and the anonymization process, see the Technical document.
For more information on configuration, see Configuring Digital Adoption.
Due Back Date Indicated in "Lender Will Supply" Message
Previously, in the Lender Will Supply message/email, if the requested item was already shipped for another request then Alma would not indicate when it was due back. From November, the message/email includes this date. Below is a sample email letter that shows the due back date.
For more information, see Configuring Letters in Alma.
Additional Personal Delivery Locations
Patrons who qualify for personal delivery can now choose a pickup location different from their registered home or office address. This enables libraries to offer a personal delivery service to addresses other than the home or office addresses.
It is also possible for patrons to update their registered home or office address (or other personal delivery address) while requesting personal delivery in Primo. This enables patrons to use the personal delivery service even if their home and office address isn't pre-loaded in the system.
The ability for patrons to add/edit their personal delivery locations is for PrimoVE users only.
For more information, see Configuring Additional Personal Delivery Locations.
Allow any Field from the Bibliographic Record to be Used when Defining a General Electronic Service
A new "General Electronic Service Bib Fields Enrichment" configuration screen (Configuration > Fulfillment > Discovery Interface Display Logic) was created. This enables institutions to define which field will be extracted from the record's metadata and be available for use when defining an "Availability Rule" or enhancing the "URL template" field upon definition of a "General Electronic Service" (Configuration > Fulfillment > Discovery Interface Display Logic > General Electronic Services).
Below is an example workflow:
1. Access the new configuration screen and add a new row to point to the specific bibliographic field (020_a in the example).
2. You can find the newly defined bibliographic field in the input parameters section of a rule.
3. You can also utilize the newly defined field in the URL Template field of the general electronic service.
4. Below is an example of how this will appear to patrons in the Discovery (Primo) system, as well as how the actual URL will be constructed.
When adding a row to the "General Electronic Service Bib Fields Enrichment" configuration screen, you will need to define the Record format, Bibliographic field and subfield. The defined value within the "Field Name in General Electronic Service" will be the one that appears when defining the General Electronic Rule/URL template.
1. When 2 bibliographic records are matched the logic will only apply on the "Selected" bibliographic record.
2. In case the URL template field starts with a parameter place holder with no text or URL before it (and regardless of what comes after it), no decoding will be done to
the first parameter's information.
For more information, see General Electronic Services.
Include Patron Email when Pushing Borrowing Request to Tipasa
When setting up Alma to push borrowing requests into Tipasa (see Resource Sharing Partners), selecting the Send Requester Information option will now send Tipasa the patron email in addition to the patron ID.
This enables Tipasa to continue processing a digital request using a known patron email.
Linked Open Data Enrichment for SpMaBN Vocabularies
The Linked Data enrichment process for bibliographic records associated with SpMaBN authorities now include the generation of URIs that link to the corresponding SpMaBN authority records. This enhancement ensures that libraries collaborating with SpMaBN authorities can harness the advantages of their Linked Open Data capabilities.
For more information, see Authority Vocabularies in the Community Zone.
All "BIBFRAME Records" and "MARC Records as BIBFRAME" in Alma Receive an Alma URI
We've enhanced the way Alma's URI for BIBFRAME records is organized. Now, the structure looks like this: cname.alma.exlibrisgroup.com/[format]/[works_or_instances]/[MMSID]. This new format applies to MARC records converted to BIBFRAME and native BIBFRAME records. Moreover, if an institution prefers, they can change the beginning of the web address (URL prefix) from cname.alma.exlibrisgroup.com to their own or any other prefix, for example, bgu.ac.il. This change can be made in the linked data integration profile and will be resolved if the domain is registered to the same IP address by the institution’s IT department.
This update particularly benefits institutions aiming to engage with BIBFRAME records, as they can establish a consistent and enduring URI format for their records, regardless of the Integrated Library System (ILS) in use.
For more information, see Working with Bibliographic Records and also: Linked Data.
Removing Alma URI for MARC Records Published as BIBFRAME
Updated - November 27, 2023: This functionality will only be available in the December 2024 release.
When publishing MARC records that are converted to BIBFRAME format, you have the option to decide whether to include an Alma URI in the record. This choice can be made by toggling the checkbox within the publishing profile.
If the intention is to republish records as BIBFRAME to Alma through third-party linked data editors, it's recommended to publish the records without an Alma URI.
On the other hand, if the aim is to provide records to a third party, it's important to include the Alma URI. This ensures the information can be effectively connected back to Alma.
For more information, see Creating a General Publishing Profile.
Authority Records Search by Subdivisions
Alma offers the functionality to conduct comprehensive searches within authority records. Before, it was not always possible to include data from subdivisions when searching for all types of subject authority records. Subject authority search indexes were enhanced to enable including subdivision data in keywords as well as other searches, for all relevant subject authorities. This robust feature enhances the precision and flexibility of the search process, making it easier to locate specific information within the authority records database. Whether you're seeking subdivisions related to subject headings, geographic locations, or any other pertinent data, Alma's search capabilities empower you to efficiently explore and access the information you require within these records.
For more information, Filtering Search Results.
Language Note (546) Added to MARC 21 Notes Search Index
Field 546, subfields a and b, detailing language information in the MARC 21 context, was added to the "Notes" search index. After the completion of semi-annual indexing or upon record modifications and saving, users can conduct searches based on the content of the specified subfields (546 a,b). This enhancement is helpful for libraries that maintain language notes in their catalog and want to be able to search by their content.
For more information, see MARC 21 Search Indexes.
Creating Itemized Physical, Digital and Electronic Title Sets Using MMS ID
Previously, MMS ID could be used only when creating All Titles itemized sets. Now it is also available when creating itemized sets of Physical Titles, Digital Titles or Electronic Titles. This enables libraries to create these sets from a list of MMS IDs, similar to other bibliographic identifier fields used for creating these sets. If an MMS ID in the list belongs to a record that doesn't have the inventory type associated with the set, it will not be found by the set creation process and won't be added to the set.
For more information, see Managing Search Queries and Sets.
Not Empty and Is Empty Operators Added to More Advanced Searches
The Is Empty and Not Empty operators are incorporated into additional search indexes within the advanced search feature. This enhancement enables more robust and powerful search capabilities.
For more information, see Performing an Advanced Search.
Browse Enhancements
When utilizing the browsing feature, Alma now retains the previously chosen options from the drop-down menus. This function is designed to spare librarians from the need to repeatedly re-select these values.
Within the Browse Shelf Listing section, Alma's memory encompasses the settings for "Call Number Level", "Call Number Type", "Library", and "Location". The remembered settings are used only when opening a blank Browse Shelf Listing form (not when opening a pre-populated form from a call number field or the Item Editor), and updated only if the operator manually changes the selection in one of the drop-downs before triggering the browse action. The default value for Call Number Type, controlled by the customer parameter call_number_type, is applied initially for each user. Once a user opts for a call number type, the customer parameter value is no longer considered.
In both the Browse Bibliographic Headings and Browse Authority Headings, Alma upholds the selected "Heading Type", along with the selected "Source Code" and "Vocabulary" for each respective type.
This enhancement greatly saves time and effort for librarians who often use Alma's browsing features.
For more information, see Browsing the Shelf Listing and Browsing Bibliographic Headings.
Updates to MARC21 Profile
The following MARC21 updates are now available for bibliographic, holdings and authority profiles:
- Update No. 35, December 2022
- Update No. 36, June 2023
Semi-Annual Re-indexing
Updated November 22, 2023 - During November, 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 November semi-annual re-indexing. See the list below:
- Language Note (546) Added to MARC 21 Notes Search Index, see here.
- Authority Records Search by Subdivisions, see here.
- New Search Indexes for URI Cataloged in $$1, see here.
- Adding Support for UNIMARC Authority Subfield 250 $v, see here.
- Support for MARC 21 Parallel Description in Another Language of Cataloging Related Records, see here.
- Related Records Update as Part of an Import Redirection, click here.
- Restrict Editing of Bibliographic 035 Fields With a Particular Prefix, click here.
- Publishing Network Bib Records to OCLC Using the Network Zone MMSID, click here.
- Restrict Editing Bibliographic Metadata Fields, click here.
Enhanced Missing Item Workflows
Previously, the ability to switch the missing status of an item was confined to the items list. Now, it's feasible to indicate whether an item is missing or found directly from the search results of physical items. This functionality is also available within the item editor page, accessible through the Save and toggle missing status action.
The Save and toggle missing status will save any changes made to the item in the editor, and then toggle the missing status, adding or removing a "Missing" process type. If an item is in another process type, this option is disabled. If an operator adds a process type to an item in place and then selects Save and toggle missing status, only the selected process type will be saved and the "Missing" process type will not be applied.
This enhancement streamlines the management of missing items, significantly boosting efficiency in the process.
For more information, see Updating Item Level Information.
Option to Append to Existing Note Field in the Job Change Physical Items
Previously, when using the Change Physical Items Information job to add notes, you could either replace existing notes or skip items that already had notes. Now, there's a new option called Append to field which lets libraries add a new note to the existing one, with a space and semicolon as separators. This is useful for adding a note to all items in a set without erasing previous notes.
For more information, see the Change Physical Items information job.
Validating the Item Inventory Price When Editing an Item
Now, institutions can set up a rule (called a regular expression or regex) that defines which characters are allowed when manually typing in an inventory price within the item editor. If an inventory price is edited and saved with an incorrect format, the system notifies the user that the entered price doesn't match the institution's rule. This lets them review and fix the data if necessary, ensuring accurate entry of inventory prices.
Choosing a regex that matches the values in their PO Lines is important for libraries that automatically fill in inventory prices from the PO Line. This helps prevent frequent notifications to users about mismatched prices.
For more information, see Working with Items. For more information on the customer parameter that controls the configuration, see Configuring Other Settings (Resource Management).
Running Jobs on Physical Holdings Sets
Previously, physical inventory tasks were limited to running on sets of Physical Titles or Physical Items. With the improved Physical Holdings set management in the new sets user interface, these tasks can now also be performed on sets of Physical Holdings. When running a job on a Physical Holdings set, tasks that affect physical holdings will now only involve the holdings within the chosen set. Similarly, tasks that impact physical items will only affect items that are part of the physical holdings within the set, based on where they are permanently located.
This enhancement is helpful when you need to focus on specific holdings, simplifying the process.
For more information, see Manual Jobs.
Link Resolver Usage Added to Portfolio Search Results
November 2023 Electronic Resource Management Idea Exchange
When reviewing search results for portfolios, you'll now see a counter that tells you how many times patrons were shown the portfolio's service and how many times they actually clicked on it using the link resolver. This combined count is also displayed at the title level. This usage data is provided for Network Zone institutions as well, and you can find it in both electronic portfolio search results and on the Held by page.
The time period of the data in the counters is for the past 12 months.
This new feature is an addition to the COUNTER usage information already available in analytics. It's designed to help institutions that use data to make informed decisions about their electronic holdings.
Additionally, the portfolio usage is shown in different ways for Institution Zone and Network Zone institutions:
In the Institution Zone:
- In portfolio search results, you'll see two numbers:
- The number of times the portfolio appeared in the "View it" section.
- The number of times patrons clicked on the portfolio. This is displayed as "Link Resolver Usage: x out of y".
- For "All Title" search results in the Other details tab, you'll see total usage values for all the portfolios under the title and the total number of times the portfolios appeared.
- In electronic title search results in the Other details tab, you'll also see total usage values for all the portfolios under the title.
In the Network Zone:
- You can view portfolio usage in electronic portfolio search results.
- In the Held by tab for all titles, you'll find usage information per portfolio, per institution.
- The usage data presented in the Other details tab is taken from Alma analytics.
- For Network Zone institutions, the Held by page displays the usage for each institution.
For more information, see Viewing Inventory/Other Details.
Modification to the Crossref Integration Profile
Due to modifications in Crossref's authentication requirements, users no longer need to provide a username and password when setting up a new DOI augmentation integration with Crossref. Instead, Crossref now mandates the inclusion of an email address as part of the enrichment request. If a default institution email is configured in Alma, the Crossref integration uses this email address. See Configuring Institution/Library Contact Information for information on where the default institution's email is defined. However, if no such email is defined, the institution ID is appended as a suffix to a generic email format:
InstitutionID@exlibrisgroup.com.
Here's an example URL:
https://doi.crossref.org/servlet/query?id=10.1080/00094056.2015.1090856&pid=InstitutioID@exlibrisgroup.com&format=unixref
This alteration also affects existing Crossref integration profiles; the username and password fields will no longer be applicable.
For more information, Alma Resolver Augmentation Configuration.
RemoteXS Resolver Proxy Type Added as Integration Proxy Option
A new integration has been introduced within Alma's resolver proxy integration, specifically catering to the RemoteXS resolver proxy. To access this integration, navigate to: Configuration Menu > General > External Systems > Integration Profiles. Select Add Integration Profile, and in the "integration type" section, opt for "resolver proxy."
Institutions utilizing the RemoteXS proxy now have the capability to configure Alma's link resolver to seamlessly integrate with this proxy.
For more information, see Configuring a Proxy.
Link Resolver Communication with Crossref
Previously, for OpenURLs coming from CDI, the Alma link resolver would fetch data from Crossref for lookup enrichment. Since CDI records have sufficient metadata, Alma will no longer fetch enrichment data from Crossref in these cases.
For more information, see Build Context Object in Alma Link Resolver Workflow.
Automatic Upload Electronic Holdings from Taylor & Francis (Journals)
Update October 25, 2023: Due to issues on the vendor side, this integration is postponed and is now planned for February 2024. We apologize for the inconvenience.
Libraries can now easily update their holdings for Taylor & Francis books and journals through the Automatic Upload of Electronic Holdings feature. When activated, this process automatically downloads a file with your holdings information from the Taylor & Francis platform in a standardized format, and then updates your holdings in the Taylor & Francis collection. This integration eliminates the need for manual updates when the Taylor & Francis side makes changes.
The following Community Zone collections should be activated in order to utilize the automated process:
- (Books) - Taylor & Francis eBooks Complete (Community Zone Electronic Collection ID = 611000000000000660)
- (Journals) - Taylor & Francis Online (Community Zone Collection ID = 611000000000002216)
- All portfolios that are updated from the various upload electronic holdings integrations modify the portfolio as "Available".
- All portfolios are activated from the Community Zone.
- A portfolio that is not found in the Community Zone, will not be created locally. The job only activates matching portfolios from the Community Zone.
For more information, see Upload Electronic Holdings from Taylor and Francis.
Detailed Information for Contributed and Modified Community Zone Bibliographic Records and Portfolios
Customers are now able to fully understand who contributed and who made modifications to Community Zone Bib records and portfolios.
Previously, Community Zone Bibliographic records and portfolios within editable collections (Management level: Community) featured a sole "Contributed By" field for contributions. When institutions (with appropriate contribution permissions) edited these Bibliographic records or portfolios, the editing institution's name was displayed as the "Contributor."
In the November release, a new "Modified By" field was introduced for Bibliographic records and portfolios in the Community Zone search results. This field captures edits that have been both contributed and made. Importantly, the original "Contributed By" value will remain intact and won't be overwritten.
For Bibliographic Records:
Each bibliographic record in the Community Zone has the Contributed By and Modified By fields. The existing Contributed By data is corrected to accurately reflect the true contributing institution, while the Modified By field contains the accurate information about the institution that made the modification.
For Electronic Portfolios:
Each portfolio displays the Contributed By field exclusively. Since there is no way to retrieve historical data for portfolio contributions, this data has not been corrected. In the future, when a modification occurs, a Modified By field will become visible.
For more information, see:
Average MARC Record Quality Measured to Community Zone Collections
November 2023 Electronic Resource Management Idea Exchange
A newly introduced Bibliographic Rank field is now visible in Community Zone collections. This field presents the average rank of the bibliographic records within the collection and operates across three distinct levels:
- Low - 0-39
- Med 40-79
- High 80-150
The option to customize views has been expanded to include the Bibliographic Rank and Brief Level fields for portfolio-level information. Users can now select to display these details in the search results if desired.
The inclusion of Community Zone collection quality data, such as the average Bibliographic Rank, empowers users to address inquiries about the quality of MARC records within a specific Community Zone collection.
For more information, see Bibliographic Ranking in Community Zone Collections.
Display of Microsoft Office Documents Now Supported by Digital Viewer
The display of Microsoft Office documents, such as Word, PowerPoint, and Excel are now supported by the Digital Viewer.
- Word and PowerPoint documents must not exceed 10 MB and Excel documents must not exceed 5 MB.
- For Microsoft Office documents, if the representation is associated with an access rights policy that restricts downloads, the document is not displayed, as was the case previously. For more information on configuring access rights policies, see Access Rights Policies for Digital Objects.
Master Usage Type Renamed to Primary
As part of our continuous efforts to promote Diversity, Equity, and Inclusion and to remove any unintentional bias from our system, we are renaming the Master Usage Type to Primary. This is relevant when:
- Adding or editing a representation:
Usage Type
- Configuring a digital import profile:
Usage Type
This change was implemented across Alma. For the next feature release in February, the change will be implemented in APIs, SRU, and other external interfaces.
New Default Thumbnail Images
New default thumbnail images for digital files are now available. These images clearly display the file format of the file. Some examples are:
jpg – | |
mp4 – | |
pdf – |
For more information on thumbnail images for digital files, see Managing Digital Files from the Digital Representation Resource Editor.
Rollout of the New Layout for the PO Lines Task List
As of August 2023, the new, next-generation, Alma UI design is available for the PO Lines task list. In this release, the new UI will automatically bet set as default for all users. If needed, individual users can opt-out of the new task-list layout. In February 2024, the new UI will be set as default for all users with no option to switch back to the classic interface.
For a general overview of the new PO Lines task list, see New Unified PO Line Task List. See also Searching for PO Lines - New Layout; Managing PO Lines - New Layout.
For more information about the rollout plan, see Rollout Plan and New Unified PO Line Task List in the Alma 2023 Roadmap Webinar Series.
Change of Behaviour after Creating a new PO Line (New Interface)
When creating a new PO line manually in Alma, for users who finish their flow by selecting Order Now, Save or Save and continue, Alma will navigate to the list with the specific POL. This change was implemented following feedback received from customers.
This behaviour will only apply for newly created PO lines. For existing PO lines, when users edit and select one of the above three actions, the page will remain as is.
For more information, see Adding Information to the PO Line.
Customize Facets in the New PO Line Interface
Users of the new PO line interface can now customize the order of the facets as well as hide facets that are used less often. This requires you to be opted in to the new PO line interface (see Feature Rollout Configuration). To view the new functionality, run a search that presents you with the new PO line list and then select the gear icon located on the top right corner of the search results. From there select the Facets Customization option and use the drag and drop option to change the order of the facets and/or hide selected facets.
For more information, see Record and Section Customization, Customizing Facets.
PO Line Templates - Addition of Two New Fields (Labels + Quantity for Pricing)
Two additional fields were added to the elements that are saved when a user saves a template for a PO line.
- Labels
- Quantity for pricing.
When loading a template that was saved with the Update Net Price according to item quantity field not checked, this field will be un-checked in the created PO line, even if the po_line_quantity_updated_with_items_number customer parameter is true.
For more information, see Manually Creating a PO Line and Fields that are Saved in a PO Line Template.
Update to the URL Used for auto SUSHI Harvest from Ebook Central
November 2023 Acquisitions
Update November 19, 2023: From December 5, 2023, Ebook Central no longer supports COUNTER release 4, and will transition exclusively to COUNTER release 5. The new URL will be publicized once finalized by Ebook Central.
The existing Counter 5 SUSHI harvest from Ebook Central, with the following URL: https://pqbi.prod.proquest.com/release/sushi/ebooks/r5/, will still be supported and will allow automated harvest of usage date. This service will be deprecated once the transition is complete.
- If you have the "Ebook Central" Sushi account" configured as seen in the image below, the new URL will appear within the "Vendor URL" field automatically, and all should function as expected. In case you experience any issues with the automated harvesting, please contact Ex Libris support.
- If you have a different "Vendor URL" defined for Ebook Central, you may need to modify the URL to the new one.
- In order to harvest usage data from PQIS, the following URL will still function: https://pqbi.prod.proquest.com/release/sushi/ebooks/r5/
New "Save and Dismiss" Function Added to the Manage EDI Tasks Page
Originally, in the pop-up that appears in the "Manage EDI tasks" page, the user needed to Save and then "Dismiss" the relevant line from the list. In order to enhance the workflow, a new Save and Dismiss button was added to the pop-up that appears when selecting the Update Expected Receipt Date option. This enables the users to save their changes as well as dismiss the task, in a single click.
For more information, see Managing EDI Order Responses.
“New Order” Import Profile Supports Single Record with Multiple Locations and Creates POL for each Location
The “New Order” Import Profile now supports creation of a PO line for each Item created under a single bibliographic record. This is implemented by the new Split PO Lines by Library Location checkbox that is available in the "POL information" tab of the "New Order" import profile (EOD).
This new checkbox only appears for "Physical" and "Mixed" import profiles.
For more information see Managing Import Profiles.
New Field for Electronic Collection Material Types in Update PO Lines Information Job
Up until today, users who utilized the "Update PO line information" Job in order to update material types for Electronic Collections, could only select material types associated with Electronic Portfolios. In most cases, the modification worked, but not all material types which are supported for electronic portfolios are supported for electronic collections. In order to resolve this, a new dedicated Material type (Electronic - collection) field for electronic collections was added to the "Update PO line information" Job. See Configuring Resource Management for more information.
In addition, if non-relevant material types are selected in the job parameters, then the Material Type will not be updated in the PO Line. For example, if Material type (Physical) is selected in the job parameters, when the set contains electronic PO lines, then the Material Type will not be updated in the electronic PO lines. When the selected material type is the only parameter selected in the job, then non-relevant material types are skipped and the PO line is added to the Skipped PO Lines section in the report.
For more information see Manual Jobs.
Added 4th and 5th Reporting Codes to Update PO Lines Information Job
The "Update PO Lines Information" job which enables users to update PO lines in bulk using a dedicated set/s was enhanced to include the 4th and 5th reporting codes.
For more information, see Configuring Processes.
ERP Number in Exported Invoices
Today, for institutions which have Alma integrated with an ERP system, when an order is created in Alma it is passed to the ERP system. If required by the institution, the ERP reference number is recorded on the PO line. As of the November release, invoices which hold invoice lines associated to PO lines with an ERP number, will have the ERP number indicated on the invoice line. This information is also available within the PO line section when exporting an invoice.
For more information, see Creating Invoices and Exporting an Invoice to XML.
Additional Vendor Code in Exported Purchase Orders
Up until today, the Export PO to ERP job exported only the vendor_code. As of today, the additional_vendor_code will be exported as well.
For more information, see Financial Systems.
Item Retention Functionality Added to "New Order" and "Update inventory" Import Profiles
The existing item retention functionality (see Working with Physical Items) which allows institutions to mark physical items as Committed to retain (items which cannot be withdrawn from the library) was added to the "New Order" and "Update Inventory" import profiles.
Institutions that use these import profiles can indicate in the imported file, items they wish to mark as committed to retain. As a result, items created from the import process will be marked as committed to retain.
The following applies to items which are committed to retain and are associated with a PO line:
- An icon is added in the "Ordered items" section.
- When selecting Delete on the row actions, the item is removed from the PO line but is not deleted from the system (since it is committed to retain).
- When cancelling the PO line, the item is not deleted from the system (since it is committed to retain).
For more information, see Managing Import Profiles.
Fund Editor — Expended and Encumbered Balances as Links
This enhancement will be introduced once the November release update is installed (November 12).
The Expended Balance and Encumbered Balance were previously shown as text. They are now displayed as links. Selecting the link takes you to a list of related orders.
For example, when accessing a fund and clicking on the encumbered balance amount (150.00 USD in the example below), the user will be navigated to a list of PO line search results with the orders which encumbered the fund. When these encumbered orders become expenditures, it will appear in the list of the expended balance.
Acquisitions users who can view/edit funds will be able to easily understand which PO lines caused encumbrances and expenditures on the fund balance.
In addition, the following fields were added to the Order Lines advanced search.
- Encumbered from (fund code)
- Encumbered from (fund name)
- Encumbered from (fund id)
- Expended from (fund code)
- Expended from (fund name)
- Expended from (fund id)
For more information, see Funds and Ledgers.
New Privilege Added Enabling Users to View Funds and Ledgers Owned by the Institution and Available for the Library
Until today, users with the following acquisition roles scoped to a specific library (Law for example) were not able to view funds and ledgers which were owned by the institution and were available for their library (Law).
- Fund Manager
- Fund-Ledger Viewer
- Ledger manager
- Purchase Request Manager
- Purchase Request Operator
- Purchasing Manager
- Purchasing Operator
To allow users to view funds and ledgers that are owned by the institution, and are available for the library that their role is scoped to, a new privilege called “Fund ledger view by available for” was added to the above acquisitions roles.
When the new privilege is enabled, users with one of the 7 roles above (when scoped to a specific library) will be able to view funds and ledgers which are owned by the institution and have that library as part of their fund’s Available for settings.
For example, a user with the Fund-Ledger Viewer role (scoped to the Law Library)...
...will be able to view the following fund (since the Available for field is set to Law Library):
This privilege is not enabled by default, for any of the 7 roles above. In order to enable this new privilege, please contact Ex Libris support.
For more information, see the spreadsheet in Privileges Report and the section on Ledger and Fund Availability.
Enhancement to the Recalculate PO Line Encumbrances Based on Current Exchange Rates Job
A new recalculate_fund_transaction_with_explicit_exchange_rate customer parameter was added to the Acquisitions configuration menu (Configuration->Acquisitions->Other settings).
The new functionality behind this customer parameter is only relevant for institutions that use the "Explicit Exchange Rate" functionality (enabled in Configuration -> Acquisitions -> Other settings -> currency_exchange_use_explicit_ratio). For more information see Configuring Explicit Exchange Rates.
Currently (by default) with the recalculate_fund_transaction_with_explicit_exchange_rate customer parameter set to "false", Alma calculates the explicit exchange rate on the fund associated with the PO line , once only, and marks the transaction on the fund as "Explicit exchange rate = Yes". When the Recalculate PO Line Encumbrances Based on Current Exchange Rates job is run (see Scheduled Jobs), Alma does not recalculate the transaction again, according to the explicit exchange rate. This is in order to maintain the exchange rate value of the day it was applied.
When the recalculate_fund_transaction_with_explicit_exchange_rate customer parameter is set to "true", Alma recalculates the explicit exchange rate on the fund associated with the PO line, every time that the Recalculate PO Line Encumbrances Based on Current Exchange Rates job (see the Scheduled Jobs table) is run. Alma does this recalculation, even if the transaction on the fund is marked as "Explicit exchange rate = Yes" and the explicit exchange rate was previously applied.
1. To maintain existing functionality, the new recalculate_fund_transaction_with_explicit_exchange_rate customer parameter is set to "false" by default. The new functionality will not apply unless the institution changes the customer parameter to "true".
2. The Recalculate PO Line Encumbrances Based on Current Exchange Rates job is inactive by default. Institutions can enable it by accessing
Admin > Monitor Jobs > Scheduled (tab).
For more information, see Other Settings.
Accessibility Improvements
Ex Libris is committed to diligently address a wide range of accessibility issues as part of our ongoing efforts. Our dedication to improving accessibility encompasses a comprehensive approach, focusing on making our products, services, and digital content more inclusive and usable for all individuals, regardless of their abilities or disabilities.
We are pleased to announce that within our November release, numerous accessibility improvements and fixes have been implemented, in compliance to WCAG 2.1 AA standard, including the following:
- Provided the required ARIA labels attributes, tooltips and elements role in various screens.
- For Digital Uploader and Metadata Editor - fixed the support for a screen reader to properly announce the navigation through tables and announce the table headers along with the cell data.
- Labels/names of multiple buttons with the same name that were performing different actions in various screens is now fixed.
- Advanced Search - value fields with error message were fixed to associate with the respective field to allow the screen reader to state it.
- Fixed keyboard focus and navigation order in various workflows and screens.
- Tooltips that appeared only on hover are now available to access using the keyboard, to support screen reader in various screens.
- Metadata Editor Indication Rules Form – The form’s visual heading text is now marked as heading for text reader.
- Metadata Editor Records - keyboard trap that prevented navigation into/from, the editing form of Dublin Core’s is now fixed.
- The accessible label needed for voice dictation of some controls was fixed to include visible label text in various screens.
- Buttons text visibility was improved in various screens.
- Selected state of an element is now conveyed to screen reader in various screens.
- Added missing ARIA labels in various screens.
- The expand/collapse state of a toggle-type element and checkboxes now states its current status as expected in various screens.
- Reading order was fixed for a proper logical content screen reading in various screens.
- Improvement of the responsiveness of the search bar display when zooming in was implemented.
- Error/Status messages are now automatically announced by the screen reader in various screens.
- Ensuring unique IDs of active elements.
- And more…
These efforts are a testament to our dedication to ensuring that our offerings are more accessible and user-friendly, and to our ongoing effort to improve product accessibility.
Letters Configuration - X-Path to Specify a Location within the XML
The XSL editor now provides the X-Path for a particular XML element when you click on that element within the XML editor textbox. This feature proves valuable, especially when you need to copy an XML element into the XSL. You can quickly access this functionality using the keyboard shortcut: Ctrl-Shift-H.
For more information, see How to Customize Letter Templates.
Enable Automatic Rollover of SAML IdP Certificate
In August, Alma introduced the ability to configure an additional SAML certificate to avoid a period of time when the SAML authentication is down for maintenance. Now, Alma facilitates a rollover process by managing two IDP certificates simultaneously. It is now possible to configure the Integration profile to fetch the metadata when it is modified by the IdP.
For more information, see Automatic Rollover of an IdP Signing Certificate.
To improve the process and prevent interruptions when replacing SAML certificates, we've taken steps to make Alma work with two certificates at once. This way, authentication can be attempted using either certificate.
Now, we are introducing a feature that detects changes in the IdP's certificate and automatically updates Alma's integration profile with the new certificate. This ensures smooth authentication without manual steps, reducing downtime and maintaining security.
Ex Libris aims to automate certificate updates for consistent SAML authentication in Alma, reducing disruptions and improving system reliability.
For more information, Replacing a Signed Certificate.
Mapping Tables Enhancements
The following improvements aim to enhance the functionality and usability of mapping tables, providing users with a more intuitive and efficient experience.
- Inner Search: An inner search functionality is added to enhance the mapping table experience. Users can now search within the mapping table to quickly locate specific entries.
- Responsive Columns: To improve readability and user experience, users can expand/reduce the width of the columns and change the columns' order (using drag and drop), making navigating and understanding the content simpler and more intuitive.
- Responsive Columns with Text: Mapping table columns now display text instead of fields.
- Page Titles: Page titles are incorporated as headers for mapping tables, providing clearer context and easier identification of mapping table content.
- Pagination: A pagination feature is introduced to effectively manage large mapping tables. Users can now navigate through mapping table entries using page numbers, creating a more efficient and user-friendly experience.
For more information, see Mapping Tables.
Added Option to Edit User from Alma User Card
Alma introduces a new feature that makes it easier for Alma staff users to access user details directly from the task lists. This change is designed to streamline their work and save time.
Key Changes:
- The Requester field in the Alma Borrowing task list (and other relevant fields) now includes a linkable user name.
- Staff users can select the user's name within the task list to quickly access and edit their details.
Enhanced User Experience:
- The user's name appears in blue and can be clicked on to open their profile.
- Selecting the user's name takes the staff user to the user details page, where edits can be made.
- This link's functionality depends on the user's roles and permissions, ensuring secure access to sensitive information.
Before this update, staff users had to manually copy the user's name or identifier, search for the user separately, and then proceed to edit. This extra step has been removed, making the process more efficient and user-friendly.
For more information, see Creating a Borrowing Request.
New Configurations (Limited) Subject Area
The new Configurations (Limited) subject area was added to Alma analytics. Currently, it contains fields that enable you to create reports to answer business questions regarding fulfillment policies and fulfillment terms of use configurations. In the future, the ability to create reports regarding fulfillment rules configurations will be added as well.
For more information, see Configurations (Limited).
Analytics New Layout Now the Exclusive Layout Available
The Analytics New Layout that was made available as an opt-in option for the May release and available by default for the August release is now the exclusive layout available. It is no longer possible to revert to the old layout. For more information on the new layout, see Working with Analytics Objects.
For a Webinar describing the capabilities and functionality of the new Analytics layout, see New Alma Analytics User Interface.
Enhanced Manage Subscriptions Section in Analytics Object List
The Manage Subscriptions section in the Analytics object list was enhanced with the following new features:
- When toggling Schedule Report, a Manage Subscriptions section now appears in the pane and in the list of sections at the left side:
Manage Subscriptions Section
- Instead of a Manage Subscriptions link, an Add Subscribers link appears. When selected, a new area appears that allows you to add subscribers to the report and view a list of existing subscribers. This replaces the previous functionality where a separate page appeared.
Add Subscribers
- If Subscribe to the analytics object is toggled, the user appears in the list of subscribers.
- External email addresses are validated for proper format and if they are already in the list.
- You can customize the columns that appear by selecting the Customize icon and export the list to Excel by selecting the Export icon .
For more information, see Working with Analytics Objects.
New Analytics Usage Tracking Data Visualization Dashboard
A new out-of-the-box Analytics Usage Tracking dashboard is now accessible. It offers reports for tracking analytics queries and responses, giving clear insights into how analytics are used and how well they perform, including identifying errors and timeouts.
You can find it in the Alma catalog at Alma > Analytics Usage Tracking > Data Visualization > Usage Tracking.
Item Creation Date Filter Added to ACRL and IPEDS Dashboard
The Item Creation Date filter was added to the ACRL and IPEDS dashboard reports. This filter lets you sort the reports based on when the item was created.
You can use this filter in the following reports under the Library Collection Number of Titles (Physical) tab:
- ACRL Physical Books Title Count
- ACRL Physical Media Title Count
- ACRL Physical Serials Title Count
And also, in the reports under the Library Collections Number of Titles (Electronic) tab:
- ACRL Digital/Electronic Books Title Count
- ACRL Digital/Electronic Media Title Count
- ACRL Digital/Electronic Serials Title Count
Search Analytics Object List by Description and Report Name
You can now search for Analytics Objects by object Description and Report Name. To support this feature, Description and Report Name were added as options from the Find drop-down list.
Rollout of the New Layout for the PO Lines Task List
The next-generation Alma UI design is now available for the PO Lines task list (Acquisitions > Purchase Order Lines > All PO Lines, when the user opts in). In this release, individual users can opt-in to try out the new task-list layout, or continue using the classic version of the layout.
The new layout is designed to provide users who manage PO lines with a more streamlined experience, in which more information is available at a glance and new search and facet options make it easier to locate PO lines with certain characteristics.
The main new features of the new UI are:
- Details pane: A work area, called the Details pane, can be opened on the right side of the PO-line list. Most aspects of a PO line can be edited in the Details pane without losing sight of the task list, and the new arrangement speeds up the editing process.
- Sections menu in the Details pane: The fields of the Details pane are divided into sections, and a collapsible Sections menu enables users to quickly navigate between the sections.
- Multiple-facet selection: Multiple criteria can be selected in each facet category, providing more flexibility in the creation of a filtered PO-line list.
- Workflow Step and assignee information as facets: Workflow Step (status) and assignee information are facet categories, enabling searching for PO lines by specifying multiple Workflow Steps and a number of specific assignees.
- Enhanced Advanced search interface: Multiple search criteria can be grouped and nested, and the relationships between them can be defined as either AND or OR.
- Sliding panel: When access to other pages is required, the pages open in a panel that "slides" out from the right side of the window, only partially covering the task list. This enables work on all aspects of the PO line without losing sight of the PO-list context.
- Streamlined access to notes: Notes can be seen, added, searched, sorted, and managed in the new Details pane. This makes these important elements more noticeable and easier to manage when reviewing the PO-line list or processing PO lines.
For a general overview of the new PO Lines task list, see New Unified PO Line Task List. See also Searching for PO Lines - New Layout; Managing PO Lines - New Layout.
By default, in this release the PO-line task list continues to be opened in the classic UI. However, we encourage users to opt-in to the new layout and take advantage of its many new features and benefits. To opt into the new layout of the PO Lines task list, from the User menu, select Feature Rollout Configuration (persistent menu > > Feature Rollout Configuration), and then activate the New Unified PO Line Task List. As part of the November 2023 release, the new layout will be turned on by default, although users will still have the option to opt out at that time. Finally, beginning with the February 2024 release, only the new layout will be supported. This schedule is tentative and subject to change, based on customer feedback. For more information about opting into using the new UI for features for which it is available, see Opting In or Out of a New Feature.
A webinar on “The New Unified PO Line Task List” will be delivered in two separate time zones on August 08, 2023. For further information and registration see the Alma 2023 Roadmap Webinar Series page.
New Layout for Manage Sets Page
August 2023 Resource Management
The next-generation Alma UI design is now available for the Manage Sets page (Admin > Manage Jobs and Set > Manage Sets).
The updated design is available for all users. There will be no gradual roll-out for users to opt in/out.
The New Layout is designed to provide users who manage sets with a more streamlined experience, in which more information is available at a glance and new facet options make it easier to locate sets with certain characteristics.
This release introduces a range of enhancements aimed at improving the creation and usage of sets in Alma. The enhancements focus on providing a quick and intuitive experience for users, streamlining workflows, and increase overall efficiency.
Due to applying the improved infrastructure, the search set functionality has been slightly changed so that the asterisk ( * ) wildcard character should be used when searching for a string that begins with the searched characters. For example: search for “ser*” to search for “serials” along with “series” and ”serology”.
- Key updates:
- Streamlined set creation: We have implemented a more straightforward and user-friendly approach to creating sets. Users will now find it easier than ever to generate sets, with simplified processes and fewer steps.
- Improved set utilization: Recognizing the value of utilizing existing sets efficiently, we have introduced a quick and intuitive method for leveraging pre-existing sets. This enhancement enables users to access and utilize sets seamlessly in various tasks and searches.
- Creating Itemized Physical Holdings Sets
The physical holdings sets management was enhanced as part of the improved sets management enabling operators to easily create and manage itemized as well as logical sets of physical holdings records. This is especially useful when you want your set to include specific holdings, or to create an itemized set from a logical set of all holdings that fulfill a condition at a specific point in time.
For more information, see Managing Search Queries and Sets.
A webinar on "Search and Sets Functionality in Alma using the New UI for Managing Sets" will be delivered in two separate time zones on November 13 and 14. For further information and registration see the Alma 2023 Roadmap Webinar Series page.
Accrued Fees Now Appear in User Details
The Fines/Fees tab of the User Details page (Admin > Find and manage Users > [select user]) now includes information about fees that patrons are currently accruing for overdue loans that they have not yet returned. Previously, this tab included overdue fines information only for loans that were already returned, which were included in the sum that appears under Active balance. The Accrued fines field shows additional fines that may still be increasing, because the patron has not yet returned the loan. Note that the accrued fines are not included in the calculation of the debt limit that, if reached, would prevent the patron from borrowing additional items. For additional information, see Managing Users.
Additional Fields Added to Resource Sharing Record Display
Additional information about resource-sharing requests has been added to the resource-sharing task lists, as follows:
Optional Fields
The following optional fields can now be added to the record information displayed in the task list:
- Lending Requests:
- ISBN
- ISSN
- Publication date
- Publisher
- Place of publication
- Borrowing Requests:
- Publication date
By default, these fields are not displayed. To add them to your display, select (or ) > Records Customization to open the Records Customization pane, and then select the fields you want to add to the record display. For additional information, see New Layout 2022.
Call Number
When available, the request Call number is now shown in the Request Information section of the Details pane for both borrowing and lending requests. For additional information about working with the Details pane, see New Layout 2022.
Copyright Information on the Right Pane
August 2023 Fulfillment - Resource Sharing URM-174642
To enable librarians to work more efficiently, when the parameter rs_borrower_copyright_management (Configuration > Fulfillment > General > Other Settings) is set to true (default false), copyright information for requests is now available and manageable from the right pane in addition to the Edit pane of a request.
The copyright information can only be edited for requests that have not yet been sent.
Linked Open Data Enrichment for EuroVoc Authorities
The Linked Data enrichment process for bibliographic records that are linked to EuroVoc authorities now also generate URIs to the EuroVoc authority records, so that libraries that work with EuroVoc authorities can benefit from their Linked Open Data capabilities.
For more information, see Working with Authority Records.
New Search Indexes for URI Cataloged in $$1
To enhance search capabilities, we have introduced new search indexes for cataloged URIs in $$1. These indexes allow for more efficient searching based on associated URIs.
These new indexes are:
- Real World Object URI: indexing $$1 from supporting fields
- ORCID - Real World Object URI: indexing $$1 from supporting fields that contain ORCID URI
- ISNI - Real World Object URI: indexing $$1 from supporting fields that contain ISNI URI
This is useful for libraries that catalog URIs, and enables them to use these identifiers in their searches.
For more information, see MARC 21 Keyword Search Indexes.
ORCID URI Enrichment for Bib Records Using the Alma Refine Cloud App
Configuring an integration profile for ORCID in Alma is now possible, enabling you to use your ORCID credentials to add ORCID URIs to your Bib records using the Alma Refine cloud app.
To configure this, add an integration profile with Integration Type ORCID and enter your client ID and secret for connecting to ORCID (only a single ORCID integration profile can be added per institution). Once the integration profile is complete, you can select ORCID from the list of Refine services in the Alma Refine cloud app. This feature benefits research libraries managing numerous records by researchers with ORCID IDs, enabling inclusion of these IDs in the catalog.
For more information, see Alma Refine in the Developers Network.
For more information on configuring an ORCID integration profile, see ORCID URI Enrichment for Bib Records Using Alma Refine.
Only Generate URIs for Authority Records That Fully Match the Subject Heading
The authority control process in Alma sometimes generates partial matches between subject headings and authority records without the subdivisions. In such cases, the Linked Data enrichment process for bibliographic records that are linked to authorities generates a URI that only partially corresponds with the full subject. Libraries can now choose to prevent URI enrichment for partially linked authority records and add URIs only for full matches. To do this, set the lod_uri_enrichment_for_partial_match to false.
For more information, see Authority Control.
Adding Support for UNIMARC Authority Subfield 250 $v
UNIMARC classification version stored in subfield 250 $z is now mapped to Bibliographic field 676 $v for various related workflows across the system.
For example, when searching for a Bibliographic record from an Authority record using the “Search bibliographic records matching this value” option, the version is used. In addition, the version is now part of the Authority record display as part of the F3 browsing, as well as, part of the browse Bibliographic headings functionality. For more information, see Searching in Alma.
Browse Shelf Listing Context Display
Browsing call numbers on the Browse Shelf Listing page (Metadata Editor, > Search and Browse > Shelf Listing) was enhanced. Now, when browsing for a call number, the call number searched is the third one that is displayed. This provides users with the context of some previous call number results on the page, similar to the display in Browse Bib Headings.
Bibliographic Record Retention
A new feature has been introduced that allows libraries to prevent the deletion of a bibliographic record. To implement this, the Bibliographic Collection Retention Definition table can be configured. Administrators can specify conditions for record retention. Add a field and subfield in order for the record to be protected from deletion if the subfield contains any value. Alternatively, specify a specific value, and only records with that value in the subfield will be retained.
After configuring the table, Alma performs verifications when attempting to delete a bibliographic record. It verifies if the record contains the specified content from the table. If the content is present, the bib record is protected from deletion. Furthermore, after the table is updated, any record that matches the defined criteria will be marked as committed to retain the next time it is indexed (when changed and saved, or during the semi-annual re-indexing). This allows for the retained records to be searchable within the system.
The institution’s table is consulted when deleting local records, and when attempting to delete a bibliographic record that is linked to the Community Zone (the removal of the linked record from the local institution is restricted based on the institution’s configuration).
For collaborative networks, network zone records’ retention is determined based on the configuration specified in the Network Zone’s table.
This feature is particularly beneficial for libraries with collaborative collections, that aim to safeguard specific records from deletion, as well as for libraries that want to make sure important records, for example; rare materials, donations, and so forth, are not accidentally removed from the catalog.
For more information, see Bibliographic Record Retention.
Metadata Editor Enhancements: Undo Remove, Cut and Paste Field Actions
This feature will be available starting with the August Update Release on August 13.
Previously, the removal of fields from a bibliographic record could not be undone. A new functionality called "Undo Remove, Cut, Paste Field" (Ctrl+Shift+Z) is introduced, that enables catalogers to undo such actions, providing a convenient way to restore accidentally removed fields without having to revert to a previous version of the record. This enhancement saves time and effort while ensuring accurate cataloging.
Browse Authority Headings
A new feature called Browse Authority Headings is now available, enabling users to browse authority files for name and subject authority records. This browsing functionality displays both the preferred and non-preferred terms in the authority record, clearly indicating which terms are preferred. Libraries can now easily explore the authority files used in their cataloging workflows, access authority records, and view any linked bibliographic records.
This enhancement is particularly beneficial for librarians who want to browse the authority vocabulary using a specific name or subject, even if they are unsure whether it is the preferred term or not. For librarians without cataloging privileges, the authority record browsing is a read-only capability. It is automatically enabled in all Alma roles, similar to the repository and authority searches.
For more information, see Browse Authority Headings.
Match on Title Type Option Added to the Import Mechanism
Alma's import mechanism was enhanced to include the option to match on the title type, electronic or physical. When importing records to Alma, a matching option that considers the title type (print or electronic) is now available. Incoming print titles are matched to print titles in the repository, and incoming electronic titles are matched to electronic titles in the repository.
In addition, a new option to disregard matches for bibliographic Community Zone linked records was added to the Import profile configuration.
For more information, see Creating/Editing an Import Profile: Match Profile.
For more information on the various Alma Resource Types, click here.
Control the Ability to Ignore Title Based Link Resolving
Currently, when Alma gets an open URL from Primo, it tries to find resources according to three main methods:
- Match by identifier
If no identifier exists/no match was found:
- Match by title and author
If no title+author exists/no match was found:
- Search by title only ("Fuzzy Match")
A new option controlled by a customer parameter, avoid_fuzzy_search_resolving (Configuration -> Resources -> Other settings), enables the institution to indicate to Alma to avoid "Fuzzy matches" ("title only" matches) attempts. By default, the new customer parameter is set to "False" and Alma continues behaving as it does currently. The new functionality is only active when the customer parameter is set to "True".
If the open URL contains only a title, Alma attempts to find a match, since there are no other elements by which to search.
This logic applies to electronic resources (View it) and physical resources (Get it).
If enabled, the existing CP: find_get_it_based_on_standard_identifiers_only, continues functioning as is and takes precedence over the new logic and is relevant only for physical inventory (Get it).
For more information, see Control Ability to Ignore Title Based Link Resolving.
For more information on the customer parameter, see Configuring Other Settings (Resource Management).
Applying the Library Scope to the Physical Titles Search
The library scope available for the physical items and holdings search now affects also the physical titles search, so that librarians that define a preferred library's scope see in the search results only physical titles that have holdings in the defined libraries. The library scope set by the librarian is remembered by the system and applied across sessions and search types until the librarian chooses to change it.
This is helpful for librarians who are interested only in titles held by specific libraries and saves the need to add a library search condition for every physical title search.
For more information, see Searching in Alma.
Support for MARC 21 Parallel Description in Another Language of Cataloging Related Records
A new type of analytical linking was added to the MARC21 standard, Parallel Description in Another Language of Cataloging (788). This type is now supported in Alma's workflows that consider analytical linking, for example, publishing profiles enrichment.
Related Records Update as Part of an Import Redirection
The import redirection mechanism now updates the related record fields where the 'secondary record' ID is replaced with the new 'primary record' ID either by 035 or MMS ID.
Automated Upload of Electronic Holdings Now Supported for PROJECT MUSE Titles
Alma has expanded its integration capabilities to include PROJECT MUSE titles, in addition to the publishers/vendors it already works with. As a result, customers now have the option to create an integration profile with PROJECT MUSE, enabling them to automate the updating of their holdings.
The Automated Upload of Electronic holdings process has been instrumental in saving the library considerable manual effort and time. Furthermore, it has enhanced the accuracy and efficiency of the overall workflow.
For more information, see Automatic Upload of Electronic Holdings.
For more information on creating the Project MUSE integration profile, see Upload Electronic Holdings from Project MUSE.
Overlap Analysis - Include Related Physical Titles in Electronic Reports
In addition to the "Include Physical title matching indication in the electronic reports" that was released in May, a new checkbox enables users to also lookup Related physical titles and display a hint indication in the electronic reports. The Overlap Analysis tool, through Look Up Titles analysis type, now supports Physical Titles matches and Related Physical Titles matches.
While executing the existing analysis of Look Up Titles or Compare Collections, users receive a hint indication in the results Excel files regarding the availability/existence of a matching Physical inventory (a physical title that has one or more physical items). Once this type of match which has a related physical title with physical inventory is found, the job marks the related physical indication. This physical hint indication is included as 4 new columns in the Excel report:
- Has Physical Matching (Yes / No)
- Physical Holdings Library: Location (count)
- Has Related Physical Matching (Yes / No)
- Related Physical Holdings Library: Location (count)
The "Related" report incorporates a new column, Relation type that has the following values:
- Contains
- Empty
When the "Contains" indication is displayed in the new column, an additional indication (Related title) is displayed next to the MMS ID.
For more information, see Enhanced Overlap and Collection Analysis Tool.
A webinar on “New and Improved Alma Overlap Analysis Tool” will be delivered in two separate time zones on September 05, 2023. For further information and registration see the Alma 2023 Roadmap Webinar Series page.
Control Relinking a Portfolio to Different Bibliographic Record
Alma now supports controlling who can relink a portfolio to a different bibliographic record. We have implemented two measures to maintain the ability of existing users with the Electronic Inventory Operator role to relink portfolios to another bibliographic record. Firstly, a new privilege has been created to manage the visibility of the "Relink to another Bibliographic record" function. Secondly, a new role called "Electronic Inventory Operator - Limited" has been introduced. This new role is identical to the existing "Electronic Inventory Operator" role, except that the privilege to perform the "Relink to another bibliographic record" function is disabled by default.
If institutions have added the new Electronic Inventory Operator - Limited role and the "Relink" action on the portfolio is still displayed to users, it is possible that another role has been granted this privilege. In such cases, institutions should contact Ex Libris support to have the privilege removed from the relevant role.
For more information, see Relinking Items to Another Bibliographic Record.
Logical Collections
You can now assign titles to collections automatically based on a logical query instead of assigning them manually. To support this feature, a new Logical Collection checkbox was added to the Add New Collection page when creating a collection (Resources > Manage Inventory > Manage Collections).
For more information on adding logical collections, see Adding a Logical Collection.
In addition, you can now search for logical collections with the advanced search:
To support this development two new jobs are now available:
- Synchronize All Logical Collections – this scheduled job updates all logical collections according to their set queries.
For more information, see Synchronize All Logical Collections Job.
- Update Logical Collections from Set - this manual job updates the collection sets that you select according to their set queries.
For more information, see Update Logical Collection from Set.
-
Watch the Logical Collections with Automatic Title Assignment video (2:25 mins).
Long Term Digital Loans
Long term digital loans is a process by which libraries can lend out digital copies (representations) of physical materials to patrons for periods of a day or more. The system imitates the experience of lending physical items by enabling you to limit the number of digital copies being lent concurrently and configuring the time period of the loan. Like with physical items, the requester enters a waitlist if the digital copy is on loan. Alma keeps track of the patrons who requested the digital representation and notifies the next person in the waitlist when it is available. Users can also indicate the list of physical items that are represented by each digital resource.
Long term digital loans introduces a rich set of policies, is fully integrated into the Alma requests workflow, and is accessible from the patron Library Card in Primo. For more information, see Long Term Digital Loans.
To activate this functionality, contact Ex Libris Support.
Additional Advanced Search Options for Order Lines
New advanced search options have been added for Order lines:
- Alert
- Assigned User
- Assignment
- Creation Date
- PO Line in Claim
- Renewal Date
- Sent Date
For additional information, see Searching in Alma.
Additional EDI Responses Added to the Review Tab
Certain types of vendor responses to EDI orders, such as those that indicate the ordered item is out of print or not available from the vendor, are likely to lead to the cancellation of those orders by library staff. Alma automatically places PO lines that received such responses in the Review tab of the Manage EDI Tasks page (Acquisitions > Purchase Order Lines > Manage EDI Tasks). This makes it easier for staff to find these orders quickly, and also provides them with the option of cancelling these orders from within the Review tab.
Five new EDI order-response codes have been added to the list of those that are placed in the Review tab of the Manage EDI Tasks page:
- AU – Publisher's address unknown
- CS – Status uncertain: check with customer service
- HK – Paperback out of print: hardback available
- OP – Out of print
- PK – Hardback out of print: paperback available
For additional information about the Review tab of the Manage EDI Tasks page, see Electronic Data Interchange (EDI).
Restrict Editing of Bibliographic 035 Fields With a Particular Prefix
Consortia central office is able to control which 035 fields of the Network Zone Bibliographic records are protected, enabling the consortia office to maintain the quality of Network Zone Bibliographic records by preventing unwanted edits of specific fields.
Example use case:
Consortia Central Office can protect Network Zone bibliographic records 035 fields with particular prefixes from any edits or deletion by the consortia members.
For more information, see Restrict Editing of Metadata Fields.
Network-Zone Translations of Policy Names and Descriptions Are Now Distributed to Institutions
In an Alma system that supports multiple interface languages, some fields support translation of their values into the supported languages. (These fields are identified by the Translate Information icon - see The Alma User Interface.) When the environment is a Network Zone, these values are distributed from the Network Zone to the member institutions, so that users in the various institutions that belong to the Network Zone see these values in their current interface language. The Distribute Fulfillment Network Configuration job performs the distribution process for policies, Terms of Use, and fulfillment units configured in the Network Zone. (This job can be scheduled to run automatically - see Scheduled Jobs - or it can be run manually from Fulfillment > Advanced Tools - General > Distribute Fulfillment Network Configuration.)
The names and descriptions of some policies now support translation in multi-language environments, and are now distributed from the Network Zone to its member institutions by the Distribute Fulfillment Network Configuration job. Where relevant, they are also distributed to the Primo applications of those institutions. For example, the Policy Description of Due Date policies would appear in Primo in their translated form when Primo is opened in a supported language and translations into that language are defined for them.
For additional information, see Centrally Managing Configurations in a Network Zone; Configuring Fulfillment Information in the Network Zone.
Publishing Network Bib Records to OCLC Using the Network Zone MMSID
A new option for network members is added to the Publish Bibliographic Record to OCLC profile. This new option enables a member the choice of using the Network Zone (NZ) MMS ID for the NZ records being published.
This is helpful for network members that import records from OCLC to their network zone and need OCLC to have their network's system number.
Restrict Editing Bibliographic Metadata Fields
The Consortia central office can control which bibliographic metadata fields can be edited by its members, enabling it to maintain the quality of the Network Zone bibliographic records by preventing unwanted edits/deletion of specific fields.
This is applied only to the consortia members. The Network Zone institution is exempt from the restrictions policy that it implements.
Separating User Search by Library Affiliation
Libraries that implement library independence can now be set up to separate also their users search by library scope. This way, operators from one library cannot search for patrons of another library. Setting this option is done by using the Configuration menu > User Management > General > Other Settings menu to set the limit_user_search_by_library_scope parameter to true.
This addition to the library independence theme creates an option for improved privacy of user records in the Alma institution.
See Library Independence and Fulfillment Library Independence.
Option to Hide User Contact Card
Removing the privilege to view user pop-up cards from user roles is now possible. To remove the privilege, please contact Ex Libris support.
Sign SAML AuthnRequest
Some institutions require that SAML authentication requests must be signed to be accepted by the system. Until now, there was only the option to sign the logout requests. Alma now supports the SAML authentication requests that are signed.
For more information, see Gathering Information from Your Identity Provider in the Developers Network.
Mail Handling Integration Profile - Test Email Button
Alma's Mail Handling integration profile now includes testing the email configuration. When executed, an email is sent to the preferred email of the logged-in user. Testing the configuration is accessed by: Configuration > General > External Systems > Integration Profiles. Locate the Mail Handling profile and select Edit from the row actions. Select the Actions tab.
For more information, see Configuring Outgoing Email.
Regenerate Public Key in S/FTP Profile
Previously, the Public Key associated with an S/FTP profile remained static and could not be updated or refreshed. However, this constraint has now been rectified, and users can now refresh the Public Key by following these steps: Go to Alma configuration > General > S/FTP definitions and click the Regenerate RSA Keys.
For more information, see Configuring S/FTP Connections.
Code Tables Enhancements
The following improvements aim to enhance the functionality and usability of code tables, providing users with a more intuitive and efficient experience.
-
Inner Search: An inner search functionality has been added to enhance the code table experience. Users can now search within the code table to quickly locate specific entries.
-
Drag and Drop: A new drag and drop feature has been implemented, allowing users to easily rearrange and reorganize code table entries by dragging and dropping them into desired positions.
-
Responsive Columns with Text: To improve readability and user experience, code table columns now display text instead of fields, making navigating and understanding the content simpler and more intuitive.
-
Page Titles: Page titles have been incorporated as headers for code tables, providing clearer context and easier identification of code table content.
-
Pagination: A pagination feature has been introduced to effectively manage large code tables. Users can now navigate through code table entries using page numbers, creating a more efficient and user-friendly experience.
For more information, see Code Table Enhancements.
Enable Removal of Global Embargo from Community Zone Portfolios in Community-Managed Collections
Previously, users had the ability to edit Community Zone data for titles in Community-Managed Collections. However, they could not remove the global embargo from portfolios within these collections. Now, the community-managed collections in the Community Zone enable Alma users to utilize all editing options for both Collections and Portfolios.
For more information, see Contributing to the Community Zone – Portfolios.
Add SAML Metadata URL By Institution Code and Integration Profile
Alma enables users to add or use a SAML Metadata URL link by providing an institution code and the integration profile code. You can link to the metadata file (that is configured at a specific integration profile) by:
For more information, see the SAML documentation in the Developers Network.
New and Improved Letters Configuration Interface
A new letters configuration interface was implemented, to create an improved and more intuitive user experience. This includes:
-
XSL/XML and preview of the output, now all in one window.
Letters Preview Window -
Error detection and reporting while editing.
-
Enhanced preview pane with easy navigation between visual and html view.
-
Quicker access to configuration of labels and letter examples.
-
New save draft feature.
For more information see Configuring Alma Letters.
A webinar on “The New User Interface for Customizing Letters in Alma” will be delivered in two separate time zones on August 09, 2023. For further information and registration see the Alma 2023 Roadmap Webinar Series page.
Enable Easy Rollover of Alma Signed Certificate for SAML Authentication
When the expiration of an Alma SAML certificate is imminent, customers are required to make two necessary adjustments. Firstly, they need to modify the integration profile in Alma, ensuring that the new certificate is incorporated. Secondly, they must update the Identity Provider (IDP) settings to utilize the recently generated certificate for authentication purposes. These 2 steps needed to be done simultaneously in order to avoid a period of time when the SAML authentication is down for maintenance.
Customers now have the capability to configure an additional certificate in Alma, and then update the IDP at a later time.
When a request for authentication is made to Alma, the system attempts to use both certificates, ensuring compatibility with both the old and new certificates.
For more information, Replacing a Signed Certificate.
Customize Alma Homepage to Display Data Visualization Workbook
Alma enhances its main menu functionality by enabling users to customize their homepage to display a Data Visualization Workbook. The dashboard drop-down menu is moved from the Analytics menu to the Main menu above the search bar.
Update SAML Self-Signed Certificate to Use SHA2
The current Self-Signed SAML Certificate (expiring on December 31, 2025) uses the SHA1 hash function. If your institution uses this certificate you can replace it now with a new certificate that uses the SHA2 hash which expires on December 31, 2030. This must be done in coordination with your IDP. For more information, see Replacing a Signed Certificate.
No immediate action is needed. Replacing the certificate can be done at any time until its expiry, on December 31, 2025.
"Fuzzy Search" Added to Alma Menu Search Bar
Enhancements have been made to the Alma internal search menu functionality, incorporating "smart" search capabilities. As a result, the search feature now provides suggestions for synonyms, interchangeable terms, and even support for spelling mistakes. This enhancement facilitates users' navigation making it easier to find links in the Alma search menu.
Starting in August 2023, similar terms functionality will be supported only for English. Spelling is supported in the following languages: English, German, Spanish, Danish, Finnish, French, Hungarian, Italian, Japanese, Dutch, Norwegian, Portuguese, Romanian, Russian, and Thai.
Similar terms will be gradually enriched with additional languages in later releases.
Report Successful Primo Patron Logins
Before the May release, the "System Events" subject area reported successful sign-in events and included both Alma and Primo VE. After the May release, the login event no longer recorded for Primo logins and now reports only on Alma logins. As part of the August release, the System Events subject area includes two separate event types:
- Alma logins: Successful login
- Primo logins: Successful login - Primo
Institutions can opt out of the Primo events being reported by using the new customer parameter, enable_login_event (default is true), in the Discovery Customer Settings.
For more information, see the Discovery Customer Settings.
Analytics New Layout Now Available by Default
The Analytics New Layout that was made available as an opt-in option for the May release is now available by default for all customers. You can still choose to revert to the old layout (from > Feature Rollout Preferences). From the November release, the Analytics New Layout will be the only layout available.
For a Webinar describing the capabilities and functionality of the new Analytics user interface, see New Alma Analytics User Interface.
Search Analytics Object List by Object Creator
You can now search for Analytics Objects by object creator. To support this feature, Object Creator was added as an option from the Find drop-down list.
Searching by a partial search term is also supported.
Separate Sections for Analytics Menu Search Results
The search results that appear when searching from the Analytics Menu are now separated into two sections.
The upper section contains the objects created by your institution while the lower section contains objects that are available out-of-the-box.
Report Description from Analytics Displayed in Analytics Object List
You can add a description to reports in analytics (More > Description). These descriptions are now displayed for objects in the Analytics Objects List.
Displaying Labels for Local Parameters
It is now possible to display labels for local parameters in analytics reports. This is possible for the local parameters in the Physical Items > Holdings Details dimension and the shared Bibliographic Details dimension for all subject areas in which it appears. Now, not only the text Local Param appears but also the field assigned to the local parameter. The local parameter appears as a prefix before the current local parameter field name:
To display labels for local parameters, configure the new analytics_display_local_params parameter (Configuration > Analytics > General Configuration > Other Settings) to true.
Users must wait up to 24 hours after activating the customer parameter before the functionality will work in analytics.
New DV Button on Alma Analytics Menu Bar
A new DV button was added to the top menu bar of the classic Alma Analytics page.
Click the button to open the DV homepage in a new browser tab.
Expanded API Options
August 2023 API
The Alma API has been expanded to include the following new options:
- Location management – The Location API now includes the options to create or delete a library location. For additional information, see Configuration and Administration in the Developer Network.
- Library relations – A new Library Relations API is now available. This API can be used to retrieve, create, update, and delete library relations. For additional information, see Configuration and Administration in the Developer Network.
- Set management – A new API is now available for updating logical sets; see Sets in the Developer Network.
- Calendar management Idea Exchange – The Calendar API now supports the actions create, update and delete calendar, in addition to the previously supported action to retrieve a calendar. For additional information, see Retrieve Library Open Hours.
- Resource management – A new API for retrieving Import profile reports, for both Single matches and Multi matches, is now available. For more information: In the Developers Network, see Configuration and Administration > Jobs; in the Alma Online Help, see Viewing an Import Job Report.
UK Digital Content Store (DCS) Support for Lists Linked to Multiple Courses
The integration between Leganto and the UK CLA Digital Content Store (DCS) now supports lists that are linked to multiple courses. Items submitted to the DCS that are associated with multiple courses are sent to the DCS as individual requests, one for each course. If a new course is associated with an existing request, the requests are associated. When an item is linked to multiple courses, the DCS Status in Alma remains Request in progress until Alma receives a collective approval/rejection for all requests submitted for the item. The synchronization job between the DCS and Alma can be scheduled to run up to four times a day to update DCS request statuses. The DCS request statuses are updated using the current synchronization job between the DCS and Alma, which can be scheduled to run.
Currently, when a list is associated with one or more courses and one of the citations has DCS request, users cannot add/remove the course. The option to add/remove a course will be available in a future release.
If there is a DCS failure when extracting a citation, the Citation Alerts tab contains a Details column that includes the course code.
If multiple notes are received for the request, the value assigned to the Note field is multiple. You may need to check the DCS for more information.
For more information, see Integrating with the UKs Digital Content Store (DCS).
Search for Citations Within a Reading List
- Keyword (default selection) — When selected, this option searches the following citations' metadata fields for a match:
- Additional Person Name, Author, Book Author, Book Title, Chapter Author
- Chapter Title, Citation ID, DOI, Edition, Editor
- ISBN, ISSN, Issue, Journal Title, LCCN
- MMS ID, OCLC Number, Pages, Place of Publication, Publication Date
- Publisher, Resource Note, Source, Title, and Volume
-
Keyword searches for citations do not support the use of Boolean operators (such as AND or OR), and if these operators are specified, they are treated as keywords.
-
When special characters (such as hyphen, dash, slash, and so forth) are specified as search terms, the search will return results that both include and exclude the special characters.
- Citation ID
- Creator — The citation author's name. Note: Additional person names are not included in the search.
- ISBN
- ISSN
- MMS Id
- Title — Citation title
For more information, see Managing Reading Lists.
Filter Approval Requests by Date Range
For more information, see Digitization Approval Requests.
Option to Connect Citations to Library Resources by Title and Author Combination
Using the Resource Locate process, Leganto now provides more flexibility for matching citations to library inventory. The Resource Locate process runs automatically as citations are added to reading lists, manually on demand, or in bulk using a job. It is now possible to specify that a combination of the title and author fields can be used to identify matching resources in the library collection. The library can now configure, for example, that Leganto checks for a match using first ISBN/ISSN, and if a match is not found, check for a match using title AND author. The title and author must match the repository record for the citation to link to the bibliographic record.
To configure, enable the new parameter Title_Author in the Locate Citation by Fields table (Configuration > Fulfillment > Courses > Locate Citation by Fields). When the parameter resource_locate_mode (Configuration > Fulfillment > General > Other Settings) is set to OR, Leganto checks against all enabled fields in the order configured in the table.
For more information, see Match by Fields.
ACRL and IPEDS Dashboard
A new dashboard is now available that assists you in obtaining the information that you need to submit to ACRL and IPEDS. The dashboard is located under Alma > Shared Folders > Industry Standard Reports.
The dashboard has the following tabs that you can use to provide you with information for various reports, as required by ACRL and IPEDS:
- Library Staff
- Library Expenses
- Library Collections Number of Titles (Physical)
- Library Collections Number of Titles (Electronic) – applies to digital resources as well
- Library Collections Volume Count
- Library Circulation
- Interlibrary Loan Services
- Student Enrollment
Select the filters you require in each tab to produce the relevant data.
Create Analytics Objects from Network Reports Folder
Members of a Network Zone can now create analytics objects and create itemized sets from reports located in the network folder. The folder now appears when creating new analytics objects and when creating itemized sets from analytics:
To access this feature, the following parameters must be set to true:
- For the Network: analytics_catalog_available_for_members
- For the member: analytics_catalog_available_for_my_institution
Anonymization of Notes in Requests and Other Records
At times, personal information is entered into the Notes attached to requests and other records related to patrons. Alma's anonymization feature has therefore been expanded to make it possible to delete Notes as well as other patron information from closed loans, fines and fees, requests, and resource-sharing requests. Institutions can configure the anonymization job (Fulfillment - Handle Historical Archiving) to remove Notes from any or all of these sources. For additional information, see Configuring Fulfillment Jobs.
Option for Items Returned from Reading Rooms to Be Restored to Permanent Locations Immediately
A new option in the configuration of a reading-room circulation desk, Restore from reading room at checkin, makes it possible for items that have been temporarily moved to reading rooms to appear in Alma and in Primo as being restored to their permanent locations as soon as they are checked in for final return at the reading rooms. When this option is not selected, these items are only restored to their permanent locations when they are checked in at those destinations. The terms of use (TOU) of these items are set in accordance with their current locations, so this setting affects the time at which the TOU revert to their permanent settings, including the levels of fees and fines. For additional information, see Configuring Circulation Desks.
Additional Optional Fields Can Be Added to Resource-Sharing Task Lists
New optional fields are now available for inclusion in the rows of resource-sharing task lists in the New Layout.
The following optional fields can now be added:
Lending Request Task Lists | Borrowing Request Task Lists | ||
---|---|---|---|
Column 1
|
Column 2
|
Column 1
|
Column 2
|
These fields are hidden by default. You can choose which fields to include in your task-list displays, and where in the record display they should appear, thereby improving the visibility of those fields that are most important to you. To do so, in the task-list page, open the Customization menu (), and then select User customization > Record customization. For additional information, see New Layout 2022.
Borrowing Requests with "Ready to Be Sent" Status in Tasks List
May 2023 Fulfillment - Resource Sharing NERS Enhancement (ID #7934)URM-171534
The Tasks list of Borrowing Requests now includes links for borrowing requests that have the status Ready to be sent ("unassigned" and "assigned to me"). For additional information, see The Alma User Interface.
New Layout for Resource-Sharing Task Lists Is Now the Exclusive Option
The New Layout of Alma task lists is now the only available interface for the Borrowing Requests and the Lending Requests task lists. Users can no longer opt-out of this layout and use the previous layout.
The main new features of the new layout are:
- Details pane: A work area can be opened in a pane on the right side of the request list. This makes it possible to edit most aspects of the request without losing sight of the request list, and also speeds up the editing process.
- Multiple facet selection: Multiple criteria can be selected in each facet category, providing more flexibility in the creation of a filtered request list.
- Streamlined access to notes and patron queries: Notes and patron queries can be seen, added, and edited in the new right pane. This makes these important elements more noticeable and easier to manage when reviewing the request list or processing requests.
- Status and assignee information as facets: Activity status and assignee information are facet categories, enabling searching for requests by specifying multiple activity statuses and a number of specific assignees.
- Sliding panel: When access to the full request form, with all of its tabs, is required, it opens in a panel that "slides" out from the right side of the right panel, only partially covering the task list. This enables work on all aspects of the request without losing sight of the request-list context.
Enhanced Notes Section in Resource-Sharing Task Lists
The Notes section that appears in the Details pane of the resource-sharing task lists has been enhanced. It now provides an additional display mode, List layout mode, in addition to the Notes layout mode, which was previously available. The new layout mode supports searching within and sorting of the existing notes, as well as an alternative view of the notes themselves. To switch between the modes, select an option at the top of the section (). For additional information, see New Layout 2022.
Unused Labels Automatically Removed from Resource-Sharing Task Lists
Labels in resource-sharing task lists that are not attached to any records are now automatically removed from the list of available labels. This clears unnecessary clutter, making it easier to work with the list of labels. For additional information, see New Layout 2022.
Ship Digitally Directly from Download Electronic Resource Screen
May 2023 Fulfillment - Resource Sharing URM-184829
Alma now enables you to ship a digital request directly from the Download Electronic Resource screen. After downloading a digital request (Lending Request > Download Electronic Resource action), you can now use the Ship item digitally action to upload the electronic resource directly from the Download Electronic Resource screen. Additionally, more metadata is now available on this screen.
Sunset of the Classic Metadata Editor
After many years of service, the Classic Metadata Editor is retired and all work now continues in the new and improved Metadata Editor.
For more information on the new Metadata Editor, see Navigating the Metadata Editor Page.
Personalized Quick Links to Favorite Actions in Metadata Editor
It is now possible to create single-click shortcuts to your most commonly used actions in the Metadata Editor. The first actions also have a dedicated keyboard shortcut.
This enables each cataloger to customize the editor to suit their workflows and needs, increasing efficiency and ease of work in the Metadata Editor.
The Metadata Editor Quick Links menus are similar to the Alma menus. There are separate menus for records, templates, and rules (as the available actions differ). The Quick Links menu, opened at any given time, is according to the action menus displayed on screen. Each cataloger can add, remove or re-order their own quick links as they prefer.
For more information, see Personalized Quick Links to Favorite Actions.
New View Items Workflow in the Metadata Editor
The View Related Data menu now includes a new option called View Items, which enables quick access to the items list of the holdings record. This feature is particularly beneficial for cataloging physical resources and can enhance the efficiency of the process.
For more information, see Metadata Editor - View Related Data Menu.
Shortcut Customization UI Preference for Alt+Number Applied to Metadata Editor Menu Shortcuts
Users that select to disable the Alt+Number shortcut in their UI preference customization will also disable it for the Metadata menus. For users who rely on the Alt+Number shortcuts, we suggest using the Numbers Row on the keyboard instead of the Numpad numbers. This is because Numpad numbers may trigger external keyboard shortcuts as well.
For more information, see Global Alma Hot Keys.
Adding Cataloger Information to Record Versions from Other Network Members in Metadata Editor
When looking at the version information of a Network Zone record in the Metadata Editor that was created by another member institution, the cataloger could previously only see the member institution information. Networks can now enable seeing both the member institution and the name of the cataloger that created the version in it, by setting the customer parameter show_version_cataloger_name_for_other_members in their Network Zone institution (this will affect all members in the network).
For changes made by catalogers within the network, the version they create displays the network institution information.
This feature enables catalogers in consortia to easily identify the correct cataloger from the correct institution who updated the record, making cooperation and collaboration in the shared catalog more efficient.
Bibliographic Ranking in Metadata Editor and Record View
Alma now evaluates the completeness and richness of MARC 21 bibliographic records based on information that includes identifiers, names, subjects, informative LDR and 008 fields, publication details, etc. This is reflected in a new Bibliographic Rank, meant to provide a helpful tool for libraries to identify records that may need attention. The new bibliographic rank is displayed in the record view and in the Metadata Editor.
For more information on the bibliographic ranking, refer to:
- For Record View, see Record View Summary.
- For Metadata Editor, see Creating a MARC 21 Bibliographic Record.
Searching Records by Bibliographic Rank
A new search option for titles is added to aid libraries in identifying records that require attention. This option enables librarians to search for titles within a specific range of the new Bibliographic Rank. The search option is available after the completion of the May indexing process.
Enhanced Support for Parallel Description in Another Language of Cataloging Related Records Using MARC21
The MARC21 standard added a new type of analytical linking called "Parallel Description in Another Language of Cataloging" (788). Alma's workflows, such as publishing profile enrichment which considers analytical linking, now support this new type.
Skip Validations Option Added to the Import Mechanism
Previously, users were required to manually resolve import validation errors that occurred during the import process. This caused the import process to stop from the point the validation process occurred. The remaining records to be imported were not processed as a result. Now, the import mechanism was enhanced to provide an option to skip validations and enable the process to complete automatically without requiring manual handling.
For more information on the import profile configuration, see Creating/Editing an Import Profile.
Refine Related Records Enrichment as Part of the General Publishing Profile
As part of the general publishing process, the process of enriching related records is more sophisticated. It now involves creating an inventory of related records based on the data provided in the bibliographic record.
Pointing to a specific item of a related record is cataloged as follows:
Value in $g (MARC21 / KORMARC) $v (Unimarc / CNMARC) |
Item field | |
---|---|---|
Year | yr: | Chron I |
Volume or barcode | no: | Enum A |
Issue | iss: | Enum B |
Part | pt: | Enum C |
Pages | p: | pages |
For more information, see Add holdings/items of related records.
Searching for Standard Number Source
Once the semi-annual indexing is complete in your environment, a new advanced search index called Standard Number Source will be available. This index enables you to search for the standard number source indicated in the following fields:
- 015 $$2
- 016 $$2
- 022 $$2
- 024 $$2
General Publishing at the Campus Level
(Updated - November 19, 2024) Institutions with multiple campuses are able to configure their publishing profile to publish their bibs per campus (in addition to the existing options of per institution or per holdings record), using their campus codes or OCLC symbols. This is especially useful for institutions that want to share the availability of resources on their different campuses.
For more information, see:
Semi-Annual Re-indexing
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:
- Searching for Standard Number Source, see here.
- Searching Records by Bibliographic Rank, see here.
- Edition Information Display in Search Results Enhanced to Support ISBD Cataloging, see here.
- Field 070 Added to NAL Call Number Index, see here.
- Enhanced Support for Parallel Description in Another Language of Cataloging Related Records Using MARC21, see here.
- UNIMARC Bibliographic 7XX $4 Includes a Closed List of Values, see here.
New Authority Index: Other Standard Identifier (024)
The staff search now includes a new identifier called Other Standard Identifier (024) as part of its authority index. For more information, see MARC 21 Authority Search Index Mapping.
Import Report Enhancement
Enhancements have been made to the import reporting process, with the addition of separate reports for single matches and multi-matches. For more information, see Viewing an Import Profile Job Report.
New Authorized Field CNMARC 702
An additional access point is incorporated into the CNMARC 702 field.
Add Not Contains or Not Equals to Alma Titles and Inventory Search Indexes Where Contains or Equals Currently Exist
It is now possible to run Not Equals and Not Contains searches in the titles, inventory & authority searches, enabling more powerful and detailed searches in the catalog. As part of the development:
- Not Contains search operators were added to indexes where the index supported a "Contains" search.
- Not Equals search operators were added to indexes where the index supported an "Equals" search.
When searching with a lower-level index (an index that belongs to an entity contained in the searched entity, for instance, searching for physical holdings by item data, searching for electronic titles by portfolio data, etc.), a not contains or not equals search retrieves results where one or more entity matches the query. For example, when searching for physical titles where holdings' location "not equals" stacks - if a title has two holdings, one fulfilling the condition (location=reference) and another not meeting it (location=stacks) - the search finds this title since it has holdings that match the search criteria.
The indexes indicated below remain as is and do not have the option to search by Not Equals, Not Contains, and Not Empty:
-
CDI Search Rights
-
CDI Fulltext Rights
-
CDI Fulltext Link
- CDI Types
- CDI Newspapers
- CDI Collection ID
Due Date Added to Items List
Presently, operators cannot easily view the due date of items in the Items List and need to check each loan individually. A new column can now be added to the physical items table, containing the due date of items on loan.
The new column can be added to the physical items table by clicking on the cogwheel icon in its top right corner.
For more information, see Working with the List of Items.
New and Generic Physical Items Material Types
Alma now offers an increased range of physical material types, including generic options that libraries can customize according to their requirements. This update is particularly advantageous for libraries with specialized materials, such as medical libraries that lend anatomical models, as they can now tailor the available type descriptions to their specific needs.
Institutions can activate several new material types in their Alma environment, including HathiTrust Material, Fascicule, Microphone, Locker, and Musical Instrument.
For more information, see Configuring Physical Item Material Type Descriptions.
Community Zone Updates Task List to Include Indication Regarding Collection Level Management
Currently, Community Zone (CZ) operation planned activity such as deletion of electronic collections are communicated in advance to Alma customers via Community Zone Release Notes. The existing CZ Update Task List now indicates to the institution the changes made to the CZ collection's management level, users can focus on these changes by selecting the “Electronic Collection Management Level in Community Zone field updated” option from the Report Type filter.
This is mostly relevant for institutions to see what the planned changes are to CZ content, by reviewing collections that are planned to be deleted in the near future. This enables institutions to prepare in advance for any potential change which have an impact on the institution’s electronic CZ linked inventory.
Additionally, a new Management Level in Community Zone search index can be found under "E collection" and users can search under the Institution Zone (IZ), Community Zone (CZ), and the Network Zone (NZ).
For more information, see Actions on a Collection Following a Community Zone Update.
This functionality of searching for the Management Level of an Electronic Collection is fully functional only after the semi-annual Alma re-indexing.
Overlap Analysis Job Supports Physical as well as Electronic Titles
Customers have the ability to upload a list of titles and compare it with the institution’s Electronic (supported) and Physical holdings (or both). This enables the institution to make informative decisions regarding titles/collections that they own or would like to purchase and as a result, potentially assist the institution to manage the financial budget expenses/savings.
For more information, see Enhanced Overlap and Collection Analysis Tool.
Public Access Model to Support Subscription Titles
For the Upload Electronic Holdings of ProQuest Ebook Central, the only titles that were previously passed to Alma with the Public Access Model information are "Owned" titles. Now Alma facilitates the ability to attain the Public Access Model value also for "Subscription" titles. This enhancement automatically adds a "UA (Unlimited Access)" access model for all Subscription titles.
For more information, see Proquest Ebook Central Upload Electronic Holdings - Addition of Public Access Model Information.
The data for existing portfolios in your institution is updated gradually.
Alma Integration with InCites
The Alma Collection Report in InCites is intended to help institutions to get insights about their holdings regarding publication types, research areas, usage, and publication model trends. Data shared from Alma is used exclusively to generate this report for institutions using Alma and is not shared with other Clarivate products or services.
InCites data is refreshed on the last Friday of each month. As such, from the time a customer opts in, they either see the report showing up with data at the end of the month, or, they should see the report with data the following month.
For general information on the Alma integration with InCites, see InCites and Alma integration enhancements on collection development reporting.
For more information on how to share your data with Web of Science, see How to activate and use the Journal Citation Reports (JCR) cloud app and the Developers Network blog regarding Journal Citation Reports (JCR) cloud app.
HAN Integration Enhancement
Users of the HAN proxy who are utilizing HAN’s multi-license functionality can now manage various licenses in Alma to accommodate the scenario where an electronic resource can have a distinct service per license, in the View It section. For example, this feature is intended to address situations where different levels of access to the E-Resource are required depending on the type of patron, such as researchers or external users. The option to enable this enhancement is controlled by the customer parameter: han_proxy_multi_license (located in Alma Configuration > Resources > General > Other Settings).
Display logic rules handle these as one bulk.
For more information, see Configuring Other Settings (Resource Management).
Change Electronic Portfolio Information Job Now Supports the Public Access Model Field
The existing job Change Electronic Portfolio Information is enhanced by supporting the Public Access Model field. This enables updating the Public Access Model field on a predefined set of portfolios.
For more information, see Manual Jobs and Their Relevant Parameters.
Editable Lines in Closed Invoices
- Subscription dates range (unless Accrual mode is enabled)
- Additional information
- Check subscription date overlap
- Price note
- Note
- Reporting Codes 1-5
Editing of closed invoice lines can be performed manually in Alma or through the API (except for Reporting Codes 4 and 5). Institutions can block the option to edit closed invoice lines by changing the setting of the allow_edit_closed_invoice_line Customer Parameter to false. For additional information, see Creating Invoices.
New PO Line Facet: Vendor Account
A new facet has been added for PO lines: Vendor Account. This facet is now available in the Order lines search results and in the PO Lines tab of the Vendor details page (Acquisitions > Acquisitions Infrastructure > Vendors > [select vendor] > PO Lines tab). Institutions can now very easily and quickly filter a list of PO lines by vendor accounts, which can improve workflows when there is a need to focus on PO lines from a specific vendor account. For additional information, see Reviewing PO Lines.
From Year Now Included in Rollover Ledgers Report
The From Year of the Rollover Ledgers job report is now displayed in the report results. This can be helpful for analysis as well as for customer support. For additional information, see Viewing Completed Jobs.
New SAML Certificate
The current DigiCert SAML Certificate will expire on June 8th. If your institution uses this certificate, Ex Libris recommends that you consult with the IT dept. in your institution, and if required, replace the certificate for Alma and/or Primo VE. If replacing the certificate, this must be done in coordination with your IDP. For more information, see Replacing a Signed Certificate.
If your institution uses ADFS, Ex Libris highly recommends that you replace the certificate to avoid any complications.
User's Role Profiles Now Recorded in Account Notes
May 4 Update - The feature was not included in the release on May 7. It will be released with the Release Update on May 14.
Users' role profiles are now recorded in the user-account's Notes tab when they are applied. This makes it possible to find all users to which a particular role profile was applied in the past, by searching for the role profile's name or ID number. A logical set of these users can also be saved, and used as input for the Update/Notify Users job, which can update the roles assigned to the users in the set. For additional information, see Roles and Registration Configuration.
Enhanced Sections Component for New Layout of Record Lists
In the New Layout of record lists, the Sections menu of the Details pane, which provides quick navigation between record sections, has been redesigned and enhanced. It is now located in the center of the page and can be expanded and collapsed as desired, making it more flexible and easier to work with. In addition, it provides a variety of convenient features, including:
- Display in Split-view mode, with panes that can be resized
- Counters in parentheses indicating the number of entities currently defined in the section (for sections that may or may not contain any data - e.g., Notes (2) to indicate that two notes exist in the Notes section)
- Indicators (*) beside sections that contain mandatory fields (in Edit mode only)
The new Sections menu has thus far been implemented in the following record lists:
- Resource-sharing task lists
- PO line lists (early testers only)
- Analytics object lists
- Physical Holdings search results
For additional information, see New Layout 2022.
Detailed Description for Menu Items
In order to enhance ease of use and clarity in the Alma menu, a new feature has been implemented. Users can now hover over a link (before clicking it) to view a brief description in the "Additional Information" area, located at the bottom of the menu. To activate or deactivate this feature, simply click the arrow in the "description" box.
Enhanced Advanced Search Functionality with Fast Erasing Capability
The "fast erasing" new feature is implemented in Advanced search, enabling users to expedite their search process. The feature includes the ability to "erase" search fields by clicking an "X" rather than selecting the text and then deleting it.
This functionality is currently only available in the updated Advanced search sections such as Physical Holdings.
Library Independence for Alma Analytics
The Library Independence feature allows you to restrict the data that appears in Analytics reports to include only data from a specific library. This prevents the users from viewing unauthorized data and enables librarians to focus only on the relevant data for their libraries.
For more information, see Working with Library Independence.
Analytics New Layout Developments
The following new features are released relating to the new Alma Analytics Layout:
Change to Analytics New Layout Rollout Schedule and Known Issues
URM-189353The schedule of the phased rollout of the new analytics layout was changed. The new schedule is as follows:
- May release – The previous version of the layout is displayed by default, but you can configure Alma Analytics to display the new version.
- August release – The new version of the layout is displayed by default, but you can configure Alma Analytics to display the previous version.
- November release – The new version of the layout is the only version available.
There are several known issues regarding scheduling reports when moving to the new analytics layout. For more information, see Transitioning to the New Analytics User Interface.
Filter Analytics Object List by Badges
URM-182379You can now filter the Analytics Object List by the following badges:
- Scheduled
- Widget
- Subscribed
- Homepage Dashboard
For more information on the Analytics Object List, see Working with Analytics Objects.
Analytics Object List Now Customizable
URM-189600You can now customize many elements of the Analytics Object List and determine which section appear and in what order. To customize the Analytics Object List, select the customization icon at the top right of the page. The following options are available that enable you to configure the sections of the edit view, the actions available for the records, and the elements displayed in the record view:
For more information, see Customizing the Analytics Object List.
Out-of-the-Box Reports Removed from Analytics Objects List
URM-182159Out-of-the-box reports no longer appear in the drop-down list when creating analytics objects, since they cannot be used to create analytics objects. If you want to share or schedule an out-of-the-box report, save the report in your institution folder with a new name and create the analytics object with that copy.
For more information on analytics objects, see Creating an Analytics Object.
Exporting Analytics Object List to Excel
URM-182766You can now export the Analytics Object List to Excel format. You do this by selecting the export icon located above the list. The following fields are exported:
- Type
- Display Name
- Report Name
- Description
- Subject Areas
- Analytic Folder
- Add as widget
- Out of the Box Reports
- Schedule Report
- Add as dashboard
- Source System
- Object Creator
- Object Creation Date
Report Preview Available for Data Visualization Reports
URM-187262The Report Preview area of the Analytics Objects List now also displays Data Visualization reports. This enables you to view a preview of the report without having to open it in the analytics interface.
Scheduling Data Visualization Reports
URM-184526 URM-185935You can now schedule Data Visualization (DV) reports as you can for analytics dashboards and reports. Users subscribed to receive the DV reports receive a link to the DV report that they can select to display the report. Since sending DV reports as an attachment is not possible, the only option is to send a link to the live report. Note that opening the link requires the receiver having the appropriate role or permissions to view the report.
For more information, see Scheduling and Subscribing to Reports and Dashboards.
Alma Menu Features Now Support Analytics
URM-189470The following Alma menu features now support Alma Analytics:
- Quick Links
- Recent Pages
- Search for Any Link
Out-of-the-Box Dashboard Prompts for Library Independence
You can now add an out-of-the-box prompt that is pre-configured for library independence to dashboards. If the user has the Library Level Analytics Consumer role scoped to specific libraries, the prompt displays the library names within the user’s scope from which the user can filer the reports of the dashboard. The prompts are located in the same location as the Library Code Active filters (Shared Folders > Alma > Subject Area Contents > SUBJECT AREA).
DV Dashboard Templates for Library Independence
Out-of-the-box DV dashboard templates are now available with the Library Code Active filter already configured. You can use these templates to create dashboards that are filtered to the scope of the user. The dashboards are located in the same location as the Library Code Active filters (Shared Folders > Alma > Subject Area Contents > SUBJECT AREA). To use these dashboards, you must save them to a local location.
For CLA Users (UK): Course Synchronization Between Leganto and the DCS
Librarians who have courses in the DCS that do not match the Leganto courses can now override the course in the DCS with information from Leganto. When the integration profile Digital content store is active, the option to update DCS courses is now available from the Course Bulk Update job (Admin > Manage Jobs and Sets > Run a Job). When Update course in DCS is checked in the Course Bulk Update job, librarians can now update their DCS courses in bulk to match their Alma courses.
The following parameters are all automatically updated in the DCS course based on the values in Alma:
- Course code
- Course name
- Number of weeks
- Number of participants
- Processing department
- Instructor name
- Instructor email
- Course status
- Active - sets the DCS course to Active
- Archived - sets the DCS course to Archived
- Inactive - sets the DCS course to Archived
The job event now includes a Failed to update DCS event.
For more information, see Course Synchronization Between Leganto and the DCS.
Customize Copyright Approval and Reject Reasons
You can now customize the copyright approval and reject reasons (Fulfillment > Resource Requests > Approval Requests List).
Copyright approval reasons list
|
Copyright rejection reasons list
|
You can customize the approval and reject reasons using the Configuration > Fulfillment > Copyright Management > Copyright approval reasons and Configuration > Fulfillment Copyright Management > Copyright reject reasons tables. You can edit any of the existing reasons or use the Add Row button to add new reasons. The reasons can now be translated to the Alma display language.
For more information, see Customizing Copyright Approval and Reject Reasons.
Enrich Multiple Citations Using DOI
Leganto can now automatically enrich citations containing a DOI with additional metadata in bulk by checking Enrich by DOI in the Reading List Citation Update Task job (Admin > Manage Jobs and Sets > Run a Job). The default setting for this checkbox is unchecked.
For more information, see Enriching Citation Metadata.
Find Matching Bibliographic Records for Multiple Citations - Run Resource Locate on Citation Sets
It is now possible to locate a set of citations by using the new Reading List Citation Process and Enrich job (Admin > Manage Jobs and Sets > Run a Job). Perform locate on type is not included in this new version of the Process and Enrich Citations job (Fulfillment > Advanced Tools - Reading Lists > Process and Enrich Citations). When Resource locate repository is checked (this checkbox is unchecked by default), you can choose to either manually handle citations when multiple matches are found or use the first matching resource for a specific inventory type. When Use first matching resource of a specific inventory type, if exists (otherwise handle manually) is selected, drop-down lists for Physical, Electronic, and Digital are displayed. The default priority selections for these drop-down lists are set according to your priority settings in resource_locate_multiple_matches_priority (Configuration Menu > Fulfillment > General > Other Settings).
The Process and Enrich Citations job (Fulfillment > Advanced Tools - Reading Lists > Process and Enrich Citations) is still available for use.
You can use the Reading List Citation Process and Enrich job to perform a resource locate on a specific set by selecting a specific facet, such as the new Not located facet, which returns all citations that do not have a Resource located status.
Easily Identify Citations that are Not Located
The Resource Locate facet (Fulfillment > Course Reserves > Citations) now includes a Not Located facet which accounts for all resources with the statuses Multiple Resources Located, Locate Not Run, No Resources Located, Locate Failed, and Information Incomplete.
For more information, see Reading List Citation Process and Enrich and Manual Jobs on Defined Sets.
Alma Support for Japanese Library Systems
As part of Ex Libris's commitment to the Japanese market, we have developed a range of Alma features that are specifically geared to the requirements of Japanese libraries. The primary developments in this sphere are described below.
Integration of Alma with the NACSIS Catalog
Alma can incorporate the NACSIS central catalog in its metadata management system, and supports the following NACSIS-catalog features:
- Holdings management (NACSIS Cloud App)
- Bibliographic and authorities management:
- Copying of cataloging from NACSIS to Alma (NACSIS Cloud App)
- Contributions from Alma to NACSIS
- NACSIS member-information management (NACSIS Cloud App)
- MARC21 to/from CAT-P crosswalk
For additional information, see Integration with NACSIS-CAT/ILL.
Integration of NACSIS-ILL Resource Sharing
The integration of the Japanese NACSIS-ILL Resource Sharing system with Alma makes it possible to create new NACSIS-ILL borrowing and lending requests in Alma, and to manage the entire workflow of borrowing and lending requests within Alma. It supports the following features and processes:
- Ability to create new NACSIS borrowing requests (NACSIS Cloud App)
- A sync job to retrieve NACSIS ILL request statuses into Alma
- Resource Sharing workflow is performed within Alma, and actions are pushed to NACSIS, including the following actions:
- Borrowing-request actions: Receive, Return, Cancel, Renew Request, Accept, Callback
- Lending-request actions: Ship, Check In, Reject, Renew Reply, Accept, Callback
For additional information, see Integration with NACSIS-ILL.
JP-KBART Support
The Alma portfolio loader can import JP-KBART portfolios of electronic resources from vendors to the library's electronic collections. For additional information, see Managing Electronic Resources.
Option for Identifying the Creator or Modifier of an API Request
When API requests are sent to Alma, and an entity (an item, user, invoice, etc.) is created or updated, the modifier/creator is recorded. Until now, this was always API, Ex Libris. Alma can now be configured to register the modifier/creator of an entity as the application/API-key instead of this default user name. This makes it possible to identify which application updated an entity when multiple applications use the API for this purpose. To turn this option on, under General Configuration > Other Settings, set the detailed_creator_and_modifier_for_api_changes Customer Parameter to true. For additional information, see Registering updates by API according to the API-key name.
Send Patrons Their User Data by Email
Users with user-management roles can now send patrons the complete XML record of the data stored about them in their user accounts, including attachments, from the User Details page. The XML file is sent to the patron's preferred email as an attachment to the Personal Information Letter. For additional information, see Managing Users.
Additional Parameters for Automatic Loan-Renewal Rules
Two powerful new types of parameters can now be used in configuring automatic loan-renewal rules: locations and statistical categories:
- Locations: Location-based auto-renewal parameters make it possible to create distinct rules for locations within individual libraries. For example, items in reading rooms, for which automatic renewal is not allowed, and items in other locations in the same library, for which renewals are permitted, can have different automatic renewal rules.
- Statistical categories: Primarily used for analytical reports, statistical categories are created by institutions and assigned to patrons as required. Examples of possible statistical categories are "Citizenship" (with possible values Australia, Canada, China, and so forth) and "Degree Program" (Bachelor's, Masters, PhD, and so forth). Employing statistical categories as parameters in automatic loan-renewal rules makes it possible to fine-tune auto-renewal rules for the various types of patrons served by the institution.
For additional information, see Configuring Automatic Loan-Renewal Rules.
User Statistical Categories as Parameters in Fulfillment-Unit Rules
Request-Cancellation Reasons Now Customizable
It is now possible for each institution to customize the list of request-cancellation reasons that appears in the dropdown list of reasons when cancelling requests like holds or resource-sharing borrowing requests. The text displayed for each of the standard reasons can be modified, and reasons that are not relevant to the institution can be removed from the dropdown list. In addition, the institution can create up to ten new reasons to add to the dropdown list. These new options enable the institution to create a list of options that only includes reasons that are actually in use in their libraries, thus preventing problems that arise when an inappropriate reason is selected. The list of cancellation reasons can be edited at Configuration menu > Fulfillment > Request Cancellation Reasons. For additional information, see Configuring Request Cancellation Reasons.
Customization of Resource-Sharing Record View and Row Actions List
Users can now customize the task lists of the resource-sharing borrowing and lending task lists by choosing which fields will appear for each item, and the order and locations in which they will appear. In addition, the order of the row actions of each task can now be configured, and options that are not required can be hidden from the list entirely.
These new options add to the flexibility of the task lists, and enable libraries to improve the efficiency of their work by reducing clutter and making the fields required for their workflow easier to locate. Future releases will add additional fields to the task lists, further expanding the configuration options.
For additional information, see Customizing the Record Display; More Actions and Main Action Buttons.
Storage Location ID Updates
February 2023 Resource Management
The updates are especially useful for libraries that work with remote storage facilities and hold the storage ID on their physical items in Alma.
-
Including Item's Storage Location ID in Z39.50 Response
It is now possible to include a physical item's Storage Location ID in the Z39.50 response, when querying the server using the OPAC format. This enables systems that rely on the item's Storage Location ID to expose this information for third party integration using the Z39.50 server.
For more information, see Z39.50 Search.
- Storage Location ID Available in the Physical Items Search Results
The item's Storage Location ID is available to add to the physical items search results page. For more information, see Searching in Alma.
- Storage Location ID Added to the Physical Items List
A new column, Storage Location ID, is now available to add to the items list. For more information, see Physical Items.
Alt Key Menu Keyboard Shortcuts in New Metadata Editor
It is now possible to easily and quickly access the menus in the new Metadata Editor using a keyboard only, to increase cataloging efficiency and ease of use. This is especially useful for catalogers that rely on keyboard shortcuts in their work.
For more information, see Global Alma Hot Keys.
Open GND Authority Records in New Metadata Editor View Mode
Catalogers that do not have sufficient privileges to edit GND authority records (based on cataloging level) can now open the authority records in the New Metadata Editor view mode and perform permitted actions such as duplicate records and others. For more information, see Working with the Gemeinsame Normdatei (GND) Integrated Authority Records.
Show List of All External Resources Instead of a Search
Previously in Alma, the Resource Management Configuration > External Resources only enabled an option to search for a specific resource. Now, Alma enables the option to Show All Resources that lists all available external resources. This allows users to browse through all resources.
For more information, see Configuring External Search Resources.
Import Enhancements
- Using Normalization Processes When Creating Inventory and POL Using Import Profiles
Previously the inventory and POL mapping in the import profile used the source records from the input file as they appeared in the file. It is now possible to use a dedicated normalization process in the import profile to update the data used in inventory and POL mapping. For example, a library may remove the currency information from the List price field, or add a temporary location information to the field mapped to items. The normalization will only be applied for inventory and for PO Lines, and will not be part of the record when saved to the catalog. For more information, see Creating/Editing an Import Profile: Normalization and Validation.
- Assign Cataloging Level to Imported Records
A new option was added to define the cataloging level assigned to records imported to Alma using the MD import profile.
-
New records - assigned with the configured cataloging level.
-
Matched records - if the existing cataloging level is equal to or lower than the cataloging level configured in the import profile, the cataloging level configured will be assigned to all matched records. Otherwise, records are rejected and reported in the import report.
For more information, see Creating/Editing an Import Profile: Set Management Tags. -
UNIMARC Profile Updates
- Enhancement of UNIMARC 100 Field Positions 25 and 34-35
UNIMARC field 100 positions 25 and 34-35 now support a closed list of values.
- Enhancement of UNIMARC 101 Field
UNIMARC field 101 has incorporated the following enhancements:
-
Field 101 has become repeatable
-
Enhanced the usage of the second indicator
-
Added support for $2
-
- Enhancement of UNIMARC Bib 100 $a-j
UNIMARC Bibliographic field 100 subfields a-j now supports a three-letter controlled vocabulary of country codes.
GND Profile Update
Some changes were introduced to the GND format.
Changes were made to the CV lists of the following subfields:
- 065 $a
- 380 $a
- 382 $a
- 667 $a
- 670 $a and $b
Updates to MARC21 Profile
The following MARC21 updates are now available for Bibliographic, Holdings, and Authority profiles:
- Update No. 33, November 2021
- Update No. 34, July 2022
In addition to the periodical updates, included are a few small fixes to the MARC 21 profiles. These fixes are detailed below:
In the MARC 21 Bibliographic profile:
- 383 - removed redundant values in second indicator
- 550 – removed redundant values in Second indicator
- Removed subfield ‘1’ from 880
- 610 $s – changed to Repeatable
- 034 – added subfield ‘0’
In the MARC 21 Authority Profile:
- 100 - Subfields ‘g’ and ‘s’ changed to Repeatable
- 111- Subfield ‘d’ changed to Repeatable
- 130- Updated the first Indicator to Undefined
- 336, 370, 372 – added Subfield ‘0’
- Added field 348
-
Field 378 updated to Not Repeatable
-
382 - added subfields ‘e’ and ‘t’
-
383 - Updated Second indicator to Undefined
- 670 - added subfield ‘w’
- 672 - added subfields ‘4’ and ‘5’
- 700 - Added subfields ‘1’, ‘4’, ‘I’. Updated subfields ‘g’ and ‘s’ to Repeatable.
- 400 – subfields ‘g’ and ‘s’ updated to Repeatable
- 450- added subfield ‘I’
- 500- added subfield ‘1’. Subfields ‘g’ and ‘s’ updated to Repeatable
- 511 – added subfield ‘j’
Control the Availability of Portfolios Automatically at a Pre-defined Date
Two additional fields have been added to the Portfolio Editor screen (as well as to the New Portfolio screen when adding a new local portfolio):
- Available from date - Specifies when the portfolio will be automatically set to "Available."
- Available until date - Specifies when the portfolio will be automatically set to "Not available."
The image below presents the new fields in the portfolio editing screen:
These two fields enable users to set a date which defines:
- When the portfolio will become "Available"
- When the portfolio will become "Not available"
- A date-range in which the portfolio will be "Available"
A daily job (Electronic portfolio availability update) runs every day and checks the dates defined on the portfolios and according to these dates, sets the portfolio as "Available" or "Not available".
These two new fields enable institutions who have electronic collections where they purchase 1 year of access for selected titles to set a date when these selected titles will be set as "Not available".
The Available from and Available until fields were also added to the following:
- Change Electronic portfolio information job
- API
For more information, see Editing a Portfolio Using the Electronic Portfolio Editor.
Ebook Central Upload Electronic Holdings - Addition of Public Access Model Information
Proquest Ebook Central Upload Electronic Holdings integration now includes information regarding the Access Model associated with the electronic resources. The Access Model information passed from Ebook Central is only passed for "Owned" titles. The Access Model information passed from Ebook Central is reflected within the "Public Access Model" field of the electronic portfolio.
The Public Access Model field reflects aggregated information regarding the portfolio's Access Model, see the table below for a few examples of the Access Model reflection in Alma and in Ebook Central:
Scenario | Ebook Central | Public access model presented on the portfolio in Alma |
---|---|---|
1 | Title has access model 1U | 1U |
2 | Title has access model 2x1U | 2U |
3 | Title has access model 2x1U and 3U | 5U |
4 | Title has access model 2x1U and 3U and NL | NL (5U once the NL is over) |
5 | Title has access model 2x1U and 3U and UA | UA |
Any new Public Access Model code and description are added to the Access Model configuration screen (Configuration > Acquisitions > Access Model).
Customers who use the "Old" (ProQuest Ebook Central Upload Electronic Holdings) job WILL NOT benefit from this enhancement and are encouraged to move to the new job.
To maintain the stability of the integration (as there may be many existing portfolios), Alma gradually populates the Public Access Model information for existing portfolios under the relevant ProQuest Ebook Central collection for all institutions (institutions that work with the newer job, only). Be aware that the gradual population process may take several weeks to complete.
Regardless of the gradual population process, newly added portfolios (in the daily update) will reflect this information immediately.
For more information, see ProQuest Ebook Central Upload Electronic Holdings Transition.
Electronic Service - Expiry Date Option for the Service Temporarily Unavailable Message
Today, when the patron clicks on View it to see the services of the resource, they see the Service temporarily unavailable message (if this was set). In order to set this message, a user needs to access the Electronic Service Editor page and set the date and Temporary Unavailable reason.
Within the Electronic Service Editor page, a new field Display unavailable message until date allows the Alma user to set a date where the Temporary Unavailable message will expire and no longer appear in the View it.
This saves the Alma user from the need to proactively move the Display temporarily unavailable message back to No.
The Update collection job was enhanced to add this new field.
For more information, see Activation Tab Options.
MARC 21 to DC Crosswalk Now Configurable
You can now customize the XSL file that maps the MARC 21 to Dublin Core crosswalk. This allows you to determine how MARC 21 records are converted when publishing to Dublin Core or Qualified Dublin Core formats. To support this feature, the new Digital Publishing Crosswalk XSLs link was added to Configuration > Resources > Record Export. To see this link, you must have the Catalog Administrator role with the Digital Publishing Crosswalks privilege selected.
- Select Digital Publishing Crosswalk XSLs (Configuration > Resources > Record Export). The following appears:
Crosswalk Configuration Files
- From the actions button, select Edit for the configuration file. The following appears:
Example Configuration File
- Edit the file and select Save.
The MARC 21 to DC crosswalk is implemented according to your customizations when publishing MARC 21 records to DC.
For more information on publishing, see Publishing and Inventory Enrichment (General Publishing).
Internet Archive Book Reader (IABR) Now Supports Right-to-Left Paging
The Internet Archive Book Reader (IABR) now supports right-to-left paging when reading books in right-to-left languages. To support this feature, the new Paging Direction by Content Language option was added to the Service Details tab when configuring IABR (Configuration > Fulfillment > Discovery Interface Display Logic > Viewer Service > Internet Archive Book Reader).
- ara - Arabicfield
- arc - Official Aramaic (700-300 BCE); Imperial Aramaic (700-300 BCE)
- aze - Azerbaijani
- div - Divehi; Dhivehi; Maldivian
- per - Persian
- fas - Persian
- hau - Hausa
- heb - Hebrew
- kas - Kashmiri
- khw - Khowar
- kur - Kurdish
- pus - Pushto; Pashto
- sam - Samaritan Aramaic
- syc - Classical Syriac
- syr - Syriac
- urd - Urdu
- yid - Yiddish
For more information, see Configuring Right-to-Left Paging for the Internet Archive Book Reader.
Alma Viewer Enhanced to Improve Display of the File
The following adjustments were made to the Alma viewer to provide enhanced focus on the file content:
- The Alma viewer user interface was redesigned to provide more space for file content.
- The Alma Viewer was enhanced to enable you to configure the Contents and Descriptions panes to be collapsed by default and to set a default zoom for PDF files.
This feature is configurable from the new Expand Content Pane, Expand Description Pane, and PDF Default Zoom configuration options located at Configuration > Fulfillment > Viewer Services > Alma Viewer.
Expand Content Pane, Expand Description Pane, and PDF Default Zoom Check Boxes - When the panes are collapsed, the buttons and file label are all located in the same toolbar.
Activation Notes in Electronic Resource Activation Task List
This feature will be supported in a future release.
Activation notes are now included in the Electronic Resource Activation Task List (Resources > Manage Inventory > Manage Electronic Resource Activation). An activation note is a note that is added to the PO line of an electronic resource and displayed in the activation task list during activation of the resource, enabling the person creating the PO line to provide relevant information or instructions to the one activating it. They are similar to the Receiving Notes that can be attached to PO lines of physical resources (see Manually Creating a PO Line).
Activation notes cannot currently be created in Alma (although they will be supported in the future – see New Unified PO Line Task List), but if a PO line for an electronic resource was migrated from another system, and it had a receiving note attached to it in the previous system, the content of that receiving note appears as an Activation Note in Alma.
Improve the UI/Discoverability of the License Terms Translatable Text Area
Alma has improved the UI/discoverability of the translatable text area for License Terms. A globe icon is added, that when clicked, opens a screen similar to regular translatable fields. The UI will be populated based on the contents of the text area, and when closed, will add the correctly-formatted text to the text area.
For more information, see Managing Licenses and Amendments.
Library-Level Statistical Categories
A new option, library-level statistics, has been added to Alma, and is available in institutions in which library independence has been established (see Library Independence). When this option is activated for an institution, statistical categories can be assigned to patrons per library. In this case, an owner library is added to the properties of each statistical category that is assigned to a patron. Only users whose roles are scoped to the owner library can see or access the statistical categories it owns. Statistical categories that are outside of a user's scope are not displayed to them when they view user information or retrieved in searches they perform, and are excluded from jobs and API calls they execute.
For information about assigning statistical categories to users, see Managing Users. For information about creating statistical categories, see User Details Configuration.
Entity Type Dropdown in Simple Search
February 2023 Administration and Infrastructure
Librarians can now quickly select the type of search (entity type) they are searching (in simple search) by starting to type its name in the Search field, for example "Electronic collection", and having it auto-complete in the field. This is especially helpful in saving time when the simple search dropdown contains a long list of search types (entity types).
Moreover, this ability reduces mousing - making simple searches more accessible. For more information, see Performing a Simple Search.
Licenses - Enhancements to LicenseTermsPermittedProhibited Options
February 2023 Administration and Infrastructure (Updated February 15, 2023)
The license term “LicenseTermsPermittedProhibited” is enhanced with additional options to match the DLF standard. The new options are:
- Permitted (Explicit)
- Permitted (Interpreted)
- Prohibited (Explicit)
- Prohibited (Interpreted)
- Silent (Uninterpreted)
This is in addition to the existing values of:
- Silent
- Uninterpreted
- Prohibited
- Permitted
- Not Applicable
For more information see Managing License Terms
Translations for the newly added values will be available in the following Alma release. Manual translations can be added.
The functionality above was introduced in a different manner in the February release and was modified on February 15th due to customer feedback.
Options that were available prior to the Alma February release were added back to the list of options, and additional values were added to comply with the DLF standard.
Below is a table describing all the options for the “LicenseTermsPermittedProhibited” license term and the changes that were done according to customer feedback.
Drop down values | Value changes |
---|---|
Permitted |
Customers who had the “Permitted (Explicit)” selected in the February release will move back to this value. |
Permitted (Explicit) |
Customers who had this value selected in the February release will move back to “Permitted” value. |
Permitted (Interpreted) |
Customers who selected this value in the February release will still have this value selected. |
Prohibited |
Customers who had the “Prohibited (Explicit)” selected in the February release will move back to this value. |
Prohibited (Explicit) |
Customers who had this value selected in the February release will move back to “Prohibited” value. |
Prohibited (Interpreted) |
Customers who selected this value in the February release will still have this value selected. |
Silent |
Customers who had this value selected before the February release, and did not modify it in the February release, will have this value selected. |
Silent (Uninterpreted) |
Customers who selected this value in the February release will still have this value selected. |
Uninterpreted |
Customers who had this value selected before the February release, and did not modify it in the February release, will have this value selected. |
Not Applicable |
New Analytics User Interface
The Alma Analytics user interface was redesigned with several enhanced features that improve the display of information and simplify many procedures and workflows. The new interface will be rolled out in the following stages:
- February release – The previous version of the interface is displayed by default, but you can configure Alma Analytics to display the new version.
- May release – The new version of the interface is displayed by default, but you can configure Alma Analytics to display the previous version.
- August release – The new version of the interface is the only version available.
To display the new version of the interface, select the User icon and then select Feature Rollout Configuration:
The following enhancements were implemented:
- The options and layout when selecting Analytics from the Main Menu was enhanced:
- At the top of the area, a list of your favorite reports and dashboards appear:
Main Analytics Link Options
- From the My Analytics area you can access the Analytics Object list (if you have the relevant role) and display the new Shared with Me page where you can view the reports to which you have access:
Shared with Me
- From the Create Analysis section, you can select the renamed Access Analytics link to create reports and access out-of-the-box reports and dashboards.
- At the top of the area, a list of your favorite reports and dashboards appear:
- The Analytics Object List was redesigned:
Analytics Objects List
- Visual indicators mark the objects as Subscribed, Scheduled Report, Added as a Widget, and Report in Favorites.
- Additional information appears for each object, such as the subject area the report or dashboard is from, the user who created the object and the date created, and the user who modified the object and the date modified.
- New functionality is now available for Analytics Objects, including:
- Editing an analytics object in split view, so that you can keep the list of objects open while you edit:
Split View
- Viewing a preview of the report or dashboard so you can confirm the functioning of the reports:
Preview Report
- Editing an analytics object in split view, so that you can keep the list of objects open while you edit:
For the complete description of the features of the new Analytics Interface, see Working with Analytics Objects.
For a description of the options on the Analytics menu, see Navigating Analytics.
API-Key Support for Multiple IP Ranges
The existing security feature that uses API keys to limit access to Alma has been expanded. When employing this feature, customers create an API-key in https://developers.exlibrisgroup.com/manage/keys/, and then specify IP addresses from which requests can be accepted. Requests from IP addresses that are not included in the list of accepted IP addresses are rejected by Alma. Previously, Alma API keys could only be configured to accept requests from individual IP addresses or a single range of IP addresses. They can now accept multiple ranges of IP addresses; the ranges must be defined in CIDR format, and separated by commas - e.g., 1.1.1.1/27,1.1.1.3/15.
Access to Letter Components Added to the API
Access to Code-Table Translations Added to the API
Search for Reading List by List ID
You can now search Reading lists by List ID in Alma.
List ID searches are not currently included in All searches. This option will be available in a later release.
For more information, see Reading List Search Fields.
User-Information Pop-Ups in New-Layout Task Lists Are Now Available and Customizable
In the New Layout of the Resource Sharing borrowing-request and lending-request task lists, assignee and requester names are now buttons that, when selected, open pop-ups in which additional user information is displayed. Alma users can thus quickly access information such as a requester's user group or contact details, but the information does not clutter the display when it is not needed. For additional information, see New Layout 2022.
Which user information appears in these pop-ups can be configured by the institution. Thus, one institution may choose to display physical addresses and personal phone numbers in the pop-up, while another chooses to hide this information, but includes user groups and email addresses. For additional information, see Configuring User Information for Pop-ups.
Additional Enhancements
- December 2023 Administration and Infrastructure SF: 06853262 06862264
It was not possible to search for translations in code tables. This was fixed by adding the search by "Translation" for Code Tables and only applied in multi-language environments. For more information, see Inner Search.URM-204310Code Table filter displaying the Translation column - December 2023 Analytics Idea Exchange SF: 06727765 URM-190545
The Service Authentication Note and Service Public Note fields were added to E-Inventory > Service Details. These fields display the authentication note and public note that are entered in the Notes tab of the electronic service. For more information, see Managing Electronic Resources. - December 2023 Analytics URM-198537
The bibliographic record Bibliographic Rank field was added to the Bibliographic Details dimension in every subject area in which it appears. This field displays a number that signifies the value of the bibliographic data in the record relative to other records for the title. For more information, see Bibliographic Ranking in Metadata Editor.
- November 2023 Linked Data
The URLs associated with ISBNs used in the Linked Data enrichment process for bibliographic records have been eliminated, as per the request of the Linked Data Community of Practice. These URLs originated from isbnsearch.org and were not provided by an officially recognized ISBN maintenance agency.URM-199431The authoritative ISBN agency does not currently provide URIs for ISBNs. - November 2023 Linked Data
The URI format for the Linked Data enrichment process applied to bibliographic records connected to GND authorities is revised to conform to the entity URI structure, now following the format: http://d-nb.info/gnd/XXXXXXXXX URM-199434 - November 2023 Resource Management
MD Import: The import redirection mechanism has been enhanced to provide a more comprehensive representation of changes by updating the record versions of the related records. This improvement offers a clearer and more informative indication of changes done to related records by the redirection process.URM-195831 - Digital Resource Management 2023
The originating system ID is now imported from the header:identifier field for Dublin Core and MODS records (and is not populated by the MMS ID) when importing records using the OAI-PMH protocol. - November 2023 Analytics URM-198563
Ten Patron Statistical Categories fields were added to Fulfillment > Patron Details. These fields allow you to map ten statistical categories. This allows you to filter reports based on advanced user information typically stored in the statistical category fields. Statistical categories fields exist also in the Borrower Details dimension, but the behavior is different.For the fields in the Borrower Details dimension, the information is from the time of the loan only when the data is anonymized. If it is not anonymized, it is the data at the time the report is run.
For the fields in the Patron Details dimension, the data is from the time of the loan regardless of whether or not the fields are anonymized.
To make this point clear, the Patron Details dimension was renamed to Patron Details at Time of Loan.
For more information, see Configuring Statistical Categories for Analytics.
- November 2023 Analytics URM-199524
The value for the Reading List Type field (Course Reserves > Reading Lists) was changed from Parent to Sample List to better indicate that the reading list is used as a template for other lists. - November 2023 Analytics URM-199084
The following fields were added to Alma Analytics. These fields allow you to create reports that include information about the location of the institution and its libraries. The address configured as the Preferred Address is the one available in analytics. The fields were added to the Library, Physical Item Details, Location, and Institution dimensions in all subject areas in which they appear:- Address Line 1
- City
- State Province
- Country
- Postal Code
We recommend that you configure the address of your institution as well as the addresses of the libraries of your institution in Alma. This will allow you to take advantage of the map feature available with Data Visualization Analytics. For example, the following map shows the number of physical titles according to the geographic location of the library:
Data Visualization MapFor more information about Data Visualization, see Data Visualization (DV).
To configure institution addresses in Alma:- Open the Organization Unit Details page (Configuration > General > Add a Library or Edit Library Information).
- Select the Contact Information tab.
- Click Add Address. The following appears:
Add Address
- Enter the address information.
- Select Yes for the Preferred address field.
- Select Add and Close.
To configure library addresses in Alma:- Open the Organization Unit Details page (Configuration > General > Add a Library or Edit Library Information).
- For a library, select the More actions icon and select Edit.
- Select the Contact Information tab and select Add Address. The Add Address dialog box opens.
- Enter the address information.
- Select Yes for the Preferred address field.
- Select Add and Close.
For more information on adding address information, see Configuring Institution/Library Contact Information.
- November 2023 Analytics URM-203533
The Request Type field was added to Link Resolver Usage > OpenURL Context Details. It indicates if the request type is single service or View it. - November 2023 Analytics URM-182161
The Has Service field was added to Link Resolver Usage > OpenURL Service Details. It indicates (Yes/No) if the request has services. - November 2023 Fulfillment - Resource Sharing URM-189225
Renewing NCIP Based P2P Resource Sharing requests (see Dev Network) no longer makes use of the Ext element in the message. Instead, a lender's ItemRenewed message with a DueDate element that is different from the exiting due date is interpreted as accepting the renew request. Note that this should not have any functional implications. - November 2023 Fulfillment - Course Reserves URM-1886373
To support bulk updates of URLS, when SourceURL is configured (Configuration > Leganto > General > Field Normalization), when Update source URL is checked, you can now update citation URLs in bulk when the Reading List Citation Update Task job (Admin > Manage Jobs and Sets > Monitor Jobs) runs.The Update source URL checkbox is hidden when the Delete citations checkbox is checked.
Bulk update Source URLUpdate source URLFor more information, see Manual Jobs on Defined Sets.
- September 2023 Analytics URM-XXX
The following fields were added to E-Inventory > Electronic Collection:- Electronic Collection Management Level in CZ – who maintains the community managed collection. For more information, see Managing Electronic Collections.
- Electronic Collection Pending Deletion Date – the date on which the electronic collection will be deleted
- September 2023 Fulfillment URM-196588
It is now possible to disable automatically adding a note to users with role profile information. This disables adding the note for future user updates. For more information, see "Add roles using a profile" in Adding Roles to Users.
- August 2023 Resource Management SF: 06290848 Idea Exchange
When viewing a bib record's related records in search results > other details, the number of results displayed was raised from 500 to 1,000. For more information, see Search Results tab > Other Details.URM-170486 - August 2023 Resource Management URM-192028URM-192023
NACSIS Cloud App Enhancements:- The holdings results page as part of the creation of a NACSIS borrowing request now allows the option to select which table columns to display. For more information, see Integration with NACSIS-ILL.
- The holdings search filter section as part of the creation of a NACSIS borrowing request now incorporates a sticky selection (the UI remembers the last selection of the user) for various filters. For more information, see Integration with NACSIS-ILL.
- August 2023 Resource Management URM-191350
GND Profile Updates: Ongoing GND profile updates. - August 2023 Analytics URM-189560
The Title Committed to Retain field was added to the Bibliographic Details dimension of all subject areas in which it appears. It indicates (Y/N) if the bibliographic record is marked as Committed to Retain. For more information on this feature, see Bibliographic Record Retention. - August 2023 Analytics URM-193119
A Year-Month field in format YYYY-MM was added to all date dimensions for all subject areas. It allows you to sort reports by year and month. - August 2023 Analytics URM-195241
(URM-195241) The Analytics Object subject area was enhanced to support the new Analytics Object Layout including support for data visualization dashboards. To support this enhancement, many new fields were added to the Analytics Objects Measures and Analytics Objects Details dimensions.- For Analytics Objects Measures, the following fields were added:
- Num of Objects of Type DV
- Num of DV Objects Marked for Homepage
- Num of Objects Delivered by Attachment
- Num of Objects Delivered by Link
- Num of Objects Delivered by FTP
- Num of Users Who Pinned Object
- Num of Shared Internal Users
- Num of Shared Users by Role
In addition, the following field names were changed:
- Num of Objects of Type Scheduled Report was renamed to Num of Scheduled Objects.
- Num of Objects of Type Widget was renamed to Num of Objects Added as Widget.
- Num of Used Subscriptions was renamed to Num of Subscribed Users.
- Num of Used Widgets was renamed to Number of Widget Instances Displayed.
The following fields were marked as to be deprecated and will be removed in a future release:
- Num of Objects of Type Dashboard - Active
- Num of Objects of Type Dashboard - Not Active
- Num of Objects of Type Scheduled Report - Active
- Num of Objects of Type Scheduled Report - Not Active
- For Analytics Objects Details, the following fields were added:
- Subject Area
- Is Out of Box
- Is Widget
- Is DV Homepage
- Is Scheduled
- Scheduled by Link/ Attachment
- Shared Internal Users
- Shared Roles
In addition, the following field names were changed:
- Object Name was renamed to Report Name.
- Scheduled Report Format was renamed to Scheduled Report Delivery Format.
For more information, see Analytics Objects.
- For Analytics Objects Measures, the following fields were added:
- August 2023 Digtal Resource Management
The Alma Viewer was renamed to the Digital Viewer to better conform with its usage across products. - August 2023 Fulfillment - Course Reserves URM-190725
It is now possible to use the customization wheel to add the Course ID to the Alma courses table display. Additionally, this column is included in the Excel file export. The ID column is hidden by default.Course ID
- July 2023 Analytics URM-X191976
The following fields were added to the Analytics Usage Tracking subject area:- Usage Tracking Measures > Total Rows Retrieved
- Usage Tracking Measures > Average Rows Retrieved
- Query Details > Number of Rows per Report
- July 2023 Analytics SF: 06490230 URM-187005
The Role Cant Edit Restricted User field was added to Users > Roles and the Cant Edit Restricted Users field was marked as "to be deprecated" from the following locations. This was done, because the Cant Edit Restricted User functionality is a function of the role and not of the user.Subject Area Dimension Analytics Objects Created By Borrowing Requests (Resource Sharing) Requester Course Reserves Librarian Digital Waitlist User Details E-Inventory Cost Usage POL Approver Electronic Collection PO Line Approver 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 PO Line Approver Purchase Request Approver Purchase Request Assigned To Purchase Request Creator Purchase Request Modified By Purchase Request Requester Requests Requester Users User Details
- June 2023 Analytics URM-189899
The Request Creator field was added to Requests > Request Details. It displays the original creator of the request. This is opposed to the Creator field which, after a request is completed or cancelled, displays the user that completed or cancelled the request. - June 2023 Analytics SF: 06640142 URM-186764
The PO Line Inventory Active Library Code field was added to the PO Line dimension of the Funds Expenditure, Physical Items, and Purchase Requests subject areas. It displays the inventory linked to PO Lines from active (non-deleted) libraries. This is in contrast to the PO Line Inventory Library Code, which displays the inventory linked to PO Lines from both active and deleted libraries. - June 2023 Analytics URM-190717
The following fields were added to Analytics Usage Tracking subject area:- Query Details > Error Code – the code of the error
- Query Details > Error Text – the text of the error message
- Query Details > Report Duration – the time the report took to run
- Usage Tracking Measures > Average Time in Secs – the average time to run the report
- Query Date > Query Year Month Key – the year and month, in format 2023-02
- June 2023 Analytics SF:06611746 06611742 06611744 URM-188903
The possible values for the Analytics Usage Tracking > Usage > Object Type field were expanded. They are now:- Dashboard
- Report
- Data Visualization
- Workbook
- Product Embedded Reports
- May 2023 Resource Management SF: 05320435
The UNIMARC Bibliographic profile now includes a closed list of values for 7XX fields in the subfield $4. For more information, see Working with Bibliographic Records. The UNIMARC Bibliographic 7XX $4 enhancement is in continuation of the enhancements included in the February 2023 Release. For a list of the enhancements in the February 2023 release, click here.URM-178916 - May 2023 Resource Management
Previously, edition information in the title search results was limited to the edition statement (250$$a). Now, the edition information also includes the remainder of the edition statement (250$$b), enabling librarians to fully and accurately identify the edition from the search results. - May 2023 Resource Management
The 070 is the standard NAL (National Agricultural Library) call number index per library of Congress Standards. Once the semi-annual reindexing is completed, it will be included in the NAL Type Call Number search index. - May 2023 Administration and Infrastructure
Alma's session timeout feature recognizes user activity in Analytics and extends the Alma session to prevent a timeout while the user is active in Analytics. This means that if the user is working in Analytics during an Alma session, their session remains active without interruption. Once a user's session in Alma is about to end, Alma runs a check to verify if the user was active in Analytics within the last hour. If active, Alma extends the session until the next session's end cycle and runs the check again. If no activity in Analytics, the session ends. - May 2023 Digital Resource Management URM-126640
The Universal Viewer now supports the 3D formats .glb and .gltf. Note that for .gltf, files that include pointers to additional external files are not supported. - May 2023 Analytics URM-186765
The Item Receiving Date dimension was added to Physical Items subject area. It includes fields that enable you to create reports on how many items were received by the library per period of time.For more information on the Physical Items subject area, see Physical Items.
- May 2023 Analytics SF: 06447308 06683567 URM-182984
The DC Description field was added to the Bibliographic Details dimension in all subject areas in which it appears. It displays the description of the DC record.For more information on the Bibliographic Details dimension, see Bibliographic Details.
- May 2023 Analytics SF: 06577926 URM-184115
The Item Issue Date (Calendar) field was added to Physical Items > Physical Item Details. It displays the issue date of the physical item.For more information on the Physical Items subject area, see Physical Items.
- May 2023 Fulfillment - Resource Sharing URM-189222
The following fields are now available in the following letters (Configuration > General > Letters > Letters Configuration):Field Label XML Field Ful Incoming Slip LetterGroup Qualifiergroup_qualifierRenewals Allowedrenewals_allowedBorrowing Library Address Informationborrowing_library_addressPartner Codepartner_codeResource Sharing Shipping Slip LetterRenewals Allowedrenewals_allowedFul Resource Request Slip Letter
Group Qualifiergroup_qualifierRenewals Allowedrenewals_allowedPartner Codepartner_codeResource Sharing Receive Slip Letter
Group Qualifiergroup_qualifierLibrary Location for Institutions with Multiple LibrariespickupLibraryNameRenewals Allowedrenewals_allowedBorrowing Library Address Informationborrowing_library_addressPartner Codepartner_codeResource Sharing Return Slip Letter
Group Qualifiergroup_qualifierLibrary Location for Institutions with Multiple Libraries
pickupLibraryName
Renewals Allowedrenewals_allowedBorrowing Library Address Informationborrowing_library_addressBorrower Overdue Email Letter
Partner Codepartner_codeFor more information, see Configuring Alma Letters.
- May 2023 Fulfillment - Resource Sharing URM-184830
Titles with physical holdings now display the Holdings information (name, shelving location, call number, and availability) in the right pane.The Holdings information displays whatever information is available. When some of the Holdings information is not available, the field for the unavailable information does not appear.
Holdings - May 2023 Fulfillment - Resource Sharing SF: 06618079 06664331 URM-187017
You can now set the default sent from email address to be different from the main library email address. When rs_use_addressfrom_letter_param (Fulfillment Configuration Menu > General > Other Settings) is set to true (default false), instead of letters being sent from the Preferred Email Address set in Fulfillment > Library Management > Contact Information, the email is sent from the letter configuration addressFrom (Configuration > General > Letters > Letters Configuration) on the following letters:- Externally Obtained Letter
- Lending Recall Email Letter
- Borrower Claim Email Letter
- Ful Cancel Email Letter
- Ful Renew Email Letter
- Ful Incoming Slip Letter
- Ful Damaged Email Letter
- Ful Lost Email Letter
- Borrower Overdue Email Letter
- Ful Outgoing Email Letter
- Borrower Receive Email Letter
- Borrower Return Email Letter
- Lender Checked-in Email Letter
- Lender Reject Email Letter
- Lender Response Email Letter
- Lender Ship Email Letter
- Lender Will Supply Email Letter
- Query To Patron Letter
- Resource Sharing Request Confirmation Letter
- Resource Sharing Return Slip Letter
- Resource Sharing Shipping Slip Letter
Preferred email addressaddressFrom email addressIn addition, for the following letters, signature_email needs to be replaced in the XSL with address_from in order to prevent the preferred email address from appearing at the bottom of the email:
- Externally Obtained Letter
- Query To Patron Letter
XSLPreferred email address on three lettersFor more information, see Configuring Alma Letters.
- May 2023 Fulfillment - Course Reserves SF: 06572598 Idea Exchange URM-162845
You can now use the Leganto API to update citation tags. Use the following PUT method, containing a URL with the course ID, reading list, reading list ID, citation, citation ID, and the word tags. The body must include the tags you want the citation to include. For example:If the body <citation_tag> is empty, all tags are removed from the citation.
For more information, see Developer Network - Courses.
- April 2023 Resource Management
Previously, edition information in the title search results was limited to the edition statement (250$$a). Now, the edition information also includes the remainder of the edition statement (250$$b), enabling librarians to fully and accurately identify the edition from the search results. - April 2023 Resource Management
The 070 is the standard NAL (National Agricultural Library) call number index per library of Congress Standards. Once the semi-annual reindexing is completed, it will be included in the NAL Type Call Number search index. - April 2023 Administration and Infrastructure
Alma's session timeout feature recognizes user activity in Analytics and extends the Alma session to prevent a timeout while the user is active in Analytics. This means that if the user is working in Analytics during an Alma session, their session remains active without interruption. - April 2023 Analytics SF: 06593328 URM-186017
The Cost Usage Institution for Consortia folder was added under E-Inventory > Cost Usage. It contains the Cost Usage Institution Code and Cost Usage Institution Name fields. They display the institution code and institution name of the network member. - April 2023 Analytics URM-180828
The Statistical Category Description field was added to Users > Statistics. It displays the statistical category description and can be used with the Statistical Category field, which displays the statistical category code.
- March 2023 Analytics URM-184642
The Partner Institution field was added to Borrowing Requests > Partner. This field displays the partner institution, which enables better reporting of borrowing requests per the supplying institution. - March 2023 Analytics URM-176587
The Statistical Category Type field was added to Users > Statistics. It displays the statistical category type, which provides additional information about statistical categories in addition to the Statistical Category field.For more information on configuring statistical categories for analytics, see Configuring Statistical Categories for Analytics.
In addition, for the Borrowing Requests, Fines and Fees, Fulfillment, and Requests subject areas, the Statistical Categories 1 - 10 fields now display library level data, since their user data can be anonymized, while for all other subject areas they display institution level data.
- March 2023 Analytics SF: 06434690 URM-184685
When Alma attempts to match electronic resource usage from COUNTER reports with the resource in Alma, Alma now first attempts to match with the Online ISSN (called the Normalized EISSN in Alma Analytics) and if that is unsuccessful with the Print ISSN (called the Normalized ISSN in Analytics) and not the opposite as was the case previously. For more information, see Matching the resource from COUNTER report to the resource in Alma for cost per use. - March 2023 Analytics URM-184130
The values of the E-Inventory > Service URL Information > Service Is Free and Service Is Free (override) fields were changed from 1/0 to Yes/No. - March 2023 Analytics URM-183938
The Borrowing Requests and Lending Requests subject areas were renamed to Borrowing Requests (Resource Sharing) and Lending Requests (Resource Sharing) respectively. This is to clarify that these subject areas report on resource sharing borrowing and lending requests and not general Alma requests, which are reported on from the Requests subject area.In addition, the Usage subject area was renamed to Usage (COUNTER) to indicate that it reports on electronic resource usage derived from COUNTER reports.
- March 2023 Analytics URM-184286
The Statistical Category field (Users > Statistics) was restored to display the statistical category code as was the case before the February release.
- February 2023 Resource Management URM-179343
To assure a more accurate look-up of Series title and Uniform title, the access point of UNIMARC fields 410/411 and 500 will lead to the relevant entries based on a type defined in the 154 $a field. - February 2023 Resource Management URM-178894
Libraries can now configure more flexible scheduling for general publishing. - February 2023 Physical Resource Management URM-171615
The publishing to OCLC was enhanced to handle the reported instability of connections with OCLC FTP servers, where OCLC servers fail to receive files. The following is the enhancement:- If a file fails to be uploaded to the FTP server due to server instability, the publishing job will complete with errors. The job report will detail that the connection to OCLC’s FTP server failed, and it will be possible to download the failed files from the job report, so they are not lost.
- February 2023 Analytics URM-180834
It is now possible to have the data anonymized in the following fields of the System Events subject area:To request that these fields be anonymized, contact Ex Libris support.
- Event Details > Event Key Value
- Event Details > Event Creator
- Security Events > Accessing User ID
- Security Events > User ID
- February 2023 API
For import jobs that have run, a report showing the source file that was imported can now be generated through the API, given the Job ID. For additional information, see Configuration and Administration. - February 2023 API
The Linked Data section of bibliographic records now includes Creator and Contributor Wikidata links when they are available. For additional information about linked data, see Linked Data in Repository Search Results; Linked Data.
- February 2023 Analytics SF: 05299713 05460695 06464393 06484214 URM-182644
The Electronic Collection Bibliographic Details dimension was added to the E-Inventory subject area. The fields of this dimension enable you to create reports that contain information concerning the bibliographic details of electronic collections. This is especially useful for reports concerning collections without portfolios. The fields of this dimension are the same as in the Bibliographic Details dimension found in many subject areas with an added prefix of E-Collection Bib.For more information, see Electronic Collection Bibliographic Details.
Watch the Bib Details of E-Collections in E-Inventory Analytics Reports video (1:20 minutes). - February 2023 Analytics URM-182402
The names of the Fund Ledger dimension and the following field names were changed to remove the word Ledger from their name to more accurately describe the information they display. The term Fund Ledger refers to a parent fund, while these fields display information at both the parent and child level. Note that any existing reports that use the old field names continue to work.The changed dimension and field names are located in the Funds Expenditure, Purchase Requests, Physical Items, and E-Inventory > Cost Usage subject areas.
New Name Old Name Fund (Dimension) Fund Ledger Fund Code Fund Ledger Code Fund ID Fund Ledger ID Fund Name Fund Ledger Name Fund Status Fund Ledger Status Fund Owner Code Fund Ledger Owner Code Fund Owner Name Fund Ledger Owner Name Fund Name Fund Ledger Name Parent Fund Code Parent Fund Ledger Code Parent Fund ID Parent Fund Ledger ID - February 2023 Analytics URM-182443
The names of the following fields in the Fund Expenditure subject area were changed to clarify that they display the name of the user:New Name Old Name Dimension Invoice - Approver Name Invoice - Approved By Invoice Line License Modifier Name License Modified By PO Line License License Creator Name License Creator PO Line License - February 2023 Analytics URM-184286
The Statistical Category field (Users > Statistics) now displays the statistical category description and not the statistical category code. Any report filters that are based on the statistical category code may need to be updated.Watch the Additional Analytics User Statistics video (1:16 minutes). - February 2023 Fulfillment - Course Reserves URM-180474
When copying a citation, the Created by on the new citation is attributed to the user who copied the citation.
- February 2023 Fulfillment - Course Reserves URM-153988
For consistency and clarity, the Brief Display Request Status label is now labeled Citation Status to match the Citation Status facet label and the data in analytics.
Brief Display Citation Status - February 2023 Fulfillment - Course Reserves URM-178004
The List Last Set to Complete Date field was added to the Reading Lists dimension in the Leganto Student Usage, Leganto Instructor Usage Events, and Course Reserves subject areas. It displays the most recent date that the reading list was set to complete.
- February 2023 Fulfillment - Course Reserves SF: 06454739 URM-177711
The Citation Hidden Links field was added to the Citations dimension of the Leganto Student Usage and Leganto Instructor Usage Events subject areas and the Reading List Citations dimension of the Course Reserves and Purchase Requests subject areas. It indicates if there are hidden links in the citation.
- February 2023 Fulfillment - Course Reserves URM-175007
The Reading List Type field was added to the Reading Lists dimension in the Leganto Student Usage, Leganto Instructor Usage Events, and Course Reserves subject areas. It indicates if the reading list is designated as the parent list. Possible values are Parent and blank (no value). - February 2023 Fulfillment - Course Reserves SF: 06481498 URM-178971
The Start Page 2 and End Page 2 fields were added to the Citation Metadata Details dimension of the Leganto Student Usage, Leganto Instructor Usage Events, and Course Reserves subject areas. They display an additional start and end page.The Number of Pages field now displays the number of pages between the Start Page and End Page fields and the Start Page 2 and End Page 2 fields.In addition, the names of the Article Number of Pages, Article Start Page, and Article End Page were changed to Number of Pages, Start Page, and End Page.
- February 2023 Fulfillment - Course Reserves URM-179659
The following field names were changed in Analytics for better clarity and consistency:New Name Old Name Location Course Created By Course Creator - Course Reserves > Courses
- Leganto Student Usage > Reading Lists
- Leganto Instructor Usage > Courses
- Requests > Request for Course
Reading List Created By Reading List Creator - Course Reserves > Reading Lists
- Leganto Student Usage > Reading Lists
- Leganto Instructor Usage > Reading Lists
Number of Suggestions Leganto List Num of Student Suggestions - Course Reserves > Reading Lists
- Leganto Student Usage > Reading Lists
- Leganto Instructor Usage > Reading Lists
Section Created By Section Creator - Course Reserves > Leganto Reading List Sections
- Leganto Student Usage > Reading List Sections
- Leganto Instructor Usage > Reading List Sections
Citation Created By Citation Creator - Course Reserves > Reading List Citations
- Leganto Student Usage > Citations
- Leganto Instructor Usage > Citations
- Purchase Requests > Reading List Citations
Number of Files Downloaded Number of Files Download Leganto Student Usage > Student Usage Number of Student Comments Students Discussions Leganto Student Usage > Student Usage - February 2023 Fulfillment - Course Reserves URM-180468
For Norwegian customers, files available from Bolk now only display to students when permitted according to the permissions set in Leganto. For example:- Files for citations that are not marked as complete do not display to students
- Files only display when access to materials is allowed according to the publishing visibility
- February 2023 Fulfillment - Course Reserves URM-180928
The No List Expected field was added to the Course dimension in the Leganto Student Usage, Leganto Instructor Usage Events, Course Reserves, and Requests subject areas. (Possible values: Checked and Unchecked). It indicates if the No List Expected checkbox is selected on the course record in Alma or not. For more information on this checkbox, see Indicating that Courses Deliberately Have No Reading List. - February 2023 Fulfillment - Resource Sharing URM-166608
When scanning in an item on the lending side (Fulfillment > Resource Requests > Scan In Items), emails were not sent to the borrower. When an email address is configured for the Printer Details (Configuration > Fulfillment > General > Printers), the Resource Sharing Shipping Slip is now emailed.
- January 2023 Analytics URM-180923
In continuation of the December release, an additional five statistical categories are now available to be reported on in Alma Analytics in the following additional locations:The additional statistical categories added to Fulfillment > Borrower Details are only available with data added going forward.- Borrowing Requests > Requester
- Fines and Fees > User Details
- Fulfillment > Borrower Details
- Requests > Requester
- January 2023 Analytics URM-180834
It is now possible to have the data anonymized in the following fields of the System Events subject area:To request that these fields be anonymized, contact Ex Libris support.
- Event Details > Event Key Value
- Event Details > Event Creator
- Security Events > Accessing User ID
- Security Events > User ID
- January 2023 Analytics URM-177583
The Available From Date and Available Until Date fields were added to E-Inventory > Portfolio. They display the start and end dates that the portfolio is available. - January 2023 Analytics URM-181807
The Label and Label History fields (Borrowing Requests > Borrowing Request Details and Lending Requests > Lending Request Details) are now available to Alma customers. They display the customized labels added to borrowing and lending requests and the history of label deletions. - January 2023 Analytics URM-152264
The Loan Hour field was added to Fulfillment > Loan Date. It indicates the hour of the loan in 24 hour format.
Resolved Issues
- November 2023 Release Update Fulfillment - Resource Sharing SF: 06953848 URM-209673
ISO 18626 renewReply messages sent from Alma are not received at the partner. This was fixed. - November 2023 Release Update Physical Resource Management URM-209653
The "Records not deleted since they have local extensions" and "Records not deleted since they have related records" counters in the import job report mistakenly appear in the November 2023 release. This was fixed and the counters will no longer appear until the feature is released. - November 2023 Release Update Physical Resource Management SF: 06947430 URM-209501
The new load of locations per library for the Browse Shelf Listing Sticky functionality caused an error for the EMPTY library. This was fixed. - November 2023 Release Update Fulfillment SF: 06572730 06947330 06947717 06947970 06948379 06948430 06948461 06948491 06948881 06949083 06950591 URM-209542
In the Quick Printing window, transit slips for returned fulfillment network items are blank. This was fixed. - November 2023 Release Update Analytics SF: 06947331 06948127 URM-209496
When filtering renewals by barcode from the Loan Details dimension, the result was zero. This was fixed. - November 2023 Release Update Resource Management SF: 06947351 06947385 06947648 06947693 06947815 06948400 URM-209481
Linked data enrichment jobs failed when there was a non-numeric second indicator in the MARC fields. This was fixed, and now the linked data enrichment handles numeric and non-numeric second indicator values. - November 2023 Release Update Acquisitions SF: 06947579 06947703 06947802 06947997 06948740 06949317 06949609 URM-209476
PO lines cannot be updated and display the message "The fund is not in the current fiscal year". This was fixed. - November 2023 Release Update Acquisitions SF: 06948247 06948506 06949663 06949767 URM-209545
Clicking "Save and Continue" on an invoice did not work. This was fixed. - November 2023 Release Update Resource Management URM-209580
The new functionality for preventing DOI enrichment when the resource comes from CDI did not populate the DOI value to the target URL. This was fixed.
- August 2023 Release Update Resource Management SF: 06838716 URM-201559
Metadata Editor: Crtl+Shift+Z did not work on multiple fields. This was fixed.
- May 2023 Release Update Electronic Resource Management SF: 06684955 06722282 URM-193365
The Parser Parameters (override) information of local portfolios was exported into the URL field when using extended export instead of into the Parser Parameter field. This was fixed. - May 2023 Release Update Fulfillment - Resource Sharing SF: 06746776 06746834 06746961 06747169 06748218 06749190 06750351 06750442 URM-193247
When an institution has a circulation desk in the resource sharing library that does not have a hold shelf, the resource sharing request did not appear in the borrowing list. This was fixed. - May 2023 Release Update Resource Management SF: 06745023 URM-193264
The general publishing job failed at the initialization phase for Network members > General publishing based on blended sets with CZ records retrieved from the member. This was fixed. - May 2023 Release Update Administration and Infrastructure URM-185310
When the user attempts to open the results of two sets, an internal error occurs. This was fixed.
- February 2023 Release Update Electronic Resource Management SF: 06648372 06648374 06648382 06648398 06648796URM-187247
Local portfolios were created with the default available from and available until dates. When the Feature Flag turned active in the February release, the job to update the portfolio availability status by dates was activated, and changed the local portfolio status. Ex Libris reverted the data and activated all local portfolios that were changed in the job. - February 2023 Release Update Resource Management SF: 06647912 06649885 06649922 06650085 0665020506648796URM-187312
It was not possible to add special characters in the Metadata Editor using the ASCII codes with the February release of the new Metadata Editor keyboard shortcuts. This issue was fixed. - February 2023 Release Update Resource Management SF: 06648192 06648193 06648317 06648796URM-187220
Error in MARC21 BIB 655 Controlled vocabularies. The authorities were properly coded and linked via F3 but got an error stating the value is not part of the controlled vocabulary. This was fixed.
- December 2023 Acquisitions SF: 06963554 06989108 06977290 06959029 06991106 06564712 06993990 06989019 06990431 06964709 06967758 06988184 06972275 06967378 URM-211795
In open predicted items, for weekly (52) or daily (365) patterns, the items were created with incorrect data. This was fixed. This was caused by a regression from the issue in the November release where weekly and daily prediction patterns did not count the next cycle correctly. That regression was cancelled from November and will be fixed in February. - December 2023 Acquisitions SF: 06842716 URM-206253
Recently used reporting codes were not displayed. This was fixed and they are now displayed. Note that this only works when there are 10 or more items in the list box. - December 2023 Acquisitions SF: 06853972 06894334 URM-205138
In the new UI, when trying to save a migrated PO Line where the Subscription interval was -1, the PO line could not be saved and an error message "Subscription interval field is invalid" was displayed. This was fixed. - December 2023 Acquisitions SF: 06873410 URM-207211
An error message was displayed when rejecting a Purchase Request created from a citation, after the citation was removed. This was fixed. - December 2023 Acquisitions SF: 06916779 06958584 URM-207792
When saving POLs in the new UI, an error would sometimes display: Acquisition method was not selected, please enter the required data. This was fixed. - December 2023 Acquisitions SF: 06950755 06950824 06950593 URM-209594
When trying to create manual PO for PO Lines that are in "In Review" status and their "Manual packaging" indicator is checked - an error message was displayed. This was fixed and now a warning message explain the customer that the PO line is not in the correct status is displayed. - December 2023 Acquisitions SF: 06766995 URM-198754
In some cases, the disencumbrance amount was a few KRW less than encumbrance/expenditure. This was fixed. - December 2023 Acquisitions SF: 06786441 URM-199602
When the invoice lines tab in a PO Line was sorted by line number, in some cases some of the lines would disappear. This was fixed. - December 2023 Acquisitions SF: 06867353 06806833 URM-205213
The Note column was not added to an invoice created from an Excel file. This was fixed. - December 2023 Acquisitions SF: 06877390 URM-206143
There was no invoice payment date in fund transactions for an invoice marked as internal copy. This was fixed, and now if an invoice is marked as internal copy or prepaid, the invoice payment date in the fund transaction is updated when the invoice moves to the Closed status. - December 2023 Acquisitions SF: 06856305 URM-207621
A mistake in translation was corrected for the following label: "Invoice Total Price is over {0}. It may require Managerial Approval". - December 2023 Acquisitions SF: 06898046 URM-207692
In the Invoice Approval queue users were able to “assign to” users that could not approve them. This was fixed and now only users that have the "Invoice Manager" role appear in the list. - December 2023 Acquisitions SF: 06631090 06754707 05300329 URM-155048
An error message was displayed when a Staff user at a customer tried to receive a specific PO Line. This was fixed. - December 2023 Acquisitions SF: 06773322 URM-206118
The PO Line Claim Aggregated Letter subject was taken from the PO Line Claim letter. This was fixed. - December 2023 Acquisitions SF: 06756483 URM-195410
Overencumbrance Limit Percent was not blocking the creation of the encumbrance transaction due to an error in calculation (the available balance was not taken into account). This was fixed. - December 2023 Acquisitions SF: 06815133 URM-203440
In the new UI, after saving an order, there was a difference between fund and net price. This was fixed. The amounts now match and the (rounding) calculation is consistent in the UI and server. For example, in both calculations 47.405 = 47.41 (and not 47.40). - December 2023 Acquisitions SF: 06737831 URM-196836
When a Vendor was changed on an invoice that had the vendor account populated, the change did not remove the vendor account from the invoice. This caused incorrect 'Vendor Account' information in re-exported invoice files for the ERP. This was fixed. Now, when the vendor is changed and the invoice is saved, Alma verifies that the vendor account is valid. - December 2023 Acquisitions SF: 06557556 URM-180280
Previously, when the Change PO Line Status job was used to close PO lines for electronic resources, the PO lines were closed, but the job report said that they were skipped and could not be closed. This was fixed. Now the job report correctly states that these PO lines are closed. - December 2023 Acquisitions SF: 06855546 URM-207413
In the Acquisition health check process, the "Reporting codes for funds and invoices/orders match" error did not hold the invoice number, only the invoice line number. This was fixed. - December 2023 Administration and Infrastructure SF: 06738500 06640552 URM-190055
Previously After marking a loan as lost, the Advanced search for users with the "Fine/Fee total sum" field did not work properly. This was fixed. - December 2023 Administration and Infrastructure SF: 06738500 06640552 URM-207781
Previously when doing an add/waive/dispute/restore fee without selecting the "Save" button, the Advanced search for users with the "Fine/Fee total sum" field did not work properly. This was fixed, and users can now add/waive/dispute/restore fees without having to select the "Save" button. - December 2023 Administration and Infrastructure SF: 05312403 05330237 URM-131691
Certain links with special characters did not resolve correctly. This was fixed by creating a new customer parameter (temp_use_encode_uri_for_all_parsers). This customer parameter can be activated by Ex Libris Support. - December 2023 Administration and Infrastructure SF: 06819823 URM-199830
General Configuration menu disappears from user with proper roles. This is fixed - December 2023 Administration and Infrastructure SF: 06854816 06859868 URM-203119
Notes added to any "Other Settings" configuration table are incorrectly visible on all of the equivalent other settings tables. This was fixed and the Notes no longer appear. - December 2023 Administration and Infrastructure SF: 06853262 06862264 URM-204310
It was not possible to search for translations in code tables. This was fixed by adding the search by "Translation" for Code Tables (relevant languages are displayed) and only applied in multi-language environments. - December 2023 Administration and Infrastructure SF: 06891657 URM-206805
The "more action" text does not display when the cursor hovers over the ellipsis button. This was fixed - December 2023 Administration and Infrastructure SF: 06777632 URM-198851
The number of standalone portfolios recommendations was different from the real number when pressing the link. This issue was fixed by updating the recommendations in the "Smart Recommendation Reflection Job". - December 2023 Analytics SF: 06709400 06846976 URM-192010
After previewing an Alma report with the Analytics New Layout the Primo report previews did not work. This was fixed. - December 2023 Analytics SF: 06797041 06737107 06704635 06865123 06719836 06682513 06796047 URM-206884
When exporting analytics reports, the reports never complete the export process. This was fixed by adding the RCOUNT(1) column to the report. - December 2023 Analytics SF: 06956025 URM-209646
An incorrect value appeared for the Analytics Objects > Analytics Object Details > Scheduled Frequency field in analytics reports. This was fixed. - December 2023 Analytics SF: 06880726 06856644 URM-205038
The report URL of analytics objects did not work if the report name contained diacritics. This was fixed. - December 2023 Analytics SF: 06875183 URM-207756
Users with many roles assigned to them received an error message when clicking the Shared with Me link from the main Analytics menu. This was fixed. - December 2023 APIs SF: 06861816 URM-204402
Performance improvements were done in the create loan API. - December 2023 APIs SF: 06817852 URM-204721
In the Get Vendor API, the contact people from the vendor account were missing in the response XML. This was fixed. - December 2023 APIs SF: 06766918 URM-207843
User block expiry time was changed by Update User Details API requests. This was fixed. - December 2023 APIs SF: 06845568 URM-207363
The new PO Line task list did not support Cloud Apps. This was fixed - December 2023 Digital Resource Management SF: 06741566 URM-207111
When accessing digital representations on a mobile device, the user was able to bypass the obtrusive copyrights by using the top toolbar. This was fixed. - December 2023 Digital Resource Management SF: 06900780 URM-207209
Representations with access rights configured to not allow downloading were able to be printed by pressing CTRP+P. This was fixed, so now pressing CTRP+P does not print the representation. - December 2023 Digital Resource Management SF: 06675294 URM-207365
In the Alma Viewer, some pages of PDFs were cut off at the bottom of the page. This was fixed. - December 2023 Digital Resource Management SF: 06595961 URM-189485
Duplicate digital services appeared when selecting the View It link from Primo. This was fixed. - December 2023 Electronic Resource Management SF: 06820705 URM-202166
Previous coverage in the portfolio editor is removed from the history tab when coverage is updated. This was fixed. The history now displays all of the previous changes. - December 2023 Electronic Resource Management SF: 06838917 URM-206370
In collections management, when a name column was moved to the first column, the link in this column was redirecting to the wrong collection. This was fixed. - December 2023 Fulfillment SF: 06844213 06759154 URM-194816
The Pick From Shelf page sometimes failed to open if there were very long call numbers that contained special characters. This was fixed. - December 2023 Fulfillment SF: 06684433 06762570 06730805 06708573 06847405 06681627 06947566 06956077 06731941 URM-192103
In some cases, the Quick print dialog window for the Resource Sharing Shipping Slip Letter was not displayed as expected. This was fixed. - December 2023 Fulfillment SF: 06931958 06768588 06736512 06666558 URM-196657
In some cases, the 'Loans - Due Date Correction after Calendar Change' job modified loans due date even though it did not fall on a closed day. This was fixed. Now, the loans due date is NOT recalculated when one of the following conditions is met: The library is open in the due date and the Regular Due Date policy specifies an exact hour. The library is open in the due date, the loan is a Resource Sharing loan and the ignore_lender_due_date Customer Parameter is false. - December 2023 Fulfillment SF: 06795512 URM-206550
A new field was added to the XML of loan-related letters: loaned_at_library. It contains the name of the library where the loan was performed. - December 2023 Fulfillment SF: 05311949 06281313 06756119 06656620 05302120 06921394 URM-140217
When changing the location of a digitization request, the pickup location is not recalculated. As a result, the pickup location is not the related location for the department. This was fixed. - December 2023 Fulfillment SF: 06720904 URM-197283
Corrupted data caused creation of new requests to fail. Thiis was fixed. In addition, a check was added where if for whatever reason corrupted data does exist, it will not result in a failure to create new requests. - December 2023 Fulfillment SF: 06755377 06755364 URM-199517
The Item history was displaying an incorrect Return circulation desk name. This was fixed for most cases. There is a specific case where the Return circulation desk name will be empty - this is still being resolved. - December 2023 Fulfillment – Resource Sharing SF: 06767740 URM-198752
Using the create request form with the "send directly to partner" functionality resulted in trying to create a Rapido request with an offer, even though a partner was chosen for the request. This was fixed and the regular send directly to partner workflow used. - December 2023 Fulfillment – Resource Sharing SF: 06873339 URM-206593
For a certain borrowing request, the customer received an error when trying to reject a partner with the "Other" reason. This was fixed. - December 2023 Fulfillment – Resource Sharing SF: 06872486 URM-205148
Manually marking a borrowing request as 'lost' would fail in some cases with an error. This was fixed. - December 2023 Fulfillment – Resource Sharing SF: 06620792 URM-196056
Special characters in the 'atitle' caused differences in the target URL between SFX and Alma so that it did not resolve correctly. This was fixed. - December 2023 Physical Resource Management SF: 06885713 URM-206880
When trying to run the Job Change "Physical items information" job, in the form Use Receiving number sequence / Use Weeding number Sequence, the "Select" button throws an error message. This was fixed. - December 2023 Resource Management SF: 06863747 URM-206031
General Publishing > When publishing in 'Binary' format and selecting 'Include all records each time file is published', the finalizing phase sometimes took a long time to complete. This was fixed and the finalizing phase was improved. - December 2023 Resource Management SF: 06868929 URM-205954
The utilization of Boolean nesting and 'Add Group' in the Advanced Search for Physical Holdings does not yield the expected results. This was fixed. - December 2023 Resource Management SF: 06790888 URM-201071
The Hong Kong TSVCC characters conversion table was missing characters and needed to be enhanced. This was fixed by adding the missing characters (甯, 寗, 襍, 㱷, 䌖). - December 2023 Resource Management SF: 06683144 06790824 URM-189939
Bib records with dual appearances of headings, one without subdivisions and the other with, experienced a full linking error for the latter. This caused the removal of subdivisions during the preferred term correction job. The issue has been rectified, ensuring that headings with subdivisions are now partially linked, and the subdivisions persist after the preferred term correction job. Importantly, the fix is safeguarded by the default-enabled customer parameter "temp_ptc_strips_subdivisions_fix." - December 2023 Resource Management URM-195300
NACSIS Cloud App: The Shipping cost field was erroneously editable by the borrower. This was fixed and editing of this field is blocked for borrowers in all borrowing request forms. - December 2023 Resource Management URM-199801
Numerous accessibility issues were reported pertaining to the Metadata Editor Records and Indication Rules Forms. All the reported issues (too numerous to list individually) were rectified. - December 2023 Resource Management SF: 5311740 05330440 05767812 05835863 URM-93797
Facets counters issue in Holdings search and Physical items search. There was a difference in numbers between the facet and the displayed results. This was fixed. - December 2023 Resource Management SF: 06748296 06833004 URM-198726
UNIMARC: F3 does not find authority and bib headings for the field 500 and does not link the headings. This was fixed by adding a new customer parameter: 'unimarc_uniform_title_headings_split'. When set to 'true' - F3 opens different lists for 410 (Series) and 500 (Uniform title). When set to 'false' - F3 opens a combined list for 410 (Series) and 500 (Uniform title). The default value is 'true'. - December 2023 Resource Management SF: 06687592 URM-191830
SBN contribution of parent records - When '463' fields are removed in Alma, the record was changed to a regular record (instead of parent record) upon contribution. This was fixed. Now, when the new customer parameter 'sbn_dont_update_parent_links_upon_contribution' is set to 'true', the record remains a parent record after the contribution.
- November 2023 Acquisitions SF: 06746551 URM-193471
The packaging job created many report events instead of one event that linked to the processed records. This was fixed and there is now one event in the report that presents the count of the created POs. - November 2023 Acquisitions SF: 06677829 URM-195970
The Invoice Service API changed the voucher_date value to a day before what was sent. This was fixed. - November 2023 Acquisitions SF: 06659027 URM-199818
Purchase requests could be created from a citation with deleted inventory. This was fixed. - November 2023 Acquisitions SF: 06870839 URM-205134
For the new UI for PO lines, in the advanced order lines search, the date format did not match regional standards. This was fixed. - November 2023 Acquisitions SF: 06770849 URM-196596
An error occurred for a specific PO in review when selecting Save and Continue. This was due to a data issue and was fixed. - November 2023 Acquisitions SF: 06819403 06796008 06789480 URM-198762
When trying to change the acquisition method for two migrated PO lines, the "Update PO Lines Information - Advanced" job completed with errors. This was fixed. - November 2023 Acquisitions SF: 06538626 06634001 06730632 URM-190334
Previously, the Data Corrector Correct Invoice Task failed to delete invoices that did not have invoice lines or whose invoice lines did not have PO lines. This was fixed and the procedure now deletes invoices as it should. - November 2023 Acquisitions SF: 06275266 06564712 06621140 06573671 06638644 URM-171236
Weekly and daily prediction patterns did not count the next cycle correctly. The first cycle of "Open predicted items" worked properly, but when clicking again on the "Next predicted item's information" menu item, the dialog box presented the information from the previous cycle. This was fixed. - November 2023 Acquisitions SF: 06836931 06816763 URM-203330
The job report for “Ledger-Open New Fiscal Period” had incorrect data in the “From Year” field when selecting a previous fiscal year. This was fixed. - November 2023 Acquisitions SF: 06717608 06885014 URM-193372
The output file name was changed to include the PO Number in the file name: edi.aaaaaa.YYYYMMDD.HHMMSS.MS.n.xxxxxx where the aaaaaa part holds the PO Number. - November 2023 Administration and Infrastructure SF: 06823555 06594003 06799554 06567575 URM-182492
The "Update/Notify Users" job was not toggling the Account Type of some accounts from "Internal" to "External". This was fixed. - November 2023 Administration and Infrastructure SF: 06552850 URM-184807
Two problems relating to the composition of a general email to a user were fixed: Previously, the email form was missing the asterisk indicating that the "Body" field was mandatory. In addition, the error message that appeared when an email with an incorrect From/To/CC address was sent was not phrased clearly. Both of these problems were fixed. The "Body" field is now marked with an asterisk, and the error message that appears when an email with an incorrect address is sent is phrased clearly. - November 2023 Administration and Infrastructure SF: 06470557 URM-186079
Institutions that enabled the Cataloging Level option didn't see that field in the user registration form. This was fixed, and it now appears in the user registration form. - November 2023 Administration and Infrastructure SF: 06674550 URM-191300
Previously the "View Fines/Fees Notification Jobs" button led incorrectly to a list of "Loans - Overdue and Lost Item" jobs. This was fixed and now the button leads to the list of "Fines\Fees Notifications" Jobs. - November 2023 Administration and Infrastructure SF: 06700924 URM-193238
Implementing the User EXPORT in the Student Information System profile failed when choosing a value other than the primary ID in the User ID Type field. This was fixed. - November 2023 Administration and Infrastructure SF: 06850227 06877524 06846403 06842795 06855228 06847822 URM-202185
Letters configuration >Letters example: Customizing Letters has no option to delete letter examples. This was fixed. A new action, "Delete" was added to letters uploaded or added by users. The Delete action is not offered to the DefaultLetter.xml (out-of-box letter example). - November 2023 Administration and Infrastructure SF: 06845886 06855779 06863693 06856895 06883971 06859929 06889838 URM-204254
The new XSL Editor UI - "Send example by mail" did not handle "Subject" and "AddressFrom" correctly. This was fixed and the "Send example by mail" takes the Subject and AddressFrom from the XML. - November 2023 Administration and Infrastructure SF: 05322319 05319240 06826866 06533384 06654450 06473503 06644802 06827070 06287140 06446587 06607546 06604525 06632724 06569319 05308745 06661962 05308702 06527416 06586791 06684289 06690909 06704004 URM-167233
Library names are not translated to Japanese on some APDs and displayed in English. Refresh does not help. This was fixed and the Library names are translated properly. - November 2023 Administration and Infrastructure SF: 06733771 URM-202168
When the same recipient received an email from various Alma libraries, Gmail's cache sometimes confused the attached logo files. This was fixed by giving each logo file a unique name. - November 2023 Administration and Infrastructure SF: 06869981 URM-205133
XSL for letter component could not be updated after saving it as a draft. This was fixed and the letter component can now be successfully saved. - November 2023 Administration and Infrastructure SF: 06562717 URM-182506
MELI: Hebrew interface issues in Alma. The HEP issues were fixed. - November 2023 Administration and Infrastructure SF: 06664946 06656208 URM-190839
When the 'Font_for_special_characters' customer parameter is enabled while editing a record in the Metadata Editor and focusing on a long field that is split into multiple lines, the field is reduced to one line and cut off. This was fixed and now, upon focus, the long field's content is fully displayed. - November 2023 Administration and Infrastructure SF: 06816195 URM-198633
RTL Languages: The 'Copy' pop-up prompt is larger than expected. This was fixed and the prompt is displayed properly. - November 2023 Administration and Infrastructure SF: 06562717 URM-201489
Metadata Editor > Hebrew: In RTL languages, the arrows for sub-menus were incorrectly displayed on the right side. This was fixed and now the arrows for sub-menus are displayed on the left side. - November 2023 Administration and Infrastructure SF: 06842498 06672693 URM-202157
Library/desk selector drop-down lists are not sorted according to the Spanish alphabet. This was fixed and the list is now alphabetically displayed. - November 2023 Administration and Infrastructure SF: 06848688 06909153 06878262 06878764 URM-203272
A few of the titles of facets in the Manage Sets page were not translated. This was fixed and the facets are properly translated. - November 2023 Administration and Infrastructure SF: 06754095 URM-204514
The task list label, "Ready to be sent“ in the task list is not translatable. This was fixed by adding the functionality that enables translation of the new tasks. - November 2023 Administration and Infrastructure SF: 06845212 URM-204849
The Task Parameters tab under the configuration menu did not display parameters in View mode. This was fixed. - November 2023 Administration and Infrastructure URM-197176
Resolved the feedback concerning challenges encountered while using the Dragon Voice detection system in Alma. For more information, see the November 2023 Release Notes > Accessibility Improvements - November 2023 Administration and Infrastructure URM-198952
Ex Libris effectively managed and resolved numerous existing issues found in the Deque report. It is crucial to systematically investigate each concern, comprehend its root cause, and undertake the necessary steps to rectify or mitigate the identified issues, ensuring the seamless functionality and accessibility of the system. - November 2023 Administration and Infrastructure SF: 06769857 URM-197609
Some Job Names and Descriptions were missing translations. This was fixed and the translations are working properly. - November 2023 Administration and Infrastructure SF: 06705534 URM-191275
Importing Excel files to a code-table failed for some of the code tables. This was fixed and now importing Excel files works properly. - November 2023 Administration and Infrastructure SF: 06843178 06855343 URM-203546
New Letter Editor: Letter templates with a terminate clause could not be saved. This was fixed and the templates can now be saved. - November 2023 Administration and Infrastructure SF: 06736482 URM-198682
When exporting sections of "Job Reports to Excel", a few column headers were missing. This was fixed and the column headers are now displayed. - November 2023 Analytics SF: 06847018 URM-203436
The Alma Analytics Menu does not open on Android devices. This was fixed by removing the search bars from the Alma menus. - November 2023 Analytics SF: 6552521 06553683 06553690 06553699 06553830 06553996 06568285 06570196 06570208 06627076 06627085 06627230 06627249 06627251 06627303 06629098 06630302 06630370 06630391 06630398 06630583 06647292 06647362 06682460 06682513 06704422 06704447 06704432 06704460 06704504 06704536, 06704635 06704764 06719836 06719971 06720035 06720142 06720132 06736968 06737107 06788480 06796051 06796047 06796056 06796056 06811546 06865123
When exporting an analytics report in any format, the error message "Server is busy. Please retry after some time." was displayed. This was fixed by making a change in the configurations. - November 2023 Analytics SF: 06610334 06663880 06667537 06692247 06875247, URM-184816
Data in the Analytics Usage Tracking subject area was not being updated. This was fixed by switching to a new method to harvest the data. - November 2023 Analytics SF: 06700562 URM-196712
The default data format for the Object ID in the Analytics Objects subject area inserts a comma as a thousand separator. This was fixed, and now the separator does not appear. - November 2023 Analytics SF: 06842785 URM-205355
Export from the Analytics Object List and Share with Me in the analytics new layout failed in some cases. This was fixed. - November 2023 Analytics SF: 06549289 URM-184771
In the Borrowing Requests Analytics report, the Days of Request Sent to Material Arrival field sometimes displayed a negative number. This was fixed. - November 2023 Analytics SF: 06772175 URM-198181
Analytics reports with a large number of rows produced an Out of Memory error when displayed in the Preview window of the analytics new layout. This was fixed by limiting the preview to the first page of the report. - November 2023 Analytics SF: 06798758 URM-198240
In the analytics new layout, editing roles and internal users from the Share section did not update the Object Modified By information. This was fixed. - November 2023 APIs SF: 06331666 06742445 URM-180575
When updating a location's Fulfillment Unit via the API, the change was not effective immediately unless the location was edited and saved manually. This was fixed. - November 2023 APIs SF: 06666552 URM-189420
Previously, the "Get Lending Requests" API was limited to 100 results. This has been increased to 1000 results. - November 2023 APIs SF: 06682984 URM-191251
The rest_user.xsd description file was updated and now mentions that the external_id should (and not "must" as was previously written) match a valid SIS external system profile. - November 2023 APIs SF: 06802193 URM-203351
There were issues with running an MD-Import job using an API. This was fixed. - November 2023 APIs SF: 06889925 URM-207750
The Create PO Line API applied a discount twice. This was fixed and now, when creating a PO line from the API, the discount is calculated once. - November 2023 Digital Resource Management SF: 06056941 URM-171763
Sometimes, when several representations are created in parallel, two IEDs were created for the same bibliographic record. This was fixed and now only one IED is created. - November 2023 Digital Resource Management URM-URM-203470 URM-204259
Previously, the Synchronize All Logical Collections Job (Configuration > Resources > General > Resource Management Jobs Configuration) was set to Active by default, and the Default Collection was mandatory. Now the job is set to Inactive by default, and the Default Collection is only mandatory when the job is set to Active. - November 2023 Electronic Resource Management SF: 06495024 URM-185182
On rare occasions, a wrong Interface Name caused wrong information in Analytics. This was fixed and a data corrector was built to fix the wrong data. - November 2023 Electronic Resource Management SF: 06799196 URM-198632
Extended export of portfolios from the Community Zone (of a large collection) was completed successfully but files did not open. This was fixed. - November 2023 Electronic Resource Management SF: 06851725 URM-206128
On rare occasions, the "Relink portfolio to another bibliographic record" button did not appear in the "General" tab in the Portfolio Editor, even when it should have been. This was fixed. - November 2023 Electronic Resource Management SF: 06648421 URM-198394
On rare occasions the advanced search for the portfolio's modification date retrieved results outside of the searched range. This was fixed. - November 2023 Electronic Resource Management SF: 06565326 06865497 URM-199104
Overlap analysis lookup titles did not find matches to title identifiers with special characters. This was fixed. - November 2023 Fulfillment SF: 06572730 06784765 URM-198089
When returning items on the Return Items page, quick printing would only print the last one. This was fixed and now all the letters are printed. - November 2023 Fulfillment SF: 06446126 06573885 06054826 05316646 05318675 URM-198578
The "On shelf request policy" sometimes caused requests for PO-line interested users to fail. This was fixed. The "On shelf request policy" is no longer applied for interested user requests. - November 2023 Fulfillment SF: 06563226 URM-182390
In some cases, Alma allowed more loans per user via Self Check than was permitted in the loan-limit configuration. This was fixed and the Self-Check loan limit is now applied correctly. - November 2023 Fulfillment SF: 06790028 06818616 URM-197281
When printing multiple resource request slips, a single request took up more than one page in the new version of Chrome. This was fixed. - November 2023 Fulfillment SF: 06673052 URM-191827
Previously, the Reloan Limit policy did not apply unless the material type field was filled out for the item. This was fixed and now the Reloan Limit policy also applies when the material type field is empty. - November 2023 Fulfillment SF: 06665894 URM-191211
When there were multiple active requests on the same title, sometimes the wrong requester details were displayed on the Resource Request Slip. This was fixed. - November 2023 Fulfillment SF: 06707022 06720790 URM-191672
In some cases, the Requests - Recalculate after Inventory Update job failed, since it tried to handle electronic titles. This was fixed. - November 2023 Fulfillment SF: 06320240 URM-172500
The start and end time of a booking request in Primo was always the entered time (the opening hours were not checked). This was fixed. - November 2023 Fulfillment – Resource Sharing SF: 06598039 URM-184111
In some cases, borrowing requests got stuck in a Created Borrowing Request status. This was fixed. - November 2023 Fulfillment – Resource Sharing SF: 06848626 URM-202220
Previously, borrowing requests were created for libraries that were temporarily not allowing any borrowing requests. This was fixed. - November 2023 Fulfillment – Resource Sharing SF: 06832645 06913712 06854389 06889289 06868770 URM-203443
In some cases, lending requests received from RapidIll were auto-rejected. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06656516 URM-201796
When sending a RequestItem message to an NCIP P2P partner, Alma would always send both the PhysicalAddress and the ElectronicAddress in the ShippingInfromation element. This was fixed and now Alma sends only PhysicalAddress if the requested format is physical and only ElectronicAddress if the requested format is electronic. In addition, when sending ElectronicAddress, the ElectronicAddressType element now comes before the ElectronicAddressData element. - November 2023 Fulfillment Resource Sharing SF: 06656516 URM-201797
When Alma responded to an NCIP P2P request for renewal, it sent a RenewItemResponse with invalid elements. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06574318 URM-185306
In some cases, the Assignee facet filtered results incorrectly. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06653445 URM-187447
Previously, labels did not appear in a number of Resource Sharing letters when they should have. This was fixed, and now the labels appear in these letters as they should. The following letters were impacted by this issue: DocumentDeliveryNotificationItemLetter, FulDigitizationNotificationItemLetter, FulOutgoingEmailLetter, BorrowerClaimEmailLetter, FulRenewEmailLetter, FulCancelEmailLetter, BorrowerOverdueEmailLetter, LendingRecallEmailLetter, QueryToPatrontLetter, ExternallyObtainedLetter, BorrowerReturnEmailLetter, BorrowerReceiveEmailLetter, GeneralMessageEmailLetter, LostEmailLetter and DamagedEmailLetter. - November 2023 Fulfillment Resource Sharing SF: 06658062 06053160 URM-188061
Previously, the Digitization Notification Item Letter did not populate the metadata included in the lending request. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06674022 06405817 URM-189534
In some cases, downloading the SAML URL from the Ful Digitization Notification Item Letter gave a “Resource was not found” message. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06464466 URM-189565
Previously, the alternative address option capitalization did not match the BLDSS specifications. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06800831 06599182 URM-191365
Resource sharing locates would fail when the 'ISBN' string was included in the ISBN field. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06654459 URM-191680
Previously, when receiving a request multiple times, the Receive fee was applied to each request. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06598672 06678577 06594015 URM-193839
An error was displayed when trying to request multiple barcode renewal requests for a borrowing request. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06723609 06729014 06727316 URM-194927
In some cases, selecting the browser back button caused an error in Alma. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06750955 URM-195170
Previously, the export request spreadsheet did not include a Journal Title column. This was fixed and the borrowing and lending exports now include this column. - November 2023 Fulfillment Resource Sharing SF: 06739538 06847946 06850794 06881040 06868145 06766503 URM-196499
In some cases, borrowing requests were sent twice, which created lending requests with duplicate external IDs. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06771180 06810359 06734926 URM-197256
Previously, the Override and Renew button was not visible in non-English environments. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 06649573 URM-196673
Duplicate borrowing request blocks were preventing requests for different items on the same title. This was fixed. - November 2023 Fulfillment Resource Sharing SF: 05310778 URM-173952
When an NCIP flow deleted the item, it did not fully close all requests associated with it. This was fixed by closing all fulfilment requests in the check-in process. - November 2023 Fulfillment Resource Sharing SF: 06646761 URM-191006
When creating a request in Alma and then updating the request through Netpunkt, there were duplicate partner rows in the Rota tab. This was fixed. - November 2023 Physical Resource Management SF: 06600429 URM-185856
While creating a new physical item, when an Enumeration or a Chron field was not empty, the description was not automatically generated at the first save. This was fixed. - November 2023 Physical Resource Management SF: 06720884 URM-191742
Change Holding Information job completed with errors using a Holdings Normalization process when the normalization rule included a leading whitespace referring to the holdings' location. This was fixed. - November 2023 Physical Resource Management SF: 06730347 URM-193133
Physical Item Editor: Unable to add dates prior to 1900 into the receiving date field in item records. This was fixed - November 2023 Physical Resource Management SF: 06754868 URM-194662
Physical Titles Repository Search results > Holdings List: The "delete holdings" operation deletes all originally multiple selected holdings, even if the user unchecked one of them after a "delete holdings" and cancel of a confirmation message. This was fixed. - November 2023 Physical Resource Management SF: 06752482 URM-198835
Material types that were disabled were displayed as an option in quick cataloging while creating a new physical item from the existing holding type. This was fixed. - November 2023 Physical Resource Management SF: 06556188 URM-202173
When a bib record has more than one holding and there is more than one item in each holding, the Change Physical Items Information job creates multiple identical holdings if the items are moved to the same target holding. This was fixed. - November 2023 Resource Management SF: 06759796 URM-198278
On rare occasions, general publishing creates invalid XML files. This was fixed. - November 2023 Resource Management SF: 06690742 06626278 URM-192178
Bibliographic records were deleted only in the Institution Zone when a purchase request is rejected and not in the Network Zone. This was fixed so that if a Network Zone cached bib record is deleted from the Institution Zone, it will attempt to delete in the Network Zone. - November 2023 Resource Management SF: 06803610 URM-201919
Normalization rules that replace a hashtag (#) field indicator (first or second) with, for example, a space, did not work. For example, the "Change Holdings Information" job that ran on a holdings record with field 852 first indicator "#", using a normalization process with the rule: changeFirstIndicator "852" to " " if (exists "852.{#,*}") , did not change the first indicator to " ". This was fixed. - November 2023 Resource Management SF: 06287200 URM-171171
When a failed search using a permanent location is performed, an error appears, and when you try to change the search parameters, the location code displays instead of the location name after a failed advanced search. This was fixed and now the search operates properly. - November 2023 Resource Management SF: 06452535 URM-181802
Certain resource types were not defined in the resource type field. This was fixed by: 1) The redundant entry "Resource Type" was removed from the list of the "Resource Type" index entries in Advanced Search and 2) The following (missing) entries were added to the "Resource Type" advanced search index: "3D artifact - Digital", "Atlas - Microfilm", "Atlas - Microfiche", and "Atlas - Microopaque". - November 2023 Resource Management SF: 06677226 06878316 URM-189459
Authorities Search: "Search bibliographic records matching this value" displays only matches for some local authorities using the search query "contains phrase". This was fixed. The "Search bibliographic records matching this value" button now uses only the "Contains keywords" operator instead of "Contains phrase" (which does not retrieve bib results in some cases). - November 2023 Resource Management SF: 05301320 URM-154034
Records in Japanese whose titles include the sequence ["?" (UC30FC) and "?" (UC30FB)], were not found when searched as a title. This was fixed and title searches now successfully find the mentioned characters. - November 2023 Resource Management SF: 06558845 URM-186265
The field "other.." in the Get-It page was not translated. This was fixed. It now can be translated from the Code Table Labels in the Fulfillment Section. - November 2023 Resource Management SF: 06764781 URM-195255
Han proxy license types did not translate in ViewIt in German UI. This was fixed. - November 2023 Resource Management SF: 05299554 URM-149292
While editing a bib record in the metadata editor, and breaking the link of a field that is linked to an authority record (by ctrl+x/adding or removing character) and then pressing F8 (add new field), the cursor jumps to the $a of the new field (not expected). It should jump to the tag of the new field (expected). This was fixed and now the cursor jumps to the tag area. - November 2023 Resource Management SF: 06697440 06726589 06727402 06693634 06791340 06734639 URM-190884
In the Metadata Editor, sometimes no records were displayed in the navigation pane (records list). The issue occurs after collapsing the navigation pane, hiding the Metadata Editor, opening it again, and expanding the navigation pane. This was fixed and now the records are displayed in the navigation pane as expected. - November 2023 Resource Management SF: 06664574 URM-191265
Metadata Editor > UNIMARC: Field Information was not displayed. This was fixed and now the Metadata Editor displays an explanation for the field. - November 2023 Resource Management SF: 06690329 URM-193184
When activating a portfolio from the Community Zone, a cached (linked) record is created in the institution. However, the Brief Level of the newly created local record was copied from the Community Zone record rather than being calculated according to the institution's Brief Level rules. This was fixed. - November 2023 Resource Management SF: 06750533 URM-193447
In the MD Editor, the "Record Save" shortcut (Ctrl+S) did not work when the user's catalog level was lower than the record level. This was fixed. - November 2023 Resource Management SF: 06757688 URM-194781
When the 'Font_for_special_characters' customer parameter was enabled, the records in the Metadata Editor still initially loaded with the original font. This was fixed and now the records are initially loaded with the special (Calibri) font. - November 2023 Resource Management SF: 06645723 URM-194958
Metadata Editor > Browse Bibliographic Headings: When a bib heading of LCNAMES contains a quotation mark, the "Open in Repository Search" button did not respond. This was fixed. - November 2023 Resource Management SF: 06757689 URM-195216
When the 'Font_for_special_characters' customer parameter was enabled while editing a record in the Metadata Editor and a value for a subfield from a controlled vocabulary wasselected, the record flashes momentarily to the regular font. This was fixed and now the font is not momentarily changed. - November 2023 Resource Management SF: 06722317 URM-196346
In control fields such as LDR and 008, when "Force form editing" was enabled, the form did not open immediately and it was possible to accidentally add a character that caused a line break. This was fixed, and the form opens as soon as the cursor is moved to the control field. Note that if LDR is set to force form editing, the LDR form is open when entering the record. - November 2023 Resource Management SF: 06804092 URM-199461
Metadata Editor: Special characters in the Language Dropdown of the 008 field were not displayed properly. This was fixed. - November 2023 Resource Management
Accessibility issues: The following issues from the ADR report have been resolved: ADR_15422-37, ADR_15422-11, ADR_15422-27, ADR_15422-28, ADR_15422-30 (N/A), ADR_15422-32. - November 2023 Resource Management SF: 06797477 URM-198071
Metadata Editor > KORMARC: Leader position 7 was requested to be updated. This was resolved and 041 $$k was added to the metadata profile. - November 2023 Resource Management SF: 06561495 URM-183768
Metadata Editor: In the preview mode of the "Duplicated records" pane, the "Edit" option was not working in any language other than English. This was fixed. - November 2023 Resource Management SF: 06768611 06799874 06749867 06872858 06847320 06704615 06754848 URM-191643
The Preferred Term Correction job did not flip headings. This was because corrupted authority records have non-preferred headings marked as preferred. The root cause was fixed, and now new authority headings are marked as preferred only if they actually are. The upcoming semi-annual indexing will gradually fix existing harmed records (Nov-Dec). - November 2023 Resource Management SF: 06738812 URM-193463
When a local authority has a directional character, sometimes a link from the bib to the local heading is not working correctly. The deployment of this fix is gradual, depending on the record's update or full inventory indexing (the next job is planned for November). - November 2023 Resource Management SF: 06569253 URM-183165
Repository import using OAI MARC21 Bibliographic fails with the error "File Failed in Loading". This was fixed and the files now load properly. - November 2023 Resource Management SF: 06800454 06709008 06767353 06757865 06747275 06750229 06754779 06747433 URM-193438
Selecting "Resolve Import Issues" gives a blank screen with an error message and a unique tracking ID. This was fixed and no errors are displayed. - November 2023 Resource Management SF: 05316751 URM-166408
UNIMARC decimal classification sorts the main class value at the end of the list. This was fixed. The fix will be deployed gradually with the next semiannual indexing (planned for November). - November 2023 Resource Management SF: 06776098 URM-198070
KORMARC: When adding 041 $$k, a warning is displayed saying "Sub-field "k" is not listed in profile for field 041". According to KORMARC, it is valid. This was resolved and 041 $$k was added to the metadata profile. - November 2023 Resource Management SF: 06484262 URM-180512
Cloud App NACSIS-CAT: Issues arose with 490 and 830 fields after the August release. This was fixed. Series statements (490 fields) and Series added entries (830 fields) along with relevant alternative graphic representations (880 fields) are now correctly created. - November 2023 Resource Management SF: 06499527 URM-180812
Cloud App NACSIS-CAT: When a title has several PTBL, specially more than 3, the order gets shuffled in Alma. This was fixed. Series statements (490 fields) and Series added entries (830 fields) along with relevant alternative graphic representations (880 fields) are correctly created. - November 2023 Resource Management SF: 06546956 URM-182558
Cloud App NACSIS-CAT: An error occurs when contributing records with 2 subfields a in tag 490 and if there is tag 830, the contribution of 490 is skipped. This was fixed. PTBL group is now correctly populated from contents of the 490 field and linked Alternate Graphic Representations (AKA 880 fields).
- October 2023 Acquisitions SF: 5299957 URM-164301
When a hold request from an interested user was added to the queue, it was incorrectly added at the end of the queue. This was because other requests that should have a lower priority had already been activated in the queue. The order in which these processes are performed was reversed so that interested users are entered into the queue before activation takes place and are thus given the correct priority in the queue. - October 2023 Acquisitions SF: 6734801 URM-195383
There was a problem when trying to add funds when the fund code contained only numbers. This was fixed. - October 2023 Acquisitions SF:6702686 URM-191469
Until now, it was possible in Alma to create two invoices for the same supplier with the same invoice number. This was fixed. Now, when the customer parameter "invoice_not_unique" is false, it is impossible to duplicate the invoice number of the same supplier. - October 2023 Acquisitions SF:6629131 URM-195393
Past funds were accessible in the recent funds drop-down list when creating PO lines. This was fixed. Now, if the user has a previous fiscal year fund, when selecting "Save and Continue" or "Order Now", a message is displayed that the fund is not in the current fiscal year. - October 2023 Analytics SF:6711398 URM-199209
Usage data from several SUSHI files did not appear in Analytics. This was fixed.
- September 2023 Acquisitions SF: 06733671 06808998 06847149 URM-198228
When all claimed PO Lines were from the same owning library, the PO Line Aggregated Claim Letter used the sender address from the institution instead of the library. This was fixed and the address from the library is used in these cases. - September 2023 Acquisitions SF: 06715538 06688912
When a purchase request was created from Primo/VE, Alma did not populate the default value for the Interested user. The default value would only be populated when editing and saving the purchase request. This was fixed. - September 2023 Acquisitions SF: 06734935 URM-198161
In some cases, when editing a PO Line to add an Associated order, the information did not display properly in the Summary tab. This was fixed. - September 2023 Acquisitions SF: 06819403 06796008 06789480 URM-198762
When trying to change the acquisition method for two migrated PO lines, the "Update PO Lines Information - Advanced" job completed with errors. This was fixed. - September 2023 Acquisitions SF: 06621972 URM-191573
A user with only the invoice operator role was able to approve invoices. This was fixed. - September 2023 Acquisitions SF: 06636125 URM-197109
The new UI/Discoverability of the License Terms Translatable Text Area feature did not work with Amendment type licenses. This was fixed. - September 2023 Acquisitions SF: 06654839 06630153 06053479 URM-169267
Trials did not get the most updated URL from the collection. This was fixed. - September 2023 Acquisitions SF: 06705518 URM-192212
When selecting Transfer Funds, if previous FY funds were in the Recent drop down, then funds could be transferred to that old fund. This was fixed. Note that a similar issue was fixed in the past in the Transfer Fund form. - September 2023 Acquisitions SF: 06737831 URM-196836
When a Vendor was changed on an invoice that had the vendor account populated, the change did not remove the vendor account from the invoice. This caused incorrect 'Vendor Account' information in re-exported invoice files for the ERP. This was fixed. Now, when the vendor is changed and the invoice is saved, Alma verifies that the vendor account is valid. - September 2023 Acquisitions SF: 06572487 URM-190982
The item parent fields were not loaded in IR_A1 reports for Proquest. This was fixed. - September 2023 Acquisitions SF: 06710685 06725092 URM-191642
The ERP export job would run for 24 hours and create duplicate XML output files. This was fixed. - September 2023 Acquisitions SF: 06523609 URM-197272
The "Create inventory only for new bibliographic records" field was removed from New Order and Update inventory profiles, as this functionality is only supported in Import Repository. - September 2023 Administration and Infrastructure SF: 06618247 06629929 URM-189672
Previously, A ‘PIN Number Generation Letter’ is sent every time the user account type was toggled, from Internal to External and vice versa. This was fixed and now the letter is not sent when toggling the user account type. - September 2023 Administration and Infrastructure SF: 06661903 06491578 URM-191287
Large number of rows in mapping table appears to cause "Statistical Categories/Types" configuration page to crash. This is fixed. Solution: if there are more than 1000 options in combobox it becomes read only and user can add and remove but not edit. - September 2023 Administration and Infrastructure SF: 06848637 URM-202175
Within the "New Letters XSL Editor", the function 'Save and distribute' was not triggering the network letters distribution job. This was fixed. - September 2023 Administration and Infrastructure SF: 06801585 URM-198534
Previously, an error occurred when deleting a newly created remote storage location. This was fixed. - September 2023 Analytics SF: 06725222 URM-196030
When the Material Type field from the Physical Items dimension was added to reports, the values of the measure fields were doubled. This was fixed and now the data is correct. - September 2023 Analytics SF: 06753573 URM-196706
When creating an analytics report for courses without citations, the report displayed that there were citations for the course. This was fixed, and now reports for courses without citations display that the courses have no citations. - September 2023 Analytics SF: 06701845 URM-196988
When a holdings record was deleted, the modification date was not updated in Analytics. This was fixed. - September 2023 API SF: 06718186 URM-192961
An error occurred when trying to update the fund for some orders via API ("The funding list contains invalid values"). This was fixed. - September 2023 Digital Resource Management SF: 06444002 URM-180365
Changing the label of a representation was not saved. This was fixed. - September 2023 Digital Resource Management SF: 06675310 URM-190999
The Universal Viewer failed to display PDF files and instead displayed an error message. This was fixed. - September 2023 Digital Resource Management SF: 06562231 URM-195966
Digital titles with access rights of an embargo by publication year were not available even after the specified time period after the publication year passed. This was fixed. - September 2023 Digital Resource Management SF: 06792130 URM-198416
In the Digital Deposit Form, labels with periods were not displayed properly in the form. This was fixed. - September 2023 Digital Resource Management SF: 06847179 URM-201899
Changes to file labels in the Digital File Editor could not be saved. This was fixed. - September 2023 Electronic Resource Management SF: 06692362 06758368 06533449 06676292 06432269 URM-180856
The material type value is not displayed in the portfolio list view of the service if the value is stored in the electronic material type. This was fixed and now the material type in the electronic pages displays the value of the electronic material type if it exists, otherwise the bib material type. - September 2023 Electronic Resource Management SF: 06676452 URM-190464
Collection Group was deleted when a new one is added, overwriting the previously edited group. This happened after editing a collection/service/portfolio group settings, and then clicking the 'Cancel' button. This was fixed, and saving a new group is created successfully. - September 2023 Electronic Resource Management SF: 06765560 06781159 URM-195399
Not all portfolios were activated by the portfolio loader. This was fixed, the portfolio loader now activates the portfolios from the input file. - September 2023 Electronic Resource Management SF: 06792165 URM-196905
The library field under the Electronic Collection history tab appeared incorrectly when clearing the library from the collection's library field. This was fixed, the library field in the history now shows the correct information. - September 2023 Fulfillment SF: 06734542 URM-197906
Previously, in some cases, an error occurred when trying to import the “RequestCancellationReasons” table without the "RemoteStorageCannotFulfill" cancellation reason. This was fixed. - September 2023 Fulfillment SF: 06619983 05330734 URM-187450
For RFID Integration with the 3M system, when writing data to a new RFID tag, Alma did not set the security status correctly. This was fixed. - September 2023 Fulfillment SF: 06684433 06730805 06708573 06847405 06681627 06731941 URM-192103
The Quick print dialogue window for the Resource Sharing Shipping Slip Letter was not displayed as expected. This was fixed. - September 2023 Fulfillment SF: 06755629 06728939 06802161 06812791 URM-194997
The Shortened Due Date letter was sent twice each time. This was fixed. - September 2023 Fulfillment SF: 06340072 06638824 URM-177022
Previously, when using the Deliver Digital Documents screen, if Automatic Printing was configured and the request being handled was not active, a Resource Request Slip was incorrectly printed when selecting the Done button. This was fixed, and the slip is no longer printed in this scenario. - September 2023 Fulfillment SF: 06644774 URM-191347
When cancelling a physical item request for an item on the hold shelf, the item is placed on the expired hold shelf. With two other requests in the queue, where the first has personal delivery as the pickup location, activating the next step in languages other than English, caused the item to fulfill both requests at once. This was fixed. - September 2023 Fulfillment SF: 06816361 06731958 06786521 06823437 06791762 06792465 06796291 URM-198493
Course names could not be edited in a non-English UI. This was fixed. - September 2023 Fulfillment SF: 05331127 URM-139784
Leganto sources were excluded from the Alma Link Resolver Usage report. This was fixed. - September 2023 Fulfillment – Resource Sharing SF: 06373220 URM-185286
The Manual Locate job would find resources in the partners catalogue, even though the partner didn't have the year when the requested article was published. This was fixed. - September 2023 Fulfillment – Resource Sharing SF: 06578293 URM-189612
When an item was requested for personal delivery, but the library staff marked it as reading room only, the request was still sent as a personal delivery rather than being sent to the reading room. This was fixed. - September 2023 Fulfillment – Resource Sharing SF: 06755495 06746375 URM-194761
The Record Customization option to display the Requested Media in the task lists, was not available in the borrowing requests task list and the lending task list. This was fixed. - September 2023 Fulfillment – Resource Sharing SF: 06614933 06571619 URM-182623
The partner listed on the Lending Request right pane was mistakenly listed as Lending Library rather than Borrowing Library. This was fixed. - September 2023 Fulfillment – Resource Sharing SF: 06680840 06708573 06681627 06690682 URM-189608
The print slip did not open even when a success message was displayed, and the slip was sent by email. This was fixed. - September 2023 Fulfillment – Resource Sharing SF: 06760744 06734687 06728285 URM-191584
Previously, when submitting an article request from a journal created an incorrect record. This was fixed. - September 2023 Fulfillment – Resource Sharing SF: 06649501 06589810 URM-166763
When sending files using the Fill locally action, the Upload file page did not open correctly. This was fixed. - September 2023 Resource Management SF: 06502462 URM-184488
Item Call Number: Occasionally, the same item call number was generated twice, so two different items were saved with the same call number value. This was fixed by blocking the item call number sequence (AKA "accession configuration") upon saving an item. Now, when two users try to generate and save new sequences of the same prefix, the table is blocked until the first item is saved and only then a new sequence is generated for the second item. - September 2023 Resource Management SF: 06843546 URM-200926
Campus Level Publishing: If the last copy is deleted on a symbol but exists on another, a record is published in the “deletes” file with the correct symbol in the symbol field, but the LDR/05 is showing “c” rather than “d” to indicate these holdings should be deleted from OCLC. This was fixed and now the deleted holdings are published with "d" in position 05 of the LDR field. - September 2023 Resource Management SF: 06836336 URM-203107
Could not create Physical Holdings sets filtered for Permanent Physical Location. This was fixed and now the advanced search retrieves results. - September 2023 Resource Management SF: 06761098 URM-198438
When the customer parameter "use_holdings_form" is activated, the Metadata Editor froze after trying to edit a holding that had already been opened a first time using the "View Inventory" > "Edit". This is fixed. - September 2023 Resource Management SF: 06704291 05310288 06655194 URM-100803
An error message was displayed when opening the mapping table for New Order Import Profile. This was fixed. - September 2023 Resource Management SF: 06794814 URM-198396
CNMARC - In the Metadata Editor, "Author Code" cannot be generated via "Enhance the Record" when there is a character “?” “zha” in 090. This was fixed. - September 2023 Resource Management SF: 05328281 URM-190247
SBN Contribution - The update of relator terms in tag 7XX subfield 4 was not updating the SBN. This was fixed and now the terms in tag 7XX subfield 4 are updated.
- August 2023 Acquisitions SF: 06631718 06760660 URM-189322
Previously, it was possible for a PO line to be deleted even if it had an invoice. This was fixed. Now, if a PO line has an invoice, it cannot be deleted. - August 2023 Acquisitions SF: 06672543 06725154 URM-195938
Previously, searches for PO lines in the Receiving Workbench included deleted PO lines. This has been fixed. Alma ignores deleted records when searching for PO lines in the Receiving Workbench. - August 2023 Acquisitions SF: 06729988 06411162 URM-176429
Previously, if a PO line for a subscription was in the claims list because some of the issues in the subscription were not received by their expected dates, although other issues were already received, changing the expected dates of the issues that were not yet received to dates in the future did not remove the PO line from the claims list. This was fixed. When the expected dates of issues that were not yet received are all changed to be in the future, the PO line is removed from the claims list. - August 2023 Acquisitions SF: 06590940 URM-190544
Previously, when a PO line whose acquisition method was Legal Deposit - No Letter went into claim, Alma sent the vendor the regular Claim letter. This was fixed. Alma now sends the Legal Deposit claim letter in this case. - August 2023 Acquisitions SF: 06693587 URM-191095
Previously, when the vendor of a PO line was replaced after the resource was received, the expected receiving date of the PO line was automatically modified, which in some cases caused the PO line to go into claim. This was fixed. Replacing the vendor of a PO line does not affect the expected receiving date. - August 2023 Acquisitions SF: 06694704 URM-193120
Previously, when a Legal Deposit Claim Letter was sent to a vendor, it gave the total number of items ordered as the total number of missing items, even if some of the ordered items were already received. This was fixed. The Legal Deposit Claim Letter now specifies the correct number of items that were not yet received. - August 2023 Acquisitions SF: 06701140 URM-191443
Two issues involving the EAN Account code list were corrected: (1) Previously, the sort mechanism of the list did not work. This was fixed. The account codes are now sorted alpha-numerically. (2) Previously, deleted and inactive account codes could be added to EAN list. They can no longer be added. - August 2023 Administration and Infrastructure SF: 06765370 URM-196559
Previously, patron fines with the status In Dispute were shown with a remaining amount of 0. This was fixed; the correct amount in dispute is now displayed. - August 2023 Administration and Infrastructure SF: 06636532 06551883 06572893 06551931 URM-182511
Previously, an error message was mistakenly displayed when a user working in the User Roles Profiles list tried to save a profile after deleting another profile. This was fixed. Saving a profile after deleting another profile no longer causes an error message to appear. - August 2023 Administration and Infrastructure SF: 06653508 URM-188861
Previously, any user with a Circulation Desk role could send a Personal Information Letter to a patron. Access to this letter for Circulation Desk roles is now controlled by the privilege "Send Patron Information Letter." By default, this privilege is activated for users with a Circulation Desk role, but the institution can deactivate it if they wish, so users with Circulation Desk roles will not be able to send these letters anymore. - August 2023 Administration and Infrastructure SF: 06572893 06650604 URM-189172
Previously, user blocks were only added to the user history after "Save" was selected in the user's record. This was fixed, and now every block that is added to a user (either manually or following an overdue item return) is immediately added to the user's history. - August 2023 Administration and Infrastructure SF: 06667582 URM-189633
Previously, in a specific case, there was a difficulty when a library card was scanned for the "Requester" field during the creation of a Patron Physical Item Request from an Alma repository search. This was fixed. When a library card is scanned in this situation, it now quickly and seamlessly. - August 2023 Administration and Infrastructure SF: 06689349 URM-191834
In a specific case, a user with Administrator roles was unable to see the Tasks list. This was fixed. The user can now see the Tasks list. - August 2023 Administration and Infrastructure SF: 06800703 06805939 URM-197690
Secure FTP Service: Generating keys for the Secure FTP Service failed for some customers. This was fixed and private keys can now be generated. - August 2023 Administration and Infrastructure SF: 06255631 06720158 URM-166635
Ellipsis buttons in the Alma UI/Searches are not compatible with voice dictation software. This was fixed and now the Ellipsis button in the action list is now also recognized by voice dictation (using the phrase: "More Actions"). - August 2023 Administration and Infrastructure SF: 06623904 URM-189539
Previously, there were missing translations for the word "All" in the User Details Fees tab. However, this issue has been successfully resolved and the missing translations were fixed. - August 2023 Administration and Infrastructure SF: 06715081 URM-194831
On the Pick-from-Shelf task-list, the Destination facet was not displaying translated library names. This was fixed. - August 2023 Administration and Infrastructure SF: 06638141 URM-186735
The ‘resource_sharing_request_id.png’ image is now available on the Resource Sharing Shipping Slip letter. - August 2023 Analytics SF: 06589415 URM-185145
The pickup location was displayed in Alma, but in analytics, for the pickup location, it displayed 'None'. This was fixed. - August 2023 Analytics SF: 06671408 URM-192564
Usage data for TR_J1 Usage in the E-inventory subject area does not match with the usage in the Usage Data (Counter) subject area. This was fixed. - August 2023 Analytics SF: 06779138 URM-196671
When creating an analytics object with the "ACRL &; IPEDS Dashboard", an error message “Path not Found” was displayed. This was fixed. - August 2023 Analytics SF: 06700562 URM-196712
The default data format for the Object ID in the Analytics Objects subject area inserts a comma as a thousand separator. This was fixed, and now the separator does not appear. - August 2023 Analytics SF: 06768315 URM-195862
Historical events were not reported by the Physical Items Historical Events subject area. This was fixed. - August 2023 Analytics SF: 06698941 URM-195341
When confirming the deletion of analytics objects in the new Analytics Objects List, the checkboxes were cleared, causing the user to be uncertain if the correct objects were being deleted. This was fixed, and now the checkboxes appear selected. - August 2023 Analytics URM-186087
The default text in a search box was confusing. It was changed to "Start typing to search." - August 2023 API SF: 06684071 URM-191370
Previously, the Update Purchase Request API did not update the currency value. This was fixed and now the currency value is correctly updated. - August 2023 API SF: 06722149 URM-197016
A change that was made to the XML of invoice exports was not reflected in the Developer Network documentation. The documentation has now been updated. - August 2023 Digital Resource Management SF: 06751212 06702271 URM-191255
The Alma viewer does not display PDFs when they are opened. This was fixed. - August 2023 Digital Resource Management SF: 06682322 URM-191750
Alma open remote representations in the Default View instead of the Current View. This is fixed. - August 2023 Digital Resource Management SF: 06722477 URM-196452
In Primo VE, Quick Access did not display digital resources with the IIIF viewer. This was fixed. - August 2023 Digital Resource Management SF: 06803753 URM-198169
In the FireFox browser, the file label in Quick Access was not updated correctly when moving back and forth between files. This was fixed. - August 2023 Electronic Resource Management SF: 06566356 URM-188915
In some cases, a user with Electronic Inventory Operator role could not activate a Community Zone Portfolio via the service. This was fixed and an operator is now able to add portfolios from the Community Zone to a collection. - August 2023 Electronic Resource Management SF: 06577001 URM-188989
The activation report summary was displaying incorrect information for portfolios not in the Community Zone collection. The "Localize and activate" option was mistakenly appearing for these portfolios. This was fixed and the activation report now shows accurate information for all portfolios. - August 2023 Electronic Resource Management SF: 06717551 06800972 URM-191520
Activating New Schedule for 'Upload Electronic Holdings' Job does not "Delete" the previous schedule. This was fixed, when saving the integration profile the previous schedule is deleted. - August 2023 Fulfillment SF: 06264721 URM-167487
In some cases, when an item whose bibliographic record had a large total number of items (such as 2,000), scanning its barcode took a very long time to complete. This has been fixed. Now, when the barcode of such an item is scanned, it is processed at the expected rate. - August 2023 Fulfillment SF: 06555418 URM-195673
Previously, the XML of the following letters did not contain the name of the loan circulation desk: Ful Overdue And Lost Loan Notification Letter, Ful Overdue And Lost Loan Letter, Ful Lost Loan Notification Letter, and Ful Lost Loan Letter. This was fixed. The name of the loan circulation desk has been added to all of these letters. - August 2023 Fulfillment SF: 06777511 URM-198314
Previously, in the "Patron Services" page, when the user switched between "All loans" and "Loans of this session," the cursor was not placed in the "Scan item barcode" field as it should have been. This was fixed. The cursor is now placed in the "Scan item barcode" field after these options are selected. - August 2023 Fulfillment SF: 06640489 URM-189787
Previously, in a specific case, when two distinct personal delivery requests existed for different copies of the same item, and one of the copies was scanned in on the Scan In Items page, incorrect information was displayed about the loan. This was fixed. The information that is displayed now is correct. - August 2023 Fulfillment SF: 06550721 URM-182892
Previously, if a patron came to pick up a booked item after the release time of his booking request had passed, the item's due date was not shortened even if it conflicted with a different booking. This was fixed. Now if the booking release time passes and the booking can no longer be fulfilled due to a conflict with a different booking, the booking request is cancelled, and the due date is shortened. - August 2023 Fulfillment SF: 06731901 URM-195667
Previously, DOI enrichment was causing problems in cases where the print ISSN from Crossref incorrectly contained "00000000." This was fixed. In cases where the print (or electronic) ISSN from Crossref returns "00000000," the original ISSN/eISSN is not overwritten. - August 2023 Fulfillment SF: 06378996 06659565 06422495 06644211 06354571 URM-172167
Previously, some Inventory Remote Storage Update - Automated Retrieval System (ARS) jobs were completed with the warning, "Failed to send Inventory Add Message." The problem was traced to a timeout issue. To fix the problem, a new customer parameter, asrs_job_message_delay, has been added (in Configuration Menu > Resources > Other Settings). This CP makes it possible to set a delay, in milliseconds, between each message. By default, no delay is set. If this warning appears, this CP can be used to configure a delay. - August 2023 Fulfillment – Resource Sharing SF: 06493894 06706084 06661180 06723618 06762904 06468567 URM-179649
In some cases, selecting "Show file" on a borrowing request did not open the associated file. This was fixed. Now, selecting "Show file" in these cases opens the associated file as it should. - August 2023 Fulfillment – Resource Sharing SF: 06710337 06596490 06695832 06502911 06568229 URM-181429
Previously, the "Alma Network" checkbox was automatically selected in locate profiles that were copied from the CZ. In addition, the "Holdings code" field was hidden in the Partner Configuration page when the partner record was copied from the CZ. These problems were fixed. The "Alma Network" checkbox is no longer pre-selected in locate profiles that are copied from the CZ, and the "Holdings code" field is no longer hidden in the Partner Configuration page of partners that were copied from the CZ. - August 2023 Fulfillment – Resource Sharing SF: 06620641 06550689 URM-181443
In some cases, changing the order of a resource-sharing request's rota generated an error. This was fixed. An error is no longer generated in these cases. - August 2023 Fulfillment – Resource Sharing SF: 06434853 URM-184467
In the FulPlaceOnHoldShelfLetter that is sent to the requesting patron when a physical, non-returnable item is received by the library from a resource-sharing partner, the organization_unit that appeared was the institution when it should have been the resource-sharing library. This was corrected. The organizational_unit that now appears in the letter is the resource-sharing library. - August 2023 Fulfillment – Resource Sharing SF: 06575145 06567914 06595539 URM-184613
When using Patron Query Templates, Firefox was incorrectly configured to use a single-line text box for the body of the patron query. This was fixed. Firefox now provides a multi-line text box for this field. - August 2023 Fulfillment – Resource Sharing SF: 06592213 URM-184960
Previously, in the Resource Sharing Lending Requests task list, in Firefox, it was not possible to copy the title of a resource when it was displayed as a link. This was fixed. The title can now be copied in Firefox, although it must be selected by dragging the mouse from left to right. - August 2023 Fulfillment – Resource Sharing SF: 06581513 URM-185293
Previously, Publication Date, Publisher, and Place of Publication were not shown in Resource Sharing Lending Requests task lists. They have now been added to the optional row details, and users can turn their display on in the Records Customization settings. - August 2023 Fulfillment – Resource Sharing SF: 06575763 URM-186798
In some cases, when performing a return for a Borrowing Request, the setting for Automatically print slip defaulted to "No." This was fixed. It now retains the last setting that was chosen by the user, as it should. - August 2023 Fulfillment – Resource Sharing SF: 06561704 URM-187001
In some cases, Borrowing Requests were not showing the pickup location. This was fixed. The pickup locations are now shown in these Borrowing Requests. - August 2023 Fulfillment – Resource Sharing SF: 06764361 06664826 06773090 URM-191260
In some cases, modifications made to the list of Reject Reasons available for Resource Sharing requests were not saved, and were therefore not implemented. This was fixed. They are now saved and implemented as they should be. - August 2023 Fulfillment – Resource Sharing SF: 06390023 06631176 URM-178945
Previously, when a lending request with an MMS_ID from the Network Zone was sent from RapidILL, Alma rejected the request. This was fixed. Now Alma correctly creates lending requests with Network Zone MMS_IDs. - August 2023 Physical Resource Management SF: 06568799 URM-184565
Browse bibliographic records - heading_info index: browsing by LC call number (cataloged in the bib field 050) did not show any results on the right-hand side to match the number of results on the list on the left-hand side. This has been fixed and will be deployed gradually with the next semi-annual indexing. - August 2023 Physical Resource Management SF: 06556188 URM-184681
Change Physical Items Information job: when the input set includes two items of the same bibliographic record (each in a separate holdings record), and the job is configured to move the items to a different permanent location, two duplicate holdings records are created with the same library and location (which is not allowed), and the items are moved to these holdings. This has been fixed. That is, a single holdings record is created with the designated library and location, and the two items are moved to it. - August 2023 Resource Management SF: 06654430 05314131 06660967 06058017 06230664 URM-148420
OAI publishing profiles using an Indication Rule to filter out specific records still published the records. This was fixed and the records are filtered accordingly. - August 2023 Resource Management SF: 06394703 URM-173841
In the report for Change Physical Items Information job, "success" and "failure" titles appeared in the email as "<b>Success<b>" and "<b>Failure<b>". This was fixed by removing the bold formatting from the titles. - August 2023 Resource Management SF: 06386298 URM-174348
Incorrect Number of Bib Records showing as linked to an authority record in the Community Zone. This was fixed by changing the CP: "temp_enable_use_solr_in_f3_count" to false. - August 2023 Resource Management SF: 06748611 06779742 URM-194529
The incorrect "Serial/Integrating Resource" option has been removed from the list of options of the "Bibliographic Format" index in advanced search. At the same time, this option has been re-instated to the values list for creating a new 006 field in the MD Editor. In addition, the text for the "m" code entry of the values for field 006 was incorrect; “Computer file". This has been fixed to "Computer file/Electronic resource". - August 2023 Resource Management SF: 06631655 URM-186781
Browse bibliographic records: In some cases, the records indicated on the left side (by a number beside the heading) were not shown on the right side for viewing. This has been fixed and will be deployed gradually with the next semi-annual indexing. - August 2023 Resource Management SF: 06678231 URM-190833
In some cases, when browsing bib headings by title, the same bibliographic record was displayed twice in the results on the right-hand side. This has been fixed and will be deployed gradually with the next semi-annual indexing. - August 2023 Resource Management SF: 06738568 06630135 06585716 URM-184760
Browse Bib Headings shows no results in View. This was fixed and at least 1 bib record is displayed. - August 2023 Resource Management SF: 06672615 URM-184994
The following issues concerning Browse Bib Headings have been resolved:
1) In some cases, when browsing bib headings by title, the same bibliographic record was displayed twice in the results on the right-hand side.
2) Browse bibliographic records - heading_info index: browsing by LC call number (cataloged in the bib field 050) did not show any results on the right-hand side to match the number of results on the list on the left-hand side.
3) In some cases, the records indicated on the left side (by a number beside the heading) were not shown on the right side for viewing. Full inventory indexing is required for this fix to take effect.
4) Browse Title headings in institutions using only Unimarc as the active format: CZ-linked MARC21 records having the browsed title were not displayed on the right-hand side.
These have been fixed and will be deployed gradually with the next semi-annual indexing - August 2023 Resource Management SF: 06461546 05319674 URM-158808
Metadata Editor: LDR's German field information was not opened. This was fixed and now the "field information" action supplies the right information page. - August 2023 Resource Management SF: 06055728 URM-168378
Metadata Editor: suppression indication of a holdings record located in a suppressed location disappeared when clicking the holding. This was fixed. - August 2023 Resource Management SF: 06259059 06452859 06254000 06450042 06395892 URM-171433
Browse bibliographic records: In some cases, the records indicated on the left side (by a number beside the heading) were not shown on the right side for viewing. This has been fixed and will be deployed gradually with the next semi-annual indexing. - August 2023 Resource Management SF: 06672615 URM-189934
Browse Bibliographic Headings shows a total results number, but the titles do not show when you click "View". This was fixed. - August 2023 Resource Management SF: 06732331 06669056 06656167 06744041 URM-193507
When you customize the shortcuts menu and disable Alt+number, you can't add special characters in the Metadata Editor using Alt+number in Firefox. This was fixed and now, if the configuration allows, the special characters are added in all browsers. - August 2023 Resource Management SF: 06672012 05321685 URM-167859
When a local extension is added to a network record already opened in the member Metadata Editor using a process, after pushing this record again to the Metadata Editor, the added local extension is not displayed. This is fixed. A pop up is now displayed to inform that the record has been updated by an external process. - August 2023 Resource Management SF: 06271143 URM-170450
Metadata Editor > Create Holdings failed in specific cases. The default library was not displayed ($$b) before opening the Form Editor. This was fixed. - August 2023 Resource Management SF: 06533339 URM-184484
Metadata Editor > A wrong validation warning message is displayed when editing the control field 007 (for "c" = Electronic resource, the positions 06-08 indicate the image bit depth; possible values are 001-999): "0 is not a valid code for position 6 and 7 for field 007". This was fixed - August 2023 Resource Management SF: 06747979 URM-195317
Metadata Editor > Holdings record > Field 853 > Row Actions > Redundant “Open form editor (Ctrl+F)” label. This label was removed since it is not supported for field 853. - August 2023 Resource Management SF: 05320510 URM-163655
For fields 111 and 711, the subfield $j is no longer preventing full linking and is not stripped from the field when linking the authority. This was fixed. - August 2023 Resource Management SF: 06730118 06494929 URM-184039
The match methods 'ISBN/ISSN (exact subfield match)' and 'ISBN/ISSN (exact subfield match)/024/035' not working as expected. In some cases, the import job found a match when the import record has the ISBN in 020 $$a and the record in Alma has the ISBN in 020 $$z. This was fixed and now no match will be found between 020 $$a and $$z. Note that full indexing is required for the fix to take effect. - August 2023 Resource Management SF: 06653325 URM-187969
Metadata Editor Import: a discovery profile with OAI import protocol saved as a draft was not created properly. This was fixed. - August 2023 Resource Management SF: 06613502 URM-188949
Users encountered an issue where changing the language and subsequently opening the Metadata Editor led to inconsistent menu labels that did not align with the newly selected language. This was fixed. - August 2023 Resource Management SF: 06543418 URM-189496
MODS record was saved and indexed as OTHER type in Primo, although it should be saved as Image. This was fixed. - August 2023 Resource Management SF: 06484277 URM-180514
There were issues with mapping MARC fields to OTHN fields in CAT-P. This was fixed by adding OTHN numbers to the Alma CAT-P crosswalk. - August 2023 Resource Management SF: 06641891 URM-190049
The "Import" functionality, when working with records from the SBN central catalog was importing the truncated SBN record from the search results. This resulted in missing fields in the Alma record (Most "Search Resources" targets return full records, but not SBN.) This was fixed by retrieving the full record from SBN when doing "Import" from the SBN central catalog. - August 2023 Resource Management SF: 05325179 06749485 URM-164042
In some scenarios, both CDI options: "Do not show as Full Text available in CDI even if active in Alma" AND "Full Text active in CDI only" can be enabled and saved. These 2 options should not be permitted to be selected at the same time. This was fixed, now both option cannot be selected together. - August 2023 Resource Management SF: 06727087 URM-195827
In General Publishing: When republishing a job with the same profile, instead of allowing multiple "Pending" jobs, only 0/1 pending jobs can be in the queue; every additional job will not run and automatically be marked as Skipped.
- July 2023 Acquisitions SF:06742971 URM-193334
Previously, exporting the results of the Rollover PO Lines job produced an XLS Excel file (i.e., in legacy format). This has been fixed. The job now exports results in XLSX format. - July 2023 Acquisitions SF:06678681 URM-193420
Previously, the po_line_owner_name (library name) and po_line_owner_code (library code) fields were not included in the XML of the PO Line Aggregated Claim Letter, and thus neither the library name nor the library code could not be included in the letter. This has been fixed. These two fields were added to the XML under line_claim_letter_details. - July 2023 Acquisitions SF:06542601 URM-186414
Previously, when a purchase request was saved with EUR selected as the currency of the Estimated cost field, when the request was next opened, the currency was changed into GBP. This issue was fixed. Now, when a purchase request is created with a particular currency selected, the currency is saved correctly and not changed afterwards. - July 2023 Acquisitions SF:06700891 URM-193328
Previously, when the Manage EDI Tasks list was filtered for certain time ranges, in some cases the filtering process failed and an error message was displayed. This was fixed. The process no longer fails in these cases. - July 2023 Administration and Infrastructure SF:06760316 06522876 06577298 06606587 06523115 06524438 06590736 URM-181660
Previously, the History tab of the User Details page sometimes mistakenly included changes to user roles that did not actually occur. This was found to be caused by a problem with a SIS API process. The problem was fixed, and the History tab now reflects changes made by this SIS process correctly. - July 2023 Administration and Infrastructure SF:06689118 URM-190051
Updating translations in code-tables did not update the display of "Updated By" and "Last Updated" values. This was fixed. - July 2023 Administration and Infrastructure SF:06667923 URM-190943
When using a small laptop screen (14 inch), the Feedback button is not responsive and covers alma menu options. This was fixed. The Feedback button is now responsive and adjusts accordingly to screen size. - July 2023 Administration and Infrastructure SF:06604606 URM-191435
"Borrowing requests" and "Lending requests" incorrectly appear twice in the “Customize Tasks List”. Only one of the instances actually has an effect on the task list order. This was fixed. - July 2023 Administration and Infrastructure SF:06718285 06698944 URM-191985
When copying a URL from the report URL in the Analytics UI and then attempt to copy and paste something else in the Alma interface, only the URL is pasted. This was fixed. - July 2023 Administration and Infrastructure SF:06684219 URM-193353
Users were unable to add "Order without Inventory" to Quick Links. This was fixed and "Order without Inventory" can now be added to the favorites list. - July 2023 Administration and Infrastructure SF:05322709 05319563 05302114 05323932 URM-153586
A user identifier that was created internally for an external user could not be changed to external. This was fixed. - July 2023 Administration and Infrastructure SF:06699043 URM-192925
Translation for resource sharing request Copyright statements were not displayed for languages with code that are longer than 2 characters (such as Traditional Chinese). This was fixed. - July 2023 Analytics SF:06692517 06782452 06681417 06541187 06422235 06469502 06664277 06725741 06735087 06743440 06756487 URM-176328
Scheduled reports that sent the report to an FTP server sent the following error message "One of the Tag fields is empty. Both Tag fields must have a value", although the reports ran correctly. This was fixed and the error message is no longer sent. - July 2023 Analytics SF:06531765 URM-185000
The event description for event type 3000 was not defined properly. This was fixed and it is now defined as "Search electronic entities in Institution or community". - July 2023 Analytics SF:06630735 URM-189409
The Rapido Analytics folder appeared for non-Rapido customers. This was fixed, and now the folder appears only for Rapido customers. - July 2023 Analytics SF:06697526 URM-191414
The time was not displayed for the new layout of the Analytics Object List for the "Object created by" and "Object modified by" fields. This was fixed and now the time appears. - July 2023 Analytics SF:06737628 URM-192825
The Manage Widgets popup on the Alma homepage contained only widgets that were shared with the user by role and not by user identifier. This was fixed, and now users can see widgets shared by user identifier. - July 2023 APIs SF:06334199 06499665 06395253 06698172 URM-180896
Previously, updates to the "Last activity date" of a user were not always indexed correctly. As a result, an advanced search of users by "Last activity date" did not find those users when it should have. This was fixed. Updates to the "Last activity date" of a user are now correctly indexed and can be located by the "Last activity date" advanced search. - July 2023 APIs SF:06691513 URM-191379
Previously, when the API was used to update the license of an electronic collection, the license start-date was not saved. This was fixed. Now the license start-date of the electronic collection is saved correctly in these cases. - July 2023 Digital Resource Management SF:06678278 06710088 URM-189855
Password protected PDFs were not viewable with new pdf.js enabled. This was fixed. Users can now view the PDF after entering the password. - July 2023 Digital Resource Management SF:06696878 06696802 URM-190867
Android devices did not display PDF files. This was fixed. - July 2023 Digital Resource Management SF:06696813 URM-190880
The copyrights statement is not displayed properly in the Alma Viewer on devices running iOs. This was fixed. - July 2023 Digital Resource Management SF:06651256 06687361 06721849 URM-191783
PDFs were not displayed correctly in the Alma Viewer using the new PDFJS. This was fixed. - July 2023 Digital Resource Management SF:06594825 URM-191833
Viewer sessions timed out every 60 seconds regardless of how the access rights were configured. This was fixed, and now the session period follows the configuration in the access rights rule. - July 2023 Digital Resource Management SF:06684061 URM-192486
When running publishing profile? on DC output format, the job sometimes failed due to normalization, although no normalization was defined. This was fixed. The job now ignores normalization if it is not defined in the publishing profile configuration. - July 2023 Digital Resource Management SF:06675294 URM-193460
In the Alma Viewer, some PDFs are displayed with their pages slightly overlapping. This was fixed and the pages now appear correctly. - July 2023 Digital Resource Management SF:06215197 URM-165960
The Welsh language preference was not carried over from Primo to the Universal Viewer. This was fixed. - July 2023 Electronic Resource Management SF:06579004 URM-187314
In a miscellaneous collection, an empty value for embargo in the Community Zone portfolio using contribution did not work. This was fixed. - July 2023 Electronic Resource Management SF:06727087 URM-192939
General Publishing - When there are several pending publishing jobs for the same profile in the queue, only one runs successfully after the previous job is finished. This was fixed and now all the pending jobs run consecutively. - July 2023 Electronic Resource Management SF:06685508 URM-193548
Push to MDE button was missing in the title list of Collection results. This was fixed and the button is now displayed. - July 2023 Electronic Resource Management SF:06523253 URM-187307
In Overlap Analysis, lookup titles, titles with ';-'; resulted as no match in the report. This was fixed and now returns as a matched title in the report. - July 2023 Electronic Resource Management SF:06576911 URM-184850
Manage Sets: The "Add Members to Set" job always displayed "Completed with warnings" when creating an itemized set from an Excel file that consists of an ISBNs list and the codes containing hyphens separating the digits. This was fixed. Now both cases (ISBN keys with or without hyphens) are processed properly. - July 2023 Fulfillment SF:05299388 06330261 URM-153896
When an item owned by institution A was requested to be picked up at institution B and then returned at institution C, the transit slip letter set the destination to the owning library, A, instead of the pickup library, B. This was fixed. The destination in the slip now specifies the correct pickup library. - July 2023 Fulfillment SF:06667853 06400058 06444012 URM-174138
Previously, when multiple items were scanned using the RFID, the Destination field sometimes incorrectly displayed the same destination for all of the items. This was fixed. The correct destination is now displayed for each item. - July 2023 Fulfillment SF:06330303 06511139 URM-180296
Primo Get It either shows a list of inventory items related to the displayed record or a specific related item if one is specified for the record under $$g. Previously, lists of related items in Primo Get It were blank if $$g was defined, but no items were found that matched the specification it contained. This was fixed, and now all related items are shown when no matching item is found. - July 2023 Fulfillment SF:06555418 URM-182684
Previously, the XML of the Courtesy Letter and the Borrowing Activity Letter did not contain the name of the circulation desk where the loan took place. This was fixed. The name of this circulation desk (loan_circ_desk_name) has been added to these letters. - July 2023 Fulfillment SF:06568772 URM-183084
Previously, the list of electronic collections in the Online Service Order dropdown menu was not sorted alphabetically. This was fixed, and the list is now arranged in alphabetical order. - July 2023 Fulfillment SF:06769768 06765523 URM-196194
Creating a general request from primo failed if the customer parameter ';item_level_requesting'; = true. This was fixed. - July 2023 Fulfillment SF:06479254 URM-182600
Previously, in the XML of fulfillment letters, the country element in notification_data/user_for_printing contained the 3-digit country code, but not the name of the country. This was fixed. A country_display element was added to the XML of multiple fulfillment letters (e.g. FulPlaceOnHoldShelfLetter), making this information available for inclusion in these letters. - July 2023 Fulfillment SF:06722342 URM-195421
Previously, in the XML of the Resource Request Shipping Slip Letter, the country element in owning_library_details contained the 3-digit country code, but not the name of the country. This was fixed. A country_display element was added to the XML of the letter, making this information available for inclusion in this letter. - July 2023 Fulfillment SF:06610811 URM-184863
Previously, processing resources failed when their bibliographic records had very long titles (more than 4000 characters) and also contained special characters. This was fixed. Resources with bibliographic records that have these properties can now now be processed as they should be. - July 2023 Fulfillment SF:06544063 05302781 URM-158543
Items were sometimes missing from the Expired Hold Shelf list. This happened when the next request for the expired item was for pickup in a different institution. This was fixed. Now these items appear as they should, in the Send to Institution tab of the Expired Hold Shelf page. - July 2023 Fulfillment SF:06696145 URM-190470
The names that appeared in the persistent search for two of the search fields for Requests were not clear enough, causing confusion among users. These names have been modified to make them clearer. The "Requester" field is now called "Requester name," and the "Identifier" field is now called "Requester Id." - July 2023 Fulfillment SF:06380361 URM-177336
Previously, when booking requests were opened in Calendar view in Catalan, dates appeared in an incorrect format, with the day of the month after the name of the month. This is appropriate for English, but not for Catalan. This was fixed. The date now appears in Catalan with the month first and then the day. - July 2023 Fulfillment SF:06023747 06503091 05313703 06695160 URM-191959
In certain cases, the link resolver changed the genre of an article to unknown if the request was sent with no identifiers. This was fixed. The genre is now sent correctly in these cases. - July 2023 Fulfillment - Resource Sharing SF:06566953 06553928 URM-183844
Previously, when a borrowing request was created from an external search, if the search text consisted of a phrase with several words, the creation of the borrowing request would sometimes fail. This was fixed. Borrowing requests are now successfully created from search texts containing multiple words in these types of cases. - July 2023 Fulfillment - Resource Sharing SF:06635716 06577003 URM-186731
Previously, when an item from a borrowing request was received, and the format of the item was changed during the receive process (e.g., from "Digital" to "Physical non-returnable"), the sliding panel did not close as it should have. As a result, an error message appeared. This was fixed. The sliding panel now closes after the receive process is completed, and no error messages appear. - July 2023 Fulfillment - Resource Sharing SF:06653445 URM-187447
Previously, labels did not appear in a number of Resource Sharing letters when they should have. This was fixed, and now the labels appear in these letters as they should. The following letters were affected by this issue: DocumentDeliveryNotificationItemLetter, FulDigitizationNotificationItemLetter, FulOutgoingEmailLetter, BorrowerClaimEmailLetter, FulRenewEmailLetter, FulCancelEmailLetter, BorrowerOverdueEmailLetter, LendingRecallEmailLetter, QueryToPatrontLetter, ExternallyObtainedLetter, BorrowerReturnEmailLetter, BorrowerReceiveEmailLetter, GeneralMessageEmailLetter, LostEmailLetter, DamagedEmailLetter - July 2023 Fulfillment - Resource Sharing SF:06572510 URM-183800
Previously, when a borrowing request was sent from Alma to RapidILL, and the publication date it specified contained more than just the year (i.e., more than four characters - for example, "202010" or "20201022" instead of "2020"), RapidILL rejected the request, because it could not process it with the long date. This was corrected. When the publication date contains more than four characters, Alma now extracts the first four characters of the date, and sends them to RapidILL as the publication date. - July 2023 Physical Resource Management SF:06648528 URM-189898
In Analytics, the bibliographic record resource type "Analytic (Component Part)" was shown as "Unknown". This is fixed. The deployment of this fix is gradual, depending on the record';s update or full inventory indexing (the next job is planned for November). - July 2023 Resource Management SF:06669754 URM-194960
Physical Items advanced search on "Storage Location ID" finds items that start with another number. This was fixed. The "Contains exact phrase starting with" search operator has been added to the Physical Items index "Storage Location ID" in Advanced Search. Note that for this functionality to take effect, full inventory indexing is required. - July 2023 Resource Management SF:06719229 URM-191455
In certain instances, users were unable to create an itemized set after a simple search. This was fixed. - July 2023 Resource Management SF:06545551 URM-189499
External Search Resources > Search via SRU, the Leading spaces in the leader field (LDR) are removed when the record is imported to Alma. This was fixed. - July 2023 Resource Management SF:06581549 URM-183913
Previously, the Download button was not translated for digital article requests filled by RapidILL. This was fixed. - July 2023 Resource Management SF:06618064 URM-189920
UNIMARC - Field 300 was missing. This was fixed by adding the ';General Note'; field to Alma analytics under the Bibliographic Details. The deployment of this fix is gradual, depending on the record';s update or full inventory indexing (the next job is planned for November). - July 2023 Resource Management SF:06653029 URM-192101
Metadata Editor: The 008 pos. 22-23 are blank when it is edited from the "Open from the editor" option. This was fixed. - July 2023 Resource Management SF:05302909 URM-186983
When linking (with F3) a MARC21 bib heading of the non-Latin alternate representation of field 711 to an authority record and both contain subfield $e, subfield $e is duplicated. This was fixed. - July 2023 Resource Management SF:06737534 06626607 06682034 URM-191320
The "Copy and Overlay" functionality, when working with records from the SBN central catalog was using the truncated SBN record from the search results for the overlay. This resulted in missing fields in the Alma record (Most "Search Resources" targets return full records, but not SBN.) This was fixed by retrieving the full record from SBN when doing "Copy and Overlay" from the SBN central catalog. - July 2023 Resource Management SF:06749419 URM-193475
CNMARC - When the ';subfield_separator'; customer parameter is defined as one character, updating 1XX fields via the metadata editor shifted the character';s positions by one character. This was fixed. - July 2023 Resource Management SF:06223114 URM-165977
SBN contribution: The contribution of Uniform Titles sometimes failed due to a wrong SBN sequence number generated. This was fixed. - July 2023 Resource Management SF:06583015 06533571 URM-180701
SBN integration: When records are merged (manually or during batch alignment), the localization is not updated. An automated localization process was needed after the merge. This was fixed by adding functionality to the "merge" portion of the SBN authority and bibliographic alignment jobs. This new functionality looks for any localizations in the non-preferred record that belong to the institution (based on the Pole code in the SBN central catalog configuration) and if any exist, a localization request is performed to add them to the preferred record. - July 2023 Resource Management SF:06490665 URM-180712
Alma contributing records to NACSIS: 084 subfield 2 caused errors, preventing the upload of the record to NACSIS. This was fixed with additional classification codes that have been implemented. - July 2023 Resource Management SF:06569129 URM-182544
NACSIS App > Central catalog contribution: The punctuation in tag 264 is incorrectly duplicated in the central catalog. This was fixed by correcting the punctuation handling for 264 > PUB crosswalk. - July 2023 Resource Management SF:06572043 URM-184774
Cloud App > NACSIS-CAT: When a colon delimits the VT, the string after the colon is not copied to 246$b. This was fixed by checking for the colon used as a delimiter when crosswalking VT to MARC field 246 subfields a and b. Use colon as a delimiter when crosswalking MARC field 246 subfields a and b to VT.
- June 2023 Analytics SF:06661672 URM-189546
Permissions functionality for databases for data visualization dashboards was fixed. - June 2023 Analytics SF:06665709 URM-191332
The analytics object had the wrong path for the API Usage and Purchase Requests out-of-the-box dashboards. This was fixed. - June 2023 Analytics SF:06748842 URM-191767
Previously, the fields of the date dimensions in Alma Analytics reported on data going 30 years back 20 years ahead. Now, Alma Analytics reports on data from 01/01/1980 and 30 years ahead. - June 2023 Analytics SF:06696281 URM-192305
When changing the schedule of an object, the modified date of the object was updated but not the operator name. Now, the modification information is updated immediately. - June 2023 Acquisitions SF:06592482 06636916 URM-184977
In the Manage Purchase Requests page, when the Unassigned tab and the "In Review" status filter were selected, if the "Assign To" row action was performed, the "In Review" filter was removed and the Unassigned tab was not highlighted (even though it was still active). This was fixed. After "Assign To" is performed, the Unassigned tab and the "In Review" status filter are once again selected in the page. - June 2023 Acquisitions SF:06520112 URM-189780
When an item's barcode was updated via API, it was not updated in all of the relevant fields. This has been fixed. All the fields are updated as they should be. - June 2023 Acquisitions SF:06634551 URM-188167
The New Order API was generating an error when Rialto sent a POL to Alma if the "Upon no match field" was not configured in the Alma integration profile. This issue was fixed. Now, if the "Upon no match" field is null when the New Order API sends a POL to Alma, a default value, "import," is assigned to the field. - June 2023 Acquisitions SF:06290435 URM-191349
Previously, the Data Corrector did not change the Material Type of certain PO lines to Mixed Material Package as it should have. This was fixed and now works correctly. - June 2023 Acquisitions SF:06681325 06679722 URM-189705
Previously, it was not possible to create invoice numbers with certain Chinese characters in them. This was caused by a redundant encoding of the invoice number, which has now been removed. It is now possible to include all Chinese characters in invoice numbers. - June 2023 Acquisitions SF:06538626 URM-190334
Previously, the Data Corrector Correct Invoice Task failed to delete invoices that did not have invoice lines or whose invoice lines did not have PO lines. This was fixed. The procedure now deletes invoices as it should. - June 2023 Acquisitions SF:06599349 URM-190929
A typo in an "Invoice - Create From Spreadsheet" job error message was fixed. The message now reads "mandatory fields are missing," as it should. - June 2023 Acquisitions SF:06442252 06727692 05307598 URM-159240
Previously, when certain special characters were included in the name of a license, selecting the license for a PO line in the Purchase Order Line Details page generated an error. This was fixed. Names of licenses are now normalized to remove unsupported characters before they are passed to this page. - June 2023 APIs SF:06465855 URM-189204
Previously, when an item that was located in place was scanned via RFID, Alma displayed "RFID Security Status: Checked Out." This was fixed. Alma now displays "Available," as expected. - June 2023 APIs SF:06608466 URM-189051
Previously, the GET API could retrieve a maximum of 50 notes for a single PO line. This limitation was removed. Now all notes attached to a PO line are returned by this API. - June 2023 APIs SF:06667550 URM-190263
Previously, the Update Code-Table API did not check if the codeTableName in the URL was the same as the name in the code_table name XML payload. The API now checks this, and if they are not identical, an error message is sent. - June 2023 APIs SF:06611916 URM-190798
Previously, the Item Policy table was not included in the results of the GET codeTables API. This was fixed. The Item Policy table now appears in the results of this API. - June 2023 Administration and Infrastructure SF:06570629 06057150 06468339 06028016 06261385 06578108 URM-164967
Previously, it was not possible to delete a user account if the user had made any purchase requests, regardless of the statuses of the purchase requests. This was fixed. It is now possible to delete user accounts with purchase requests as long as those requests are not active. - June 2023 Administration and Infrastructure SF:06432268 URM-178314
Previously, operators with the "Can’t edit restricted users" parameter could only edit the Statistics tabs of users from restricted groups in a convoluted way. This was fixed. Now editing of user statistics is not limited even for restricted users, just as editing of blocks, notes, and fees is not limited for restricted users. - June 2023 Administration and Infrastructure SF:06536748 URM-182119
Previously, when a new user was registered with the same primary identifier as an existing user, except that the case of the characters in the primary identifier did not match, the new user was created. This should not have occurred, because the check to see if a user with that primary identifier already existed should not have been case-sensitive. This was fixed. Checking whether the primary identifier of a new user already exists is no longer case sensitive. - June 2023 Administration and Infrastructure SF:06667582 URM-189633
Previously, in a specific case, there was a difficulty when a library card was scanned for the "Requester" field during the creation of a Patron Physical Item Request from an Alma repository search. This was fixed. - June 2023 Resource Management SF:06493662 URM-181657
The "reminder creation date" changes to the day after it was created when a reminder is created in China Standard Time. This was fixed and now displays the creation date consistently, and matches the institution's time zone. - June 2023 Resource Management SF:06655063 URM-190189
For Network Repository Search > Held by, the “Public Note (physical items)” was incorrectly displayed for a portfolio with a note. This was fixed and now the “Public Note (electronic portfolios)” is displayed as expected. - June 2023 Resource Management SF:06662018 06424641 URM-126900
When the portfolio loader created local portfolios using existing bibliographic records, the action shown in the downloadable Actions report was "Localize and activate" instead of "Create local portfolio." This was fixed. - June 2023 Resource Management SF:06573106 URM-183398
The portfolio loader could not remove the Access Type if the cell was left empty in the input file. In order to resolve this, the new customer parameter: "delete_access_type_via_portfolio_loader" must be set to 'true'. - June 2023 Resource Management SF:06590749 URM-185078
In the portfolio loader, if 2 portfolios exist in the Community Zone for the same bib record, an error message in the Excel file warns that 2 bib records were found, even though it was actually 2 portfolios for 1 bib. This was fixed and the error message has been updated to indicate the appropriate warning. - June 2023 Resource Management SF:06569232 URM-186602
When changing Electronic Collection Group Settings through the Change Electronic Collection information job, the “Available For” field is not updated. This was fixed. - June 2023 Resource Management SF:06638585 URM-188927
A member MMS bib record, linked to a Network Zone with a linked Community Zone portfolio, is deleted by the Synchronize Changes from the Community Zone job when there is an update on the portfolio. This was fixed. - June 2023 Resource Management SF:06720467 URM-191556
The Overlap and Collection Analysis job got stuck in the finalization process. This was fixed and the job now completes. - June 2023 Digital Resource Management SF:06038275 URM-163798
The data corrector to replace the mmsid was not working for collection inventories. This was fixed. - June 2023 Digital Resource Management SF:06509219 URM-180414
The Alma Digital Universal Viewer displayed an incorrect runtime for large files. This was fixed. - June 2023 Digital Resource Management SF:06647911 URM-188753
The Quick Access feature changed the interface text direction from left-to-right to right-to-left. This was fixed. - June 2023 Digital Resource Management SF:06625280 URM-191627
The subject in the Delivery Registration status letter was not displayed and translated according to the user's preferred language. This was fixed. - June 2023 Resource Management SF:06581528 URM-188641
Network Zone publishing completed with the error: "Failed to retrieve records for institution". This was fixed by adding an exception task to General publishing when trying to retrieve data from members. The exception stipulates that in case of failure, there will be five retries: - June 2023 Electronic Resource Management SF:06573450 06376236 URM-181946
In overlap analysis compare collections, portfolios with complete coverage overlap did not appear in the report because of the system date format "dd-MM-yyy". This was fixed and now the portfolios appear in the complete coverage overlap report. - June 2023 Resource Management SF:06482799 06481305 URM-179046
Sets with a date-based field that are used in advanced search and saved during specific times of the day, the value shifts a day forward. This was fixed with a configuration adjustment to address timezone differences. - June 2023 Resource Management SF:06736029 06697974 06630819 URM-190935
Location search returns results but search query does not display location in results page. This was fixed - June 2023 Resource Management SF:06440276 06246170 URM-171669
Nested parentheses in the search terms caused an error resulting in one or more of the terms being removed from the search. This was fixed. - June 2023 Resource Management SF:06616482 URM-190133
The "Service unavailability" display message appeared as a link in ViewIt. This was fixed and the message now displays as plain text. - June 2023 Resource Management SF:06548942 05298959 05308857 URM-164649
The Due Date and Due Hour continued to be displayed in My Library Card and getIt even when configured to not be displayed. This was fixed. - June 2023 Resource Management SF:06660882 05325090 06230689 URM-159491
When the "How to get it" section was part of the Full View, the first "linktorsrc" link was not translated, since the $$E was removed from the linkDisplay string. This was fixed. - June 2023 Resource Management SF:06535813 06509029 URM-181486
Clicking "Available Online" displayed the getIt section instead of the viewIt section. This was fixed. - June 2023 Resource Management SF:06683389 URM-190577
There was a misspelling in the OTB Journal Search Category labels code table in the Dynamic & Structural Geology label. This was fixed. - June 2023 Resource Management SF:06293336 URM-190994
When configuring multilingual terms to be displayed in the details section, an additional comma was displayed. This was fixed. - June 2023 Resource Management SF:05315387 URM-180906
The Consortia Central Office can control which Bibliographic metadata fields can be edited by its members, allowing it to maintain the quality of the NZ Bibliographic records by preventing unwanted edits/deletion of specific fields. This is applied only to the consortia members. The Network Zone institution is exempt. - June 2023 Fulfillment SF:06470511 06378148 06499507 URM-177331
Previously, when a user record was renewed from the Manage Patron Services pop-up, the expiration date in the user history was not updated. This was fixed. The expiration date is updated as it should be. - June 2023 Fulfillment SF:06629660 URM-189031
Previously, when a digitization request was completed, the requester's name was not displayed for the request in the "Approval Requests List." This was fixed. The requester's name now appears in the list as it should. - June 2023 Fulfillment SF:06593455 URM-189953
Previously, in the Manage Patron Services Loans tab, when a policy code was configured only at the institution level, the Item Policy column displayed the policy code instead of its description. This was fixed. The item-policy description is now displayed in this column, as it should be. - June 2023 Fulfillment SF:06563226 URM-182390
In some cases, Alma allowed more loans per user via Self Check than was permitted in the loan-limit configuration. This was fixed. The Self-Check loan limit is now applied as it should be. - June 2023 Fulfillment SF:06621295 06683694 06701837 06643442 URM-190023
Previously, in the default Fulfillment Unit rule, if the Update Date, Created On, and Updated On fields had no values in the database, they were automatically set to the current date, even if no changes were made to the rule on that date. This was fixed. If any of these fields has no value in the database, it displays as "-". - June 2023 Fulfillment SF:06576151 URM-182831
A typo in a patron-block message was corrected. It now says, "Patron's card has expired". - June 2023 Fulfillment SF:06472125 URM-181864
In the Request Queue screen, the "Activate" row action appeared even when no items were available. This was fixed. Now the "Activate" row action appears only if there is an available item. - June 2023 Fulfillment – Resource Sharing SF:06481727 URM-180294
In some cases, the "Lost" action was not available for Resource Sharing lending requests for some partners. This was fixed. The "Lost" action is now available in these cases. - June 2023 Fulfillment – Resource Sharing SF:06518901 URM-183190
In some cases, when a Resource Sharing borrowing request was assigned to a fund, a disencumbrance transaction would be created incorrectly. This was fixed. Incorrect disencumbrances are no longer created in these cases. - June 2023 Fulfillment – Resource Sharing SF:06699233 06577200 URM-184870
In certain cases, when a lending request was cancelled by the borrower, its status changed to "Cancelled," but then immediately changed to "Will Supply." This has been fixed. In these cases, the status of the lending request now remains "Cancelled." - June 2023 Fulfillment – Resource Sharing SF:06520499 URM-185231
When a digitization request was converted to a Resource Sharing request, some of the metadata fields were mapped incorrectly. This was fixed. The fields are now mapped correctly. - June 2023 Fulfillment – Resource Sharing SF:06623286 URM-188075
When an "Available For" group was added to an electronic resource, locating the resource for a Resource Sharing borrowing request did not work. This has been fixed by creating a customer parameter, ignore_group_filter_in_rs_locate, which can be enabled or disabled by the lending institution. By default, the customer parameter is set to false, and the previous behavior, in which locating an electronic resource for a borrowing request does not work when an "Available For" group is added to the resource, is implemented. When the customer parameter is set to true, Resource Sharing resource locating works even for resources to which an "Available For" group is added. - June 2023 Fulfillment – Resource Sharing SF:06536306 URM-184764
Previously, when notes attached to a Resource Sharing request contained quotation marks, the notes could not be exported to ILLiad. This was fixed. Notes containing quotation marks can now be exported to ILLiad. - June 2023 Fulfillment – Resource Sharing SF:06308317 URM-182270
Previously, when a ZFL server sent a Shipped message to a Resource Sharing borrower, and the message was delayed and not sent immediately, if the message arrived at the borrowing institution after the resource was already on loan to the patron or placed on the hold shelf for the patron, the status of the borrowing request was set incorrectly in Alma, and problems processing the return of the resource also arose. This has been fixed. Now, when a ZFL server sends an update to a borrowing request after the resource was received by the borrower, the message is ignored. Note that this scenario is only relevant when the NCIP partner is defined with System Type=ZFL. - June 2023 Resource Management SF:06629702 URM-188739
Misleading entries for MARC21 controlled 008 field that holds the 'Place' of publication in position 15-17. This was fixed. The description of code 'gau' was changed from 'Georgia' to 'Georgia (U.S. State)' for better differentiation from 'gs=Georgia (Republic)'. - June 2023 Resource Management SF:06223114 URM-165977
SBN contribution: The contribution of Uniform Titles sometimes failed due to a wrong SBN sequence number generated. This was fixed. - June 2023 Resource Management SF:06542477 URM-187015
When utilizing the Cloud App "NACSIS-CAT copy-cataloging", the price is not copied to the Alma record for serials. This was fixed. When a NACSIS serial record has a PRICE field, copy the value to MARC field 020 $c. - June 2023 Resource Management SF:06541198 URM-187018
In the Cloud App: "NACSIS-CAT", contributions to Central Catalog fails for serials if there is a price in 020 $c. This was fixed. When an Alma serial record has 020 $c, copy the value to the PRICE field in the NACSIS record. - June 2023 Resource Management SF:06589279 URM-188863
The Cloud App "NACSIS-CAT" incorrectly handles records for multiple publishers. This was fixed.
If the PUBL= field in a NACSIS record has multiple publishers delimited by " : " then the Alma 260 field will contain multiple $b, one for each publisher. If the Alma 260 field has multiple $b, then they will be concatenated into a single PUBL= field in the NACSIS record, delimited by " : ". - June 2023 Resource Management SF:06681438 URM-190210
Search external resources - When searching via SRU target by system number field, Alma greys out all other fields but sends all the keywords filled to the target instead of sending only the system number. This was fixed and now the search is done on the system number only. - June 2023 Resource Management SF:06659093 URM-191372
Values of NACSIS records that have the field IDENT were not imported. This was fixed by adding a mapping request: map IDENT to 856$u. Now the NACSIS field IDENT= is imported to Alma 856 $u. - June 2023 Resource Management SF:06671913 URM-191703
NACSIS Central Catalog contribution, the mapping for tag 016 needed to be corrected depending on the resource type. This was fixed as follows:
When exporting or contributing to NACSIS a serial record (LDR07 contains b or s) with field 016 ind1=7 and $2 JTNDL, the NACSIS record contains field NDLPN= with the value of 016 $a.
When exporting or contributing to NACSIS a monograph record with field 016 ind1=7 and $2 JTNDL, the NACSIS record contains field NDLCN= with the value of 016 $a. - June 2023 Administration and Infrastructure SF:06562717 URM-182505
There were multiple Hebrew interface issues in Alma. All issues were fixed. - June 2023 Administration and Infrastructure SF:06650705 URM-190930
The Feature Rollout Configuration option was labeled the same in Admin Configuration and in User Preferences. This made it difficult for users to differentiate whether the option was for administrators to configure the option for the institution or individual users to turn the option On and Off for their account. This has been fixed. The option for User Preferences (Persistent menu > User icon > Feature Rollout Configuration) has now been relabeled to "Feature Rollout Preferences". - June 2023 Administration and Infrastructure SF:06725442 URM-191725
In the Printouts Queue screen, the button 'Print Selected' does not work in the Polish user interface. This was fixed by updating the translations. - June 2023 Administration and Infrastructure SF:06698316 06695467 URM-193517
Error message displayed when clicking on some configuration options. This was fixed and users have access to all configuration menu options. - June 2023 Administration and Infrastructure SF:06641361 URM-187182
When pressing the 'Add Titles' pickup in the Collection Editor and running a search, the result was that it corrupted the recent search. This was fixed. - June 2023 Digital Resource Management SF:06677665 06652163 06658669 URM-189551
The Digital Representation viewer time remaining pop-up was obstructed by the PDF tool bar. This was fixed. - June 2023 Fulfillment – Resource Sharing SF:06560321 06594021 06556629 URM-181945
When receiving an item for a borrowing request, when Enable quick printing was not checked, the confirmation message Quick print included the text op:Quickprint:op instead of a hyperlink to quick print. This was fixed. - June 2023 Fulfillment – Resource Sharing SF:06611851 URM-183427
In some cases, the borrowing request Volume field was populated with incorrect data. This was fixed.
- May 2023 Acquisitions SF:06505197 URM-180689
Previously, when a user searched for an invoice using the persistent search box, and the invoice number contained a Kanji character, if the user then selected Go to task list from the row actions of the invoice in the search results, the Kanji character was replaced by a different character, and the invoice was not found. This has been fixed. Alma now uses the invoice’s Unique ID rather than the invoice number when Go to task list is selected from invoice search results. This makes locating the invoice more reliable, and also prevents unrelated invoices from mistakenly being found by Alma. The persistent search box continues to function as before when a user manually searches for an invoice by Unique ID. - May 2023 Acquisitions SF:06588107 06395228 URM-174475
Previously, the PO Line - Renewal job only handled a maximum of 100 PO lines each time it ran. This was fixed. It now handles all the PO lines that are due for renewal when it runs. - May 2023 Acquisitions SF:06426289 URM-180831
Previously, a user whose account was expired in Alma could create a purchase request in Primo. This has been corrected. Now, if a user whose account is expired tries to create a purchase request in Primo, an error is returned. - May 2023 Acquisitions SF:06563020 URM-183962
Previously, the PO Line-Packaging job caused duplicate order-emails to be sent to vendors. This was fixed. Alma now checks whether a PO was already sent to a vendor before it sends the PO, and if it was, it does not attempt to send it again. - May 2023 Acquisitions SF:06414361 URM-180212
Previously, when a PO line was migrated from a different system into Alma, a creation date was not always defined for the PO line in Alma. In addition, if the PO line also had a hold request from an interested user attached to it before the migration process, and the migration process could not identify the request date of the hold request, it was programmed to use the creation date of the PO line instead. If this date was also not defined, an error occurred when a user attempted to mark the PO line as Done. This has been fixed. When a hold request for an interested user exists prior to migration, if Alma cannot identify the creation date of the PO line or of the hold request, it uses the current system date as the hold-request date. (This may impact the request's place in the queue.) - May 2023 Acquisitions SF:06388047 URM-181815
Previously, if a PO line was not part of any PO, and it was included in the list of PO lines to be processed by the PO Line - Receive All job (i.e., when Receive all was selected in the the Receive New Material page - Acquisitions > Receiving and Invoicing > Receive), the job would get stuck when it attempted to retrieve the PO data and would finish very slowly. This was fixed. The job now correctly handles receiving of PO lines that are not part of POs. - May 2023 Acquisitions SF:06554296 URM-181817
Under very specific conditions, the PO Line - Claiming job failed and the claim email was not sent as it should have been. The code has been changed so that, if a similar situation arises in the future, the job will not fail, but rather will be completed with errors and/or warnings. - May 2023 Acquisitions SF:06606299 URM-184766
Previously, attempting to open the Analysis tab of a trial that had no questions defined caused an error. This was fixed. It is now possible to open the Analysis tab of a trial even if it does not have any questions defined. - May 2023 Acquisitions SF:06684128 06687053 URM-189872
Previously, when the Rollover PO Lines (PA) job was run, it was not added to the Rollover job list in Acquisitions > Advanced Tools > Rollover PO Lines list, (although it did appear in the list in Monitor Jobs > History tab). This was fixed. Now, when the Rollover PO Lines (PA) job runs, it is added to Rollover PO Lines job list as it should be. - May 2023 Acquisitions SF:06246806 06238120 URM-170818
In a particular case, SUSHI harvesting of usage reports was not working as expected. The problem could not be reproduced, but additional data will from now on be added to the log files of the harvesting process, making it possible to identify the problem in the future, if the issue arises again. - May 2023 Acquisitions SF:06354790 06243225 06369503 06637765 URM-176011
Previously, when a SUSHI account name contained special characters that could not be included in a file name, the harvesting job for the account failed when the system attempted to save the response file in the file system. This was fixed. All such special characters in SUSHI account names are replaced with "_" before the system attempts to save the response file. - May 2023 Acquisitions SF:05300946 URM-180866
Previously, monthly COUNTER5 data was not overridden by the Custom Harvest action when the Year of Publication field contained an empty string, resulting in duplicate SUSHI data. This was fixed. Monthly SUSHI data is overridden by the Custom Harvest action even when the Year of Publication field is empty. - May 2023 Acquisitions SF:06557556 URM-180280
Previously, when the Change PO Line Status job was used to close PO lines for electronic resources, the PO lines were closed, but the job report said that they were skipped and could not be closed. This was fixed. Now the job report correctly states that these PO lines are closed. - May 2023 Acquisitions SF:06633687 URM-189320
The Data Correction job was failing in the production environment. This was fixed. The job now runs properly in all environments. - May 2023 Administration and Infrastructure SF:06311179 06572935 URM-175172
In a specific case, when a logical set was used as input for an Update/Notify Users job, the number of users in the set was not calculated accurately. As a result, some of the users in the set were not processed by the job. This was fixed. The number of users in the set is now calculated accurately, and all of the users are processed correctly by the job. - May 2023 Administration and Infrastructure SF:06443966 URM-182139
In the UPLOAD ELECTRONIC HOLDINGS Integration Profile, scheduling cannot be disabled. This was fixed. - May 2023 Administration and Infrastructure SF:06394806 URM-173885
Alma UI Location selector dropdown and library configuration lists are not sorted according to Icelandic Alphabet. This was fixed and now when selecting a circulation desk, these libraries/circulation desks are displayed after the letter 'A'. - May 2023 Administration and Infrastructure SF:06562717 URM-182586
The Hebrew interface of the Metadata Editor experienced problems with the menus and with the list of templates/rules. This was fixed. - May 2023 Administration and Infrastructure SF:06680350 URM-183433
Resources > Manage Inventory > Manage Collections - the sorting options for Managing Collections list were not translated. This was fixed. - May 2023 Administration and Infrastructure SF:06543512 URM-187250
Buttons are not visible in Pick from Shelf screen for items with a long request note. This was fixed and the buttons are now displayed. - May 2023 Administration and Infrastructure SF:06488452 URM-181175
Scan-In Page, Item Policy dropdown is not translated. This was fixed and now the language of the Item Policy matches the language of the UI. - May 2023 Administration and Infrastructure SF:06467137 URM-184984
An email that is sent to report the status of the Change Physical Items job was displaying HTML tags in the counters. This was fixed and the tags are no longer displayed. - May 2023 Administration and Infrastructure SF:06558134 URM-189623
The SAML profile via the idpCode parameter was not considered for deposit and resorted to the default profile. This was fixed. - May 2023 Administration and Infrastructure URM-140833
Emails sent to non-patron users are generated by XSLTs to HTML and are not accessible, failing checks by various accessibility tools. This was fixed and now the default XSLT for emails generates HTMLs that pass WCAG 2.1 level A and level AA. - May 2023 Analytics SF:06318005 URM-173383
The Classification Code field in Analytics displayed Unknown for codes that are Library of Congress classifications. This was fixed and the missing LC classification codes were added. - May 2023 Analytics SF:06478805 06591684 URM-183761
The Available for My Institution field only worked properly when the Available for Group Members field was included in the report. This was fixed, and now the Available for My Institution field works independently. - May 2023 Analytics SF:06668908 06652110 URM-189710
Reports using the Receiving Operator field erroneously displayed many null values. This was fixed, and now the Receiving Operator field displays the correct values. - May 2023 Analytics SF:06576065 05317614 URM-165508
The user expiration date in Analytics is not the same as in the Alma interface. This was fixed. - May 2023 Analytics SF:06691826 06690483 URM-186290
If a scheduled object in the new UI was deleted, the job was not deleted and continued to send emails with the reports to users. This was fixed. - May 2023 Analytics URM-190879
The default scheduling in the new Analytics UI was set to every 6 hours. This was too frequent, so it was changed to every Monday at 9:00. - May 2023 Analytics SF:6651527 06682886 URM-184286
The value for Fines and Fees > User Details > Statistical Categories 1 - 10 was the code and not the description. This was fixed. - May 2023 Analytics SF:06648562 URM-190500
It was not possible to subscribe to old reports with the new Analytics UI. This was fixed by adding the Subscribe to the analytics objects toggle even when reports were scheduled in the old UI. - May 2023 APIs SF:06637439 URM-187246
Previously, when a user updated user information in the Quick User Management page (Fulfillment > Checkout/Checkin > Manage Patron Services > [select user] > Edit User Info), when the changes were saved, old data would sometimes be inserted into the updated field instead of the newly updated information. This was fixed. Updated user information that is input in this way is now saved correctly in the user record. - May 2023 Digital Resource Management SF:06630726 URM-187039
Data retrieved by SRU was incorrect. This was fixed by updating the MARC to MODS xsl to MODS 3.7. - May 2023 Electronic Resource Management SF:06583306 05300554 URM-164151
Consortia Topology: Activating the same Community Zone (CZ) records for different members in parallel resulted in multiple Network Zone (NZ) bibliographic records pointing to the same CZ record. This was fixed and now parallel activation of the members triggers creating a single NZ record for each CZ linked record. - May 2023 Electronic Resource Management SF:06637453 06358908 URM-183275
Local portfolios are created with Global Date Information instead of Local Date Information. This was fixed by changing the global coverage section to be editable according to the portfolio's linkage. - May 2023 Electronic Resource Management SF:06625408 URM-188896
The Upload Electronics Holding job didn't find a match on a few specific portfolios even though they existed. This was fixed. - May 2023 Electronic Resource Management SF:06663392 URM-189585
Electronic Collection History log failed to record change from Static URL to Dynamic URL. This was fixed and now the field called parser parameters in the history log are the URL type of the new content.
For example: The user changes the URL content from X to Y and the URL type from static to dynamic.
History after saving: Field Name: URL Type, Old Value: Static URL, New Value: Dynamic URL.
Field name: Dynamic URL, old value: X , new value: Y. - May 2023 Electronic Resource Management SF:06640122 URM-187040
Alma service icons are not appearing under the Additional tab and under Availability in the Portfolio list of a service. This was fixed and icons are now displayed. - May 2023 Electronic Resource Management URM-171702
Only one record is displayed in the Community Zone update task list for IEPA, CDI, BIB changes, even if there are 2 local instances for the same IEPA in CZ. This has been resolved and in such cases, after adding the missing record, it is necessary to check that the displayed IEPA name is correct. - May 2023 Fulfillment SF:06557788 URM-183783
Previously, if an item was requested at one location for pickup at a different location, the pickup location was configured for automatic printing, and quick printing was enabled there, quick print was triggered as soon as the request was submitted. At that time, the quick-print pop-up appeared in Alma at the requesting location, and, regardless of whether the letter was actually printed or not, it was marked as printed in the Printouts queue. As a result, batch printing jobs run by API that should have printed the letter did not print it, because it was no longer in the printing queue. This behavior has been changed. When quick printing is configured for a pickup location, it is not triggered when a request is submitted at another location. Instead, the printing status of the letter is set to Pending. With this status, the letter is included in batch printing initiated by API. - May 2023 Fulfillment SF:06476446 URM-181007
Previously, when returning items via RFID from the Patron Services page (Fulfillment > Checkout/Checkin > Manage Patron Services > [select user] > Returns tab), the last setting of the Place directly on hold shelf option was not saved. Instead, it automatically reverted to being turned on. This was fixed. The last setting of the option now becomes the default setting for the next RFID return. - May 2023 Fulfillment SF:06438780 URM-178648
Previously, the Loan Status Notice Letter was not sent to the borrower of an item when its due date was changed via API. Now an optional parameter, notify_user, has been added to the API. This parameter is a Boolean flag for choosing whether to notify the borrower of changes in the loan due date. By default, the parameter is set to false, and no notification is sent to the borrower. - May 2023 Fulfillment SF:06503471 URM-180281
Previously, in certain cases, it was not possible to loan certain items, or to delete requests attached to those items. When a user attempted to perform one of these actions for these items, an error message appeared. This was fixed. These items can be loaned, and requests for them can be deleted, as expected. - May 2023 Fulfillment SF:06369672 URM-176612
In some cases, the Journal Services Page displayed an incorrect coverage summary that included a filtered portfolio when it should not have. This has been fixed. The correct coverage summary is now displayed. - May 2023 Fulfillment SF:06299336 05301549 URM-157003
In a fulfillment network, when a loaned item was returned to an institution in the network to which the item did not belong, if the return was performed in the Return Items page, a loan receipt was not sent to the patron. This has been fixed. When a loan is returned to any institution in the fulfillment network, a loan receipt is sent to the patron. - May 2023 Fulfillment – Resource Sharing SF:06483037 06557742 URM-178080
In the new UI, dropdown lists did not 'remember' the last selection, and make it the first option in the list, as they did in the previous layout. These drop-down lists now 'remember' the last selection and place it at the top of the list. - May 2023 Fulfillment – Resource Sharing SF:06305981 URM-178597
Previously, in certain cases, when a user attempted to create a Resource Sharing borrowing request for a non-book resource from an External Resource search, the request could not be created, and an error message appeared. This has been fixed and is working correctly now. - May 2023 Fulfillment – Resource Sharing SF:06473938 06681485 URM-179801
Previously, searching for borrowing requests by Remote Record ID in the New Layout of the RS task list did not return any results. This occurred because the Remote Record ID was not indexed in the New Layout. This has been corrected. This field is now indexed and searchable. - May 2023 Fulfillment – Resource Sharing SF:06487127 URM-181579
In the New Layout of RS borrowing requests, it was not possible to override blocks on renewals and renewal requests. This has been fixed. It is now possible to override blocks in these cases. - May 2023 Fulfillment – Resource Sharing SF:06599733 06580668 URM-183178
Digital files were unavailable after being fulfilled, even though the days set in the document_delivery_cleanup_days parameter (Configuration Menu > Fulfillment > General > Other Settings) had not passed. This was fixed. - May 2023 Fulfillment – Resource Sharing SF:06639438 URM-187109
In some cases, expired files appeared as available in patron accounts even though the files were no longer accessible. This was fixed. - May 2023 Physical Resource Management SF:06453038 URM-178675
The Review and Confirm page for the Change Holdings Information job was not displaying the names of the task parameters. This is fixed and task parameters are now displayed. - May 2023 Physical Resource Management SF:06602528 URM-184105
Change Holdings Information Job > Failed Records List: An internal identifier was displayed instead of the holdings' MMS ID. This was fixed. - May 2023 Resource Management SF:06337301 URM-183349
General Publishing > Related Records enrichment: Only partial relations of processed records were added to the published file for big sets (>50K). This was fixed, and all the relations are now published. - May 2023 Resource Management SF:06680350 URM-189535
The sorting options for Managing Collections list were not translated. This was fixed and the translations are displayed correctly. - May 2023 Resource Management SF:06685491 URM-189646
Removing a collection title does not update the database table's: collection_members, modification_date and modified_by columns. This was fixed and the table is now updated correctly. - May 2023 Resource Management SF:06640878 URM-190038
Selecting Add to collection results in an internal error where rows with collectionPid=null were added in the collection_members table. This was fixed . - May 2023 Resource Management SF:06557327 URM-181989
Metadata Editor: Using the Show all items button in an empty Network Zone holdings record displays items from a previously opened holding. This was fixed. - May 2023 Resource Management SF:06645618 URM-187444
Special characters (such as apostrophe or ampersand) in the Additional Staff Search Fields were not displayed properly. This was fixed - May 2023 Resource Management SF:06652465 URM-188163
When trying to delete a specific Physical titles set, the following message was displayed: An error occurred while deleting the set. This is fixed and sets are now deleted without errors. - May 2023 Resource Management SF:05315148 URM-166665
Non-sorting characters like <<>> are used to remove articles from titles - and therefore they are not considered in the browse bib headings for titles. But this was not working for titles saved in 7xx fields. This is fixed and now these headings can be found only using the title without the leading article in the browsing. - May 2023 Resource Management SF:06597295 URM-186599
Direct full display or permalink of search webhook records does not display all full text availability link for some records. This was fixed. - May 2023 Resource Management SF:06340952 06612887 URM-171428
In MODS records, the language information wasn't always presented in Alma and Primo. This has been fixed. - May 2023 Resource Management SF:06533440 URM-180699
When importing authority records from SBN, the LDR has only a few positions filled, most of them are empty. This was fixed and the LDR is now maintained as in the central catalog. - May 2023 Resource Management SF:06533571 URM-180701
SBN integration - automated localization process was needed after merge. This was resolved by adding functionality to the 'merge' portion of the SBN authority and bibliographic alignment jobs. This new functionality looks for any localizations in the non-preferred record that belong to the institution (based on the Library code in the SBN central catalog configuration) and if any exist, a localization request is performed to add them to the preferred record.
- April 2023 Analytics SF:06287214 URM-170424
Chinese characters within graphs in Analytics reports were disappearing from the reports. This was fixed by a quarterly fix of the OAS. - April 2023 Analytics SF:06620598 URM-185289
When filtering an analytics report in the Users subject area by email, an unexpected string of characters was displayed with the email address. This was fixed, and now the email address appears without the string of characters. - April 2023 Analytics SF:06643656 URM-187091
The AE100 LC classification code was missing from the the LC Classification codes list. It was added. - April 2023 Analytics SF:06580889 URM-187315
The KZ and KI schedules were missing from the the LC Classification codes list. They were added. - April 2023 Acquisitions SF:06512683 06561839 05313290 URM-180760
Duplicate entries of license terms appeared in Primo and Primo VE. These duplicate entries no longer appear. - April 2023 Acquisitions SF:06514976 06522573 URM-181444
Previously, when getting PO lines with interested users via the API, the PO line of the request was case sensitive. This was fixed. It is no longer case sensitive. - April 2023 Acquisitions SF:06378897 06522995 URM-175115
Previously, when a user attempted to link an item to a continuous PO line, which is not a supported action (Items can be linked to one-time PO lines, but not to continuous PO lines), no alert was shown. Now, an alert is shown. - April 2023 Acquisitions SF:06535404 URM-181476
Previously, approval details (approval_date, approved_by, and approved_by_id) were left blank in the XML of the Order List letter. They are now added to XML as they should be. - April 2023 Acquisitions SF:06566170 06597278 URM-183106
When a Claim letter was supposed to be sent to a vendor, if the acq_vendor_account_email customer parameter was set to true, but the vendor account had no email address associated with it, the letter was not sent, even if the there was an email address associated with the vendor itself. Now, if the acq_vendor_account_email parameter is set to true, and no email is associated with the vendor account, but there is an email associated with the vendor itself, the Claim letter is sent to the vendor email. - April 2023 Acquisitions SF:06493219 06548850 URM-183181
In the Electronic Resource Activation Task List, when a user selected Done, the system assumed a PO line was connected to the electronic resource. When this was not the case, an error was generated. An extra check has now been implemented when Done is selected, to ensure that a PO line is actually connected to the electronic resource before the Done action is implemented, and thus preventing this error from occurring. - April 2023 Acquisitions SF:05309931 06327064 URM-125695
When a Claim letter was sent for a PO line that had no item description and used the newSubject format, the word 'null' was appended to the end of the letter's subject line where the item description would normally be appended. This was fixed; if a PO line has no item description, nothing is appended to the subject line of the Claim letter in its place. - April 2023 Acquisitions SF:06542574 06544040 URM-181059
The Trial Survey Form did not work properly; participants in trials received multiple emails inviting them to take part, but the survey forms they accessed were blank. This was fixed; the survey forms contain the questions they should contain, and the email invitations are not sent more often than expected. - April 2023 Acquisitions SF:06519562 06583280 06628800 06631635 URM-182988
Previously, multiple import jobs could try to update the same fund at the same time, resulting in data that was not processed. Now, the number of times each job can update a fund is minimized reducing the chances of conflicts between two separate jobs. - April 2023 Acquisitions SF:06496144 URM-188126
Previously, in the Rollover Ledger report, the value of the From Year parameter was not presented in the report. Now, it appears in the report for both the Copy and the Delete actions. - April 2023 Acquisitions SF:06449316 05323936 06653402 06409322 06488312 URM-154898
When two instances of the EDI-Load Files job ran simultaneously, the jobs did not always import all of the invoices from the vendor's server. Now, multiple instances of the job are not allowed to run at the same time - each new instance waist until the previous one has finished. As a result, all invoices are imported as they should be. - April 2023 Acquisitions SF:06594183 URM-184564
Under certain conditions, the EDI - Loads Files RIALTO job completed with the error 'Error on creating entity from xml,' and invoices failed to import. This has been fixed; this error no longer occurs when this job runs. - April 2023 Acquisitions SF:06560370 URM-183197
When an FTP transfer was interrupted during the disconnect process, after the files were actually already successfully transferred to the target server, the transfer process was repeated, resulting in duplicate copies of the files being transferred to the target. This has been fixed; if an exception is thrown during the disconnect stage of an FTP transfer, the file transfer is not repeated. - April 2023 Acquisitions SF:06561445 URM-183530
Previously, when invoices were exported to external financial systems, the PO number of the PO lines included in the invoice was not exported. Now, a new po_number field was added to the po_line_info section in the exported XML. If the PO line is part of a PO, the PO number is extracted to this field. - April 2023 Acquisitions SF:06639221 URM-187453
In certain cases, selecting Custom Harvest for a vendor from the Usage Data tab of the Vendor Details page opened a blank page. This was fixed; Custom Harvest now opens correctly in these cases. - April 2023 Acquisitions SF:06643239 URM-187448
Previously, when an electronic PO line that was not linked to a resource was set to claim, the Claiming job failed. This was fixed; the Claiming job no longer fails in this case. - April 2023 APIs SF:06639092 URM-187443
Previously, authenticating a user via the Alma Users API required an API key with a write permissions. Now, an API key with read-only access is sufficient for authenticating a user via API. This differs from the authentication requirements of other POST APIs, which continue to require write permissions, because this API does not alter data. - April 2023 APIs SF:06484251 URM-180684
Previously, the full list of serial database names was not checked when determining if an imported record was a monograph or a serial. This has been fixed; the full list of serial database names is now checked during this process. - April 2023 Administration and Infrastructure SF:06360858 URM-173894
Previously, when a logical set of users based on user status was created, it produced an empty set of results. This was fixed; logical sets of this sort now return the correct results. - April 2023 Administration and Infrastructure SF:06541041 06594326 06594392 06610271 06624002 06624256 06624642 06625009 06625250 06625377 06626298 06627525 06628717 06631829 06631839 06632929 06633433 06633698 06633869 06634945 06635115 06638445 06639183 06641015 06642126 06642231 06643736 06643745 06645631 06645994 URM-186282
Some widgets in the Alma UI are no longer displayed correctly. This was fixed and the widgets now display correctly. - April 2023 Resource Management SF:06481305 06482799 URM-179046
Sets with a date-based field that are used in advanced search and saved during specific times of the day, the value shifts a day forward. This was fixed with a configuration adjustment to address timezone differences. - April 2023 Resource Management URM-182719
Metadata Editor: Warning messages and "Record saved" messages that have interactive elements do not receive focus when tabbing through the Alma UI for screen readers. As a result, the elements cannot be operated with a keyboard. This was fixed. - April 2023 Resource Management URM-179090
Metadata import created BIB version and distribution for unmodified BIB records. This was fixed by comparing the existing BIB in the database and if there are no differences, it is not saved. - April 2023 Resource Management SF:06455704 05310335 05310834 URM-179135
Moving an item to another permanent location via the Change Physical Items Information job: when both 'update_call_number_type_upon_item_move' and 'use_marc_record_holdings_template' customer parameters were set to 'true', the target holdings record was not assigned the call number type defined in the target physical location; instead, the first indicator of the default holdings record template was used (a space was converted to '#'). This was fixed. - April 2023 Resource Management SF:06602761 URM-184822
Previously, an issue existed in the 'Continuous Tab' (Acquisitions > Receives > Continuous Tab) where if a customer selected the Duplicate button to copy an item's details but then edited the description without updating it, the system would not display an alert for the item description. This issue has now been resolved and an alert is now shown in this scenario. - April 2023 Resource Management SF:05317929 URM-171701
Community Zone update task list displayed the wrong name of the collection for a SERVICE change. This was fixed by changing 'updatePps' to take the package name from each IEPA individually, instead of taking it from the first one. - April 2023 Resource Management SF:05301384 URM-182682
When searching for titles in the Community Zone scope, the count of electronic portfolios for a title was sometimes incorrect. This was fixed by a performance improvement made when creating the 'Update in Community' pop-up for a contributed collection. - April 2023 Resource Management SF:06474399 URM-178227
MODS records deleted a space in the name of a collection. This was fixed. - April 2023 Resource Management SF:06657123 06658548 06651313 URM-188287
Print Preview for PDFs in the Alma viewer displayed an empty page. This was fixed and now the page to be printed is displayed. - April 2023 Resource Management SF:06536686 06568124 URM-181966
General Publishing: Previously, two jobs related to the same General Publishing profile could not run in parallel, where the second job was immediately aborted with the status Skipped. This is fixed, now the second job waits (status 'Pending') until the first job is completed and then continues running. - April 2023 Resource Management SF:06498260 URM-181958
Headers were not displayed while searching electronic titles in the Community Zone and selecting to view the portfolio list. This is fixed and Collection Headers are added to the display. - April 2023 Resource Management SF:05313754 URM-123295
The 'Catalog set' function does not work as expected for bibliographic records from the Community Zone, if the Metadata Editor is loaded for the first time. This was fixed and now the whole set is pushed to the Metadata Editor. - April 2023 Resource Management SF:06463158 06613730 URM-178076
Creating a Physical Title Set using an Excel file with empty lines caused an error. This was fixed and these lines are now skipped. - April 2023 Resource Management SF:06442585 URM-183798
In the link resolver, when calculating consolidated coverage for a title with multiple portfolios where one of the portfolios partially supplements the second portfolio's coverage, the consolidated coverage was not displayed correctly. This was fixed. - April 2023 Resource Management SF:06285033 URM-168241
Export errors occurred to Mendeley in cases where the field 'year' contains 'u' or '?'. This was fixed and errors are now prevented. - April 2023 Resource Management SF:06210999 05312626 URM-157988
The new feature: 'Metadata Editor Holdings 852 $b - Support for Libraries Sorting by User Location' was not working as expected. This was fixed. The 'Currency at' library is now displayed in the form's dropdown. - April 2023 Resource Management SF:06328275 06596178 URM-170931
SBN integration profile: The 'Merge routine' did not include the disabled merge rules. This is fixed and now the list contains both enabled and disabled rules. - April 2023 Resource Management SF:06509466 URM-180687
Alma normalizes 'Chinese Book Classification Call Number' headings for customers' special 'non-ASCII' sorting order. Alma also applies special normalization to the sequence number portion to sort them sequentially, rather than alphabetically. However, if there are multiple instances of a space or a forward slash followed by digits, Alma cannot identify the sequence number. This was fixed and now Alma can accurately normalize the call number. - April 2023 Resource Management SF:06517140 06524540 URM-180688
Templates contributed to the Community Zone disappeared after some time. This has been fixed. - April 2023 Resource Management SF:06463588 URM-177820
Authority heading lookup (F3) - When working with authority headings that contain both Hanja and Hangul in the same field, the authority was sometimes not displayed in the list of suggested headings. This has been corrected. Contact Exlibris support to activate this fix. - April 2023 Resource Management SF:06514525 URM-181534
Bibliographic Record Relations are not being updated by 'MMS - Build Record Relations' after being 'Merge and Combine' in the Metadata Editor. This was fixed with a configuration update. - April 2023 Resource Management SF:06358027 URM-173974
The jobs for some digital import profiles are completed with errors from time to time, but the job report shows no reason and the Events List is empty. This was fixed. Now, if a Metadata import job fails when importing records from OAI, an added event is displayed to notify users. - April 2023 Resource Management SF:06558869 URM-184010
The second indicator values of the 260 field in the Ex Libris Metadata Configuration List for Marc21 Bibliographic was incorrect according to the Library of Congress. This was fixed. The indicator may have values #, 0, or 1 instead of #. - April 2023 Resource Management SF:06223114 URM-165977
SBN contribution: The contribution of Uniform Titles sometimes failed due to a wrong SBN sequence number generated. This was fixed. - April 2023 Resource Management SF:06490811 URM-180417
Cloud App NACSIS-CAT: The linked record IDs from <BHNT>BHBID were not copied to $w of the resulting 780 or 785 fields. This was fixed. - April 2023 Resource Management SF:06484247 URM-180510
IDs from the first <AL>AID= element in a NACSIS record was erroneously reused in the subsequent <AL> group without an AID= element in the Alma records. This was fixed. - April 2023 Resource Management SF:06490667 URM-180513
Records from NACSIS sometimes contain OTHN= elements with prefixes that are not capitalized correctly. This was fixed. Alma now corrects the capitalization of these prefixes: (JP-ItNTS), (JP-ToTOH), (OCoLC). - April 2023 Resource Management SF:06492233 URM-180648
In some cases, when an Alma field 505 $t ended with a slash preceded by a space ' /', it duplicated the record. This was fixed by removing the slash before contributing the content for such particular fields. - April 2023 Resource Management SF:06490665 URM-180712
Alma contributing records to NACSIS: 084 subfield 2 caused errors, preventing the upload of the record to NACSIS. This was fixed with additional classification codes that have been implemented. - April 2023 Resource Management SF:06490827 URM-180718
Volume information was not correctly parsed from the NACSIS <CW>CWT element when the volume contained CJK characters. This has been fixed. - April 2023 Resource Management SF:06512606 URM-180863
When exporting a subject heading from Alma bibliographic field 651 (Subject Added Entry-Geographic Name) to NACSIS, the subject heading field was incorrect. This was fixed with the correct subject heading type code in NACSIS which is 'F'. - April 2023 Resource Management SF:06494872 URM-181114
Copy Cataloging NACSIS to Alma: The NCID numbers (uniform title record IDs) were not copied to the 130 or 730 field $0. This has been fixed. - April 2023 Resource Management SF:06499475 URM-182495
When importing records from NACSIS into Alma, the complete string OTHN was not mapped into tag 035 when OTHN contains one of the following values: GPON ISSN LCCN NBN NDLCN ISBN XISBN. This has been fixed by implementing these values. - April 2023 Resource Management SF:06542519 URM-183035
When tag 016 in Alma has the subfield $$2 JTNDL, the identifier from tag 016 $$a was not mapped to the NACSIS field NDLPN. This was fixed by implementing additional specifications indicating when Alma bibliographic field 016 should be exported to the NACSIS system. - April 2023 Resource Management SF:06558906 URM-187354
In the Item's History tab when viewing a specific operator's user details pop-up, if you attempt to view another operator's details, you encounter an error screen. This was fixed. - April 2023 Resource Management SF:06327987 URM-172832
In Physical Holdings repository search results, the Copy feature highlights more than the selected field and pastes incorrectly. This was fixed. - April 2023 Fulfillment SF:06538296 06639849 06563249 06663748 06677046 URM-182351
In some cases, a loan would be renewed when the policy did not allow it to be renewed. This was fixed; renewals in these cases are not implemented when the policy prohibits them. - April 2023 Fulfillment SF:06304763 05805276 06514221 05315449 06511156 05319076 05311705 URM-91472
Previously, when a loaned item was scanned via the Scan In Items option, and the user was 'Currently At' a work order department, the 'Desk name' of the Return action that appeared in the Physical Item Editor page, in the History tab, appeared as the internal ID of the work order department instead of its name. This was fixed; the name of the work order department now appears in this location, as expected. - April 2023 Fulfillment SF:06301714 URM-172775
When a borrowed item was loaned again after being returned, the borrowing request would not have the option to request a renewal. This was fixed by removing the return date from the borrowing request when the item was loaned again. - April 2023 Fulfillment SF:06482964 06560562 06493631 06618069 URM-180521
Previously, when a Resource Sharing task was assigned to a user from the New Layout of the Resource Sharing Task List, and a General Assign To letter was sent to the user to inform them of the assignment, if a note was added when the assignment action was initiated, the note was not included in the letter, and a number appeared in its place in the letter. This was fixed; any notes added to an assignment now appear in the letter sent to the assignee. - April 2023 Fulfillment SF:06390023 06631176 URM-178945
Creating a lending request coming from Rapid ILL would fail if the mms id sent from Rapid was an NZ mms id. This was fixed and now Alma allows creating the request also for NZ mms. - April 2023 Fulfillment SF:06436236 URM-174590
Previously, loaning an item from a different institution in a fulfillment network via RFID generated an error message, 'Security bit failed to be changed: RFID error - barcode not found,' even though the loan was processed correctly. This was fixed; this message no longer appears in this case. - April 2023 Fulfillment SF:06442607 06504057 URM-179376
Previously, running two Resource Sharing Integration Profile jobs, from two different profiles, in parallel was not possible, because they blocked one another. This has been fixed, it is now possible to run two of these jobs simultaneously. - April 2023 Administration and Infrastructure SF:06662865 URM-189183
In the Alma UI, a clickable 'X' for a secondary search box overlapped the Search button. This was fixed. - April 2023 Administration and Infrastructure SF:06627842 06641487 URM-187068
The Preferred Language drop-down included Hawaiian, even when the code table was customized to include only specific languages. This was fixed. - April 2023 Administration and Infrastructure SF:06410082 06337374 URM-174399
The digital images of a representation in a collection were not displayed when clicking the delivery link URL. This was fixed. - April 2023 Administration and Infrastructure URM-185829
In the Alma UI, using the globe icon that displays the list of languages configured for the institution, it was possible to translate the relevant term for all languages, but only when using the UI in English. This was fixed and it is now enabled when the UI is in another language. To enable this, set the following feature flag to active: SPECIAL_ENT_GLOBE_TRANSLATE_IMPROVE. - April 2023 Fulfillment - Course Reserves URM-188182 SF: 06655246
In some cases, courses did not appear in Alma, but they did appear in Analytics. This was fixed.
- March 2023 Acquisitions SF: 06446126 05299957 06054826 05316646 05318675 URM-164301
When a hold request from an interested user was added to the queue, it was incorrectly added at the end of the queue, because other requests which should have had a lower priority had already been activated in the queue. The order in which these processes are performed was reversed, so that interested users are entered into the queue before activation takes place, and thus are given the correct priority in the queue. - March 2023 Acquisitions SF: 06469629 URM-179711
Previously, the Rejection reason field was displayed under Request Attributes for all purchase requests, regardless of their actual status, and if its value was not set manually, its default value appeared there. This has been corrected; the Rejection reason field is now only displayed in rejected purchase requests. - March 2023 Acquisitions SF: 06567338 06565694 06354457 06486696 URM-180397
In certain cases, when an API call failed after it changed some fields, the fields that were changed were not restored to their previous states as they should have been. This was fixed; if an API call fails, all changes it made before the failure are reversed. - March 2023 Acquisitions SF: 06502702 URM-183842
Previously, the Purchase Requests task widget sometimes included requests that were not within the user's scope and role. This has been fixed; the Purchase Requests task widget now only includes purchase requests that belong to the user's scope and role. - March 2023 Acquisitions SF: 06560540 URM-184523
Previously, in some cases, the advanced search for POs with status Sent also retrieved Closed and Cancelled POs, and did not retrieve all of the ‘Sent‘ POs. This has been fixed; the advanced search for ‘Sent‘ POs now returns the correct data. - March 2023 Acquisitions SF: 06531640 URM-181537
Previously, the API documentation incorrectly labeled some of the fields of invoice-payment information (payment_identifier, payment_date, payment_currency, and payment_amount should have been voucher_number, voucher_date, voucher_currency, and voucher_amount, respectively). The API documentation has been corrected. - March 2023 Acquisitions SF: 06650647 06651897 06651167 06651744 06651036 06650849 06651924 06651074 URM-187318
License Terms types were unexpectedly updated to have (explicit) and (interpreted) added without any other option. This was corrected and the new license terms were added on top of the existing ones. - March 2023 Acquisitions SF: 06483876 06614826 06464579 06653718 06501977 06446915 URM-178201
When the Update PO Lines Transactions job was used to transfer PO Lines to new funds, the encumbrances on the old funds were not removed as they should have been. This was fixed; when this job runs, encumbrances on old funds are updated as they should be. - March 2023 Acquisitions SF: 05316533 06530746 06411285 06544103 URM-160926
When the automatic SUSHI harvesting job returned with No valid report items found in the file, the job did not run automatically at later dates as it should have. This has been fixed; the job runs on schedule even after it returns with ‘No valid report items found in the file'. - March 2023 Acquisitions SF: 06397850 06327433 06409812 URM-176486
When the automatic SUSHI harvesting job returned with No Usage Available for Requested Dates - indicating that the data was not yet available for harvesting - the job did not try to harvest the data again for the same dates the next time it ran, as it should have. This has been fixed; the job now retries its data harvesting the next time it runs when this situation arises. - March 2023 Acquisitions SF: 06404212 URM-178548
Previously, when an import profile was used to import EOD and create a PO line from it if the creation of the inventory failed, the PO line was skipped, but no error message was returned. This was fixed; an error message is now returned when an EOD import fails. - March 2023 Administration and Infrastructure SF: 06235884 06340126 URM-177886
Previously, if a patron's account had a credit and a fine that were both for the same amount, both the credit and the fine appeared on the User Details page in the Fines/Fees tab, and the patron was sent a letter asking them to pay their outstanding debt. This behavior has been improved: if the credit and fine are both from the same library, they now cancel one another out and are both removed from the Fines/Fees tab. A letter is sent to the patron only if the patron has a non-zero balance at one or more of the libraries in the institution, and the letter lists all the libraries at which the patron has a non-zero balance. Libraries at which the patron's balance is zero are not mentioned in the letter. - March 2023 Administration and Infrastructure SF: 05323949 06283816 URM-156734
Previously, when a Purge User Records job was being configured (Admin > Purge User Records > Add a Job), the User Group field was always included in the Add Job window, regardless of what type of record was chosen under Record Type. Since the ‘User Group‘ field is not relevant to the job when the job's ‘Record Type‘ is ‘Contact,‘ the dropdown list of options for the ‘User Group‘ field contained no values when either ‘Contact‘ or ‘All‘ (which includes the ‘Contact‘ record type) were selected under ‘Record Type.‘ This field is now removed from the window when ‘Contact‘ or ‘All‘ are selected as the record type. - March 2023 Administration and Infrastructure SF: 06509612 06490383 URM-180666
Previously, whenever a fine was added or waived in a user account, the user history was unnecessarily modified. This was fixed; adding or waiving a user fine no longer generates inappropriate additions to the user history. - March 2023 Administration and Infrastructure SF: 06314657 URM-169157
Code Tables opened with a Non-English Language in the filter were incorrectly displaying the Description column in English. This was fixed. - March 2023 Administration and Infrastructure SF: 06487046 URM-183444
Alma mashup included in Primo (classic), the Work Order type was not translated (appeared in English, even when translation existed). This was fixed. - March 2023 Administration and Infrastructure SF: 06518738 URM-183835
The tooltip for the Locations Ordering Profile is misleading (regarding ‘Locations‘ instead of ‘Libraries‘) and needed to be modified. This was fixed and the tooltip now reads, ‘When selected, locations will be ordered according to discovery priority for each library in the custom Libraries Order page. - March 2023 Administration and Infrastructure SF: N/A URM-65142
Many ghost records appear in SOLR but not in the Database. This was fixed by the SOLR / DB Diff job that is triggered twice a year following the semi-annual indexing. This task's aim is to handle PA jobs to ignore such ghost records. - March 2023 Analytics SF: 06318005 URM-173383
- March 2023 Analytics SF: 06595378 URM-183851
Adding address fields to reports in the Users subject area did not display results if the reports were filtered by Primary ID. This was fixed. - March 2023 Analytics SF: 06591380 URM-184114
When exporting reports as a formatted Excel after a filter is applied an error message is displayed. This was fixed. - March 2023 Analytics SF: 06588655 URM-184194
The Users > User Details > Primary Identifier field did not work properly when reports were retrieved by API. This was fixed by adding the User Primary Identifier alias to the field. - March 2023 Analytics SF: 06574963 URM-184370
Reports created with the campusM Home Page > Menu Clicks field displayed only the 15 most clicked menu options. This was fixed and now all menu options are displayed. - March 2023 Analytics SF: 06584946 06588233 06653911 06650698 06585834 06596765 06611366 URM-184738
Adding the Retention Reason field to a report caused it to fail. This was fixed. - March 2023 API SF: 06529480 URM-183470
Previously, the Manage Members API could not populate a set with PO lines, although it should have been able to do so. Now, this API can populate a set with PO lines as expected. - March 2023 API SF: 06503140 URM-183954
Previously, the Update Electronic Collections API was not working properly. This was fixed; it now works as it should. - March 2023 API SF: 06442929 URM-184224
Previously, when the API for deleting a bibliographic record encountered a record that could not be deleted because it had objects attached to it (such as physical items, electronic portfolios, digital representations, and/or orders) if the attachments were of multiple types, the API returned the error message, Record has attachment. This message was too vague, and also was only returned in English and was not translatable. The message has been made clearer: Record has attached entities of various types. In addition, it is now translatable. - March 2023 API SF: 06564938 URM-184819
Previously, updating the Vendor Reference Number Type field of PO lines via the API did not work. This has been fixed, and now works properly. - March 2023 API SF: N/A URM-165411
Previously, updating authority records via the API failed under certain conditions, with the error, "Authority creation failed." This has been corrected; updating authority records via the API no longer fails in these cases. - March 2023 Digital SF: 06497820 05310252 URM-132070
Thumbnail images were created in the wrong orientation. This was fixed. - March 2023 Digital SF: 05301453 URM-157289
The job to generate thumbnails did not function properly. This was fixed. - March 2023 Digital SF: 05321628 URM-164090
If a title had quotes and the metadata is from Primo VE, the title in the Alma Viewer was displayed with backslashes. This was fixed. - March 2023 Digital SF: 06527577 URM-184310
If the Representation Type was changed to Auxiliary with a job, the representation link was not hidden in View IT / Primo VE by the ‘Hide service Representation Delivery Service with Usage Type = Auxiliary‘ display logic rule until the representation is re-saved. - March 2023 Digital SF: 06623522 URM-185873
The Registered access rights rule does not work if the user is not a member of a user group. This was fixed. - March 2023 Electronic Resource Management SF: 06348753 URM-171553
The Extended Export of Electronic Portfolios job took a lengthy amount of time to complete. This issue was fixed. - March 2023 Electronic Resource Management SF: 06585389 06549871 URM-182233
Export Context object to BX completes with FTP Error. This was fixed with an update to the FTP server URL. - March 2023 Fulfillment SF: 05323777 URM-173568
In some cases, the Requests - Recalculate after Inventory Update did not process all the relevant requests. This was fixed; it now processes all the relevant requests. - March 2023 Fulfillment SF: 06509469 URM-180283
Previously, when a loan was renewed, if there were no opening hours defined in the library's calendar for the maximum renew date and onward, and the Closed Library Due Date Management policy was set to Move to next open day, the Maximum Renewal Period policy was ignored when the renewal date was calculated. This was fixed; the renewal date in this situation is now calculated correctly. - March 2023 Fulfillment SF: 06543395 URM-183145
In GetIt, for a serial record, if there were multiple identical items with the same description in the same location, the digitization link appeared only for one of them even when all were digitizable. This was fixed; the digitization link now appears for all of the items. - March 2023 Fulfillment - Resource Sharing SF: 06483633 06510321 06506077 06625640 06444602 06453568 06505811 06559829 URM-177931
In certain situations, borrowing requests located items at lending institutions even when these items were unavailable. A problem with the search query on the lender's side was identified as the cause of the issue, and was fixed. - March 2023 Fulfillment - Resource Sharing SF: 06585537 06593389 06570823 URM-179004
Previously, in resource-sharing task lists, selecting Edit for an item caused the selected search index in the persistent search to change to All Titles instead of remaining unchanged, as it should have. This has been fixed; selecting ‘Edit‘ in a resource-sharing task list no longer resets the search index in the persistent search. - March 2023 Fulfillment - Resource Sharing SF: 06501226 URM-181804
Previously, if a resource-sharing lending library had multiple physical copies of a requested item, some of which could be shipped and some of which could not - depending on their TOUs - no warning message about this was displayed in the New Layout of the Lending Requests task list. Now, a warning message does appear in this situation. - March 2023 Fulfillment - Resource Sharing SF: 06478000 URM-179793
Previously, if a borrowing request for a book contained chapter or page information when the request was sent to Illiad, it was sent as a request with the document type Book Chapter. This should not have occurred when the number of pages in the request was identical to the number of pages in the book, unless the requested format was ‘digital.‘ The process has been fixed, and the document type is now set as it should be. - March 2023 Fulfillment - Resource Sharing SF: N/A URM-170010
In the Details pane of resource-sharing borrowing-request and lending-request task lists (in the New Layout), the interface of the Request form section has been improved. It now provides enhanced responsiveness and better support for non-English text. - March 2023 Physical Resource Management SF: 06582282 06268546 URM-174596
Repository Search: When exporting to Excel logical physical holdings set with thousands of results, not all results were exported. This was fixed, and now the exact results‘ number is exported. - March 2023 Resource Management SF: 06250626 06571814 URM-170172
A process containing two normalization rules, if the first rule was copying a field and the second was editing the field created (for example, by adding to it a subfield), only the first rule was applied. This was fixed. - March 2023 Resource Management SF: 06570917 06340092 06584795 URM-171346
For network members, the publishing to Primo jobs completed with errors in certain cases. This was fixed with some code changes that were implemented to reduce the number of errors. - March 2023 Resource Management SF: 06606249 URM-184842
Publishing Platform jobs fail with a deadlock detected while waiting for a resource. This was fixed by adding a technical change when running the job in republishing mode with Rebuild Entire Index to avoid deadlock errors. - March 2023 Resource Management SF: 06590744 URM-184052
There was a small typo (‘were‘, instead of ‘where‘) in the report of the Change Holdings Information job. This was fixed. - March 2023 Resource Management SF: 06570558 06589399 URM-184021
The file extension is not appearing in advanced searches for digital files. This was fixed and the file extension is displayed. - March 2023 Resource Management SF: 05304893 URM-166349
Authorities keywords search was not preserved when switching from Simple Search to Advanced Search. This was fixed. - March 2023 Resource Management SF: 06584778 06498190 06529336 URM-179673
Search by Country of Publication is not working as expected when the Alma interface language is not English. This was fixed - March 2023 Resource Management SF: 06302842 06427237 URM-174143
Itemizing a logical set of users based on expiry date does not include all results. This was fixed and now the itemized set has the same number of results as the logical set upon creation. - March 2023 Resource Management SF: 06430080 URM-178237
The holding accession number in Get It Hebrew UI was displayed in left to right (instead of, right to left) direction when including Hebrew letters and numbers. This was fixed. - March 2023 Resource Management SF: 05319695 05310115 URM-135048
FRBR group resource type did not match the preferred record. This was fixed. When FRBR preferred criteria is configured, the FRBR group resource type matches the configured type. - March 2023 Resource Management SF: 05333316 05326859 URM-149882
Primo VE - Mendeley export - only the first subject is sent; repeated occurrences are omitted. This was fixed and now all subject fields are sent to Mendeley export. - March 2023 Resource Management SF: 05312658 06539347 06529124 URM-161540
Times Cited link to WoS was not proxied when a record is open access. This was fixed. Time Cited links are now always proxied when the proxy configuration is enabled. - March 2023 Resource Management SF: 06308710 05318593 URM-161675
The Browse Search Label > ""nui.browseGap_message"" is disabled, but the message is displayed in the Browse Search results. A temporary workaround solution is available from the March 2023 release (and Classic Primo May 2023 release). Ex Libris added the following id=""browseGapAlertBar"" to the mentioned toast bar <prm-alert-bar> element that overrides the control of the displayed message: "Note: Some records are not displayed since they are restricted/suppressed from display". To disable the message from displaying, use CSS customization by adding the following to the custom1.css file in the customization package: #browseGapAlertBar { display: none; } - March 2023 Resource Management SF: 05306677 URM-162619
Labels are missing in Primo VE for many Language codes included in Alma, causing codes to display in Primo UI. This was fixed by adding labels for the following languages so their labels will be presented in the Primo VE interface languages list and not their code: Arabic, Catalan; Valencian, Czech, Basque, Finnish, Irish, Japanese, Lithuanian, Bokmal Norwegian, Norwegian Nynorsk, Northern Sami, Traditional Chinese, Hawaiian, Maori, Ukrainian - March 2023 Resource Management SF: 06303196 URM-174561
Primo VE - Sorting continues to be based on Location name rather than Library name even when Display Library name in Location facet is enabled. This was fixed. - March 2023 Resource Management SF: 06502342 06611885 URM-180506
The alphabetical sorting of subjects in the Record's Full Details was incorrectly sorted for letters with accents. This was fixed and now the sorting of subjects is correctly displayed in the Record's Full Details for letters with accents. - March 2023 Resource Management SF: 06609576 URM-184725
Primo VE: the Move Up/Down keys that control the order of the fields in the View Configuration > Brief Record Display tab are ineffective in controlling the order of fields. This was fixed and the Up/Down keys now enable users to set their preferred field order. - March 2023 Resource Management SF: 05332924 05303436 06503970 URM-150000
The Controlled Vocabulary Registry list order can not be sorted. A functional limitation assessment rendered that this option is removed. - March 2023 Resource Management SF: 06219940 06314750 URM-168859
When pushing multiple records to the Metadata Editor (MDE) at the same time, and the list of records in the MDE is sorted by entry time, clicking any record in the list caused it to jump up and change its place in the list. This was fixed and now the record stays in its place. - March 2023 Resource Management SF: 06368453 URM-171999
In the Metadata Editor, the displayed user names are not affected by the Alma user name display configuration. This was fixed, and now the lists of users in the assign record to another cataloger and release all records for user pop-ups are according to the configured format. - March 2023 Resource Management SF: 06406322 URM-178072
MODS: The Date part of Subject Heading is duplicated in Operational Record. This was fixed. The subject displays a single ‘Date‘ part in the operational record that can be viewed from the mms debug screen link for the title list resulting from all titles search. - March 2023 Resource Management SF: 06418310 URM-177792
When cataloging fields 210 $d and $h, Alma changes the field 100 d to h in pos.8 and adds the Publication Date ‘2‘ to pos.13-16. The contribution fails because of h in pos.8. This was fixed. - March 2023 Resource Management SF: 06490656 URM-180416
Cloud App NACSIS-CAT copy cataloging, some fields do not have a romanized transliteration in 880. This was fixed by adding the following missing transliterations:- When NACSIS record contains <AL>AHDNGR field with Hiragana or Katakana content and <AL>AHDNGVR does not exist or does not contain latin text, then <AL>AHDNGR is transliterated to latin and added to 880 field linked to 700 field.
- When NACSIS record contains <SH>SHR field with Hiragana or Katakana content and <SH>SHVR does not exist or does not contain latin text, then <SH>SHR is transliterated to latin and added to 880 field linked to 600/610/611/630/650/651/653 field (Actual field depends on subject heading code in <SH>SHK).
- March 2023 Resource Management SF: 06494876 URM-180814
Cloud App - NACSIS-CAT copy cataloging, fields 730 and 130 do not have a romanized transliteration. This was fixed by adding the following missing transliteration:- When NACSIS record contains <UTL>UTHDNGR field with Hiragana or Katakana content and <UTL>UTHDNGVR does not exist or does not contain latin text, then <UTL>UTHDNGR is transliterated to latin and added to 880 field linked to 130 or 730 field. (130 field if <UTL>UTFLG = *, otherwise 730 field.)
- March 2023 Resource Management SF: 05754607 05317872 06558134 URM-149800
When signing out from the Deposit link (self-deposit page), users were redirected incorrectly to an irrelevant URL. This was fixed.
- February 2023 Fulfillment SF: 06469678 06563250 06583362 06419522 URM-182010
The user‘s preferred language would not always be used for the Document Delivery letter. This was fixed; the user‘s preferred language is now used for this letter. - February 2023 Fulfillment SF: 06353800 URM-174497
Previously, when a digitization request for an article was created from a borrowing request, the start page and end page information was not included in the Note field of the digitization request as it should have been. This was fixed; when page information exists in a borrowing request, it is copied into the Note field of the digitization request created from the borrowing request. - February 2023 Fulfillment SF: 06498528 URM-180660
In the new layout of the Resource Sharing Borrowing Requests task list, when the Request Renew action was selected for a borrowing request, the due date was not extended as it should have been. This has been fixed; the due date is now extended as it should be, based on the configuration settings of the library. - February 2023 Fulfillment SF: 06251453 URM-177077
In some cases, NCIP checkout messages would reactivate completed lending requests instead of creating new ones. This was fixed; new lending requests are created in response to these messages, as appropriate. - February 2023 Fulfillment SF: 06262527 URM-173988
Previously, when the link resolver received a link for an OpenURL service page from Proquest with the genre dissertations &· theses, it did not associate this genre with the existing Alma ‘dissertation‘ genre, as it should have. This has been fixed; the link resolver now associates the Proquest dissertations &· theses genre with the Alma ‘ dissertation‘ genre. - February 2023 Fulfillment SF: 06491901 06488627 06558899 06556429 06425145 06490679 URM-179796
1. Previously, returning an item from a different institution in a fulfillment network failed if the item was overdue and the Block When Overdue policy was configured with an Open Days unit of measurement. This was fixed; items from other institutions in the fulfillment network can be returned in this situation. 2. Previously, overdue blocks were incorrectly calculated according to the opening hours of the loaned at library instead of the owning library. This was fixed; overdue blocks are now calculated based on the opening hours of the owning library, as they should be. - February 2023 Resource Management SF: 05305634 06317089 05379079 05330117 06553131 06216825 06291791 06052518 05889492 06241463 05515659 URM-105572
FRBR key ‘ Author+Title‘ does not match when the title differs due to multiple spaces not being compressed into a single space in FRBR keys. This was fixed. To have the expected behavior, customers must run the Recalculate Operation job. - February 2023 Resource Management SF: 05317595 URM-163717
Primo VE getit iframe in Leganto displayed the Primo VE footer. This was fixed and the footer is no longer displayed. - February 2023 Resource Management SF: 06400066 URM-175277
Records that are not available but have an available related item display the wrong availability location. This was fixed and the correct location is now displayed. - February 2023 Resource Management SF: 06553519 06535660 06580494 06521420 06552808 06556936 06576970 06552530 06555075 06547620 06556146 URM-180827
Non-Open Access Quicklinks were not proxied even though proxy configurations were set. This was fixed and now the Access Quicklinks are proxied. - February 2023 Resource Management SF: 06519069 06571218 06569916 URM-183118
Open Access record backlinks are proxied despite being configured as Do not proxy OA records. This was fixed and backlinks with Do not proxy... enabled will not be proxied. - February 2023 Resource Management SF: 05332005 05302909 05309184 06050493 05333230 05310481 URM-128540
MARC21 > 7xx authority records containing subfield $$e. The subfield is duplicated when linking it to the bib record. This was fixed. - February 2023 Resource Management SF: 06596075 URM-184033
Manual Locate job report stated Failed to get results for Z39.50 Locate Profile. This was fixed. - February 2023 Resource Management SF: 06569850 URM-183537
The Metadata Import job of type update inventory was stuck in finalization when the PO Line was not part of a PO or the PO Line did not have an invoice number populated. This was fixed. - February 2023 Resource Management SF: 06531604 06478093 URM-178773
The defined subfields in the profile for the MARC21 bibliographic 377 field is incorrect. This was fixed and the subfields are corrected to align with the Library of Congress. - February 2023 Resource Management SF: 06558656 URM-182199
KORMARC - The Korea government agency (38-39) dropdown field in 008 is missing some values. This was fixed and now all allowed values are displayed in the dropdown. - February 2023 Resource Management SF: 06548112 URM-182080
SBN Alignment - Scheduled job fails with no response from the server. This was fixed and the scheduled job now connects to the external system. - February 2023 Resource Management SF: 06620612 URM-185116
Alma - Z39.50 returned corrupted data in OPAC format. This was fixed by changing the customer parameter "rs_log_debug_enabled" to false. - February 2023 Physical Resource Management SF: 06257235 06336295 URM-168856
Alma displayed the wrong information in relinking item/holding notification message, the message was: Holdings: <the library name of the first Holding>: <location of the first Holding>; <Call Number of the first Holding> was deleted. This was fixed. The message now displays the correct information about the deleted Holding. - February 2023 Physical Resource Management SF: 06520548 06553060 URM-181633
The accession number configuration table is corrupted when the prefix of the sequence includes a special character. This is fixed and the table is no longer corrupted. - February 2023 Electronic Resource Management SF: 06424641 URM-126900
When the portfolio loader created local portfolios for portfolios not found in the Community Zone, the downloadable Actions report still displayed Localize and Activate in the Action column. This is fixed and it will now display Create local portfolio, to differentiate these portfolios from ones that are activated from the Community Zone. - February 2023 Electronic Resource Management SF: 06242982 URM-170718
When an institution is not using the functionality for limiting electronic inventory actions by library, some portfolios were automatically and incorrectly inheriting libraries from their collection. This was fixed. - February 2023 Electronic Resource Management SF: 06450644 06445135 URM-180730
Portfolio loader failed to load portfolios with ISBN that contain spaces in the uploaded file. This was fixed and files are now uploaded without error. - February 2023 Electronic Resource Management SF: 06377246 URM-180790
Portfolio > Edit > Attach to an electronic collection > Recently used button, the drop-down menu was cut off. This was fixed. - February 2023 Digital Resource Management SF: 06443353 06544588 URM-179762
After inputting the required information into the Alma Digital Uploader, no collections are listed even though collections exist in the PSB. This was fixed. - February 2023 Digital Resource Management SF: 05317185 URM-159754
The files of a representation were not displayed properly and could not be downloaded. This was fixed by upgrading the PDF viewer. - February 2023 Digital Resource Management SF: 06419740 URM-175956
In the Alma Viewer, for representations with multiple PDFs, selecting the Next File button did not move you to the next file in the representation. This was fixed. - February 2023 Digital Resource Management SF: 06411231 URM-176049
When PDFs were uploaded to Alma in bulk using a digital import profile, they were not displayed properly in the Alma Viewer. This was fixed, and now they are displayed properly. - February 2023 Digital Resource Management SF: 06464735 URM-180125
The following issues in the Universal Viewer were fixed:
• Could not copy embed code from the viewer to create an iframe in an external resource
• Zoom/position coordinates (xywh values) were missing from the URL (viewing position could not be captured by share link) • Could not load manifest to most IIIF viewers when pasting to prefixes - February 2023 Digital Resource Management SF: 06396152 URM-180303
Remote digital repository content embedded in the Alma Viewer was not displayed. This was fixed. - February 2023 Digital Resource Management SF: 06477247 URM-181428
When viewing a digital representation using the Waitlist feature, if a user pressed the Esc key when a session expired, the digital representation would continue to be available indefinitely and a number of concurrent users in excess of the access rights would be possible. This was fixed by disabling the Esc key. - February 2023 Digital Resource Management SF: 06545503 URM-181780
Some PDF files were displayed with a significantly lower resolution in the Universal Viewer compared to the Alma Viewer. This was fixed by increasing the default resolution from 0.7 to 1.0 to enhance image clarity. - February 2023 Digital Resource Management SF: 06572017 URM-183185
If a digital representation had an access right that prevents it from being downloaded, the text of the PDF could still be selected and copied using CTRL+C. This was fixed and now selecting text is disabled. - February 2023 Digital Resource Management SF: 06506760 URM-183742
A digital file was not displayed properly in the Alma Viewer. This was fixed by the PDF upgrade. - February 2023 Digital Resource Management SF: 06574114 URM-184445
Persian script in PDFs was not displayed properly. This was fixed by the PDF upgrade. - February 2023 Digital Resource Management SF: 06544588 06443353 URM-179762
After inputting the required information into the Alma Digital Uploader, no collections are listed even though they exist. This was fixed and collections are now displayed in the list. - February 2023 Acquisitions SF: 05314976 06213159 06560540 URM-149433
Advanced search for PO Lines by PO Status did not work correctly when a Vendor Code was also included in the search criteria or selected in a facet. This was fixed; searching by PO Status and Vendor Code now works correctly. This fix requires full indexing of PO lines in SOLR. - February 2023 Acquisitions SF: 06317573 URM-175543
Previously, performing a Receive action on a PO line for multiple copies of the same item caused all the items included in the PO line to be received, even if some of them had previously been received. As a result, previously received items that were on loan or in transit were "received" again, and the loan or transit status was cancelled. This was fixed. The Receive action now skips items in the PO line that were already received. - February 2023 Acquisitions SF: 06411162 URM-176429
Previously, if a PO line for a subscription was in the claims list because some of the issues in the subscription were not received by their expected dates, although other issues were already received, changing the expected dates of the issues that were not yet received to dates in the future did not remove the PO line from the claims list. This was fixed. When the expected dates of issues that were not yet received are all changed to be in the future, the PO line is removed from the claims list. - February 2023 Acquisitions SF: 06472470 URM-178213
Previously, the PO Line - Fiscal Period Rollover job failed when more than 1000 lines were processed by it. This issue was corrected as part of a reworking of the entire process, which has now been automated. - February 2023 Acquisitions SF: 06467159 URM-181899
Previously, if the fund for the next fiscal period was not created before the Rollover PO Lines job was run, the job added rows in the PO line‘s History tab with Net price 0.00 and List Price 0.00. This issue was corrected as part of a reworking of the entire process, which has now been automated. - February 2023 Acquisitions SF: 06508689 URM-180291
Previously, when the information in a vendor‘s EDI tab was changed, an error message appeared when the changes were saved (although the changes were, in fact, saved). This was fixed; an error message no longer appears when changes to a vendor‘s EDI information are saved. - February 2023 Acquisitions SF: 06357647 URM-172531
The EDI-Load Files process sometimes attached invoices to deleted vendor accounts. This process now only attaches invoices to active vendor accounts. - February 2023 Acquisitions SF: 06469156 URM-178128
Previously, when the Get Bib API was used at a Network Zone level with expand=e_avail, it only returned the AVE fields for the Network Zone, but not those for each member institution. This was fixed; the AVE fields are now returned both for the Network Zone and for all of the member institutions. - February 2023 Acquisitions SF: 06463693 URM-180350
When an electronic portfolio with a static URL was created in the Network Zone using the API, the link to the URL could not be opened from the Institution Zone unless the portfolio was first opened and saved in the portfolio editor. This issue was fixed; now a portfolio that is created using the API with a static link can be accessed immediately after it is created, as expected. - February 2023 Acquisitions SF: 06473890 URM-182593
The Get User Fines and Get User Fees APIs did not display the correct VAT amounts. This has been fixed; the VAT amounts are now displayed correctly. - February 2023 Acquisitions SF: 06486933 URM-180345
Previously, the Update Holding endpoint performed extremely slowly in some cases. This was fixed; the endpoint now functions at the expected speed. - February 2023 Acquisitions SF: 06442929 URM-177772
Previously, the MMS API for deleting bibliographic records from the Network Zone returned the generic INTERNAL_SERVER_ERROR error code when the Institution Zone had inventory for the same bibliographic record. Now, an error message that indicates the specific reason for the failure to delete the record is returned in this case. - February 2023 Administration and Infrastructure SF: 06518491 06518520 URM-182486
Previously, when the integration profile was configured with the Extended Fines and Fees extension, if a patron attempted to make a payment via SIP2 when no fees or fines were outstanding, a confusing error message was displayed. This message has been replaced with a No matching fee found message. - February 2023 Administration and Infrastructure SF: 06219258 URM-180368
SAML expiry mail is not sent to the address defined in the integration profile. This was fixed and the SAML certificate notifications are now sent to the defined contact email address. - February 2023 Administration and Infrastructure SF: 06054332 06601777 06590944 06507541 06498452 06511662 URM-167855
Printing more than one printout from the Printouts Queue didn‘ t operate well with some fonts. This was fixed and now the printing adheres to custom CSS styles. - February 2023 Administration and Infrastructure SF: 06254632 URM-166837
Exported Excel files were automatically formatted with a maximum column width of 100 pixels which was too wide for some screens. This was fixed by reducing the column width to 80 pixels. - February 2023 Administration and Infrastructure SF: 06433402 URM-181125
The Manage Patron Services / Recent button doesn't t display the recent search of users as expected. This was fixed. - February 2023 Administration and Infrastructure SF: 06603047 06612116 URM-185139
SFTP connection to BDS FTP server started failing after the latest upgrade of ftp.bdslive.com. This was fixed. - February 2023 Administration and Infrastructure SF: 06525046 URM-182690
Parts of the Update From Central Catalog job report were only in English. This was fixed and it will now be translated into the preferred language. - February 2023 Administration and Infrastructure SF: 06520653 URM-183442
License terms values are not translated when using the Catalan UI on Primo VE. This was fixed by adding the code table LicenseTermsPermittedProhibited to the TranslationData mapping table. - February 2023 Administration and Infrastructure SF: 06504057 URM-180128
When editing the Ex Libris system in the Resource Sharing integration profile, the selected schedule was not saved. This was fixed. - February 2023 Administration and Infrastructure SF: 06602162 URM-184040
Save itemized set in network jobs are running very slowly. This was fixed by removing the progress bar updating (the green indication that can be observed during the job run under the Monitor Jobs > Running tab), which caused this slowness. - February 2023 Administration and Infrastructure SF: 06528130 06533727 06574320 06403493 06052807 06272848 URM-163869
Digital files are not displayed properly by Web browsers. Additionally, the files are slow to load or do not load at all. This was fixed by upgrading the pdf.js to latest (v2.14.305) to resolve issues with PDF delivery. - February 2023 Administration and Infrastructure SF: 06260874 URM-167281
Alma Digital PDFs uploaded to PS