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.
1733 results found
-
Add "Send Query to Patron" option to Digitization requests menu
Currently there is not option to ask the patron about a current Digitization request. These requests are often submitted with little or vague information and a way to contact the patron for clarification is needed. The "Send Query to Patron" option for this purpose is included under "the ellipses" for Resource Sharing requests. Why does it not appear for Digitization?
55 votes -
Activate recalls by user group
Allow libraries to modify recall rules based on each user group.
Currently recalls can be turned on or all for all user groups only. It would be beneficial for many libraries, especially academic, to be able to modify recall rules by user group. As an academic institution, we would like the ability to allow certain patron groups to recall books, but block recalls by our visitor and community patrons, or patrons at other institutions. This would help prevent situations where a student working on a project or thesis from having their books recalled by a visitor patron who would like…
54 votes -
Validation check for outgoing vendor emails
Please add a validation check for outgoing vendor emails. Otherwise a spelling mistake might go unnoticed.
54 votes -
Notes Tabs not in Analytics
We would like to be able to retrieve all the details in the Notes Tabs for Borrowing and Lending requests via Analytics. Currently, only the Request Note is retrievable.
54 votes -
Waitlist functionality for short-term loans
It would be helpful to have a waitlist functionality for short-term loans (i.e. for reserve items). This would allow patrons to put their name on a list to be next in line once a short-term loan item has been returned. Alma would send an email/text to the patron when the item is returned telling the patron they have a specific window of time (e.g. 5 minutes, configurable by the institution) to check out the item. During that window of time no other patrons can check it out. After the window of time has expired the next person on the waitlist…
54 votes -
don't mark zero usage SUSHI reports as invalid
When SUSHI harvests a report that has no usage for the selected dates, it is labeled as invalid. This is misleading. As long as all the correct headings for the report are in place, the report should be considered valid.
54 votes -
Customize display of fields in Alma Article request form
We would like to display the fields in the Alma article request form in the following order: Journal name, year, volume, issue, pages, article title, article author, and issn - and not in the order these fields are currently hard-coded (e.g. author initials splits volume and issue, and publication date is at the end of the form)
53 votes -
Add User Note Creation Date and Creator as query-able fields in Anayltics
Please make it so that we can create analysis in analytics that display the creation date and creators of user notes. Both fields would be very useful filters for us.
53 votes -
Description Templates -- Create reference table for months and seasons
Hi,
I'm wondering if it would be possible to create some sort of reference table for the months and seasons. This would be for use in the description templates. Then we could use MM, MON, and MONTH (for example), to indicate whether the two digit code in the particular Chron field should be displayed numerically, as the standard abbreviation, or spelled out.
Having such a table would mean that for each type of pattern a single template could take the place of the 12 or 16 we have to create now.
This would be much more efficient right off the…
53 votes -
Allow staff to override auto return when a borrowing request is received after needed by date has passed or request has been cancelled
When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.
Likewise, Alma automatically updates borrowing reqeusts to returned when they've been cancelled…
53 votes -
FUND / Ledger facet missing from PO Line user interface
All PO Lines has multiple facets but FUND or Ledger is not one of them.
Funds, both allocated & summary, are fundamental to purchasing and we'd like to be able to filter the PO Line display by these variables.
Please add a facet in the All PO Lines user interface for FUND.
53 votes -
Improve the ease of reordering the Online Services Order and General Electronic Services Order tables
Currently, items in the General Electronic Services Order and Online Services Order tables need to be moved using up and down arrows. This can be very time-consuming if the tables contain numerous items. It would significantly improve the ease of use i, the items in this list could be resorted either through drag-and-drop or by moving a given item to a numbered slot in the table (similar to the Netflix interface).
52 votes -
Location color schemes
I would like to make it an option to change the color scheme of the ALMA top ribbon/possibly sidebar to differentiate locations especially between Main Circulation Desk and Acquisitions, of which I have to switch regularly. This would save me time spent on correcting errors due to being in the wrong location for a particular procedure.
52 votes -
Establishment of stronger passwords for the creation of internal ALMA/Primo users
As an universities consortium from Galicia, CISUG, we are representing three member universities. Our univesrities have a security problem in the management the keys for internal users in Alma.
Alma's internal authentication system allows the user can create complex passwords, but this should be a requirement, not the user's responsibility as to whether they are secure or not.
Our request is that:
ALMA enforce passwords to be at least 8 characters long, and allow the system administrator to increase that minimum.ALMA allows to force mixed case, numbers, and special characters to créate paswords.
…Alma checks that the password is
52 votes -
Move requests and temporary locations - option to flag for processing, etc.
At present the item move requests sometimes work too seamlessly. Especially for items that are onloan when the request are made (or the item is restored to its permanent location). This is an issue when the items need manual intervention, e.g. relabelling. Items go through the process without being flagged unless another process is used, e.g. a work order or fulfillment note.
It should be possible to flag items for manual intervention when they arrive at their new or original location. A message on the lines of 'Move Request: check labels etc.,' in the manner of a fulfillment note.
52 votes -
Persistent User Group Data in Borrowing Requests Subject Area
We would like to request that the Borrowing Requests subject area in Analytics captures and stores the patron's information (specifically the User Group) at the time of the transaction, rather than pulling the current status from the user record.
Currently, historical reports on borrowing requests reflect the requester's present-day group. If a student who made a request three years ago is now a staff member, or if their record has been deleted, the historical data is either overwritten or lost. This makes the data entirely out of context and renders historical analysis and longitudinal reporting impossible.
In the Fulfillment subject…
52 votes -
Option to set return time to 15 minutes before closing
We issue equipment such as laptops to students. These must be returned before the library closes.
In the current TOUs it is only possible to set the due time to closing time. However, we really need to check all equipment is back, and therefore would like to set the due time to 15 mins (or 30mins) before closing.We would also do this for short loans, as these require being returned before the library shuts. Otherwise the student will receive fines.
Changing the closing time of the library would be too confusing for everyone
51 votes -
Common link between a POL and a License (for updating collections)
A POL has a licence connected to it. It would be great if when adding that POL to an Alma Collection, that the connecting licence would be automatically added to the collection as well. And working in reverse, when adding a licence to an Alma collection, it would be nice if the POL connected to the licence was automatically added to the collection as well (thus saving time adding two things to a collection, when they are already related).
51 votes -
Make Push Selected to MDE button available for Itemized Sets
'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…
51 votes -
Allow request-type webhooks to be triggered only under certain conditions
We would like the ability to configure request webhooks such that they are triggered only when certain conditions are met. Request webhooks for patron physical item requests include the user’s primary ID and the title they have requested. This type of circulation information should in most circumstances stay within the library and not be shared with third parties. But it may be necessary to enable a third-party integration in order to provide needed services, such as a smart locker delivery service. Currently, request-type webhooks are triggered by any request in Alma, regardless of request type or destination. We would like…
51 votes
- Don't see your idea?