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
-
Pick from Shelf, sort by title
Hello,
Currently our Pick from Shelf has 4 options to sort the titles:
Location Name- Asc
Location Name - Desc
Call Number - Asc
Call Number - DescI would like to see the titles sorted into alphabetical order.
Thanks!
3 votes -
Current loaned item borrower user group as parameter in terms of use
Sometimes we need to restrict requests based on the group of the user that has the item currently borrowed, not only the group of the user that is trying to request.
This is particularly useful when you have items loaned to a user for an specific loan period (sometimes even for months or years) and you want to avoid users to request that item loaned to that specific user group but allow them to request items currently loaned to other user groups.
Take teachers and students for an example. You would like students to be able to request items currently…
3 votes -
List the "Pick from Shelf" list, "Monitor Requests and item processes" and results from a "Requests" search in order from latest to oldest
We would find it helpful if it were possible to view requests (both active and complete) in order from latest to older without the need to export and filter
3 votes -
Allow Request Notes to be edited even with complex Fulfilment Rules
We introduced Fulfillment Rules to check if there are any "Process Types" assigned to an item and make them unrequestable. For example if an item is MISSING, REQUESTED, LOST, LOANED, etc.
This allows an item without a process type to be requested fine. Unfortunately, the moment you try to edit the Request Note and update the request, it ends up rechecking the Fulfillment rules and oddly cancels the request.
We were hoping we can use the edit Request Note process to mark items when our library officers have done 1st/2nd/3rd shelf searching of items before they become officially marked as…
3 votes -
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 -
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 -
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 -
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 -
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 -
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 -
Physical Item Hold Requests
Multi site library - prevent users from placing a physical item hold request on items that are available on the shelf of the library they are placing the hold request from - if the item is not available on the shelf but a copy is available at a different location then placing a physical item hold request should be allowed.
2 votes -
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 -
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 -
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 -
Permanent physical location for items in process
We have found that when working through items in process/Monitor physical item requests that the permanent location is not included when exporting to Excel. This is very inconvenient when a staff member is trying to locate the item.
1 vote -
patron names
Could the Patron name be displayed in the "Pick Up Request " window in Alma just as the 'Requestors Note". This saves time instead of having to click to find the name of the requestor.
1 vote -
Prevent placing different request types on the same item
Currently in Alma there is no cross check and no way to prevent a patron from placing both a Physical Item Request and the Digitization Request on a single item. The Ex Libris expectation is that requests will be reconciled through the request queues. However this adds additional time to the request process as it requires contacting the requester to confirm which type of request they need. I encountered the lack of a preventive configuration created a concrete clash as it came to our attention when a patron placed both types of requests on an item. This impacted 3 locations…
1 vote -
1 vote
-
Alternative work order behavior - Usage should be departmental, not individual
We would like an alternative to how work orders work now. We want the department (or “agent”) to initiate the request, rather than an individual using their own personal account. So that usage is calculated as “departmental” or work order, rather than the individual.
1 vote -
Allow customization of the Notify User check box in Confirm Request Cancellation box.
Current default is that this item is checked, however with local processes, we would prefer not to automatically notify the patron in most circumstances. It would be better for us to opt-in than to opt-out.
1 vote
- Don't see your idea?