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.
1791 results found
-
Added fine/fee notification
It is possible to schedule a job sending letters for outstanding fines and fees. However, it would be helpful if patrons could get a notification the moment a fee or fine is created aside from this "reminder letter". We would like to have the option to "notify user" when adding a fine or fee.
13 votes -
stallardv@cardiff.ac.uk
Add 'Campus' as an option to display in Citations on Alma
Currently in the citations page in Alma, you can choose to show Course Code, Name, Terms and Number of Participants. We'd like to be able to show the Campus details here too. When working on citations from the various citation task lists, it would be very useful to see whether the citation is from a reading list for our overseas or home campus.
3 votes -
Suggested update to Automatic Due‑Date Adjustment for Early Patron Expiry
At UWA, users receive no warning when their records expire in Alma. If we implemented the Automatic Due‑Date Adjustment for Early Patron Expiry, users would receive an email advising that their loans were due the same day, which is not client-focused.
Would it be possible to have a configurable loan grace period, so that loans would be due a certain amount of time after user expiry?
8 votes -
Alma Analytics: Cost per Use - calculate use on all platforms
When using Alma Analytics for cost per use reports, only use from the chosen COUNTER Platform are calculated. In part, this is because in Electronic Portfolio Editor, only one COUNTER Platform may be chosen. This is a problem for our Ovid Journal collections as Ovid records use across three platforms. We would like all use to be calculated in Alma Analytic Cost per Use reports, whether this be solved by allowing us to choose multiple platforms in Alma or have Alma Analytics calculate all use, not just the COUNTER Platform chosen in Alma.
26 votes -
Add RBMS CVRMC (Controlled Vocabulary for Rare Materials Cataloguing)
We would like to suggest adding RBMS CVRMC, (Controlled Vocabulary for Rare Materials Cataloguing) to the authority vocabularies in the resource management configuration.
The vocabulary comprises terms specific to the needs of the rare materials community and combines six separate, print thesauri used for recording the genre and physical characteristics of cataloged materials
RBMSCV is available at the Library of Congress' linked data service https://id.loc.gov/vocabulary/rbmscv.htmlWe add the terms at present in a 655 _7 $a heading $2 rbmscv but they do not authorize when we hit f3
Adding CVRMC terms would help greatly with user needs when searching PRIMO
1 vote -
Preserve “Requester Note” when converting Purchase Request to Resource Sharing Request
When a Purchase Request is converted to a Resource Sharing Request in Alma, the system automatically adds the note “Request has been converted from purchase request” to the new Borrowing Request, and the original “Requester Note” is not retained. This requires staff to manually copy the original note into the Borrowing Request to preserve patron context and avoid missed information. Automatically carrying over the “Requester Note” would make the conversion process faster, more consistent, and less error-prone.
87 votes -
reminder
I understand that there is an intention to add Reminders to the task widget. Since the reminder is at the bibliographic title level, would it be possible to add a "flag" that would display when retrieving records? This would provide a visual cue to staff that there is a reminder for this record, and they could investigate further if needed.
1 vote -
Request for Enhancement: Add a search bar and facets to itemized sets in Alma
Description:
In Alma, logical sets let you search inside the set and use facets. This makes them much easier to work with, especially when the set is large.Itemized sets are treated as a static list of records, so they do not support internal search or facets in the same way. Even though this is how they are designed, it makes them harder to use in practice. When a set is large, it becomes difficult to find specific records or understand what is in the set without a lot of manual effort.
Suggestion:
Add a search bar and facets to…16 votes -
Request for Enhancement: ALMA Records Customization Functionality
Currently, the Records Customization feature in Alma only allows for configuring the visibility and order of fields, but does not support modifying the structure or composition of individual fields.
We would like to request an enhancement that enables institutions to customize the structure of each field according to their needs.
For example, the Creator and Imprint information are currently displayed as a single combined field. We would like these to be separated so that institutions can independently select and display only the elements they require.
3 votes -
maria.nordgren@umu.se
When adding a portfolio from CZ from a collection that is not in your IZ. The whole collection is imported to IZ. We use this for moving a portfolio from one collection to another. Example one portfolio is missing in ClinicalKey Dentistry, but is found in ClinicalKey Books, I can activate the portfolio, but then the ClinicalKey books collection is transfered to IZ. We would like to be able to activate a single porfolio without that the collection is imported
6 votes -
Rename Fulfilment Request status "READY" to either "PENDING" or "INQUEUE"
Currently Fulfilment request status READY - is misleading given its definition is
"The request is still in the queue, not activated yet. Currently, there is no available item to fulfill the request."It does not even mean "ready to be requested" given the request has been made already.
Note also "READY" is displayed in the User Request area in Alma, and this can be confusing to the client facing staff. They have to understand and be able to explain to clients that their requests are NOT READY yet despite the Alma labels says READY.
See Case#10569064
1 vote -
Enable adding labels in bulk to title-level records for large sets
During large-scale projects such as: weeding/deletion, we need to mark many records with a label indicating their status.
Current Limitation:
Labels cannot be applied efficiently to large numbers of records; it is limited to 50 at a time.Requested Enhancement:
Provide a bulk mechanism to add labels to title level records beyond current limits.Benefit:
Improves efficiency, reduces manual work, and supports large collection management workflows.77 votes -
RS Pick Slip configuration
Currently the FUL Incoming Slip Letter can only be configured to display the Library of Congress classification, and not the Item Permanent Call Number. This means the pick slip generated in the Resource Sharing lending workflow shows an incorrect call number.
Please make the Item Permanent Call Number available as a configurable field in the FUL Incoming Letter, so that pick slips display the correct shelf location.
1 vote -
ellipses in specific contexts(三点リーダー“…”)
In Japan, we use ellipses in specific contexts.
Please adjust both Cloud App and Alma so that typing three middle dots and converting them results in an ellipsis (“…”) with three dots centered.
*Note: This is not three periods (“...”).I believe this issue is likely caused by the font type, language settings, or similar factors.
Thank you for your cooperation.3 votes -
madelene.turnbull@otago.ac.nz
Add ability to include or exclude specific location codes in the Retention / Deselection workflows
Currently the retention and deselection workflows only allow selection for inclusion at the library level. It would be helpful to be able to include or exclude specific location codes within a library's collections, for example it would be helpful to be able to exclude from deselection recommendations all titles in our Special Collections location codes. Currently the only way to do this is to run the search, export results to excel then filter by collection code.
3 votes -
We would like to request an enhancement to Alma.
When a user reports that a borrowed item has been lost, and the item is not returned within a certain period, we would like to have a function that allows the circulation staff to change the item’s status from "Lost" back to "Loaned."
6 votes -
DARA recommendations for autoholdings should ignore open access collections
DARA recommends using autoholdings. However, it does so even when it really shouldn't recommend it. Situation: an institution has activated an open access collection, and doesn't subscribe to anything from that vendor, but DARA recommends using that vendor's autoholdings, which confuses librarians. The correct operation of the DARA recommendations would be to ignore open access collections.
3 votes -
Enhance Analytics Support for Authority Records (Additional MARC Fields)
We would like to propose an enhancement to Alma Analytics for authority records.
Currently, Alma Analytics provides limited support for authority fields, such as 1XX and 373. However, many other important MARC authority fields are not available for reporting and analysis.
We recommend adding more authority fields to Analytics, including but not limited to:
046 – Special coded dates (commonly used for birth and death dates of authors)
372 – Field of activity
374 – Occupation
375 – GenderThese fields are widely used in authority records and are highly valuable for data analysis, authority control, and research purposes.
Providing…
1 vote -
Add full MARC records to CZ for Mohr Siebeck
This collection of Mohr Siebeck eBooks contains many titles with metadata that are too poor and need to be enriched. Could you please follow up with Mohr Siebeck?
MMS-ID: 9919375751300041
Thank you for your intervention!
Kind regards,1 vote -
Counting Searches in Alma Persistent Search Box
We know that the usage actions in Primo VE can be retrieved in Analytics to measure patrons’ various search actions. This helps library identify the strengths and limitations of current Primo VE user interface, and review it to better meet patrons’ needs.
However, there is currently NO way to retrieve search counts from Alma’s search persistent box in Analytics.
Counting Searches in Alma Persistent Search Box
Library staff often use the Alma persistent search box to search for records for various library operations—for example, locating a bibliographic record to create a PO line—across the institution and community zones (and the…
2 votes
- Don't see your idea?