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.
-
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.7 votes -
Welcome Letter for the new patron profiles automatically or manually created
With our previous library system, Aleph, we were able to send a customized Welcome Letter to the patrons whose profiles had been created either automatically or manually.
The Welcome Letter allowed us to promote the library services to an audience that was often not sufficiently informed.
There is no such a possibility in Alma.
It could be great if, daily or weekly, a job identifies the brand new patrons and sends them a highly customizable letter.
Thanks,
Sergio
7 votes -
a specific type of "User notes" shown under "notes" tab
Currently, all user notes (which can be added manually) are hidden behind the "notes" tab (which can't be manually added), as shown in the attachment. It would be great if a specific type of "user notes"(for example, circulation notes) could be listed under "notes" tab, so that those notes will be more obvious to desk staff.
7 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.
<userstatistics>
<userstatistic segmenttype="External">
<statisticcategory desc="STAPS">
4200013
</statisticcategory>
<categorytype desc="Code SISE">
BSISE
</categorytype>
</userstatistic>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…
6 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…
6 votes -
User Registration Terms of Use - Have expiration dates be able to set from the calendar
When creating TOU for User Registration, we should have the ability, much like with due dates in Fulfillment, to set the expiration date to not only various amounts of time, but to a calendar date. We have some patrons who end their privileges at the end of the semester, and it would be very helpful.
6 votes -
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.
6 votes -
patron purge letter
It would be helpful if Alma had an email letter that was linked to the user expiry date and could be sent to the client once their account is due to or has expired.
6 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 -
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 -
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 -
Improve how operator transactions/history is displayed throughout system due to privacy concerns
Operator identifiers are displayed throughout the system in various places, such as History and Notes tabs and the Receiving Operator field in the Physical Item Editor. These display as the operator's employee number, which has been raised by staff as a privacy concern. Currently, configuration can be set to disable this display only in the History tab, and only for users that do not have Manager or Administrator roles assigned to them. This is problematic for several reasons:
- Privacy concerns being raised by staff that their employee id is viewable by other users throughout the system
- "Hide" function…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 -
To add the "primary identifier" to the export list of the user set
We would like to add the "primary identifier" to the export list of the user set.
We will use the excel file with "primary identifier" to establish the User set, but not all the primary identifier can be loaded into the user set. So
We would like to add the "primary identifier" to the export list of the user set in order that we could know which primary identifier can not be loaded into the User set.4 votes -
User record list of roles should display Expiration Date -- not Status Date
In the display of Roles for a given user, displaying the Status Date (when the Role was created or last edited) is virtually useless. Much more valuable would be to instead display the Expiration Date for that Role. This is something that we must currently click into the record to see, and is something of much more value -- especially when checking on the status of student staff.
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 -
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.
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.
<userstatistics>
<userstatistic segmenttype="External">
<statisticcategory desc="STAPS">
4200013
</statisticcategory>
<categorytype desc="Code SISE">
BSISE
</categorytype>
</userstatistic>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…
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 -
To add purge date option rather then use days since purge date
To add the exact purge date option rather then use days since purge date. If the date option is available, we can run a job and set the purge exact purge date rather than purge users that are not meant to be purged
3 votes
- Don't see your idea?