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.
1983 results found
-
Add Fulfillment Note to the New 2025 Manage Patron Services Table Customization
We use the Fulfillment Note field to track Lost Items by recording the patron ID, replacement cost, and billing date to our Finance department, allowing us to efficiently identify returned lost items. Additionally, we check out lost items to a dedicated patron record to facilitate tracking, reordering, or withdrawal over time. Adding this feature to the Manage Patron Services Customization Table would help ensure these notes are consistently recorded.
15 votes -
Additional Exportable Fields
When viewing electronic collection results, after a search, we would like the ability to export several additional fields: Alternative Title, General note (electronic collection), and General note (Service). This would allow our consortium to do some real-time analysis of how multiple collections are setup which would save significant time over having to click into each electronic collection individually.
41 votes -
NR - Normalization rules editor -- fix display to ltr + use monospaced font
1.
Currently there's a problem with the NR editor when there are too many rtl characters (Hebrew, Arabic, etc.) in the NR, the whole display changes to rtl. This renders the NR unintelligible and makes editing it in Alma impossible -- you have to edit it outside AlmaWe would like the direction of the NR editor to be fixed to ltr regardless of the composition of the characters used
2.
We would like to have the NR editor use a monospaced font. This would make the code neater and easier to read24 votesHello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed to handle complex normalization tasks and offers the flexibility of a full programming language, enabling advanced data manipulation. It will complement our existing normalization rules based on DROOLS, preserving all of its current capabilities.
Would the addition of this new type of normalization rule address the requirement outlined in this idea?
-
Additional Local Parameter fields in Local Authorities dimension
There can be up to 100 local fields 9xx in the "Local Authorities" and none of them can be retrieved in Analytics. Could it be possible to have, at least, the same number of "Local Params" as in the he "Physical Items" or the "Titles" table?
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/080Analytics/Alma_Analytics_Subject_Areas/Physical_Items#Local_ParamThanks.
17 votes -
Display Open Access Indicator based on Setting at the Portfolio Level
Currently, the Open Access (OA) indicator displays in Community Zone records when the record contains a 506 field with the following formatting:
506 0_ $f Unrestricted online access $2 star
Records in the Directory of Open Access Journals (DOAJ) collection are automatically enriched with this data, but not records in any other collection. The rationale is that the OA indicator may appear on records that are not available as OA in all collections, leading to a confusing display. However, this can lead to cases where institutions do have OA access, but cannot display the OA indicator.
To avoid both of…
59 votes -
Post download links for digtization requests to user's Primo account
Currently, Alma will post a download link to the user's Primo account when a resource sharing request is filled digitally. Alma does not post a download link to Primo when a digitization request is filled. This difference can be confusing for users, so it would be very helpful if download links for both resource sharing and digitization requests were posted to the user's Primo account.
34 votes -
The ability to save and release multiple records at once from the MD Editor
We would like to have the option to save and release more than one record at a time in the MD Editor. I often have 20+ records open and it would be much more efficient to be able to save and release them all at once instead of having to do each one by hand. It would also be great to have the option to either check which records you would like to save and release or select all.
Thank you! 😊
19 votes -
Add Alternative Title to Alma Analytics
Adding the Alternative Title for an electronic collection would allow us fully use Alma Analytics and not need to maintain separate reports that are created outside of Alma. As a consortium, this would also allow more information sharing with our members and more efficient troubleshooting and maintenance.
40 votes -
Please add restrict request function for fulfillment network requests in Primo VE between institutions.
We are a library consortium facilitating interlibrary loans through a fulfillment network with Network Zone, rather than AFN.
It allows patrons to find items from other institutions directly and request them. Our goal is for patrons of Institution A to use Institution A's Primo VE to request books from Institution B.
If Institution A has the book available for borrowing, requesting the book from Library B will not be possible.
Implementing the above feature in Alma to restrict requests in this manner would not only save shipping costs but also reduce waiting times for patrons.
We previously submitted this requirement,…
118 votes -
Ability to surface details of recipients/subscribers to Scheduled Analytics Reports
Allow for export/inclusion of subscriber details when exporting list of scheduled reports or creating Analytics reports from Analytics Usage Tracking subject area or Analytics Objects subject area.
I am trying to do an audit on recipients/subscribers of our Scheduled Reports in Alma. The aim is to streamline who receives which reports/ remove staff who have moved roles and/or staff who have left the institution.
Currently neither the extract of Analytics Objects from Alma or any of the Analytics Subject Areas include details about the recipients/subscribers and I feel this would be very useful for auditing/access control.
35 votes -
Overlap and Collection Analysis reports enhancement
As a collection development librarian, I propose allowing the selection of multiple collections we want to compare. Repeating the same process for different collections is time-consuming. For example, we have 8 active IEEE collections, and I have to match them one by one with other collections.
Also, is it possible to re-run the Overlap analysis report if I forget to include some collections, instead of creating a new analysis each time?18 votes -
Additional "Suppress from FRBR/dedup" option and display
When viewing a bib record, the pop-out information to the side of the screen lists whether or not the bib is suppressed from discovery and suppressed from search. It would be helpful if this info also contained whether the bib was suppressed from FRBR/dedup.
Additionally, when you edit a bib record, you can select "Suppress from Discovery" and "Suppress from External Search" under the Record Actions dropdown menu. It would be helpful if there was also a "Suppress from FRBR/dedup" here.
46 votes -
Limit number of resource sharing partners in a borrowing request's rota
We sometimes see instances where a problematic resource sharing requests are sent to dozens of partners before they're cancelled or go unfilled. It would be very helpful if we could somehow limit the number of partners that appear in a request's rota. Since we would always want to include a lender of last resort like ILLiad or WorlsShare ILL as the final partner, it would probably be best to allow us to limit the number of partners from a specific rota template that can be added to a rota.
26 votes -
Add Electronic Service Information Update Job
Electronic Portfolios and Electronic Collections each have an Information Update job in Alma. Electronic services need the same functionality because they are also affected in bulk by changes.
Job Name: Change Electronic service information
Job Description: Update Electronic service information for a set of Electronic services
Job Content Type: Electronic Service
Job Type: Information UpdateUse Case: ProQuest began requiring a value for the CLIENTID parameter in the Linking Parser Parameters section of all ProQuest electronic services. With over 50 ProQuest electronic collections activated, that meant that over 50 electronic services had to be manually edited one at a time…
45 votes -
Add a "Pick up location" line under the "Pick Up Requested Resources" columns
For institutions with multiple campuses that share items, there is no way to see what the pick-up location for an item is on the Pickup Requested Resources page. you must export the data to excel, print it out, process the hold, or search for the item's request separately. This creates a lot of unnecessary steps for such simple information and makes it difficult for institutions that track item movement between campuses. My suggestion is to add a line in the columns under each request that states what the pick-up location is. View files to see example. Thank you
18 votes -
Please add 3xx field support in Bibliographic Details dimension of Alma Analytics
Currently there are many fields in the 3xx range which are not supported OTB in the Bibliographic Details dimension of Alma Analytics.
We have mapped 300 to a Local Param several years ago, but we are stymied in our work updating to RDA consistently as the desired foundation for then considering LOD work in BIBFRAME, given this is a key area with many 3xx fields utilised such as 334, 335, 336, 337, 338, 340, 344, 345, 346, 347, 380 and 382.
Although the number of Local Params increased in 2024 finally from 10 to 30 we use many of these…30 votes -
Include more than 30 or an unlimited number of local parameters in Alma Analytics
We find Analytics to be very powerful, but we are hampered by its limitation to only selected MARC and a limit of 30 local parameters.
We hope ExLibris will include more or an unlimited number of local parameters in the future.
When we signed up for Alma, our team expected all MARC bib codes would be available in Analytics and they are not. In addition, we have defined several local fields and must assign them a local parameter to be able to output them in Analytics. We have been rationing the 30-alloted local parameters ever since.
31 votes -
Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)
Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)
1) Add Vendor Type: Example: I want to analyze the vendor file based on vendors that are only Access Providers/Licensors and not Material Suppliers, or just Material Suppliers.
2) Add Vendor Accounts as output, including options to output Payment Methods. Example: we recently had a campus financial system migration, and I want to isolate those vendors who pass through the ERP export vs. Credit Card vendors. Similar to Bank Transfers - if my campus has a change in policy that needs communication, I want to be able to…
29 votes -
Enable us to display items in an "Unavailable" location type as Unavailable in Primo
We need the ability to show items that are assigned to a location with Type = UNAVAILBLE to show as unavailable in Primo
The primary use cases that prompt this idea are:
1. A library is closed for renovation and the items are inaccessible to staff and patrons, but the items must still be discoverable so that patrons can be directed to Resource Sharing in Primo.
2. Portions of a collection are temporarily inaccessible to staff and patrons, and the items are assigned to a temp location, but must still be discoverable so that patrons can be redirected to Resource…79 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.
15 votes
- Don't see your idea?