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
-
Visibility that staff is working on a Borrowing or Lending request via facet
Description
Enhancing visibility into requests currently being processed by colleagues will significantly improve the efficiency and effectiveness of Resource Sharing Borrowing and Lending operations.
Please add a facet option to filter out any “free” requests that aren’t being worked on by other staff. By streamlining workflows, libraries can ensure a smoother process, a better client experience, and a more coordinated collaboration among borrowing and lending libraries.
Alternatively, it could be a note on the request or something similar - a visibility feature that allows staff to better allocate their time by avoiding overlaps and duplicate efforts.
Impact of Problem
Our…
7 votes -
Modify locations by batch
We need to update some or all of our location fulfillment Unit of all of our library.
Unfortunately, the Update Location API does not support bulk updates for multiple locations in a single request. Each API call is limited to a single location code.
We'd like to be able to make batch changes to our libraries' reader service units.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).
3 votes -
Ability to remark letter example
In letter administration, currently when you switch to use a different letter example, the information you've got is the same letter name and the only difference is the date it is saved. for example FulUserBorrowingActivityLetter - 02/12/2024 04:08:56 GMT. It does not mean a lot when you are trying to switch to a difference example, one would rather it be remark as something more useful or special about that example, such as specific - usergroup, loan type, from library, etc.
4 votes -
Make Order Status field available in the Interested In Letter XSL
We would like additional Purchase Order fields added to the XSL available for the ‘Interested In Letter’ please, specifically the Order Status field. This will enable us to use conditional statements in the letter template so that certain blocks of text can be included or hidden depending on a given field. We take that approach already with other Alma letters. For example, in the ‘On Hold Shelf Letter’ template, we use <xsl:if> statements to draw on the Pickup Location available in the XSL and display different guidance to recipients depending on the location from which they are collecting a request.
…
5 votes -
Enable sending of emails to non-preferred email addresses
Currently, when contacting users using the Update/Notify Users job in conjunction with the User Notifications Letter, the process will only send to the preferred email address in the patron record. For our former students whose patron records have expired in Alma, this means that the notifications go to their student email address to which they no longer have access.
To contact our former students once their Alma account has expired in line with university IT regulations, we have to take their unique identifier out of Alma and contact them using a separate external system. This entails a lot of extra…
6 votes -
Allow EOD to generate multiple items (multi-volume sets) via Import Profiles
Currently, importing Embedded Order Data to generate POLs with a New Order Import Profile creates a single item per quantity ordered in the POL. Similarly, Update Inventory imports can't update more than one item. Unfortunately, when ordering multi-volume sets, this means volumes 2-n are left off the POL and must be added manually. This creates significant manual work for acquisitions teams, for both approval plans and firm orders. Being able to specify Quantity ordered AND Number of Items (per set) would disambiguate how many volumes we expect to receive, and allow for code that could specify barcode/enumeration on each of…
14 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…
30 votes -
Add “previous year” as an option in serials subscription date range drop down menu for invoice lines.
Some of the invoices we process are for serials subscriptions for the previous calendar year. Having “previous year” as an option, for invoice line subscription ranges would be helpful.
14 votes -
Remove 'Level URL' from CZ collections
We'd like to move more Electronic Collections onto fewer bib records to help with organisation of our e-resources within Alma. If there are multiple IZ collections linked to an unsuppressed bib record, you can control how many URLs display in the Primo record by controlling which Electronic Collections have Level URLs. However, this is not possible when using CZ collections as there is already a Level URL hardcoded into the collection. I don't think it's possible to override the Level URL with 'nothing' to hide that collection's link from Primo. We'd like the ability to be able to hide that…
3 votes -
Usability issues with the New Circ UI
- When processing items from a cart, if they are scanned at Return items and the item is a Ship physically item, the new UI just brings up the item and in small letters says Next Step - System - and the library its to go to. It also says not on loan (which in this case is not helpful, because there is an active request). The system "ships" the item, but doesn't tell you that it did and in order to print the shipping slip staff have to go back to the lending queue and find it.
- We believe if…
11 votes -
When creating a new local portfolio generates a new bib record, the portfolio's material type should determine the bib's material type.
ExL documentation states, "When creating a new bibliographic record, the portfolio material is not taken into account. Thus, when you add a local portfolio and set a specific electronic material type, a bibliographic record is also created, but with 'Book' as the material, regardless of the portfolio's material. When adding ISSN, the material remains to be 'Book'. "
This is imprecise and creates issues for discovery: when I create a new portfolio for a Kanopy video and select Electronic Material Type=Streaming Video, the bib record is encoded for a book. So in Primo, the video's Resource Type shows as book,…
46 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 -
Prevent deletion in Community Zone based on field or value in specific field.
Blocking deletion in Community Zone based on field or value in specific field. Possibility to be definded as a parameter for each CZ vocabulary.
103 votesAs you all know, the Community Zone content is shared among all Alma customers, each with different requirements. Therefore, I’m not sure this request would be acceptable to the wider Alma community. That said, if there were a consensus on a closed list of fields that CZ bibliographic records should be restricted from deleting per MARC profile, this capability already exists and is managed by the Ex Libris Content Operations team. Unfortunately, this is not available for authorities. Do you think such a consensus could be reached?
-
Create a set from records held in the Metadata Editor
It would be useful to be able to save all of the records that you are working on in the metadata editor as a set to come back to later.
For example, this would be helpful when working on a bound with where you need to work on several records at the same time and need to add links across the records. At the moment, if this work is not completed and we need to return to it later, we would then need to create an itemised set by searching for and adding each record individually. Instead, it would be…
76 votes -
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 -
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 quota of ISO-ILL Lending requests
We would like to determine a daily quota of ISO-ILL Lending requests, like with RapidILL.
Ideally, Alma would automatically reject requests beyond the quota and send them to other ISO Partners.15 votes -
Add Bibliographic Details shared dimension to Physical Items Historical Events Report
Use case: What are the languages (Bib Details) for items in a certain work order status (Physical Items Historical Events)? It doesn't seem possible to report on languages from Physical Items Historical Events because it doesn't have the Bib Details shared dimension. The Physical Items report doesn't seem to have work order status. Adding the Bib Details shared dimension to the Physical Items Historical Events report would be very helpful to avoid having to feed results of one report to the other. See https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46741807-in-alma-analytics-physical-items-subject-area
3 votes
.jpg){kind=link}
- Don't see your idea?