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.
1690 results found
-
Don't Require Clicking 'Done' to Trigger Loan Receipt Notices
Currently, staff need to click done after checking out items to a patron to trigger loan receipts. This is an unnecessary step and should be eliminated. Instead, trigger receipts when an item is checked out, much like how returned item notices are triggered.
18 votes -
Ability for fulfillment staff to renew patron loans from other institutions under network activity in Alma
Our consortium would like circulation desk staff to have the ability within Alma to renew items on loan from other institutions from under a user's network activity tab (renew all and renew selected, though renew all being more helpful if both are not possible).
Currently, only the user has access to a renewal option via their Primo VE My Library Card.
74 votes -
Move general email feature outside of the User's form
The General Email function is currently located inside the form for updating general information in the user record.
If there are any problems with missing mandatory data in the form then the email cannot be used at all.
Since it is unrelated to user general information I would suggest that the Send Message function should be located outside of the user data area perhaps up near the buttons "Toggle Account Type", "Open for Update". (See screenshot)
Additionally, the general mail could perhaps be added to the letters that can be sent from "Manage Patron Services"I would also support greater…
19 votes -
Merge Patron Accounts API
Add an API endpoint that provides a programatic interface to the merging patron accounts functionality.
34 votes -
Metadata Editor should add the year automatically to the 866 field
Currently the Metadata editor does not add automatically the year to the 866 field. If we want the year to be in our 866 we have to add it manually. Actually this is the only way our patrons can see the year in Primo.
69 votes -
Relay that job report gives real time
We have more than one jobs that start at certain time and ran for long time (more than 10 hours) but reports the job ran only for about 3 hours.
You can see SFC #00795696 for example.
My idea is to get the real times it took a job to run from start till end19 votes -
Get auto-renewals dates back into Analytics
Since the recently released August version, Analytics does not longer show the auto-renewal date due to a mentioned performance improvement on the nightly job. Please consider rolling back this change as it actually makes it impossible to get how many auto-renewals were made on a certain day in the past, since the only date we currently have is the Last Renewal Date which is updated every time the job runs. We virtually lost our auto-renewals log integrity.
I know we still have this Last Renewal Date, the amount of auto-renewals and the Loan Date, and we could easily calculate the…
66 votes -
Permanent collections
Colecciones permanentes:
Si un título tienen todos sus ítems asignados a una colección permanente de documentos perdidos, extraviados, descartados, etc. , el sistema Alma debe evitar que el registro se recupere y visualice a través de Primo, esto a fin de que los usuarios no visualicen un recurso que no tiene la biblioteca y a fin de evitar de realizar otro proceso de cambio.Permanent collections:
If a title has all its items assigned to a permanent collection of lost, missing, discarded documents, etc. , the Alma system must prevent the registry from being recovered and viewed through Primo, so…93 votes -
Fulfillment Configuration Utility for resource sharing
I would like Fulfillment Configuration Utility to also work for Resource Sharing. Or a separate service for RS.
It is invaluable in troubleshooting.
This service could be a light in the dark cave that is RS.
18 votes -
Fulfillment Network: when a patron loses a book from another institution, allow for automated blocking of that patron at all institutions
So in other words, when a patron from institution A checks out a book from institution B and then Alma marks it is lost, it would be great if Alma could automatically place a consortial block on that patron so they are unable to check out books from any institution. We currently have this working as a custom integration using the Alma API, but it would be great if this were native functionality in Alma.
50 votes -
make "test access" work when direct linking is enabled
The "test access" button in Alma does not work when direct linking is enabled in Primo. When trying to test access for an electronic portfolio, Alma loads a blank page forcing staff to click "display in a new window" in order to proceed. We recommend that this behavior be changed so that test access works the same regardless of whether direct linking is enabled.
72 votes -
Allow user preferred pick up location while retaining other options
Currently in the TOU you can allow pick-up at "Any pick-up location" or at" User affiliated Campus Pick-up locations". If the latter is set, only pick-up locations of the user's campus are available. We need an extension to the former rule, that lets the user's preferred pick-up location (a new parameter in the user profile) be selected as default option, while still allowing the user to select a different location when placing the request.
Obviously, the "User preferred pick-up library" needs to be added to the user profile.77 votes -
Ignore call number prefix ($$k) in BROWSE SHELFLIST in Alma
Alma's Browse Shelflist function includes the call number prefix (holdings record field 852 $$k) when generating the browse list. At the University at Buffalo, we use that prefix for oversize volumes, and for a variety of other sub-locations, designations and shelving areas.
As a result, any holdings with a prefix ($$k) does not show up alongside holdings in the same call number range, essentially hiding many titles from staff who seek to browse the shelf list.
An advanced search for specific library holdings, permanent call number type, and permanent call number does not remedy this issue, as it does not…
42 votes -
Add a Description column in the Received Items List page
Subject: Add a Description column in the Received Items List page
As a Receiving operator, I would like to be able to see the description of the item I am receiving in the Received Items List page, without needing to click on Edit Inventory Item to navigate to the physical item editor.
25 votes -
All items loan and hold requests history - in citation view.
The new information available in the 'Other details' tab of items is great, can we also have this information made available in the citation view 'More Info' tab please?
18 votes -
Allow each items’ request policy with specific parameters (location, keyword etc.) to be excluded from the title-level request policy
I believe this is an expansion on this idea https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/31119715-title-level-request-and-item-level-request
But we are dealing with ASRS in our case so I thought it might be a little more elaborate.
We would like to have the option to allow each items’ request policy with specific parameters (location, keyword etc.) to be excluded from the title-level request policy.
Currently we have "No requesting" as our general policy that's applied to all of our items except for the ones in ASRS. The problem is that when items with multiple copies and identical call number exist both at open-stack library and ASRS, the No…
83 votes -
Display the date a work order is created
When a work order is created to put an item in process internally ("Technical Services (CAMS)" or "Show to supervisor" or "Preservation") it would be helpful to have Alma display the date this status change happened.
It could be in the "item history", and/or the "In process" display, and /or in the "list of items." Currently, the receipt date is the last date displayed in these locations, which does not help with locating an in-process item.
88 votes -
Allow customization of close_paid_lost_loans parameter
When the closepaidlostloans parameter to false and lost loans are closed (either manually or through the Close Lost Loans job), refunds/credits are not automatically given to patrons if the item is subsequently found and returned. When setting the closepaidlostloans parameter to true and the lost loan is closed (automatically setting the Lost and Paid status), a refund/credit IS applied to the patron’s account if the item is subsequently found and returned, providing the Lost Loan Refund Ratio is greater than 0.
For libraries that wish to take advantage of this new Process Type, but…
82 votes -
Add location creation modification details to Alma config and Events SA in analytics
Staff should be able to see who and when locations were created and/or modified in both the Alma config interface and in the Events Subject Area.
13 votes -
Prevent change of due-date when the item is under the recalled status.
Or have an alert message of some kind when the due date is being changed.
Because when the due date is changed, the recalled item reverts back to its initial status making it difficult to determine if there are requests placed on the item.228 votes
- Don't see your idea?