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.
128 results found
-
Change role attributes via SIS batch load
I would like to be able to change user role information (roles status, expiration date, delete or add a role) via the Student Information System external integration batch uploads. Currently, user roles can only be modified manually in the UI or with an API call.
5 votes -
Password reset
It would be beneficial to all users to have a "Forgot your password?" link on the login page to get a reminder via e-mail, or be able to reset your password. This current system of having it completely controlled by the administrator is antiquated and needs to be replaced.
5 votes -
add course name to the course tab on the user profile
At the moment the only columns available in the Course tab on the user profile is course code and section.
Course codes will often consist of a line of numbers so the option to add course name as a column would add great value.
5 votes -
Purge User Records – Add field to prevent purge of users with active requests.
In addition to Number of days, user record, user group, and waive threshold, an institution should have the option:
Do not purge if there is active request(s)5 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 -
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 -
Batch Job to add User Notes with option to choose "Note Type" and select "User viewable" and "Pop up note"
Currently, there is no option to choose "Note Type" and select "User viewable" and "Pop up note" boxes while adding User Notes in batch.
4 votes -
Users remove blocks
It would be usefull for an operator to delete selected blocks in the tab block of an user card in the same way of fines/fees, marking them and delete them in one go.
This idea because the operators can't run the job "Users - Remove Blocks".We think especially at those libraries where users are not always on time to return books and deleting them individually it's a waste of time.
it is not nice to delete blocks one by one.
It would be better if the operator could mark blocks and delete them in one go.4 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 -
4 votes
-
Permit only public notes in patron files
According to Swiss Data Protection Laws, all notes in a patron file have to be viewable by the patron.
As consequence, we want either:
- Only have public notes in the patron file. Non public notes do not exist. This may be an option that can be activated or deactivated by administrators.
Or:
- The User Viewable attribute is ticked by default. Again, this may be activated or deactivated by administrators.4 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 -
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 -
Add options to retain manually-added (internal) information when toggling a record to external user
Currently, notes (and other internal fields) disappear from internal patron records after toggled to external patron records. Per support documentation https://developers.exlibrisgroup.com/alma/integrations/user-management and testing, this is intended behavior in Alma based on assumptions made and imposed by the system. As a community college, we have many students who leave school for some time and become community users and then enroll again after a period of time. Many community members also become students, staff or faculty. In order not to lose the vital internal information, we have to do time-consuming work arounds.
3 votes -
Login via code in addition to the link for the E-Mail Authentication
Today the E-Mail Authentication only has the option of logging the user in via a link in the E-Mail. This restricts the user to logging in on a computer where they have an e-mail client of which excludes most kiosk solutions and makes it a hassle if the user usually uses their e-mail on for example their phone but uses Primo on another computer.
Adding the option of logging in via a code (in the same e-mail) which the user can enter on the device where the user initiated the login process rather than the device where the user read…
3 votes -
Make the Send Message emails more customisable
Today it is possible to send messages to individual users from the General Information tab on the User Details screen, but the functionality is very basic. To be truly useful it should be possible to create your own templates and to customise them the same way we can customise Alma Letters. Without the usual letter components, such as a header with the institution logo, which are present in other Alma letters, the messages look unprofessional and can easily be mistaken as spam. If it would be possible to create templates containing and editable body text and combine it with the…
3 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 -
Make address fields one of the searchable fields in user searches
Addresses on a patron record (at least the preferred address fields) need to be a searchable field in the universal search box on the dashboard.
We often find a need to on the fly find all the patrons who might come from a particular address.3 votes -
SIS user integration, automatic primary ID generation: prefix + sequence
Allow automatic primary ID generation for SIS user sync integration simular to when adding a patron from the patron identification page in the Alma BO: Configured prefix + sequence. (Now automatic generation in SIS is only possible as: first name + last name + sequence)
3 votes -
lock fields in patron records
A problem we have is that when Alma imports updated patron data from the University's Central Registry database -- via an integration profile -- it can overright values that should not be overwritten for certain groups of patrons.
What we require is the ability to lock fields in patron accounts so that they cannot be overwritten.
3 votes
- Don't see your idea?