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.
112 results found
-
Make 'requester' clickable after 'scan in items' step of handling a request
It would be convenient if it was possible to click on the requester after the 'scan in items' step when managing a request.
320 votesWhen scanning in a requested item, the requester name appears. There will be a link to the requester’s user record if the logged in user has priveleges to access the user edit form
-
Increase the visibility of digitization requests in case of multiple requests
When there is more than one digitization request on a same item (same or different requesters), only the first request is displayed in the Task List. When this request is completed, the second request is not listed in the Task List or in the “In Process Items” page, except when the barcode is scanned again.
We think that “In process Item” page should not be empty once the first request is completed. Or least, there should be an alert informing the operator that there is another request on the same item just ready to be fulfilled...
313 votesWe’re looking at adding an indication in the Manage In Process Items next to a request where there are more digitization requests for the same item in the queue. A row action will allow the staff to complete the current active request and activate the next.
-
Initiate consortium fulfillment requests for items in another institution from Alma
In our consortium, we would like to be able to place requests for items in other institutions on behalf of our patrons in Alma.
Scenario: a patron (dean, faculty member, etc) calls the circulation desk asking if an item is owned by the library. Circ operator searches Alma and finds the item in a consortium library. Circ operator SHOULD be able to request item in Alma from the patron's record. Right now, circ operator has to tell the patron to search Primo and request on his or her own.
268 votes -
Work Orders: package of required enhancements
Work orders are useful but often cumbersome and don't work as required. A package of enhancements/fixes would make them much more useful and useable:
• Adding notes when creating work orders in bulk. This would enable having fewer work order types as explanatory notes could be used instead.
• Makes notes more (immediately) visible when scanning in (pop up message?). Again would enable fewer work order types as items could be easily catergorised according to explanatory note upon receipt at managing department.
• Select recall/not recall at work order placement (like pick from shelf), not baked into type (and in…231 votes -
Add the ability to batch change the expiry date of items on the hold shelf
It can be useful to manipulate the Expiry date of items on the hold shelf. However you have to do this per item. It would be good to be able to batch update all items due to expire in a given period to a new value.
176 votes -
Add more flexibility in Request TOU Pickup Locations policy
We’d like more flexibility in Request TOU Pickup Locations policy.
We have more than 20 libraries and most of them are located within walking distance. Therefore, we want our patrons to go directly to those libraries instead of placing pickup requests and limit the patrons who can place such requests. Otherwise, the number of requests will become too large to handle and logistics and management cost will become enormous. Moreover, it’s not time efficient. If users go directly, they can borrow immediately, but it may take 1-2 days to deliver since there is no direct route between some libraries.
Currently,…
162 votes -
Consultation in Alma FF
There is no easy solution in Alma FF to indicate that an item has been consulted in the library and that it can be reshelved.
When items are placed on the hold shelf and are briefly consulted in the library, there is no easy way to directly reshelve them in Alma FF. The workarounds are far from ideal and are very labour-intensive when facing a large amount of physical requests: cancel the request (but this is not correct and influences our request statistics) and reshelve via the expired hold shelf, update the expiry date to yesterday (but this requires a…
159 votes -
Configurable item lists
In the several item lists we need to display several columns. In the item list "Item - in department" we need for instance columns for the item fields.
In the different lists something else should be displayed.
There for the different work steps different displays are needed.It would be best to configure which columns per list we would like to see. Thereby we need more fields from the Physical Item Editor (or for other editors) that we can configure for display in the list.
155 votes -
On-shelf requests for specific user groups
We have limited human resource for picking up the items for on-shelf requests. Therefore, we hope this service is only available for patrons in need, for example, disabled patrons or distinguished professors/researchers.
Therefore, we need Alma to support “specific user groups’ to “request for on-shelf items”, and “pick up in different library/campus only”. It would also be nice if we can limit the number of on-shelf requests in a period of time.
This will definitely help librarians to provide precise service efficiently!
146 votes -
Request letter
We would like to be able to send a user a notification about a request immediately after placing the request. The notice would give basic information about the status of the request. Something along the lines of the "interested in" letter. Running a request report once a day is insufficient for our operations.
144 votes -
Alternative Call Number in Manage Patron Services-Requests
In Manage Patron Services, tab Requests, we can’t display or add Alternative Call Number.
For us is important the visibility of this field due to it’s our location system.
We would like this field to be displayed.Thanks!
129 votes -
Expired Hold Shelf to Alma mobile
It would be practical to get the Expired Hold Shelf lists to Alma mobile so we didn't have to print them on paper.
128 votes -
Enhanced “In Transit” flow/functionality
We encounter a lack of important functionality to efficiently follow-up on In transit requests (physical item requests to another pick-up location). We would like the functionality to be extended with the following additional features:
1. A patron facing letter when the requested item is placed “in transit” by the owning library, so that the patron is better informed of the status of his request.
We want to create a situation that once a requested item is being transported, there is in fact no way back and a fee needs to paid.
2. To make it impossible for patrons to…122 votes -
More humanity in the letters: add the name of librarians who take care of the requests
Automatic processes in Alma make library staff save time and efforts, but also significantly reduce human interactions with patrons (very few emails are personally sent by librarians to patrons). Lots of Alma letters sent to patrons are nameless and only signed by generic service names like "Acquisitions Department", "Circulation Desk", "Library ABC" etc. (see @@department@@ in the Labels). Some staff members suffer from this dehumanization in the processes.
We want to give a name and a face to a request when patrons get notified and would like to enrich some Alma letters with the name of the librarian who took…
118 votes -
Provide multiple hold pickup options within a single Alma library
We'd like to provide, within a single Alma library, the following pickup location/delivery options to our users: locker, circulation desk, or mail to home. At present, this is only possible through the creation of additional libraries.
116 votes -
Add block action for patron digitization requests in User Block Definitions
The configurable blocked actions for user blocks in Alma are:
01 – loan
02 – loan, renew
03 – loan, renew, holdIt is therefore possible to configure that blocked users are not allowed to place requests at all.
We propose a distinction between the different request types in blocked actions.
Blocked users should be able to place hold requests, as it can be checked at the latest at the time of loaning whether there is a block, and users then have to take care of the unblocking (e.g. by paying fees) in order to be able to loan the…
115 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 -
Digitization Requests - remove 'next step' from process
When managing Digitization Requests after 'Scan In', there is an obligatory 'Next Step' which has to be selected before getting the option to 'Attach documents' (and get the status from 'Digitization' to 'Document delivery'). Is it possible to remove this 'next step' from the Digitization process?
99 votes -
Alma bookings - concurrent bookings issue
Our institution wants to introduce bookings in Alma for our High Demand loans, which are 3 hours.
The main issue we’ve found is concurrent bookings, see scenarios below, with a 5 minute exclusion set up:
• A books item for 11:40-12:40 - however doesn’t borrow the item within the 5 minute exclusion
• B books item at 11:46, for 11:50-12.50
• A checks out item at 11:53, despite booking for B at 11:50
What is needed is some mechanism for bookings to expire automatically once the exclusion period is reached.
88 votes -
Allow each items’ request policy with specific parameters (location, keyword etc.) to be excluded from the title-level request policy
I believe this is an expansion on this idea https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/31119715-title-level-request-and-item-level-request
But we are dealing with ASRS in our case so I thought it might be a little more elaborate.
We would like to have the option to allow each items’ request policy with specific parameters (location, keyword etc.) to be excluded from the title-level request policy.
Currently we have "No requesting" as our general policy that's applied to all of our items except for the ones in ASRS. The problem is that when items with multiple copies and identical call number exist both at open-stack library and ASRS, the No…
83 votes
- Don't see your idea?