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.
89 results found
-
Please add more "View only" roles to Alma
Alma already offers some "View only" roles:
- Fund-Ledger Viewer
- License Viewer
- Course Reserves Viewer
but there is still a need for more.Please add the following:
- Invoice Viewer
- Purchasing Viewer
- Physical Inventory ViewerThanks!
115 votes -
Automatically Trim Leading and Trailing Spaces in Patron Names
When staff create or edit patron records, Alma currently accepts leading or trailing spaces in the first name and last name fields. These spaces make the name technically unique, so the duplicate warning mechanism does not recognize the record as a duplicate. This results in poor data quality, as duplicate records are created without warning.
Proposed enhancement:
• Automatically remove any leading or trailing spaces in the first name and last name fields when a patron record is created or updated.
• Alternatively, prevent staff from entering leading or trailing spaces in these fields from the beginning.This enhancement would…
24 votes -
Protecting Additional Identifiers from the SIS loader
We receive patron information from multiple sources and files. When we run our SIS sync to add and update patrons, it removes all of the additional identifiers on the account because those come from another file. This results in us needing to overlay additional identifiers using a separate process. We would like to have the ability to protect the additional identifier fields from the SIS sync .
19 votes -
Any change to a role, or addition of a role, or replacement of a role, should be called out in release notes in a separate (or additional) s
Any change to a role, or addition of a role, or replacement of a role, should be called out in release notes in a separate (or additional) section of the release notes.
The reason for this need: Larger institutions have large numbers of Alma using staff to manage, oftentimes including student workers. It is important for Alma system administrators to have prompt awareness of changes to roles in order to make any necessary changes to staff accounts, profiles, etc. in order to maintain the security and integrity of patron data, cataloging data, norm rules, and the like.
Having changes of…
12 votes -
Preferred email address and system messages
If a user account has no preferred email address, no letters will be sent to this user. It is possible to save a user account without preferred email, and I guess that some libraries need to be able to save email addresses without having one that is preferred. But at Uppsala university we need better messages from the system about this, otherwise some users will have no preferred email and consequently get no letters from the library.
When changing an email address, the user account is saved in two steps. First through the button "Save Email" directly after the change,…
9 votes -
Show more details about Work orders in user roles
When work orders are attached to circulation desks, the details of the work order cannot be edited.
This leads to a problem with maintaining roles, since the work order only shows its associated circulation desk. It is impossible to see from the user record what work order is associated with that user, making it difficult to add or remove desired work orders.
If the role parameters could show at least the Code, then that would provide useful information. This would be useful both in the user role view and the preset user profiles.
This idea was generated because my support…
25 votes -
Add more information to the Couse tab on the user profile I Alma
The course tab only provides information about the course code and course section.
If you, like in our case, have a non-descriptive course code containing only numbers you have zero information about what the course is.If a user has multiple courses and you need to remove a course with name *** you have to look up every course to identify which course code is the one you need to delete.
The following columns should be added: Name, start date, end date, Year, Term, academic department, faculty/school – and make them sortable.
2 votes -
Patron last activity date updated by leganto use in Alma.
Leganto use is an important information of use. A patron could have zero library use but use leganto and be assigned to multiple courses.
The information is highly relevant for purging users – if you want to purge inactive users there is no way to known if there is leganto activity – and leganto activity is an important reason to not purge a user as library activity is.
1 vote -
Enable sending of emails to non-preferred email addresses
Currently, when contacting users using the Update/Notify Users job in conjunction with the User Notifications Letter, the process will only send to the preferred email address in the patron record. For our former students whose patron records have expired in Alma, this means that the notifications go to their student email address to which they no longer have access.
To contact our former students once their Alma account has expired in line with university IT regulations, we have to take their unique identifier out of Alma and contact them using a separate external system. This entails a lot of extra…
6 votes -
Field in the user record to serve as flag for anonymization
Create a field in the user record to indicate whether or not to include the patron in anonymization jobs based on their own choices. Ideally, this field can be controlled by the patron directly in their Primo account and we wouldn't need to manage custom forms or customize feeds from SIS systems to manage this. While user groups can be deployed to serve this purpose, for most institutions this is not the desired approach because of the complexities involved.
3 votes -
Remove block type from Update/Notify Users job
Currently in the Update/Notify User job you can add a block type for a set of users but you cannot remove a block type as you can for other parameters. e.g., add role/remove role.
Instead you only have the option to disable a block type which leaves behind an inactive block that may not be needed and which is marked as external data and locked, meaning you have to toggle the record to open to then manually delete one by one.
Therefore it would be useful to have an additional remove block types parameter so we can then remove in…
3 votes -
Retain loosing accounts identifier in all IZ and NZ after a merge
After merging two accounts the primary identifier of the loser account can only be found in those IZs via the search in which it was also merged manually. In such cases, the message that the two accounts have been merged is added to the Notes of the winner account; including the primary identifier of the loser account.
We think this information should appear in the NZ as well as in all other IZs so that it can be tracked which accounts have been merged. This is important, for example, in cases where fines and fees in Alma have been closed,…25 votes -
Update expiration on roles in bulk
We expire the roles for our student workers each semester, since they don't always come back to us after breaks. It would be nice if there was a way to update the expiration date of selected roles in bulk. I can see the benefit of having granularity of control on individual roles, like if someone's job function was changing after a certain point, but that's not a common scenario. It would be a lot easier if we could change a selection of them all at once, on both the user management screen and in the profile configurations. Even if I'm…
4 votes -
More options to limit access to private patron information for student employees
Some libraries hire students as part-time staff at the circulation desks or helpdesks. Per the institution or library policies, for privacy reasons, student employees may not be allowed to search for Alma users or to view the contact details of staff members or other student users.
Currently, access to contact details and searching for users are by default possible to any Alma user with Fulfillment roles. Disabling the ALLOW-USERS-SEARCH privilege can prevent access to users list in Manage Patron Services and auto-complete search in same page, but it does not affect the persistent search for users or access to Admin…
86 votes -
Death of a patron - Need to immediately and permanently cease sending all letters
In the unfortunate event that we learn that a patron passes away, we need a quick, clear, and finite procedure to immediately and permanently cease/stop any and all IZ and NZ notifications to the patron's email account, especially those that are tied to a SIS load (Example: Banner). College administration directs the library to ensure no emails are sent to the deceased's email account. We need to be able to definitively state to college administrators "Absolutely zero communications, automated or manually generated, will be sent regarding the deceased patron's library account from the IZ or NZ."
Existing work-arounds include toggling…
44 votes -
Flag an alert when a purge date falls earlier than an expiry date
A colleague has raised the point that currently when editing and saving a user record, if the purge date precedes the expiry date no alert is raised. This means if the purge date is adjusted and is set before the expiry in error, nothing alerts the user to this fact.
Would it be possible to have a an alert either in the form of a message or sidebar error alert to make the operator aware of the data issue when saving the changes?
8 votes -
Add Job Category to Staff Login Report
Add the Job category column to the Staff Login Report to facilitate the management of professional accounts
28 votes -
Option to remove Alma roles if staff not logged in for X days/months
Having an option to remove Alma roles if staff not logged in for X days/months will help automate the process of identifying and managing inactive accounts, saving administrative time.
We have a lot of staff that change job roles within the institution, but end up keeping their Alma roles unless someone tells us they are leaving the library department. Obviously this idea won't fix all the problems, but it would certainly help with reducing the risk of unauthorized access - particularly for any one that has an administrator role
3 votes -
Allow access to "Roles Privileges" configuration for General System Administrator
Allow access to "Roles Privileges" configuration for General System Administrator
Ex Libris staff have the ability to remove specific privileges from Alma roles via the "Roles Privileges" configuration (User Management - Roles and Registration - Roles Privileges)
Since roles in Alma are not very fine-grained, and roles often grant access to groups of privileges that shouldn't necessarily be granted as a set, it would be very helpful for customers to have access to the "Roles Privileges" configuration.
Ideally we would have the ability to make edits ourselves, but Read-Only access would also be valuable, because it would allow us to:
- …
67 votes -
Requests Operator role in a profile
When you set "requests operator" role in a profile, the Scope and Circulation Desk are mandatory.
It'll be better not to record scope and circulation desk in the profile so they can be set when using the profile.
Currently if you want to set the scope on another library than the one defined in the profile, you have to suppress the circulation desk, then change the scope, then set the circulation desk.3 votes
- Don't see your idea?