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.
157 results found
-
Badges for Resource Sharing
There are two Request Types in the patrons' list of Requests:
a. "Patron physical item request" which is used for regular requests and b. "Patron physical item request (resource sharing)" which is used for RS requests.
They are very similar and this is confusing for Fulfillment staff when checking Requests, especially when both types appear.
See attached file with two examples of requests: the first one is for Resource Sharing, and the second one is a regular request.
Proposed solutions:
1. We would like to suggest creating a new Resource Sharing Badge so that Fulfillment staff can clearly differentiate between…80 votes -
Add “Additional ID” as an option for the costumized view on the pages “Scan In Items” and “Manage Patron Services”
Today, when “Additional ID” is used as pickup number for borrowers picking up their hold requests, the librarian will not be able to see the Additional ID when scanning a book with a hold request on the “scan in item”-page. To see the "Additional ID", the librarian will need to enter the “Active Hold Shelf»-page.
This makes the process difficult for the librarian, when he or she needs to manually write the “Additional ID” on the pick up-slip that is placed in the book.
If “Additional ID” were added as an option for the costumized view on the “Scan In…164 votes -
Apply Automatic Convert to RS TOU when marking an item missing
When requested items are marked Missing, there are no more copies of that title, and there is a TOU term for the patron/item that allows Automatic Convert to Resource Sharing, the request should automatically convert to RS.
Currently, there is a TOU term of "Automatically convert to resource sharing," but this functionality is very limited to the use case of an expired pick from shelf item. ExL's documentation indicates this should be possible, but it is not -- when an item is marked missing, the request is automatically canceled, so any job that runs will not catch that the request…
37 votes -
Please add notification about blocks in Primo when requests are not allowed for the item or patron
This idea relates to Fulfillment configuration setting ‘Prevent Requests for Blocked Loans’ in the Alma May 2026 Release Notes (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/080General/Configuring_Fulfillment_Jobs#block_request_if_not_loanable):
In our Sandbox we changed the parameter key ‘blockrequestifnotloanable’ from NONE to PHYSICAL, which indeed activates a block when a pratron is not eligible to request an item. But now we see that in Primo the Patron is not informed about the reason for the block, so he/she gets lost.
Please add a setting that shows the user a specific notification about blocks in Primo when requests are not allowed for the item or patron…6 votes -
Limit title level request fulfillment to items from holding records without descriptions or items without descriptions
Current Problematic Functionality: Physical item requests (holds) are placed at the title level (any item from any holding record attached to the bibliographic record will be used to fill the hold) when a holding record has no items with descriptions. Requests are placed at the item level (the exact item requested will be used to fill the hold) when a holding record has one or more items with a description. As a result, if a user places a request on an item attached to a holding record with no description, but there exists on the bibliographic record a second holding…
18 votes -
NOTIFICATION TO CIRCULATION DESK REQUEST CANCELED BY USER AT HIS PRIMO PROFILE
We want that the Circulation-Desk receive a notification letter when the user cancel their requests at their Primo profile. The cancelled reason is Cancelled at patron request. Our institution have two branches, one in Madrid and other in Alcalá de Henares, when the user choice an item located in Alcalá de Henares, he can pick up in a Reading Room in Madrid, but when he did the request and did not change the room to Madrid. So they receive the notification letter that the request will be available in Alcalá de Henares and inmediatily they cancelled the request and made…
13 votes -
Option to mark Home Delivery addresses added during requests as "Preferred"
Most of our patrons do not have a pre-registered address in their records, so we rely heavily on the Home Delivery option in Primo VE, which allows users to provide their address directly during the request process. While this feature is highly valued by our patrons, it presents a significant operational issue because these addresses are not automatically marked as "Preferred" in Alma. Consequently, this information does not appear on the patron’s activity page and, more critically, it cannot be retrieved within the Analytics Fulfillment subject area, where only preferred addresses are accessible for reporting.
To resolve this, we request…
21 votes -
Pop-up window with information about blocks and reader's fees when create a request
It would be helpful if, when filling out the user request form in Alma, a pop-up window with information about the users's blocks and financial obligations appeared when their card number was entered.
A pop-up window exactly like the one that opens when you open a patron's account using the “Manage Patron Services” option.This solution would allow the users to be immediately informed of their obligations and avoid being sent from one station to another.
For example: In our library, fines can only be paid at the station on the ground floor. If the employee at that desk orders…
21 votes -
Prevent items to be loaned immediately when they are returned at a SIP2 Self check machine and have a Rapido personal delivery request
When a loaned item is returned at a SIP2 Self check machine and has a Rapido personal delivery request, the item is automatically loaned to the patron (and sorted to a request bin). Requested items then are scanned in at a circulation desk for further processing. In case of a personal delivery request, the item is immediately returned and marked for reshelving. Librarians do not see that there was a request (and a short loan).
Previously we handled personal delivery requests via a GetIt request. The effect was the same, but we were able to prevent this behaviour by de-selecting…
45 votes -
Have multiple pickup locations available in Primo when requesting items from the same library
Our wish is to be able to offer several pickup locations in Primo for the same library when documents are available for loan (not linked to a reading room desk) without having to create a new virtual library. The library must be able to configure the visibility of these pickup locations based on certain user criteria (e.g., user group).
For example, a library may offer a special room whose access is reserved for teachers and doctoral students. The library would like doctoral students/teachers to be able to choose this room as their pickup location at the time of the request…
30 votes -
Monitor request page
Currently on the Monitor requests page for the Activity status filter there are the following options:
Completed; Active, All. It would be useful to have the option that filters requests with status Rejected83 votes -
Keep patron physical requests active even if “deliver to” relationships are temporarily interrupted
Our consortia has several libraries connected through “deliver to” relationships, allowing patrons to request and pick up physical items from different sites.
Currently, when these relationships are interrupted — for example, due to maintenance, or temporary closures — all related patron requests are automatically cancelled, and patrons receive cancellation notifications. That makes them angry.
We would like Alma to preserve these requests in an active or pending state during such interruptions, so they can be fulfilled automatically once the relationship is restored, without requiring patrons to place new requests.
This would improve the user experience and reduce administrative workload for…
33 votes -
Allow prioritization of item requests based on library proximity and capacity
In our consortium, several libraries are linked through relationships. However, these libraries differ in distance, staffing levels, and delivery times.
We would like Alma to provide a way to prioritize the fulfillment of requests based on configurable criteria such as library proximity, staff availability, or delivery speed (as actual transit time rules are not efficient enough).
This enhancement would enable the system to route requests for multiple available items to the most suitable library — ideally the closest or best staffed — thereby streamlining daily operations and improving service efficiency across the consortium.22 votes -
Request from pickup in different library only - not working when the item is on loan or in trasit
One our library has a library box which they want to use as primary location for pickup for physical item requests. I created a new library for the box, I set the apropriate relationships between the library and the box. I also created special Fulfillment Unit where I selected the option "Request from pickup in different library only" as on shelf request policy. But the setting "Request from pickup in different library only" is working only in case when the item is not on loan or in transit. When the item is on loan or in transit and other patron…
6 votes -
Add "Send Query to Patron" option to Digitization requests menu
Currently there is not option to ask the patron about a current Digitization request. These requests are often submitted with little or vague information and a way to contact the patron for clarification is needed. The "Send Query to Patron" option for this purpose is included under "the ellipses" for Resource Sharing requests. Why does it not appear for Digitization?
59 votes -
Add "Process Date" facet to Resource Request Monitoring
For some library processes, the Process Date is a more useful facet than Request Date when there is a need to identify newer vs. older processes. For example, an item currently in transit may have a Request Date from months ago when it was requested by a user, whereas the Process Date is the value that tells us how long the item has been in transit.
When using Resource Request Monitoring to identify items that have been in transit the longest, it would be very helpful to have the ability to facet by Process Date in the same way we…
6 votes -
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.
5 votes -
Add a Remediation Status/Step to the Digitization Workflow
Alma's digitization process has no built-in status or step for accessibility remediation before a digitization request is delivered to a patron. Alma customers adhering to WCAG 2.1 AA under Title II ADA compliance for document delivery have no internal way to flag, route, or track items that need remediation (e.g., OCR correction, tagging, reading order) before fulfillment.
We'd like to see a dedicated "Remediation" status added to the digitization workflow, allowing staff to route an item for accessibility review before it's marked complete and delivered. This would let Alma customers track remediation volume and turnaround time via Analytics and support…
1 vote -
No automatic cancelling of request when changing item location (or a more useful error message).
When we change location for an item we always get an error message that says that the change can lead to requests being cancelled (if there are any). But since it always shows, even when there are no request (which is most of the time in our experience), it is easy to ignore.
We would like to be able to choose if a request should be cancelled or not, even if the new location shouldn’t allow requests for the user.
Another possibility is that that the error message only shows when it is relevant and there actually are requests that…19 votes -
separate work orders from patron requests
On the results from a physical titles search, each title shows the number of requests pending for that title. This number includes both patron physical item requests and internal work orders. In order to see what requests fall into which category, you have to click on the Requests link and wait for the information to load in the slider pane (this can take some time if the number of requests is large). Then you can filter by request/process type.
It would be useful for these two categories of requests to be separated from each other. For example, we circulate laptops…54 votes
- Don't see your idea?