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.
81 results found
-
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.
122 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 -
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 -
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 -
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…
9 votes -
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.
8 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…
59 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…
52 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 -
New role for limited user account editing
It would be helpful if we had a separate role for User Operator that could edit any user account's contact details and merge user records as well as run analytics on users BUT not change or add roles attached to that account OR delete records. This is primarily to allow circulation staff more control over user accounts but to restrict access to higher-level abilities for cybersecurity reasons.
1 vote -
Set transaction time in Loan/Return
Configure in User Services -Loan/Return next to the date show the time of the transaction as it is displayed on the expiration date
3 votes -
User action history report
Our institution's security protocols require systems that handle confidential patron/student data have the ability to log backend staff user actions. After inquiring to ExL, the only way to know what a staff member has done in the system is to go through their individual history tab. However, this data is incomplete and doesn't give a full scope of what actions they took. In Analytics, the options provided are not useful and do not give us any useful information.
We'd like to track things like:
- When roles were issued
- Who issued roles
- Changes in configuration and who made…5 votes -
Improve “Chat for Support” role to add product specific scoping or separate roles per product
As more products are added and managed by the Alma HEP it becomes a concern that Ex Libris is not adding necessary granularity for roles. The “Chat for Support” role does not have any granularity for different products.
For example, we would like for some of our senior acquisitions staff to have visibility and ability to open Chat sessions for minor title by title issues with Rialto, which we have recently implemented. But this is not possible, as the role gives visibility and ability to open Chat sessions for Alma also, which is not appropriate per our internal management of…1 vote -
Add "Status" to user searches
There is no current method for adding "Status" to the list of available selections when running a User search in Alma; as such, the only way to find a list of active users is to either use the filter provided post-search (the selections in which are "All," "Active and not expired," and "Not active and expired") or to use Analytics.
However, these filter options exclude searches for users who are both Active and Expired, and using Analytics to create a report for this result requires multiple steps to set up before you can get a result (and subsequently run jobs…
8 votes -
Alma - automatic warning for users about to expire with dedicated alma xml letter
It would be useful to activate an automatic warning for users about to expire with dedicated alma xml letter.
The customer could simply set up the amount of days before expiration and if the letter should be sent to all users or to specific user groups. A scheduled job could be activated, so that the letter is sent every day at a specific time.279 votes -
Possibility to duplicate a Staff User record
We do use Role Profiles to create new Sfaff Users as easily as possible.
However, we have about 30 sublibraries and colleagues, some of them working in several libraries or have special WO Department permissions, etc. Therefore we do not have suitable Role Profiles for all combinations.It would be great if we could duplicate an existing Staff User record instead of having to create a user from scratch.
Thank you in advance!
8 votes -
User Purge should be made AFN aware and not allow the deletion of a user with active transactions or fines/fees at another AFN inst.
The Alma User Purge job is not AFN-aware. It will allow the deletion of a user record from the user's home institution's IZ even when the user has active transactions or fines/fees at another AFN institution. These "orphaned" linked user records are confusing for both users and library staff and are not a best practice for user record management.
Examples of the resulting problems we've encountered thus far include:
1) If the user's home institution performs a purge and then re-loads records, the orphaned linked user records in the other AFN member institutions do not re-connect to the new version…71 votes -
Configure the User Services page to include statistical information
On the User Services page, when we are looking at a user's data, we can see the Notes and some other basic data. It would be interesting to be able to choose which of the user data we want to see here. Specifically, we are interested in including statistical data.
1 vote -
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)3 votes
- Don't see your idea?