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.
1744 results found
-
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…
9 votes -
Subject headings's in Analytics
"Subjects" in analytics (6XX MARC fields) are all jumbled up in one index. This creates a problem for analysis of correctly applied LCSH subject headings (our focus). AND, 2nd indicator signifies the type of subject heading, such as LCSH "0"; NLM "2"; etc. Currently, working with the subject index, it is impossible to filter for the type of subject heading needed in an analytics report, even though the MARC variable fields contain this data. Therefore, it would be very useful to filter for the types of subject headings we would like to see in a report, without losing recall (i.e,…
1 vote -
Fee block: automatic blocking and unblocking
The following configuration is desired:
A fee block should be set automatically once a freely selectable fee amount has been reached and after a freely selectable period of time.
- Once the fee has been paid, the block should be automatically deleted.
Reason for automatic fee blocking:
The fee limit that can be configured in Alma only refers to the maximum fee amount that may be reached, but not to the period in which a fee must be paid, regardless of the amount of the fee.Reason for automatic unblocking:
Fees can be paid at any time, especially after the planned…1 vote -
Add more fields under Customize view in the Physical item search: Provenance, Physical condition
We would appreciate it if more fields from an item could be displayed in the results list of a Physical item search:
- Provenance
- Physical conditionE.g. if you run a Physical item search for 'Physical condition' is not empty it would be great to have this field in the results list and in the Excel export file as well.
We always prefer a search in Alma to an Analytics query with the data from the previous day.Thanks!
Does anyone else need an additional field?
6 votes -
System Events Subject Area: Add "Record was Created", "Record was Updated", "Record was Deleted" for Holdings PIDs
Currently, the System Event subject area does not track the creation, update, or deletion of holdings records. Adding this functionality would provide valuable insight into how often these actions are performed by staff. This data would support performance reporting and make it also easier to identify the number of modified records when metadata corrections are needed.
2 votes -
Augment the X-Exl-Api-Remaining header to include the threshold figure
The Alma API includes the X-Exl-Api-Remaining header in responses, e.g.:
X-Exl-Api-Remaining: 192522
It would be helpful if the value for this header additionally included the threshold figure, a.k.a, the total number of requests, e.g.
X-Exl-Api-Remaining: 192522,200000
In the above example, the threshold is 200'000.
This would allow external monitoring scripts to dynamically determine the percentage of requests used for the day. Currently determining this has to based on a static threshold manually added to the script, and would need a script update if the threshold changes (due to an increase or decrease in the number of user licences).
Alternatively the…
1 vote -
Change pickup location for hold when on hold shelf
When a book is already on the hold shelf at Library A but a patron wants to pick it up at Library B instead, we should be able to edit the request to make that change.
Currently, the hold must be cancelled and then re-requested with the new pick-up location. This can be an issue in the event there is another request on the item or the item needs to go back to a different library.
2 votes -
Allow Dynamic Fields (e.g., Current Date) in the Subject Line of Email
Hi Team,
Currently, the Borrowing Activity Letter subject line is controlled entirely by a label provided by Alma, rather than through the XSL template. Because labels only support static text, it is not possible to use dynamic values—such as the current date—in the subject line.
This creates a limitation for institutions that send periodic Borrowing Activity summaries. Many libraries want to include a date (e.g., "Your Borrowing Summary – March 10 2026") so that patrons can easily distinguish one report from another. However, because Alma does not evaluate XSL or variables in label-based subject fields, dynamic values cannot be used.…1 vote -
Support linking Analytics Subject Areas Requests and Fulfillment
As analytics users, we would like to link request information to loan information in Analytics so that we can obtain a better picture of the entire end-to-end loan process for a patron, from request to loan.
For example, the Fulfillment subject area could contain fields such as:
- Loan is based on a prior request (True/False)
- Originating Request IDSimilarly, the Requests subject area could contain these fields:
- Request resulted in a loan (True/False)
- Resulting Loan ID7 votes -
Add an API endpoint to send email via Alma
Library Open Workflows support sending email using the Alma Mail node, but this uses an internal API that is not usable outside of LOW. It would be really useful if this could be made generally available so that other applications and scripts integrated with Alma could benefit from sending emails through the Alma mail setup instead of having to configure email separately via SMTP, etc with all the resulting spam-filtering issues.
4 votes -
Request expiration date in Analytics
We are trying to retrieve a list of items that are about to expire on our holdshelf but it looks like the Request Expiration Date is not available in the Requests subject area in Analytics. We were expecting it to be in the Request Details section.
Of course, the holdshelf is just a specific case, limited to patron physical item requests, but this idea can be extended to any other request type in which an expiration date is meaningful.
23 votes -
Quick Links and Keyboard Shortcuts in the Metadata Editor for Enhance the Record Normalization Processes
As a cataloger, I want to create quick links and keyboard shortcuts for normalization processes in the metadata editor, instead of selecting them via "Enhance the record", so that I can work more efficiently.
4 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 -
Support CID: resource_sharing_request_id in Letters
The Internal Identifier (XML resourcesharingrequestid) is the required file name for the batch automatic delivery of digital lending requests via the Automatically Ship Rapido Digital Requests job. The Internal Identifier is 17 characters. Supporting CID: resourcesharingrequestid within print slip letters XSL would allow the Internal Identifier to be scanned by a barcode scanner during the digitization workflow of physical materials instead of an operator manually typing in a 17 character identifier which increases errors and is time consuming.
3 votes -
New URL for psychotherapy.net
www.psychotherapy.net is now library.psychotherapy.net. Please change the URL in all collections to ensure access. Example:
Psychotherapy.net Full
Collection ID: 615450000000000871
MMS ID: 9917875822400041
Thanks in advance and kind regards,
Pascal Hauenstein1 vote -
Post Alert when import job reaches Manual Handling Required
Please add an alert to the Real-Time Notifications list, targeted to users with privileges for running import profiles, when an import job is paused with the status "Manual Handling Required."
Import profiles run manually or on a schedule may reach a paused state with status Manual Handling Required, commonly for multiple matched records that require merges, and sometimes with validation errors. Because these jobs don't run to completion, they don't appear on job history. Because these jobs are paused, they don't appear in the list of running jobs. If a user is not aware that the job is paused, import…
7 votes -
Display access model in All-titles basic search results
When you are performing a market search, the access model shows up on the holdings records if they are either attached to the POL or have been manually added to the record. This is incredibly useful and time-saving for searching! When doing an All-titles search, you have to click into the record in order to access that information. This line for access model can be easily added to the listed metadata in the All-titles results page. See attached screenshot
4 votes -
Allow merge rules for authority import profiles
It would be very useful allowing custom merge rules in Alma authority import profiles for ensure controlled, automated updates of authority records,
especially in a cooperative cataloguing environment.
Configuring these rules to selectively merge, keep, or add specific MARC fields during import, would ensure enhancing data quality for both local
and network zones.12 votes -
"Interface name" field separate from Vendor records
Have an option for the "Interface name" field in local electronic collections to be independent of Vendor records. Our vendor records are itegrated with multiple systems outside of Alma (such as our HR software, Workday). We would like to use the "Interface name" field for display purposes/logic, and possibly reporting in Analytics, but we're limited with it only be populated by Vendor records.
4 votes -
l.burns@hw.ac.uk
isc Collections AIP American Institute of Physics 2024-2025-2026 Extension
Can you please let me know when this will be added to Alma to allow activation.
Thank you.
Lynn Burns1 vote
- Don't see your idea?