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.
93 results found
-
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 -
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 -
Update expiration on roles in bulk
We expire the roles for our student workers each semester, since they don't always come back to us after breaks. It would be nice if there was a way to update the expiration date of selected roles in bulk. I can see the benefit of having granularity of control on individual roles, like if someone's job function was changing after a certain point, but that's not a common scenario. It would be a lot easier if we could change a selection of them all at once, on both the user management screen and in the profile configurations. Even if I'm…
4 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 -
Add Resource sharing requesting to block_request_if_not_loanable
Currently blockrequestifnotloanable only includes holds and bookings for items we own. And digitization requests, if you are using that functionality and not doing the fill locally workflow. We use the fill locally workflow.
A block on resource sharing requesting if people meet criteria of blockrequestifnotloanable block parameters, is essential. We are particularly trying to catch those with fees in excess of a certain amount who won't be able to check out the item they are requesting. With out it we will continue to see two types of behavior. users who cannot check…3 votes -
Requests Operator role in a profile
When you set "requests operator" role in a profile, the Scope and Circulation Desk are mandatory.
It'll be better not to record scope and circulation desk in the profile so they can be set when using the profile.
Currently if you want to set the scope on another library than the one defined in the profile, you have to suppress the circulation desk, then change the scope, then set the circulation desk.3 votes -
Option to remove Alma roles if staff not logged in for X days/months
Having an option to remove Alma roles if staff not logged in for X days/months will help automate the process of identifying and managing inactive accounts, saving administrative time.
We have a lot of staff that change job roles within the institution, but end up keeping their Alma roles unless someone tells us they are leaving the library department. Obviously this idea won't fix all the problems, but it would certainly help with reducing the risk of unauthorized access - particularly for any one that has an administrator role
3 votes -
Remove block type from Update/Notify Users job
Currently in the Update/Notify User job you can add a block type for a set of users but you cannot remove a block type as you can for other parameters. e.g., add role/remove role.
Instead you only have the option to disable a block type which leaves behind an inactive block that may not be needed and which is marked as external data and locked, meaning you have to toggle the record to open to then manually delete one by one.
Therefore it would be useful to have an additional remove block types parameter so we can then remove in…
3 votes -
Field in the user record to serve as flag for anonymization
Create a field in the user record to indicate whether or not to include the patron in anonymization jobs based on their own choices. Ideally, this field can be controlled by the patron directly in their Primo account and we wouldn't need to manage custom forms or customize feeds from SIS systems to manage this. While user groups can be deployed to serve this purpose, for most institutions this is not the desired approach because of the complexities involved.
3 votes -
Patron last activity date updated by leganto use in Alma.
Leganto use is an important information of use. A patron could have zero library use but use leganto and be assigned to multiple courses.
The information is highly relevant for purging users – if you want to purge inactive users there is no way to known if there is leganto activity – and leganto activity is an important reason to not purge a user as library activity is.
3 votes -
Track Active/Inactive status changes in the User History tab
Changes to a user's Active/Inactive status aren't captured in the User Details History tab — even though this is one of the more consequential changes a user record can undergo, directly affecting circulation and access privileges. The History tab tracks a wide range of other field changes; Status just isn't one of them. Right now, figuring out when and why a user went inactive means piecing it together from Analytics, job reports, or institutional memory instead of just checking the record.
There's a real gap between what a reasonable person expects ("History tracks changes to the user record") and what…
3 votes -
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 -
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 -
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 -
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 -
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 -
Show count of items scanned in when using the cloud app of Bulk Scan-In
When I use the cloud app of Bulk Scan-In, I would like to see how many items get scanned in.
3 votes -
3 votes
-
Repository search for Users using Fine/Fee total sum field filter should include transfer fees
Currently when search for users in the repository and filtering using Fine/Fee total sum field it only looks at users with fees with a status of active. The issue with this is that we have other configurations that include transferred fees in active fee field block and that leave transferred fees on users' accounts.
By not including transferred fees when doing this repository search it makes it difficult to find users with transferred fees in real time. Analytics is nice but it is a day behind. It also means that the logical set I created to find users with active…2 votes -
Add more information to the Couse tab on the user profile I Alma
The course tab only provides information about the course code and course section.
If you, like in our case, have a non-descriptive course code containing only numbers you have zero information about what the course is.If a user has multiple courses and you need to remove a course with name *** you have to look up every course to identify which course code is the one you need to delete.
The following columns should be added: Name, start date, end date, Year, Term, academic department, faculty/school – and make them sortable.
2 votes
- Don't see your idea?