Alma
Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
139 results found
-
Add “Report to Ex Libris” Option to Failed Scheduled Alma Jobs
Scheduled Alma jobs that end with errors do not currently provide a built-in “Report to Ex Libris” option. Reporting such issues requires opening a support case manually and copying information from the job report.
Idea: Extend the existing “Report to Ex Libris” functionality (available at the portfolio level) to scheduled Alma job reports.
For scheduled jobs that end with Error or Failed status, allow users to open a reporting screen, pre-filled with the relevant job details (Job ID, process ID, error message).
Benefit: Provides a consistent reporting experience for recurring system jobs and improves accuracy of job-related support cases.167 votes -
Reading Lists in the Task List Customise Alma task list (tasks requiring your attention) to match all our reading list statuses
As Acquisitions & Reading Lists Manager I would like to customise the Alma task list (tasks requiring your attention) to help the reading list team manage the reading list workflow as using facets is a time-consuming long way round to find the list categories each time.
Alma task list (tasks requiring your attention), section Reading lists, we would like to customise this list of tasks or add all reading list statuses each Library may have.
We have reading lists with status other than Unassigned - processing, complete, reading for processing.
We have 'updated' and 'core done' to help us manage…
68 votes -
Please get rid of the message notifications that pop up in the top right corner telling people what they just did.
These inhibit workflow. The collapse-by-default feature is extremely slow, the pop-ups block the tool bar and need to be manually removed before I can continue with my workflow. If there are reasons why people feel this feature needs to be kept, could it please at least be an optional feature that we can turn off? Thanks.
14 votes -
Improve cookies on Alma and other Clarivate sites
Alma-specific:
* Re-configure the OneTrust settings so that performance cookies default to off
* Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
* Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)Clarivate-wide:
* Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off,…25 votes -
Add function to monitor broken display logic rules
When the name of a collection/interface/service used in a rule changes the rule quietly breaks. The only way in Alma to find out it's broken is to open the specific rule in edit mode, where it says "not listed" next to the changed collection/interface/service. There is no indication in the list of rules and you are not notified when a rule breaks. We have a long list of rules in use so it's difficult to keep track of the broken rules. It would be useful to be notified when a rule breaks or to have a way of monitoring broken…
56 votes -
Sync Tasks widget display groups to match the user-selected display groups under Customize Tasks List
Currently the persistent menu Tasks function and the home page Tasks widget do not sync to display only the groups the user has selected. This leads to the Tasks widget being cluttered with information not relevant to the user and distracts from the groups they need to pay attention to.
In an academic library environment, staff members often have specialized roles (e.g., an Electronic Resources Librarian who does not need to see Fulfillment or Resource Sharing task categories). When unchecked sections continue to display, it creates unnecessary UI clutter, forces users to scroll more than necessary, and reduces the overall…
16 votes -
Have libraries' open hours as configured in Alma display in Primo or embeddable in library home pages.
We would like to display the open hours, closed exceptions, etc. that are already configured in Alma in the Primo landing page and have them able to be embedded on a library web page. That way if hours change for holidays, seasons, etc. they will be correctly shown in all locations without having to change posted hours in multiple places.
13 votes -
Alma Split View Hides Main Menu, Affecting Cloud App Access
After rolling out the new UI for the “All Titles Search” with split-view functionality, the main menu is no longer persistent. The menu (which contains location, notifications, cloud apps, etc.) disappears when entering split view.
This is particularly problematic for institutions that frequently use cloud apps in their workflows—for example, when editing physical items. While cloud apps can be pinned before entering split view, this workaround is not satisfactory. Pinning apps adds unnecessary clicks and is easy to forget, resulting in frequent toggling in and out of split view.
As a consequence, many staff members have stopped using cloud apps…
36 votes -
Securing Alma access by two factor authentication (2FA) in combination with time-based one-time passwords (TOTP)
2FA and TOTP are common and standard methods for securing access to IT systems. These concepts should be implemented in order to secure access to Alma also. A respective implementation should replace the multi-factor authentication currently implemented in Alma since it lacks security for at least the following reasons:
- Sending a link by email is insecure since email hardly can be viewed as a secure transport medium.
- Using email for transferring a second factor hardly allows to keep the second factor as being independent from the device on which Alma access takes place.
- The link which is…171 votes -
Output MARCXML file (over 8GB size) from Publication Profile compress into .tar.bz2
By default, the publication profile for an XML file is compressed into a .tar.gz file. We host the exported file on our FTP server so that it can be downloaded from the BNE website. If the file exceeds 8 GB, it is not compressed. Our IT staff have informed us that compression to .tar.bz2 makes the file even smaller. We propose that, in addition to .tar.gz, it should also be possible to compress MARCXML files using the .tar.bz2 extension.
7 votes -
Display Requester's Name in Interlibrary Loan (ILL) Request Details
We would like to request an enhancement so that the requester's name (Ful outgoing email letter-code: %reqName%) is displayed together with the Request ID in the request details when submitting an Interlibrary Loan (ILL) request to another institution.
Currently, the receiving library can only view the Request ID. Since each institution uses its own ID format and structure, the receiving library cannot identify the requester based on the ID alone or access the corresponding user information.
Displaying the requester's name along with the Request ID would allow the receiving library to identify the requester more accurately, improving the efficiency and…
3 votes -
Add and improve audit logging and system event tracking for changes to Alma configuration
Many institutions have needs and requirements to be able to track when Alma configurations change, and who changed them.
This is especially true because many Alma "administrator" roles combine complex librarian tasks with systems configuration abilities. For example, Catalog Administrator or General Systems Administrator is required to create new metadata import profiles - a task that catalogers need to do regularly. But, both roles also grant additional abilities to configure Alma behavior for resource management,
integrations and the like.Use cases include:
Monitoring changes as part of standard internal audit review. For example, an institution may identify that even though…
144 votes -
Request for Enhancement: ALMA Records Customization Functionality
Currently, the Records Customization feature in Alma only allows for configuring the visibility and order of fields, but does not support modifying the structure or composition of individual fields.
We would like to request an enhancement that enables institutions to customize the structure of each field according to their needs.
For example, the Creator and Imprint information are currently displayed as a single combined field. We would like these to be separated so that institutions can independently select and display only the elements they require.
3 votes -
Folders in "Manage sets"
We would like the option to make folders in "manage sets". This would make it easier for different depatmants to navigate through the public sets of the institution.
46 votes -
Library/location creation date and creator information
I think it could be useful to be able to view when a library/location was created and who it was created by.
3 votes -
Add Ownership Transfer Capability for Sets in Alma UI and APIs
As a Repository Manager, I want the ability to transfer ownership of sets between users so that institutional workflows, integrations, and operational processes can continue uninterrupted when staff responsibilities change.
In Alma, all users can create logical and itemized sets, but Repository Managers are responsible for overseeing and maintaining the broader set ecosystem across the institution. Repository Managers can already view all sets and delete sets created by other users, but they currently cannot reassign ownership of sets between users.
This creates operational challenges when staff leave the institution, responsibilities shift between departments, or integrations and scheduled workflows depend on…
3 votes -
The ability to share private jobs/sets individually without going public.
It would be very helpful to be able to share sets with specific individuals or with members of a particular department, without making them fully public. This would be especially useful when testing sets or presenting work to a supervisor or department head.
2 votes -
Pin POL notes to top of list
Context: when acquisition staff view POLs, there are some notes that are important to see, and other notes that are less important. However the only sorting options for POL notes are by created or updated date.
Proposal: users need the ability to pin one (or more) notes to the top of the list of POL notes, so the important notes are always easily viewable.125 votes -
Adding an entry (as a brief) in quick cataloging for a reserve item.
When working on reserves and adding a quick cataloging entry, make 'institution' the default for the placement of the new record. If you overlook that network is already selected for you, you cannot go back and change it to institution when completed. You have to remove that entry and start all over again. Another option would be to give the choice of either institution or network so that you have to choose one or the other.
1 vote -
Alma - Standardize Cross-Field Validation Across Configuration Dialogs
Request:
Implement dynamic dependency handling within Alma "Add Row" dialog boxes to support Proactive Error Prevention.The interface should only present users with valid input field combinations, ensuring that logically impossible configurations cannot be constructed.
While this request originated from a ticket regarding the Exclude Process Types from Publishing dialog, it identifies a broader need for platform-wide consistency in how Alma handles field relationships.
Functional Gap:
Currently, the "Exclude Process Types from Publishing" dialog treats [Process Type] and [In Process Type] as independent fields.The Problem: Users can construct combinations that the system knows are invalid.
The Result: The user…
2 votes
- Don't see your idea?