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.
27 results found
-
View only administrator role
The administrator role may be helpful to get a full overview of the configuration and possibilities of Alma. However, this role can have far-reaching consequences and should not be given to anyone.
A "View only" administrator role would be helpful for local Alma project group members to get access to the whole config, with no risk of modifying/deleting the configuration.22 votes -
Provide clear indication on failed "Primo Login Using Email"
"Primo Login Using Email" is a recently added feature in Alma to manage users that weren't in any external IdP. Alma would not need to manage password for those users and send them a one-time link to login to Primo. However, I discover that there are problems with the implementation of Email Login. When patron account has blocks that wouldn't allow them to log in, e.g. expired, Alma just simply not generate any email. It won't even give patron any error message like "login failed". It leaves patrons wondering why they did not receive any email. Ex Libris should add…
3 votes -
Resource Sharing library field as mandatory for user records
We would like to configure Resource Sharing library field as mandatory for (at least public) user records by having a "Resource Sharing Library" line in the drop-down in Public/Staff User Mandatory Fields table.
Additionally, it could also be interesting to allow creating user registration rules for the "Resource Sharing Library" field.18 votes -
Remove notices from patron accounts
We try so hard to anonymize. It would be nice to be able to purge patron "attachments" after a certain amount of time.
96 votes -
3 votes
The February 2017 Release includes this idea. For more details please see here:
-
Existing linked accounts need active lookup to update patron expiration date
In a consortium with shared circulation policies and privileges, linked accounts need an active lookup each time they are used so that expiration dates that may have changed since a user record was first brought into an institution other than their own, can be updated to ensure a user is still entitled to privileges at another institution.
We understand that the Alma Roadmap includes plans to bring blocks through on linked accounts using a network level block, but expiration dates are also important once a linked account is already created and is used again.
33 votes -
View history of patron record
We'd like to be able to view the history of a patron record. This would help with troubleshooting problems with updates from our SIS and also investigating problems with circulation.
2 votes
- Don't see your idea?