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.
1773 results found
-
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.
3 votes -
Encumbered Balance Amounts only link to unpaid purchase order lines
In the Summary Details of an allocated fund code, there are hyperlinked amounts listed next to Expended Balance and Encumbered Balance. We want the Encumbered Balance amount to link through to only purchase order lines that make up the total balance amount listed in the hyperlink.
Currently it links through to any purchase order line that had an encumbrance placed on it with this allocated fund code. Regardless of whether the purchase order line has already been expended and disencumbered or still has an outstanding encumbrance waiting to expend on it.
This would be helpful as it would give us…
4 votes -
Expose Shared License, Distribution, and Negotiation Details in the license REST API
The Alma license REST API (POST/PUT/GET /almaws/v1/acq/licenses) does not expose several pieces of license configuration that are available in the Alma UI. This prevents end-to-end license provisioning via API and forces manual UI work after every API call.
Fields currently absent from the API:
At the top of the License Details form — the "Shared License" on/off setting, and the "Distribution" multi-select controlling which sections are shared with member institutions (Summary, License Terms, Notes, Attachments).
In the Negotiation Details tab that appears for shared licenses — per-member rows containing Member Name, Price per year, Price increase (percentage), Currency, Start date,…
10 votes -
Enable Full MARC 21 Format for Holdings Data (MFHD) Editing in the Metadata Editor
We request that the Alma Metadata Editor (MDE) be updated to allow direct MARC-level editing for all fields in a Holdings Record as defined by the MARC 21 Format for Holdings Data (MFHD).
In the library industry, a "Holdings Record" is a unified data carrier. It includes the shelving location (852), but also other copy-specific fields such as donor (541), the provenance (561), and the individual item details (876-878). In the MARC standard, the "Holdings" and the "Item" are part of the same metadata record.
While we recognize that Alma’s underlying architecture treats “Items” as child entities of “Holdings”, the…
3 votes -
Temporary Location Status
Alma temporary location due dates are informational only; adding configurable alerts or automated actions when those dates expire would reduce manual monitoring and improve location accuracy.
1 vote -
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.
3 votes -
Add an "OA articles only" option to coverage tab in electronic portfolios.
Several autoholdings collections for journals include titles with OA content even if there is no active subscription, meaning that our only access to the journal is for the OA content. This makes it hard to provide accurate coverage information to our patrons. While we can add a public note as a workaround, it would be nice if there was an "OA only" option (maybe a checkbox) on the Coverage tab for electronic portfolios.
6 votes -
Be able to see the full email message when using Send email to partner or Send query to patron
Currently we cannot see the full context of these email messages, we only see the “body” of the email, but that does not include any pre-set text or the greeting and signature.
Staff are left guessing what information is included in the full message, and the sent messages often look poorly composed and unprofessional. It is inconvenient and time consuming to find the templates to check the complete message before sending. Knowing what the full message looks like at the moment of writing, would help staff decide exactly what to write in the email
Message.5 votes -
Be able to see the full email message when using Send email to partner or Send query to patron
Currently we cannot see the full context of these email messages, we only see the “body” of the email, but that does not include any pre-set text or the greeting and signature.
Staff are left guessing what information is included in the full message, and the sent messages often look poorly composed and unprofessional. It is inconvenient and time consuming to find the templates to check the complete message before sending. Knowing what the full message looks like at the moment of writing, would help staff decide exactly what to write in the email Message.
3 votes -
Be able to cancel, or reject, a request that is updated as shipped in error
Sometimes lenders update a request as shipped in error. Once we have confirmed with the partner that we will never receive that item, we should be able to either cancel the request, or reject it so it moves on to another partner. Currently we can only “receive” and “return”, but that creates incorrect analytics reports.
3 votes -
Add Resource Sharing partner address information to Alma Analytics
Information should include street, city, state, zip code, country, and latitude and longitude. This information is essential for creating reports showing where ILL items are coming from or going to. This would enable us to create reports showing how much borrowing and lending we do by regions, internationally, and make it possible to create maps that we can use to promote our services to patrons, library staff and university administration.
6 votes -
Request for Enhancement of the "Patron Physical Item Request" Function
We would like to request an enhancement regarding the "Patron Physical Item Request" function.
Currently, Alma recommends using the "Patron Physical Item Request" function at the title level, and customer institutions are also using the function in the same way.
When a purchase request is made, notifications for item arrival and hold requests for interested users are also processed at the title level. As a result, when multiple items (e.g., volumes/issues) are ordered under a single title, even if several items are received by the library through that order, interested users receive a notification indicating that only one item has…6 votes -
Allow cross-use of MARC21 authority fields 500 and 510
Alma currently enforces strict validation rules that restrict the use of fields 500 and 510 based on the type of authorized heading (100 vs. 110), preventing cross-usage and triggering validation alerts.
However, in real cataloguing practice (including MARC21 examples and records from the National Library of Spain), it is both common and necessary to establish relationships between different types of authorities (personal ↔ corporate) using 5XX fields. For example, a 110 record may include 500 fields linking to persons, and a 100 record may include 510 fields linking to corporate bodies.
This restriction limits the accurate representation of relationships such…95 votes -
Package different Acquisition Types in one PO
Our library receives invoices that include a mix of line items—some with associated bibliographic records and others that are payment only (non cataloged). For non cataloged items, we create suppressed purchase order lines (POLs) using the Technical acquisition type with manual packaging. For cataloged items on the same invoice, we use the Vendor Payment acquisition type.
As a result, a single invoice often requires multiple acquisition types. Currently, Alma does not allow different acquisition types to be packaged together during PO creation. Instead, we must create the PO first and then manually add Technical acquisition lines afterward, which adds unnecessary…3 votes -
Job of SUSHI Harvesting should report standard SUSHI exceptions
At the moment when running a SUSHI harvesting job, the job reports as successfull without further notice even if the vendor sends the report with an exception as described in the COUNTER API standards: https://countermetrics.stoplight.io/docs/counter-sushi-api/7ccbfsfe7nrev-exception
Example:
Alma is asked to download reports for the following timespan: begindate=2025-01-01&enddate=2025-09-30
The vendor sends the JSON file containing
"Exceptions":[{"Code":3032,"Message":"Usage No Longer Available for Requested Dates","Data":"Usage no longer retained for the following yearmonths(s): 202501, 202502, 202503, 202504, 202505, 202506, 202507, 202508, 202509"}]The Alma job closes as successfull. The months in question are marked as completed.
Expected behaviour:
Alma should either report the…3 votes -
Allow ERP Job to Fail Gracefully Without Updating Invoice Status
Occasionally, the ERP job “ERP export using profile Export Invoices for Payment PA” fails when it is unable to connect to the configured FTP destination. In these cases, invoices that are in the status “Waiting to be sent” are still updated to “Closed”, even though the export did not successfully complete.
This behavior creates a significant issue, as invoices are effectively marked as processed without actually being transmitted to the external system. As a result, staff must manually identify and correct these records, which is time-consuming and introduces risk of error.
It would be highly beneficial if Alma handled this…
3 votes -
Feature Request for Individual Interlibrary Loan Requests
We would like to request a functional enhancement regarding individual borrowing requests in the following menu:
[Alma > Fulfillment > Resource Sharing > Borrowing Requests]
When a user at an Alma customer institution (e.g., a university library) submits a KERIS interlibrary loan (ILL) request via the library website, the request is received in the Alma menu above. In such cases, the staff in charge of resource sharing must separately submit the request through WILL (the KERIS interlibrary loan system).At this stage, the staff would like to send a notification email to the user confirming that the interlibrary loan request…
6 votes -
Compare All Institutions in the NZ
The Network Zone can be made more useful if it were possible to use it to quickly compare institutions by setting. A common time consuming task is to check to see which institutions have one setting or another configured and which do not. To accomplish this currently, it is necessary to either log in to each institution and click around or log in to the NZ and then using the drop down to choose an institution and click around. Either way, staff need to open up all the institutions.
Alternatively, it would be great if, for configurations that lend themselves…
44 votes -
It's great that Ex Libris values user feedback
It's great that Ex Libris values user feedback! I love contributing ideas. Speaking of escapes, sometimes I need a little mental break. Anyone else Play Escape Road 3 free https://escaperoad-3.com when they need to de-stress? It's a fun, quick game!
1 vote -
Make explicit exchange rates editable
Our exchange rates are updated quarterly by our institution. Rather than having to delete them and recreate them every time, we should be able to edit them.
3 votes
- Don't see your idea?