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.
1755 results found
-
Clone PO LInes to order again
We create different PO Lines for the same order. We need to put different funds, different reporting codes or order more items.
There is no way to clone the PO Line as a way to keep all information and just edit the fields that we have to update.
We need to clone and put the clone in review to edit the fields we need to change and send it to the vendor.
24 votes -
API allow quantity for pricing in POL creation
We use the adquisitions API to duplicate POLs. When we are creating a new POLs based on a existing ones.
We get the original POLs json and we make some changes on it to send it again in order to create a new one.
If the POL has more than one items to be ordered (quanity for pricing field), the api ignore it and put always a 1.
The problem is that the Alma make some calculations with the amount field and the fun percentage changes, so the POL amount increases and is not the correct amount.In order to…
4 votes -
Adding newly registered patrons to the 'Recent patrons'-list
Being able to see patrons entered in a session is very useful, but it would be great if the recent list also included new patrons registered during the session.
Often times, patrons for instance request registration before they find the books they want to borrow. If we could easily access their patron services page when they return with them, it would streamline the process.
3 votes -
Access Student Photos Securely
Currently, user photos are only available via a web link https://myurl/photo/studentidentifier.jpg. This means that all student photos need to be available over the internet which in the UK is a Data Breach. There needs to be a way that only the student in question or an authorised staff member can see the photo. It is not possible to use 3rd party software like Azure to do this as the cross-site scripting protection gets in the way.
1 vote -
Include "On Hold Expiration Date" to "Physical Items"
Please include the "On Hold Expiration Date" from the Alma Physical Items Search to the Analytics field "Physical Items"
To elaborate upon why this is needed:
A title was ordered on February 8th. The "Hold Shelf expiration date" is set for February 23rd. According to the terms of use, 10 working days are correctly taken into account. However, the "Days on Hold Shelf" value displays 14 days, as weekends and holidays are included in this calculation. This discrepancy naturally makes it difficult to rely on, as the number of weekends and holidays within the pickup period may vary. We need…
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 -
user - add option for dynamic purge date - e.g. 12 months after expiration date
Right now the purge date is a static value manually inserted when registering a new user. When the user renews registration, purge date must also be manually updated.
In our library regulations we'd like to purge users after a specific amount of time after expiry date. Keeping purge dates manually up to date is however quite an error prone procedure.
It would be great to have the chance to automatically update the value in purge date when saving according to specific a timespan (e.g. 10 months or 10 years after expiration date).110 votes -
Add flags to tabs in vendor interface record area
We noticed the little corner/flag is not changing on the vendor interface details tabs when we add administrative information/access information/statistics information. We thought it would show like the notes tab with a dark corner when we enter information so we know that we have stuff in these tabs. We thought it was a glitch, so we reported to Ex Libris. They said it is by design:
The answer is that it is by design. The little corner flag is an indicator that there is system or user generated content like populated tables or lists. It doesn't indicate that form data…3 votes -
Recent Material suppliers in drop-down
Currently, when creating new orders in Alma staff users don't get a list of the most recent Material suppliers but only an alphabetical list of all of them.
It would be useful to see 1-2 most recent suppliers in the drop-down in order to gain some time when acquiring multiple books from the same suppliers.2 votes -
Homepage Notifications Order adjustable
It would be great if you could change the order of the homepage notifications. This option is already available in many areas.
3 votes -
Add Patron Limit threshold block for number of lost items
It should be possible to automatically block users based on a set threshold for the number of items they have checked out that are in a lost status.
Currently, the Patron Limits table only contains delinquency threshold blocks for Max Overdues, Max Cash, and Max Overdue Recalls.
Not all institutions automatically charge a lost item replacement fine for lost materials. For some lost items, the replacement cost may be below the Max Cash block threshold for the user’s user group, but the library would still like the user to be accountable for/aware of their lost status materials; being unable to…
61 votes -
Link POLs to EDI invoice lines using Identifier field
When loading EDI invoices from a vendor that do not include POL information, use the Alma Identifier field (usually the ISBN) to match the EDI invoice line to the POL.
2 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…
5 votes -
Loan due date should appear in Facets and/or Analytics
It should be possible to the the actual Loan Due Date given to the patron, in addition to the Due Date given by the Lender in Facets.
It should also be possible to retrieve a list of such RS requests by Loan Due Date via Analytics.1 vote -
Data visualization to include export to Excel/CSV function
Currently users without Design analytic role can use Data visualization(DV) reports but they can only export report in PDF, powerpoint. It would be very useful to have an export of data in Excel or CSV.
3 votes -
MMS ID and Keyword searching of existing RS requests
It should be possible to search existing RS requests (Borrowing and Lending) by MMS ID and Keywords using the dropdown menu.
1 vote -
Invoice templates
Allow a template so if I'm invoicing dozens of orders in a row for one vendor I don't need to go through a bunch of drop down menus every time- Just one vendor, default account, same invoice date, pre-paid, with a credit card, etc.
5 votes -
Add Financial System Code to the Vendor Dimension of Alma Analytics in the Funds Expenditure SA
The Financial System Code field is often the matchpoint between Alma and external payments systems. Being able to search or query on this would help avoid creating duplicate vendors, especially as vendor names can change so much over time, that a vendor name search will not return results. Having this reportable in Alma Analytics would be more beneficial than in the Alma Advanced Search, as it could also help to de-duplicate existing instances of having more than one vendor record for the same vendor.
25 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 -
Allow Alma to export preferred names to ILLiad when automatically creating ILLiad user records
When Alma automatically created an ILLiad user record for someone who has submitted a resource sharing request that must be exported to ILLiad, it always passes the First Name and Last Name fields to ILLiad even if the user's records contains a Preferred First Name and/or Preferred Last Name. It would be incredibly helpful if Alma could pass preferred names to ILLiad if the user's record contains any preferred names.
35 votes
- Don't see your idea?