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.
83 results found
-
Add "Faculty" to pop-up window
Add "Faculty" inside: Configuration Menu > User Management > General > Contact Information Pop-Up.
In order to display faculty in the pop-up window with the user information50 votes -
Manual Deleting of User (Patron) records and need for consistency in maintaining reportable data
At present Alma has an inconsistent method of maintaining reportable patron data when a user record is deleted. The reality is that the policies established by an institution (to keep fully reportable, or keep statistics, or fully remove) do not apply when a patron record is manually deleted - ie. Deleted in: Administration > User Management > Find and Manage Users.
“Users that are manually deleted in Alma are fully removed from the system” regardless of institution policy. The Queensland Health Libraries would like to have this situation changed so that manually deleting a user (patron) record would maintain the…
47 votes -
Show "Open for Update" override enabled
This is about the protection of data for external user records. I have copied the below text from the Alma Documentation page: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/030User_Management/010Managing_Users#UserDetails
To enable editing other fields of external users, select Open for Update, and select Yes. Edit the relevant fields and select Save. Note that changes you make to most fields will be lost after the next SIS synchronization job. However, Alma prompts you to determine whether the following fields will be overridden with the next SIS synchronization job: Title, PIN number, Job category, User group, Campus, Preferred language, Resource sharing libraries, Cataloger level, Selected patron letters. (Note…
41 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…
40 votes -
Attach printed letters to user record
We send our bill notice to a central email account for price checking before sending onto the user.
Request is for any notice to be added to a users record in the attachment tab, whether it is emailed or sent to print.
38 votes -
Make the "General Mail" feature more customizable
On the "User Details" screen in Alma, there is a "Send Message" function. If "General Mail" is selected, any message that is composed shows up as "ILLEMAILTOUSERlongstringofnumbers" under the user's Attachment tab. Unlike other letters, this is saved as a "text/plain" type, requiring the file to be downloaded before it can be viewed. It would be nice if this attachment type could be renamed, or given a more descriptive title than "ILLEMAILTO_USER," especially as it is generated from within the User Details screen and not via Resource Sharing or ILL.
34 votes -
Batch update of role expiry dates via the UI
Batch update of role expiry dates via the UI.
We have hundreds of student staff who have expiry dates on their roles (see attached for an example). Every semester, we have to manually edit each and every role for every student. This process would be so much easier if we could choose multiple roles and then batch update the expiry date.
Thank You! Lisa
30 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.
26 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
26 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 -
Allow administrators to change the labels on Alma terminology.
Allow relabeling of field tags, such as changing CHRON I to YEAR, and ENUM A to VOLUME. Let libraries have the flexability to use the terminalogy that they prefer.
25 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…
22 votes -
make permissions on changing address data more granular (email/domestic)
Aleph allows to set an option to allow users change their "address" data via Primo OVP. This allows users to edit the phone number and email in Primo, but also their domestic address. Often, the change of the domestic address must be prevented, because it is the address where a possible court order is directed to.
We want to allow users to change their email and phone number but need to disallow the change of the domestic address. Therefore, we propose that Primo and Aleph/ALMA must be designed to work in a way that allows setting permissions on each field…
22 votes -
Could we have dates showing the actual month, not represented numerically?
Many of our students can't work out when their items are due, maybe due to the increasing use of the US dating format, so they don't know if 4/10/16 is the 4th of October or the 10th of April. Using the actual months would decrease the confusion.
22 votes -
Increase time in which the "reset password" link is valid
The link that is sent to patrons to reset the Primo-password is only valid for one hour. We would like to be able to configure this duration, as it appears to be rather short. Our patrons often miss this timeframe and have to resent the link.
21 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:
- …
21 votes -
Move general email feature outside of the User's form
The General Email function is currently located inside the form for updating general information in the user record.
If there are any problems with missing mandatory data in the form then the email cannot be used at all.
Since it is unrelated to user general information I would suggest that the Send Message function should be located outside of the user data area perhaps up near the buttons "Toggle Account Type", "Open for Update". (See screenshot)
Additionally, the general mail could perhaps be added to the letters that can be sent from "Manage Patron Services"I would also support greater…
19 votes -
Add Job Category to Update/Notify Users
It seems strange that you can add User groups, roles etc in the Update/Notify USers job but the Job Category isn't available.
It would be useful if you could add this as we are starting to use Job Categories is TOU rules and being able to assign them based on a set of users would be really helpful.19 votes -
Make Notes/Blocks tabs more noticeable
When users have blocks or notes attached to their account, it would be helpful if the tab changed colour or had a red exclamation mark icon in the corner. This would alert members of staff immediately if there was something on the account that needed to be seen, i.e information about disability arrangements, reasons why a user is blocked, fine payment arrangements etc.
Currently the folded blue tab in the corner, meant to indicate that there is information in that space, makes the Notes/Blocks tabs just blend in with the rest.
Making Notes/Blocks tabs more noticeable would mean important and…
18 votes -
Make patron info updateable in Primo flag more granular
Currently the only control on allowing patrons to update info via Primo is either on or off:
http://screencast.com/t/kcSIvkkR3gWould like the ability to say for example only Visitors user group can update info via Primo.
18 votes
.png){kind=link}
.png){kind=link}
- Don't see your idea?