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
-
Batch deletion of notifications by date or letter type
I notice that I have 356 system job notifications in the attachments tab of my Alma account. Apparently these can only be deleted one at a time, which would take at least an hour or so. It doesn't appear in the letter retention section, so please could you introduce an option to batch delete these?
1 vote -
User edit--add options to "Save" and "Save and Close"
When updating a user record, it would be extremely helpful to be able to Save without closing the record. We are updating and adding identifiers. Currently I have to save (which closes the record), then open again to add the second identifier. Very time consuming. "Save" should keep the record open; "Save and Close" would be fine when you are finished updating. This option IS available when adding statistical categories.
3 votes -
Add the code to the list of Statistical Category while adding statistic for user
While adding statistic for user, Alma only shows the description in the list of Statistical Category. We would like to show the code and description both together in order to filter the value by code easily.
1 vote -
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 -
warning when saving changes in patron record before closing record
When editing a user record, it would be helpful to get a warning pop-up if you try to close the record without saving it. Sometimes when you get interrupted, it's very easy to just close the record without saving the change.
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 -
Allow replies to emails sent to users to be received in Alma
When the system sends an email to users, it should be possible to for the user to reply to that email and the response to appear in Alma in the appropriate place (prob along with a notification so staff can see that there is a reply for them). This would avoid having to manage email conversations outside of Alma. Not only would this be of benefit to Alma, but it could benefit other Platform products such as Esploro and potentially Leganto.
5 votes -
Batch upload (from template) of internal users
We do not use external SIS upload. However, it would be fantastic to be able to batch upload internal users from a template, like we can do with portfolios. At the start of each school year, we could use the list of incoming students very easily.
6 votes -
How about sending or allowing to send e-mails to users that previously booked any material from the library?
Please, configure ALMA to send e-amils to users that made a booking or let the librarians to do it manually.
1 vote -
home page notifications not to be linked to General admin role
currently only General Administrators can create Alma home page notifications. these notifications are very useful for operators e.g. issue desk staff, and it would make more sense to allow area managers the creation of these notifications. General Admin gives you access to some very complicated admin functionality, which we'd rather not make accessible to staff who shouldn't have access.
0 votes -
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 -
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 -
General Mail Attachments
Could the General Mail facility be amended to allow staff to add attachments to an email sent to a patron via the USer Management screen?
1 vote -
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.16 votes -
Add profile used to the list of Roles for a given user
It would be useful if there was an indication of the Profile used that added each role to a given users account.
8 votes -
Ability for Alma Administrators to create special menu bars for staff users.
It would be nice for our Alma Administrators to have some control over what each staff member sees on their menu bar or at least to be able to hide the configuration wheel from non-administrators. This would prevent some confusion staff members have when seeing options they do not have the privileges for, then telling us "it's not working." It would also allow us to create more simplified views for our student workers. Accidental menu customization done by staff is another problem we have. We have to try to figure out what they did in order to get their menu…
2 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 -
user title as free text field instead of pre-defined drop-down
The field user title should be definable as free text field (min 100 characters long), so that various combinations of user titles can be imported from the campus information system. Now this is not possible, because titles (resp. combinations of titles) have to be defined BEFORE importing users via API.
14 votes -
Dynamically create statistical category and type specified in the user xml notice imported from SIS
The user.xsd xml shema contains statistical category an type description.
<user_statistics>
<user_statistic segment_type="External">
<statistic_category desc="STAPS">
4200013
</statistic_category>
<category_type desc="Code SISE">
BSISE
</category_type>
</user_statistic>However, when imported from SIS, il the category and type in a user.xml file imported from SIS does not already exist in Alma configuration tables, it is not imported in the statitistical type specified.
In the example below, category 4200013 and its description STAPS, type BSISE and its description Code SISE required to have been already created in Alma configuration tables.
If its not the case, the category 420003 is imported with NO type
and no description.…
6 votes -
Dynamically create statistical category and type specified in the user xml notice imported from SIS
The user.xsd xml shema contains statistical category an type description.
<user_statistics>
<user_statistic segment_type="External">
<statistic_category desc="STAPS">
4200013
</statistic_category>
<category_type desc="Code SISE">
BSISE
</category_type>
</user_statistic>However, when imported from SIS, il the category and type in a user.xml file imported from SIS does not already exist in Alma configuration tables, it is not imported in the statitistical type specified.
In the example below, category 4200013 and its description STAPS, type BSISE and its description Code SISE required to have been already created in Alma configuration tables.
If its not the case, the category 420003 is imported with NO type
and no description.…
3 votes
- Don't see your idea?