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.
28 results found
-
From my assigned purchase requests, allow selection of multiple requests to be assigned to someone. Doing it line by line is cumbersome.
From my Assigned Purchase Requests, allow assigning multiple requests at once to someone else. Going in line by line is cumbersome.
3 votes -
Mass deletion of purchase requests
Purchase requests can be mass rejected but cannot be mass deleted after that, so they need to be deleted individually, which is frustrating and time-consuming.
2 votes -
Automatically assign purchase requests to certain users
There needs to be a way to automatically assign purchase requests to a certain staff member. I'm thinking specifically in the case of citations that come to Alma from Leganto, but I'm sure there are other instances. It makes much more sense to designate a specific person(s) who these requests should go straight to rather than having them go to an unassigned queue and the staff member(s) having to sift through it and manually assign things to themself.
1 vote -
Excel - Allow personalization of the fields to be export
Our proposal, is to allow include bibliographics fields to the excel archive.
In order to manage the purchase requests, we need an excel archive that iclude fields like ISBN, edition, year, ...1 vote -
Analytics: Add Purchase Request Requester user information at the time of request
The Purchase Request Subject Area Purchase Request Requester user information is updated every day by ETL to the current user information.
In many cases, this is useful. But it is not useful for reporting when it is important to know the information of a user at the time of an action.
As one example: We would like to report on the number of patrons submitting purchase requests by user group such as undergrads vs postgrads vs staff. If a patron submits a purchase request as an undergrad and then becomes a postgraduate, the outcome of current analytics is that all…1 vote -
Make Approved Purchase Requests Editable
It would be very helpful if it was possible to edit Purchase Requests which have been approved. Our purchase requests default to 'electronic' material type, but if the electronic version of the requested item is unavailable and we need to order print copies instead, and the staff dealing with the request forget to change the material type before clicking on 'Approve and order', this means an order is created with the wrong material type and there is no way to fix this retrospectively. It would save us a lot of rework if it was possible to change the material type…
1 vote -
Add Course Information within Purchase Request to PO Line
It would be very helpful if the details within the 'course information' section of a purchase request fed through to the POL and was visible within the 'Notes' tab of the POL. This would enable staff dealing with the orders to have all the required information in one place and would also make the audit trail more robust.
1 vote -
Letter for purchase requests initially approved and finally canceled
Sometimes it happens that a user's purchase request is initially approved by the acquisitions staff and sent to the vendor, but sometimes it ends up being canceled for some reason.
Prior to this cancellation, when this request is sent to the provider, the POL generated in Alma remains in "sent" status. Prior to this cancellation, when this request is sent to the provider, the POL generated in Alma remains in "sent" status. Then it will be manually canceled.
We request the creation of a letter in which the user is informed of this circumstance. Together with this, we request that…0 votes
- Don't see your idea?