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.
1746 results found
-
Make patron info updateable in Primo flag more granular
Currently the only control on allowing patrons to update info via Primo is either on or off:
http://screencast.com/t/kcSIvkkR3gWould like the ability to say for example only Visitors user group can update info via Primo.
18 votes -
Automatically Associate Certain Payment Methods (e.g., Credit, JV, Deposit) with Prepaid Functionality when Creating Invoices
We would like the ability to automatically associate certain Payment Methods (Credit Card, JV (Correction), Deposit Account, etc.) with Prepaid functionality when creating Invoices. 1) This would save time. 2) Most institutions do not want certain payment methods going to their ERP, but occasionally forget to check the Prepaid box. Setting this up systematically would serve as a fail-safe for such situations.
14 votes -
Add a new privilege to the "Purchasing Operator" role which will prevent users with this role from being able to delete items
This Idea was submitted by ExLibris to check the community support for the following enhancemnet:
Currently, users with "Purchasing Operator" role can delete items, the existing logic behind this is, when a PO line is created (even before it is received), there is a need for the Purchasing Operator to be able to delete the item in case of an error on the order.This Idea suggest to add a new privilege to the Purchasing Operator role which will prevent this user from being able to delete items - the new privilege should be enabled by default to maintain existing…
0 votes -
Physical PO line creation - allow the interested user defined on the PO line to place a title level request when the PO line is created
This idea was submitted by Ex Libris to evaluate the need for the enhancement specified below:
Today, when a physical PO line has an interested uset, a hold request is not created on the bibliographic title until the book is scanned in at a circulation desk (Item is received).
Customer rely on being able to see all requests on a title from the moment it is purchased. This is because they want both users and staff to be able to see the whole physical request queue from the moment a book is purchased, currently it creates uncertainties about who is…0 votes -
Allow the existing configuration of the user form to apply also on the "Vendors > Contact People tab > Add Contact" page
This idea was opened by Ex Libris to see how the community supports it.
There is an existing configuration for the user form which was added in August 2022: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2022/Alma_2022_Release_Notes#Configure_the_User_Form
Please have this configuration apply also when creating a new vendor "Contact" (Vendors > Contact People tab > Add Contact).
For example, if an institution selected that some fields should not appear in the user creation form, these field should also not appear in the vendor contact creation form.
0 votes -
From 'view vendor' list in POL, add '+' capability to Add Vendor?
Right now one has to either search vendor before order entry, or gamble that the vendor is already in the database and just try entering the POL. But then, if the vendor is NOT in the database, one has to back all the way out, add the vendor, and then start over.
It would be great to have an 'add vendor record' link right there, with a 'back' button to finish the POL in progress, That would really minimize workflow interruptions during the POL entry process. Might others find this helpful? If you hate stopping, navving somewhere else in…
0 votes
- Don't see your idea?