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.
89 results found
-
Pop-up message for activating / deactivating the patron’s identifier using the slider
To activating or deactivating the patron’s identifier, it can be done by toggling the slider to “blue color” (i.e. ON) or “gray color” (i.e. OFF) under the tab ‘Identifier’ of the patron account in Alma. The attachment shows the screen capture. Once, the slider is toggled, the identifier will be activated or deactivated immediately. The “Cancel” button on top right-hand corner (“red rectangle”) has no effect to turn it back to the old value after toggling the slider.
The patron’s identifier is an essential part of the login credentials for user authentication in Primo. After login, patron can manage the…
1 vote -
Making Alma and Salesforce Work Better Together
Hi there,
Greeting from Marcos!
Here’s how we can improve how Alma and Salesforce work together to help libraries:
Automatic Case Creation: When something goes wrong in Alma, it can automatically create a support case in Salesforce. This way, issues get attention quickly, making it faster to fix problems.
Combined Dashboard: Create a single dashboard in Salesforce Marketing that shows real-time data from Alma. This helps library staff see important information in one place, making it easier to make informed decisions.
Better Communication: Link Alma and Salesforce so that notifications and updates about cases are sent automatically to users and…
3 votes -
Allow internal users to have a phone number as default required field (not email)
We have a mix of internal users, some community users do not have email addresses. We find that it is nearly impossible to set up Alma accounts for them when they do not have an email. We would like to have the option to set those users to have a default phone number as the required contact field and the ability to print on demand any notifications they may be.
1 vote -
User Record Templates
It would be great if the library could create "templates" for different types of user records that automatically fill in things like the User Group and that have different required fields depending on the type of template. This would make it easier for staff to create user records on the spot.
14 votes -
Ability to pin and fix the facet in authorities search
It would be great if the search facet in the authorities search could be pinned and fixed, so you don't have to click and expand the facets every time you want to filter on a specific vocabulary
3 votes -
Add letter resend to Privileges Report so that it can be added to other roles and removed from Fulfillment Admin
Issue - Currently we need to give staff in reader services the Fulfillment Administrator role so that they can resend emails on users accounts. This role is too significant and gives reader services staff access to change loan rules and other processes.
Solution - Could Letter Resend be added to the Privileges Report so that it can be added to more appropriate roles (User Admin or User Manager). And it could then be removed from Fulfillment Administrator role.4 votes -
Support full SIP2 protocol
For the communication between selfcheck kiosks and Alma, the SIP2 protocol is needed.
The full protocol can be found here: https://developers.exlibrisgroup.com/wp-content/uploads/2020/01/3M-Standard-Interchange-Protocol-Version-2.00.pdfUnfortunately, Ex Libris does not support all fields that would be available in the protocol (marked as 'not supported' in this document): https://developers.exlibrisgroup.com/alma/integrations/selfcheck/sip2/
Please make the whole SIP2 protocol available for Alma.
183 votes -
Add 'Assigned date' to user roles
We often need to know the date that a role was first added to a user's account. The status date is not static and because we use the API for updates from our SIS the status date often gets updated with random dates. The API updates also make the history tab difficult to use to track down role additions versus changes.
We should be able to easily see a column that includes the date a role was initially assigned/added in the context of all of their roles in the General Information tab.
We also need the date a role was…
4 votes -
Allow a block to be created as part of the 'change to lost' overdue and lost loan profiles.
We'd like the ability to create a block when an item is made 'lost' as part of the overdue and lost loan profile schedules.
At the moment we can only add a block on the overdue notification types, which we do for the last overdue notification we send before it becomes considered lost.
However, as soon as the item is changed to lost by the profile schedule it removes the block automatically created by the overdue notification profile.
The advantage of using the profile block is that they are automatically removed if the item is renewed or returned and we…
156 votes -
Stop "User manager" role's ability to add and delete Alma administrator roles
Ideally, there shall be a separation of managing patron users and managing staff users. If that is not possible, please make it impossible for people with "user manager" role to add and delete administrator roles.
1 vote -
Adding newly registered patrons to the 'Recent patrons'-list
Being able to see patrons entered in a session is very useful, but it would be great if the recent list also included new patrons registered during the session.
Often times, patrons for instance request registration before they find the books they want to borrow. If we could easily access their patron services page when they return with them, it would streamline the process.
3 votes -
Access Student Photos Securely
Currently, user photos are only available via a web link https://myurl/photo/studentidentifier.jpg. This means that all student photos need to be available over the internet which in the UK is a Data Breach. There needs to be a way that only the student in question or an authorised staff member can see the photo. It is not possible to use 3rd party software like Azure to do this as the cross-site scripting protection gets in the way.
1 vote -
user - add option for dynamic purge date - e.g. 12 months after expiration date
Right now the purge date is a static value manually inserted when registering a new user. When the user renews registration, purge date must also be manually updated.
In our library regulations we'd like to purge users after a specific amount of time after expiry date. Keeping purge dates manually up to date is however quite an error prone procedure.
It would be great to have the chance to automatically update the value in purge date when saving according to specific a timespan (e.g. 10 months or 10 years after expiration date).111 votes -
Create a job to send a notification letter to users when their expiry date is near so they can request to renew their library user account
The option to notify users whose accounts have or will expire of their options for renewing their library user account would help us to stay engaged with users whose library user account will expire soon (or has recently expired). Users who want to continue using their library account can renew it prior to the expiry date, thus reducing any barriers to accessing their account and using library materials.
A notification letter could be created to support this type of messaging. It would be great if a job could be scheduled to send to users whose expiry date is upcoming. It…
12 votes -
Add option for patron name suffixes like Jr., Sr., or III
Name searches in Alma for names containing suffixes like Jr., Sr., or III yield strange results.
Example: Someone named Joe Johnson Jr. will have first name "Joe" and last name as "Johnson Jr." When performing searches in Alma for "Joe Johnson", "Joe Johnson*", or "Joe *Jr." will not yield any results.
Alma looks for "Jr." as a last name rather than the person's surname. This isn't helpful when SIS has the suffix but the patron may not use the suffix all the time in their everyday life.
Creating the option for a patron name suffix or updating the search for…
4 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)43 votes -
Add school address as a configurable option for the user card
In the pop up user card that displays, for example, in the Borrowing Requests screen, you can configure the home or work address to display. Since the mandatory address in our student enrolment system Callista, is mapped to the School address in Alma, please add the School address also as a configurable field for the user card.
1 vote -
Support multiple photo_identifier_type values
Allow the photoidentifiertype to accept multiple codes. Our institution recently changed primaryIDs and our card issue office cannot retrofit their db for legacy users using the old primaryID.
1 vote -
Bulk update block expiry date
In January 2018, fulfillment enhancement was added to allow library staff to manually add a block expiry date and edit the expiration date on an existing block. (See https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/12_January_2018/Alma_January_2018_Release_Notes/04Fulfillment_-_January_2018_Enhancements)
We would really like to have the option to input a block expiry date in the bulk update/notify users job when adding a block type, instead of manually adding the blocks with expiry date one at a time for a batch of library user records.
10 votes -
A "kill switch" for General System Administrators to immediately disconnect individual Alma users
Use case: A library employee (student or staff) responds to a phishing text message by providing their Single Sign-On (SSO) credentials; SSO is used on our campus for Alma authentication. I want to (1) disable all the roles on the library employee's account except for Patron; (2) disconnect the employee if he/she/they/* has an active session in Alma; and (3) be notified with the IP address of the originating computer if he/she/they/* attempts to log in again. I would like to accomplish both #1 and #2 by checking a box ("Disable roles") and moving a slider ("Disconnect user"), WITHOUT having…
64 votes
- Don't see your idea?