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.
108 results found
-
Open / Closed Stacks Request Possibilities Priority
Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.
In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.
We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item…
41 votes -
On Hold Shelf letter should display pick-up library rather than owning library
Currently, if a student places a request on a book from a different library to be picked up at their "home" library, the On Hold Shelf letter comes from the owning library with the owning library's branding, not from the pick-up location, which is what they are expecting. This is confusing to students because they are not expecting an email from a different library and often ignore it.
The On Hold Shelf letter email should have the pick-up library information/branding, not the owning library's information/branding.44 votes -
Show Additional ID under Manage Patron Services > Request
The Royal Danish Library has placed the pickup number in Additional ID. In order to have easy access to the number, we would like to see the number under Manage Patron Services / Requests. We would like to have an extra column (Additional ID)
30 votes -
XML Expansion for "Ful Resource Request Slip Letter" with Data about Reshelving Status and about Expected Date when Item will be Reshelved
For fetching requested media at the stacks we are making use of the "Ful Resource Request Slip Letter" in printed form which we customized according to our needs.
Unfortunately, the data fields that contain
- the information that the requested item might currently not be at the stacks because it has just been returned and is therefore very likely on its way back to the stacks (Status = awaiting_reshelving)
- and the information when the requested item is expected to be reshelved ("reshelving_time")
are not provided in the XML data of the "Full Resource Request Slip Letter".
This information, when be presented…
42 votes -
Enable 'School' address to be used for Personal Delivery
Currently, only addresses of the 'Home' and 'Office' Address Types can be used for Personal Delivery. Consequently, we can't use Personal Delivery and have to rely on a local workaround instead.
We would like to see 'School' addresses usable for Personal Delivery, with options in the Request Terms of Use to enable us to show only the Address Types that we use and therefore that we want our users to be able to see. E.g. we use 'Home' and 'School' but not 'Office', so we don't want our users to be able to choose that option.
Also, when the request…
13 votes -
No requesting when available items in institution
We would very much like there to be an option in Alma fulfillment units (On Shelf Request Policy): "No requesting when available items in institution".
The meaning of which would be that if there is at least one (requestable) item available at any holding, the user will not be able to make a title request. The system will consider all items in the institution, not just one holding at a time.
Currently we use the "No Requesting from available holding" option which means that when all (requestable) items on one holding are checked out, then the user can make a…
6 votes -
Add the ability to group select items in the 'Monitor Requests & Item Processes' view, the same as we can in 'Expired Holdshelf'
It would be useful to be able to group select items in the 'monitor requests and item processes' so that transit labels for them can be printed in bulk. Currently these have to be done individually per item. The ability to group select items already exists in the 'expired holdshelf' view so would (hopefully) be easy to implement
3 votes -
Not "Notify user" when canceling a "Patron physical item request"
In most situations we don’t want a request cancellation to be sent to users when we cancel a patron physical item request (Ful Cancel Request Letter). But since the checkbox “Notify user” is checked by default, the letter often gets sent by mistake, resulting in users thinking they will not receive the requested material, when in fact they will. We want the checkbox to be unchecked by default. Maybe this could be a configurable option in Alma (whether the checkbox is checked or not) so that each library can decide this for themselves?
6 votes -
Improve discoverability of rejected requests in the Monitor Requests page
We often have to locate cancelled patron physical and digitisation requests in the Monitor Requests page. However, these requests are difficult to locate as they can only be retrieved by Title (a non-unique field) and cannot be filtered or sorted.
Please add:
-A filter for request status which includes 'rejected'
-The ability to sort requests by date created or date updated so that recent rejected requests can be seen at the top of the page
-retain the requester id. The main search term we use to locate a rejected request is the requester name or id. However this is removed…12 votes -
Add Purchase Requests to blocked actions
We would like to prevent blocked users from submitting Purchase Requests. Although it is possible to ask Ex Libris to configure a blocked action for Resource Sharing Requests, it is not possible to do this for Purchase Requests. It would be useful to have a blocked action for Purchase Requests that we could use in Block Definitions.
5 votes -
restrict booking access
I would like the ability to restrict booking of equipment to certain subset of patrons. Right now, if Item is bookable, it is bookable for all patrons.
2 votes -
Sticky temp location in item record
We are running into a persistent problem, wherein our circulation staff will remove an item from a temporary location, however, while the radial button in the item record does switch from Yes to No the temporary location field sticks and doesn't re-set to blank. This is an issue with reporting. We are able to fix it by running a job but when circulation staff restore an item with a temp location, the temporary location field in the item record should also adjust to it's original status of blank instead of having the temporary location stick.
1 vote -
Show barcode field of requests in Manage Patron Services
Please add the ability to see the barcode of a requested item (where available) on the Requests tab of the Manage Patron Services screen. It is possible to see barcodes on the Monitor Requests & Item Processes screen but not this one.
1 vote -
Monitor Requests & Item Processes - Library Independence
It is possible to cancel processes at libraries that you do not have any role at using the Monitor Requests & Item Processes screen. A cancel button appears next to every request.
Patron physical item requests are correctly only visible based on your role but other processes such as work orders are visible and cancellable by all staff with access to the Monitor Requests & Item Processes page.
Visibility is not a problem as the data isn't private, but the ability to cancel a process should be limited by the scope of the role.
2 votes -
No request cancellation with change of item description
Actually it seems that Alma automatically cancels requests when there is a change of location (not the same FU rules anymore), of item policy (not the same TOU anymore) and a change of description (as this field is to be found in the request form).
For the latter, we would like to have a possibility to choose whether the request should be cancelled.101 votes -
Configurable hard coded date for request expiry
We've struggled with users not understanding the purpose of the 'Not needed after' date field in the various request forms linked to Primo VE. This often means we received requests with supplied 'Not needed after' dates of a few days later meaning they're cancelled before even being in transit or picked, particularly on unstaffed weekends. Relabelling the field hasn't helped matters due to users not paying attention to it and thinking it's a 'needed/collect on' mandatory date.
If possible we would like the ability to set a hard coded expiry range for non-processed requests. For example, if a recall request…
3 votes -
Change / improve the Booking process for staff and patrons
Hi all,
We wish to submit a proposal to change the current booking process for staff creating a booking request in Alma AND for patrons creating their own bookings in PRIMO VE.
Now, Alma’s option to submit ‘’ Booking ‘’ requests requires us to first search an item, select it and then enter booking times for each piece of equipment desired, which is very time consuming.
When patrons book equipment, they often need up to 10 or more pieces of equipment for the same booking period. This is quite inconvenient and increases the risk of mistakes in the process.
In…
19 votes -
Monitor Requests Workbench: export
When exporting (digitization) requests via the Monitor Request Workbench, we would like an overview containing also the specific request info (chapter title, pages...). The latter info can now only be obtained by manually clicking on "Edit" per request and this is only possible for active requests. For multiple digitization requests on 1 item, it is useful have all desired pages/titles exported in one overview for swift handling. Also for completed requests, it is valuable information to have all requested pages/titles in one overview.
Desired export:
- request ID + request info
- all requests (not only active)11 votes -
Ful Resource Request Slip Letter split in two
We would like the Ful Resource Request Slip Letter printout to split in two: one letter for staff when picking material from stacks, and one for use on the hold shelf for end users to see. These two functions are difficult to combine since staff need to know who the requester is at the same time as GDPR makes anonymization of the hold shelf slip necessary.
We currently try to solve this by using the Ful Hold Shelf Request Slip Letter as the hold shelf slip. But this printout is meant only for staff and so is printed in the…
3 votes -
ILL cancel/reject workflow - "Lender Reject Email Letter"
ILL workflow scenario of a library with several sublibraries.
- Step 1: The (central) Resource Sharing Department creates a fulfillment request to receive a book from a sublibrary (to be sent via interlibrary loan).
- Step 2: The sublibrary can not or will not send the book and therefore the sublibrary cancels the request. This also triggers a "Lender Reject Email Letter" to ILL partner.However, the fulfillment request cancellation form only provides these fields:
- Cancellation reason
- Cancellation noteBut a "Lender Reject Email Letter" needs the following fields:
- Reject reason
- Note to partnerThe "Cancellation…
33 votes
- Don't see your idea?