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.
121 results found
-
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.80 votes -
Skip Location for Lending Requests
For "patron physical item requests", there is an option called "Skip location". We use this option when we don't have the requested material available at our campus library, but another of our campus libraries does. In these cases, when we click on the "Skip location"-button, the request gets automatically transferred to a library which has the material available.
We would like to have a similar "Skip location"-function for lending requests. Today we have to manually transfer the lending requests between our campus libraries, if we don't have the material available at the library which originally got the request. A "Skip…
1 vote -
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 -
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?
7 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 -
Time stamp on printed Resource Request Slip Letter and Hold Shelf Request Letters
Add the time stamp to Resource Request Slip Letter and on Hold Shelf Request letters when printed.
1 vote -
Configuration option to prevent Digitization request when item is on loan.
Issue: Digitization requests are typically needed “ASAP” by our users. When an item is on loan, we don’t want to recall it as it will typically take longer than the requester can wait.
Current configuration options:
When Configuring Loan Recall Requests and the following is set to “Yes” PHYSICALTODIGITIZATION - Patron digitization request for physical resource, the item will be recalled. When set to “No” the item will not be recalled, instead a hold is placed on the item.Need: A configuration option for digitization requests that does not recall or place a hold(prevent renewal) on items that…
2 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 -
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 -
Make requests for multi-volume works fulfillable at location scanned in
Hi there,
If patrons submit a request for a multi-volume work at the holdings level, only the circulation desk for the Library where the volume is held can see the 'existing holdings requests may be fulfillable by scanned in item' message when the requested volume is scanned in.
We would like all circulation desks to be able to see this message and had the option to attach the item to the request at the holdings record.
Our use case is that we have many items held at offsite storage, which is set up as a Library in Alma but is…6 votes -
Include the workflow step status of a "pick from shelf" request in the API
If a "pick from shelf" request is created in Alma, it initially has the workflow step status "new". After printing the Resource Request Slip Letter, the workflow step status switches to "in process", showing that the request is now being fulfilled (meaning an employee is now picking the item from the shelf).
If this difference was included in the API call, it could be used by a discovery system to enable patrons to cancel a request only if the Resource Request Slip Letter has not yet been printed. Thus, patrons could cancel "new" requests, but not those that are "in…
6 votes -
Stop Change Due Date from overriding hold request
There's an issue we're having where changing the due date of a loan allows the current owner to extend their checkout time, even after a hold request has been placed. We have Alma configured so that it prevents a renewal from occuring, but change due date seems to ignore that function.
1 vote -
Generate item-level request for reading room materials
Currently, if there is one copy of an item in general stacks and another in a reading room location, assuming both are available, Alma will prioritize the stacks copy for requests and the request form will be based on the stacks request TOU. Some institutions use reading rooms for Special Collections materials, so the items may not be interchangeable and if a patron requests the reading room copy, we want the request to be specific to that item and the form to follow the reading room request TOU (limiting the pickup location).
Giving the items unique descriptions forces item-level requests,…
4 votes -
Alma to automatically process pending requests when recalls are switched back on
During Easter and Christmas vacation we turn off recalls in Alma, so requests are still placed by the user but recalls are not made. After the vacation, we turn recalls back on however Alma does not 'catch up/update' the pending requests into a recall.
We would like Alma to therefore be able to process those requests in pending and turn them into recalls once the recalls have been switched back on.
3 votes -
When cancelling requests from the pick list, display a warning message
On the pick list, requests are displayed at a title level. This means it is possible that multiple requests are present for the title. When clicking 'cancel request' from the title, all requests are cancelled, not only the first one. Since this behaviour occurs even when requests are from different requesters, for different volumes or different digitisations, we would like a warning message to appear before deleting multiple requests from this screen.
1 vote -
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 -
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…
41 votes -
User Requests Should Pop or Be more Visible for Cataloguers
When cataloguers are processing new books or fixing bibliographic records or item records, there is no notification that a user has requested the item we are working on. We won't know to give the item to Fullfillment so that they can put the item aside for the user.
I know there is a little number that indicates there is a request, but for new books ordered in there is already 1 request from Acquisitions. This does not pop-up and it is just a little number that you can barely see in the results screen. It should be much more obvious…
3 votes -
Adding a physical holdings drop down to the request brief result would help in person enquiries.
Case - Currently, when a user requests an item. If the user then comes to the libary and asks a college librarian to update them about how long before the item is ready to collect. If they search for the request and no item has been return that can fulfill the request. It takes 2/3 extra clicks to go via the 'view title in search' and find out the current availability of the items within that record.
Solution - It would better if it was possible to click on a drop down of all physical holdings on that bibliographic record…1 vote -
Ability to edit request priorities
We would like the ability to edit, i.e. rename or translate, the names of the request priorities in the Manual priority drop-down menu in the request queue. It is not entirely obvious which to choose, and we would like to be able to eg. number them from 1. to 8. It was suggested to us by Ex Libris support that we promote this question through Idea Exchange.
3 votes
- Don't see your idea?