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.
79 results found
-
Ability to run user purge on a set
The current purge job does not allow for granularity beyond the user group and the number of options and filters for the Purge User Records job is very limited.
It would be helpful to be able to run patron purge on a set of user records, or alternatively for Alma to add a user delete job (under Manage Jobs and Sets > Run a Job) that runs on a set.
(see also NERS Request ID 5304)270 votesHi,
Of course ! We will add a job that will be able to run on a set of user records and purge them, using standard validations (such as no existing loans, fees).
Thanks !
-
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.251 votes -
Add expiry date for "proxy for" users
In an academic institution, many "proxy for" users will be arranged on a semester or yearly basis, it would be good to have an expiry date so that this permission stops and does not extend into perpetuity.
236 votesThe proxy relation between two users will have an expiration date. After the expiration date, the proxy relation will be considered inactive, and be ignored by the system.
The date of expiry will be updateable in the Proxies tab of the user form.
-
How to distinguish namesakes
When you search a user (fullfiment > manage patron services), there is no possibility to distinguish to different user, who have the same nam (namesakes).
In the old UI, there was a patron card image, and, when clicking on, we accessed to a summary of the patron.
Now, we have no more solution.
Can you add this functionnality in the new UI?
Thanks a lot.
206 votesHi,
Makes sense ! Currently, the user information that is displayed in the user Ajax search results (e.g. patrons services WB) is hardcoded.
A mapping table, similar to the one that configures the user pop up, will control the fields that show in this list. The mapping table will enable the same fields that the user pop up allows, and allow setting the order of the fields.
Thanks,
-
Purchase Request Library management in User records
A new multi-selection field, Purchase Request Library, was added to the User Details page with the June 2018 release. If one or more libraries are defined for a user, the user may create purchase requests only for the listed libraries. If no libraries are defined, the user may create a purchase request for any library.
But managing Purchase Request Libraries in user records can only be done record per record; there is no possibility for batch processes.
Currently, there is no option:
- to add or remove a Purchase Request Library with the Update/Notify Users job;
- to add or…197 votesThe Purchase Request library will be supported vi SIS/API and user update job, just as the Resoruce Sharing library is.
We’ll also look into making the Purchase Request and the Resoruce Sharing library be searchable in the users advanced search option.
-
Possibility to configure that a patron can login into his/her account in ***** AFTER expiration date, to view open fees / fines and or loans
Currently a patron whose expiration date has passed is not able to log into his/her ***** account. The patron can neither see open fines/fees nor loans.
We suggest:
* institution-wide option to allow or permit users read-only-access to there ***** accound after patron’s expiry date (in Alma)
* user manager role not necessary to do any changes in role expiration dates.
* no additional functionality outside Alma needed that uses the API to achieve the goal.180 votesHi,
The login for an account that is managed in an external IdP (such as a Shibboleth IdP), is done by the IdP and not by Alma. Alma does not control the success of this type of login.
Alma does control the login status if the user record is internal, i.e. its password is managed in Alma. In that case, we will indeed allow the login to succeed even if the user is expired.
The user record status will be verified when calculating:
- GetIt services (hold/digitization/resource sharing)
- My Account renew loan option
In either case, the account will be considered active only if:
- The user record status is active
- The user record expiry date is not in the past
- The user’s patron role is active
- The user’s patron role’s expiry date is not in the past
The login, however, will not be affected by these conditions.
Thank you,
Moshe -
Allow batch deletion of user notes
It's possible to add notes to user records in batch using the "Update/Notify Users" job on a set of users. It would be helpful if we could also batch delete notes on user records.
There are occasions when we have subsets of users who receive special permissions to check out subsets of materials (e.g. students in a specific class who are the only people allowed to use specific equipment or reserve items, collections/materials where we require a signed agreement on file from the user to allow access). In these situations, we add notes to the user record to indicate whether…
178 votes -
delete users with expired purge date daily with scheduled job
Now deleting users with an expired pruge date has to be done manually and cannot be scheduled with a job. We would like to have a job that can delete these records more easy than now.
ExLibris came with this answer: Alma product management is aware of this issue and most likely scheduling will be possible in future Alma versions. However, there is no specific timeline for this solution, yet. Once the fix is released, information will be included in the relevant release notes and documentation.
It would be an efficiënt addidition in the ALMA jobs.
167 votesYes, it will be possible to schedule the purge users job.
-
Role Profiles Enhancement
When using role profiles, it would be nice if the profile could create a link to the user(s) with roles defined by the profile. Then, if you want to modify the profile, the change updates all users in the profile. Currently, you'd have to update the role profile and each individual user.
150 votesIt will be possible to maintain ongoing link between the role profile and the user record, so that you can use the template to assign a predefined set of roles to a user, and any further changes to templates will automatically affect the linked users' allowed roles.
Note - multiple profiles may be assigned to a user.
It will be possible to view the list of profiles an account is liked to for inheriting its roles, and to remove/add more profiles.
-
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 -
Make Paying Fines/Fees-Waiving Fines/Fees a separate User Role in Alma and remove them from other roles
The auditors at our institution require us to limit the number of staff members who have this ability. We had to ask Ex Libris to remove PAYFINESFEES PRIVILEGE and WAIVEFINESFEES_PRIVILEGE from a large number of roles, most of which didn't even relate to fulfillment responsibilities during our implementation.
Our Student Assistants and Operators at the Circulation Desks should not have these privileges. But they did before we had them removed.
Approving Manager and Operator, Producer Manager, User Manager, Editor Full, Assessing Manager and Operator, Arranging Operator and Manager are all roles that I don't understand, and…
113 votes -
Configurable Fines/Fees Behaviour
Configurable Fines/Fees Behaviour
We are a library that has two libraries in two different cities but we are one organization and we share the same economy. The Fines/Fees Behaviour is hardcoded to be owned by library which doesn't mirror our situation. We would like the Fines/Fees Behaviour table to be configurable.
101 votesAn approach we would like to take is to improve the Fines/Fees Notifications Profiles so that if no library is selected then a single notice will be generated with the fees of all of the libraries.
-
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).96 votes -
Set preferred SMS default to "Yes"
When adding users manually in Alma the phone number has a parameter called "Preferred SMS" which is automatically set to "No". It controls whether Alma sends SMS' to the patron or not. It can only be changed after the profile is first saved. Hence it is ease to forget to toggle this setting.
We would like to have the option to choose the default setting for Preferred SMS, or the option to toggle this setting before saving on the "Quick User Management" registration form.
92 votes -
Purge User Records - allow to keep users with Blocks
Right now the Purge User Records job does not delete users with active loans and users with a fee > than a specific threshold.
Users with active Blocks are instead deleted.
Adding to Purge User Records job an option allowing to keep the users with blocks would be very useful.87 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 -
Proxy/Principal User Search
(I'm not sure the best term, so I'm using "principal" to refer to the person a proxy is acting on behalf of)
It's possible to view a list of principal patrons that a patron is a proxy for from within the proxy's user record (the "Proxy For" tab).
It's not possible to view or search for patrons that are proxies to a principal patron.
Examples:
1) Alice and Bob are known proxies for Chad.
I can open the Proxy For tab for Alice and Bob, where Chad will be listed for both.2) Chad has several proxies, but it's uncertain…
79 votes -
More options to limit access to private patron information for student employees
Some libraries hire students as part-time staff at the circulation desks or helpdesks. Per the institution or library policies, for privacy reasons, student employees may not be allowed to search for Alma users or to view the contact details of staff members or other student users.
Currently, access to contact details and searching for users are by default possible to any Alma user with Fulfillment roles. Disabling the ALLOW-USERS-SEARCH privilege can prevent access to users list in Manage Patron Services and auto-complete search in same page, but it does not affect the persistent search for users or access to Admin…
77 votes -
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 -
Hide ‘edit’ option from My Library Card > Personal Details for specific user groups only
In Alma you can choose to hide the "Edit" option from the 'Personal Details' under 'My Library Card' for ALL your users by changing the parameter key 'primopatroninfo_updatable' to N
This works fine if all your users are set up as external users who automatically gets their contact information updated from a system outside Alma. But if you set up your students as external users and public users as internal users you will have to choose between letting the students update contact information that will be wiped out next time data is loaded in to Alma or not…
62 votes
- Don't see your idea?