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.
1693 results found
-
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.
11 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.
2 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…
1 vote -
Daily fines and fee update into analytics reporting.
Not all of us are able to setup the bursar with our Student integration systems. It would be nice if fine data was updated daily with analytics reports.
3 votes -
Allow customers to select multiple retention reasons for Item records.
Allow customers to select multiple retention reasons for Item records.
As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:
Institutional last copy
Faculty publication
Rare
Committed to some Shared Print program
Digitized material
Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff…
70 votes -
Add Alma Analytics search and reporting features for the new Administrator tab in license records.
Please add Alma Analytics search and reporting features for the new Administrator tab in license records. This will help facilitate management of staff members' assignments, reducing the risk of duplication/ confusion to occur within the workflow. Thank you for your consideration.
1 vote -
Add blocks view to new UI Manage Patron Services view
It would be really useful if, in addition to the user card, system and user notes views, we could also see user blocks. Although our staff see a pop-up when they first open the patron record, once it's acknowledged and the patron view page opens there is nothing else to indicate there is an outstanding user block.
We add a manual user block when an item is made lost, and staff sometimes forget to remove this when returning the item, especially if that person does not then borrow something else but if we had this view it would be more…
3 votes -
Browse Shelf Listing Call Numbers - 852 $$j
Under the current design, browsing shelf listing by 852 $$j is not a supported feature in Alma.
Example:
852 18 $$b SBG $$c 91 $$8 222 B $$h 22/Z 1244 $$= l $$9 00 $$j 22/Hbl E 600 $$9 09 $$x DE-22For the holdings' field 852 subfields $$h 22/Z 1244 and $$j 22/Hbl E 600, the holdings call number “22/Z 1244 22/Hbl E 600” will appear only when the browse term is “22/Z 1244 22/Hbl E 600” or “22/Z 1244,” but not when the browse term is “22/Hbl E 600”.
We need a 'Browse Shelf Listing' that lists ALL…
70 votes -
Remove block type from Update/Notify Users job
Currently in the Update/Notify User job you can add a block type for a set of users but you cannot remove a block type as you can for other parameters. e.g., add role/remove role.
Instead you only have the option to disable a block type which leaves behind an inactive block that may not be needed and which is marked as external data and locked, meaning you have to toggle the record to open to then manually delete one by one.
Therefore it would be useful to have an additional remove block types parameter so we can then remove in…
3 votes -
Use same format for all dates in Analytics
When combining different subject areas (I use the button “Combine results based on union, intersection, and difference operations”, and I am using union) I find that it is not always possible to combine dates.
For example: The date "Event Start Date"."Event Start Time" from Physical Items Historical Events cannot be combined with "Loan Date"."Loan Date" from Fulfillment.
This is due to differences in date formats.
It's hard to predict which parts of Analytics a library would want to combine. So I suggest that the date formats be standardised across Analytics6 votes -
Display of Collections in Collections Lobby in Primo VE
Ability to only display digital collections in the Collections Lobby page of the Primo View, whose profile slot includes the collection’s local scope.
Case number 081133401 vote -
Allow the keyword function to search up permanent call numbers directly
If I enter a call number into the keyword search box, it will often show no results despite showing results when the search category is switched to "permanent call number." Inputting an OCLC into the keyword search consistently yields accurate results, so why can't it do so with call numbers?
8 votes -
With the implementation of AI Metadata Assistant, a streamlined process for exporting records created in Alma to OCLC would be nice.
...and if it could automatically set holdings and loop back to Alma and insert an 035 with the newly assigned OCLC# that would be even nicer.
1 vote -
Add activation note to Get PO Line API
In the Get PO Line API (https://developers.exlibrisgroup.com/alma/apis/docs/acq/R0VUIC9hbG1hd3MvdjEvYWNxL3BvLWxpbmVzL3twb19saW5lX2lkfQ==/) the receiving_note for print acquisitions is accessible. However its' electronic purchase counterpart, the activation note, is not in the Get PO line API response.
Can this field be added?
8 votes -
Allow limits on the number of requests/holds by location
Currently, the number of requests/holds can only be limited by patron. We've experienced instances where multiple requests are placed for a given item in a short span of time (as many as 5!) Patrons do not necessarily realize that if they're the second, third, or more requestor, they are unlikely to receive an item within a semester. We would prefer to limit the number of active requests/holds for circulatable items, the better to redirect subsequent requestors to ILL. Recommend allowing limits on the number of requests/holds by location.
1 vote -
Add function to monitor broken display logic rules
When the name of a collection/interface/service used in a rule changes the rule quietly breaks. The only way in Alma to find out it's broken is to open the specific rule in edit mode, where it says "not listed" next to the changed collection/interface/service. There is no indication in the list of rules and you are not notified when a rule breaks. We have a long list of rules in use so it's difficult to keep track of the broken rules. It would be useful to be notified when a rule breaks or to have a way of monitoring broken…
53 votes -
versions in new interface
In the new interface it is no longer possible to see dates of changes other than the original creation date and who created the record plus the last edited date and who made that change. Please reinstate the ability to see more version change dates without editing the record so that users who do not have the Cataloguer role can see this information in view-only mode.
1 vote -
Posibilidad de discriminar campos para cosecha de registros por OAI
No logramos configurar la cosecha por OAI para que solo tome los datos del campo dc.source xml:lang='es-ES' y no tome los datos del campo dc:source xml:lang="en-US"
Al intentar realizar la regla, en formato oai_dc, no se encontraron parámetros para poder segmentar/discriminar los campos.
Ver caso 079718651 vote -
Error en regla XML para cosecha de registros por OAI
Para la cosecha de registros por OAI se puede crear la regla en XML pero al intentar cosechar nos genera error en el formato: Registros con error de carga{BULKID=25571960004151, JOBID=3894163620004151, ERRORMESSAGE=Parsing Error - Please check that the file is in the correct format and that the "Input record path" is correct, FILEID=3894165330004151}
Ver caso 079718651 vote
.jpg){kind=link}
- Don't see your idea?