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.
- or
No existing idea results
- ~ No ideas found ~
1780 results found
-
Community-Managed electronic collections: Add several portfolios to one title
In Community-Managed electronic collections, it is not possible to contribute a second portfolio to the same title that is pointing to a different URL. Use case: Both URLs are valid, both contain copies (in part) of the journal. It would be nice, if the contribution only gets blocked, if the URL of the newly contributed portfolio is identical to the existing one.
34 votes -
extended export to single file rather than multiple files for large collections
We would like to be able to run an extended export for large local collections that have more than 50,000 portfolios and receive a single file, rather than having to spend time manually pasting them together in excel to actually use them. the arbitrary limit serves us no purpose and adds steps to our workflow. we have very limited tools to manage local collections and this is something that has bothered our staff for years.
6 votes -
All NZ cataloger activities must be collected in Alma Analytics
The Cataloger activity report in Alma Analytics displays only partial activity when catalogers work in the Network Zone. For example, it may display a delete action but omit record modifications, leading to incomplete tracking of cataloger actions. It is included in Known Issues (https://support.proquest.com/s/known-issues/knowledge-detail?recordId=kA2QO0000000jZp0AI) with status "No Further Action".
163 votes -
Make Existing Record Primary When Merging via Search Resources
When merging records through Alma’s Search Resources, make the existing Alma record the Primary and the incoming external record the Secondary.
Currently, when bringing in external records, Import and Integration Profiles treat the existing Alma record as Primary, but Search Resources makes the external record Primary. This inconsistency forces libraries to maintain two opposing sets of merge rules, depending on how the record enters Alma.
Making the Alma record Primary in Search Resources would align the behavior with other workflows. This could be configurable or at least opt-in so libraries can adjust their merge rule settings in the External Search Resources configuration to coincide with the change.
Benefits:
Simplifies workflows by allowing a single set of merge rules.
Reduces user confusion, since rule descriptions will match consistently across scenarios.
Provides consistency in the Metadata Editor, where the record on the left will always be the Primary.When merging records through Alma’s Search Resources, make the existing Alma record the Primary and the incoming external record the Secondary.
Currently, when bringing in external records, Import and Integration Profiles treat the existing Alma record as Primary, but Search Resources makes the external record Primary. This inconsistency forces libraries to maintain two opposing sets of merge rules, depending on how the record enters Alma.
Making the Alma record Primary in Search Resources would align the behavior with other workflows. This could be configurable or at least opt-in so libraries can adjust their merge rule settings in the External Search…
8 votes -
Please add more "View only" roles to Alma
Alma already offers some "View only" roles:
- Fund-Ledger Viewer
- License Viewer
- Course Reserves Viewer
but there is still a need for more.Please add the following:
- Invoice Viewer
- Purchasing Viewer
- Physical Inventory ViewerThanks!
128 votes -
Sort "Manage sets" by modification date
It would be nice to be able to sort "Manage Sets" by when the set was modified. The current options only allow sorting by name and creation date, which can make it frustrating to find frequently used sets that aren't at either end of the alphabet and aren't super old or super new, especially when you have many sets. Sorting by modification date would provide an easy way to access the sets you are recently working on.
3 votes -
Display personal metadata editor history of opened/edited records
Currently in Alma's All Titles search you can see a list of records you have previous looked at, but it would be helpful in the metadata editor if you had a list of records that you have opened recently. Even a list of 5-10 would helpful.
8 votes -
In "Create request" for a patron, is it possible to add the item barcode as an option for searching?
2 votes -
Zeros after the decimal point disappear in the price in order line items
The problem occurs when editing an order line item where the price contains zero or two zeros after the decimal point (e.g., 31.90, 37.00, 24.80). The price was entered correctly in the Acquisition Department in the format with a decimal point and two characters following it.
When the copy was edited in the target library to add the missing data, the following message appeared during saving:
Confirmation Message - Please note the following: The value in the "inventory price" field does not match the defined structure. Are you sure ypu want to perform this action?The system automatically “cut” the zero or both zeros (i.e., to the format 31.9, 37, or 24.8), and only after re-editing the price was it possible to correctly save the changes made to the copy.
Would it be possible to make a correction so that the zeros after the decimal point do not disappear from the price?
The problem occurs when editing an order line item where the price contains zero or two zeros after the decimal point (e.g., 31.90, 37.00, 24.80). The price was entered correctly in the Acquisition Department in the format with a decimal point and two characters following it.
When the copy was edited in the target library to add the missing data, the following message appeared during saving:
Confirmation Message - Please note the following: The value in the "inventory price" field does not match the defined structure. Are you sure ypu want to perform this action?The system automatically “cut” the…
136 votes -
Add the option to edit or delete recorded responses for trials
It is not possible to edit or delete a recorded response for trials. In some cases, customers would like to test surveys before making them public to ensure everything is working properly and then delete the test responses.
It is needed to add a functionality that allows to remove individual answers.0 votes -
Intercept pickup location from ALMA and display different name in Primo
In Primo, the pickup location dropdown list currently displays our library name. This value comes directly from the Alma library name configuration.
Please create a function to intercept this value and display it instead as “Library Circulation Desk.”
4 votes -
Report a Problem Letter to include a user_email variable in emailFrom so that our ticketing system can auto-assign issues to user
The Report a Problem Letter already has a variable that used in the emailSubject label called category_name.
We'd like a user_email variable in the Report a Problem Letter that can be used in the emailFrom label
If we can insert the user email into the from field we can send the email to our ticketing system which will assign it to our user in the system automatically saving staff time.
2 votes -
Customize search indexes for any Holdings field and subfield
The current Holdings indexes skip several valid fields, such as the 347 and 562 fields. The ability to index these fields (especially the 562 field) would help find records with local information that is only recorded in the holdings record.
Additionally, the ability to index any field and subfield combination would allow libraries to use custom subfields within a valid, relevant field (e.g., a 541$g for a non-public Gift Of note).
5 votes -
Acquisitions: Add the possibility to contact the vendor when manually closing a POL
We need a way to discontinue a standing order before completion and to inform the vendor about it via email directly from Alma.
"Cancel" does have the possibility to inform the vendor about the cancellation. However, by cancelling a POL, Alma is designed to completely undo the order by detaching already received items from the order and cancelling active requests on these items (this caused us huge trouble in the past, so we can’t use it).
"Close" is currently lacking the possibility to contact the vendor via email directly from Alma.
So we suggest that an option to contact the vendor via email, similar to the existing option of “Cancel”, is added to “Close”.We need a way to discontinue a standing order before completion and to inform the vendor about it via email directly from Alma.
"Cancel" does have the possibility to inform the vendor about the cancellation. However, by cancelling a POL, Alma is designed to completely undo the order by detaching already received items from the order and cancelling active requests on these items (this caused us huge trouble in the past, so we can’t use it).
"Close" is currently lacking the possibility to contact the vendor via email directly from Alma.
So we suggest that an option to contact the…38 votes -
Enable reporting and filtering in Alma Analytics based on specific MARC indicator values by exposing them as separate, filterable fields
Please consider enhancing Alma Analytics to:
• Include MARC indicators as separate, filterable fields in the data model.
• Allow reporting and filtering based on specific indicator values for any MARC tag.
This would greatly improve our ability to manage bibliographic data quality and streamline workflows that depend on precise MARC structure.6 votes -
Información del campo-Editor de metadatos
En los diferentes campos de un registro en el editor de metadatos la información del campo podría estar en castellano.
1 vote -
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 -
Let CDI Link in Record URLs use linking parameters and additional link syntax for OpenAthens libraries
THis idea would go along with https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/49980354-collection-level-authentication-method-options-for. We need to be about to specify a customer ID for CDI Link in Record URLs because if you are an OpenAthens library, Proquest and Gale links have to have a customer ID in them or they don't work. So for example for Proquest link in record URLs, Primo should be able to append &accountid=XXXXX to the end of the URL and put in the customer ID we specify in the linking parameters for Proquest.
14 votes -
Ability to add an accessibility note at the electronic collection level
Because some MARC bibliographic records may be attached to e-portfolios in multiple e-collections, adding a 532 in the MARC record may not apply to all e-portfolios. Many e-collection providers will include accessibility information on their site. Perhaps an accessibility note could be added at the e-collection level separate from the Authentication and Public notes.
7 votes -
Enhanced Auto-Tagging of Digital Resources via AI for Alma & Primo
I propose adding an AI-based auto-tagging feature in Alma that can analyze content (PDFs, images, articles) and automatically assign metadata tags (subjects, keywords, disciplines). These tags would then flow through to Primo for better discoverability. The system could also suggest tags to cataloguers, which they can accept, edit, or reject.
Solutions like OutrightSystems have already demonstrated how AI can streamline feedback and content classification, and a similar approach applied to Ex Libris platforms could transform metadata management.
Problem / Pain Point:
Many digital collections are under-tagged or use inconsistent metadata, making search and discovery harder in Primo.
Manual tagging is time-consuming and error prone, especially for large collections (legacy content, scanned documents).
Users often miss relevant items because the items weren’t described with optimal keywords or subject headings.
Proposed Solution / Features:
Integrate a machine learning model (or leverage existing NLP tools) to extract keywords, themes, and subject headings from content.
Provide a UI in Alma for reviewing suggested tags before finalization.
Allow bulk processing for large collections.
Enable feedback loop: the system learns from curator edits to improve future suggestions.
Provide analytics dashboard: tag coverage, accuracy, suggestions accepted vs rejected, gaps in metadata areas.
Benefits / Value:
Improved discoverability in Primo: patrons can find more relevant items, even when original metadata was sparse.
Time savings for cataloguers and metadata librarians.
More consistency in tagging across collections, reducing metadata variation.
Growth in usage of digital content, because better metadata drives better search results and visibility.
Inspiration from companies like OutrightSystems shows how automated insights can enhance user experience and decision-making.
Target Components:
Alma (metadata/cataloguing), Primo (search / discovery)Additional Notes:
Could start with a pilot: select a subset of collections (e.g. digitized dissertations or historic archives) to test.
Privacy and copyright need to be considered — ensure content used for analysis is allowed; sensitive content handled appropriately.
Consider working with existing metadata schemas (Dublin Core, Library of Congress Subject Headings, etc.) so tags align with standards.
Know More:- https://www.outrightsystems.org/
I propose adding an AI-based auto-tagging feature in Alma that can analyze content (PDFs, images, articles) and automatically assign metadata tags (subjects, keywords, disciplines). These tags would then flow through to Primo for better discoverability. The system could also suggest tags to cataloguers, which they can accept, edit, or reject.
Solutions like OutrightSystems have already demonstrated how AI can streamline feedback and content classification, and a similar approach applied to Ex Libris platforms could transform metadata management.
Problem / Pain Point:
Many digital collections are under-tagged or use inconsistent metadata, making search and discovery harder in Primo.
Manual tagging is…
1 vote
.jpg){kind=link}
- Don't see your idea?