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.
146 results found
-
bulk deletion of attachment
It would be very useful to be able bulk delete or archive-off a Patron's attachments, regardless of the retention period settings.
2 votes -
Linking Proxy and Sponsor accounts
In our library, we create a separate library account for every Proxy, in addition to their personal account.
We want the Proxy and Sponsor accounts to be linked to each other so that all loans made by a Proxy on behalf of a Sponsor will automatically be registered on both accounts.
In addition, all requests placed by a Proxy on behalf of a Sponsor should be loanable on the Sponsor's account without the need of deleting the request/s from the Proxy's account.Since many Sponsors have more than one Proxy )sometimes up to 10), we would like a Proxies/Sponsor tab…
10 votes -
Merge roles and scopes when assigning two profiles to one user
The paradigm, or model, that we chose for role assignment was to group roles into profiles named for departments. Our profiles have names like Tech Serv Manager Profile, Pub Serv Staff Profile, etc.
Linda Hall Library has three circ desks. Managers have been given roles which allow them to operate at the appropriate desks (Pub Serv Manager Profile has Circulation Desk Operator configured for Courtesy Desk and Main Circ and Rare Books Manager Profile has Circulation Desk Operator configured for Main Circ and Rare Book Room Circ). Similarly, we have two different work order departments, and managers' roles are scoped…
2 votes -
Include security logging for role changes
Because roles cover a range of permissions, there is a necessity to give users a role for one need even though it gives them permission to do other things that are not wanted. One of those things can be assigning other roles.
Role assignment is the most security-sensitive function of Alma and should absolutely be tracked and the log of who made an assignment and when should be accessible to administrators. Even better would be the ability to add an email warning mechanism for particularly sensitive roles.
(Related to this but in documentation, there needs to be a table of…
1 vote -
Update user roles quickly - import the Excel file exported from another user
Currently, it's possible export a user's roles in Alma to an Excel file. However, the counterpart function isn't there: to be able to take the roles you've exported from one user and import them into another user's record. This would be such a time-saving feature because it would enable us to take the roles from one member of staff and apply the same to another.
75 votes -
Inactive/Active change to be visible in history tab
When a users account is made inactive/active it does not currently show in the history tab. I would be extremely useful to be able to view when a users account becomes inactive.
23 votes -
User update notification with loan information
We would like to send out an email to users, who's account are about to expire. However, we want to have the users current loans added to the email as a table (like the borrowing activity email). The user and librarian can then see what they need to return before their account expires.
4 votes -
Extra personal detail fields available for library users
I am working in special library so our users come from public who is affiliated with other organizations such as university, museum or architects. It would be great if Alma can offer extra fields to store additional personal detail such as occupation, affiliation, age (not birth date), age group and research interest, etc.
1 vote -
Ability to make manual notations in the history tab when updating a user's record
I think that it would be great to have a feature in the history tab that allows you to manually add a notation to indicate why a user's record was changed--similar to how a registrar's office makes comments in a student's record any time a change is made. Anytime we make a change on the backend, and then have questions at the front desk about why something was changed, it causes some confusion until we talk it out, but if this feature was there, it could limit the confusion.
I don't think adding these types of things to the note…
1 vote -
Having "nested" user records for users with dual or multiple statuses
I think that it would be useful for user records to have the option to have "nested" records where you have one user with one user profile, but under that profile, they have 2 or more identity profiles that contain other data that is linked to their different statuses.
The only parallel I can think of for it is when you have one bibliographic record and multiple item records attached to that one bib. record. All of them have the same main information, but individual record identities below.
This would be helpful because we have users that are current students…
1 vote -
Field for academic year in user profile
It would be good if there were a field in the user's profile that states the user's academic year, e.g., YEAR 1, YEAR 2, YEAR 3, etc.
114 votes -
block fine message
Allow the block message for the fine limit to be customized. Currently, the block message shows that the fine limit has been reached and then shows the amount owed. This is confusing to Student Assistants who only read the first part of the message and relate to the patron that the fine limit is all that is owned in overdue fines and fees.
1 vote -
Allowing the ability to freely assign different jobs to different users.
There are cases where we want the user to only be able to handle a specific task that is beyond their user role, but currently in order to do that we have to assign them with roles that allows them access to jobs we don’t want them to have access to.
61 votes -
automate user update job to send user emails ie about to expire
Currently the user update job can send emails to patrons. However due to the technical aspect of creating sets and running the job our user services librarians prefer to take the information out of a dashboard and widget and add them to a template email in outlook. It would be better if a schedule job could be created to send out user update emails to logical sets. Specifically for users that are about to expire - and have loans to return.
16 votes -
Save and Continue button on User Record screen
It would be really useful to have a 'Save and Continue' button when updating user information as edits can easily be lost if the user record closes (timeout). It would also mean that you could save the changes for one tab at a time.
3 votes -
Customize Patron Registration Form with more identifier field
We would like to to have more than one instance of the drop-down menu (identifier1 field) and input field so we can fill in more than one identity type in the registration form for a quick registration of the patron.
4 votes -
Record Block Expiry Date Editing History
We’d like Alma to keep track of changes made to Block Expiry Date.
We sometimes edit and shorten Block Expiry Date when users return books late due to unavoidable circumstances. However, Alma does not keep track of changes made to the Block Expiry Date in the Blocks tab. It would be great if we could review the history of changes made to the Block Expiry Date in the History tab of user record.
2 votes -
Have option to set Expiration and Purge Date to "Current Date"
It would be useful to have a button that says "Today" or "Current Date" when changing either the Expiration date or the Purge date. We often have to update records for staff and faculty who terminate and having that button would save a lot of time.
4 votes -
User ID Generation functionality also on the User Details page
Libraries can configure the automatically generated user identifiers for new patrons that are added when an operator adds a patron on the Patron Identification page. We would like that the user Primary identifier can also be generated when users are added or edited on the User Details page: Existing users (external or internal) could have their Primary identifier updated (refreshed) in a more easy and effective way by circulation desk operators.
87 votes -
Ability to Disable the Dispute Functionality for Fine/Fee
Feature Requested:
An option to turn off the ‘Dispute’ functionality for fines and fees.Use Case:
With middleware connected to Alma and our university, anything that is done in Alma needs to be propagated to the rest of campus. Since there is not a need for the dispute functionality, we have not written any middleware on handling the dispute if it were to come in through the web hook. Currently, we are training staff to just not use the dispute functionality. It would be ideal to just turn off that option so that there is not a chance of discrepancy…1 vote
- Don't see your idea?