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 ~
1689 results found
-
Flag AI created resources
As an electronic resources access manager, I would like to propose functionality be created to identify when a resources was created all or partially by artificial intelligence.
More content is being created by AI and it is getting harder and harder to detect. Gobi now has "AI-generated" as a tag under "interdisciplinary topics" when purchasing books (screenshot attached) and it would be great if Alma could do something similar to alert users when they are looking through institutions catalogs of resources.
I am not sure if this idea is for Alma only or Alma and Primo but it would be great to find a way forward in flagging know AI generated resources.
I also know this will not be a perfect fix but if resources can be flagged and the option to report/tag is provided it will help our users.
As an electronic resources access manager, I would like to propose functionality be created to identify when a resources was created all or partially by artificial intelligence.
More content is being created by AI and it is getting harder and harder to detect. Gobi now has "AI-generated" as a tag under "interdisciplinary topics" when purchasing books (screenshot attached) and it would be great if Alma could do something similar to alert users when they are looking through institutions catalogs of resources.
I am not sure if this idea is for Alma only or Alma and Primo but it would be…
18 votes -
Please integrate aspect „last copy within library / IZ / NZ“ within “Withdraw Physical Items” process
Ex Libris recently expanded the “Withdraw Physical Items” process to include more individual configurable aspects.
We would like to suggest to include the aspect “last copy in the IZ (thus: do not delete!)” as well, which would protect the last copy from deletion.
It would also be great to be able to protect the “last copy in the same library" or "last copy in the NZ” during the deletion process, if necessary.
We are familiar with the “Retention Information - committed to retain: yes” feature, but it is too troublesome for us to use, because we would have to actualize these fields every day, although contents could be outdated right in the same moment.
Because of missing space several IZs and their libraries have to give away items parallelely.
If Alma could retain items, that are unique (in the same library resp. in our IZ resp. in our NZ), would help us enourmously.
At the moment retrieving these aspects is quite difficult, takes place outside Alma (when open data sources or previous day dated Analytics data need to be checked) and can be outdated the same second, while we take the facts into decision to delete items.
Due to the vast quantities of holdings and copies we have, the enormous time pressure and the limited number of staff, we are unfortunately unable to check each title and each copy intellectually, as would be desirable. We are forced to carry out mass sorting. Powerful tools within the system would be a quantum leap forward.
Ex Libris recently expanded the “Withdraw Physical Items” process to include more individual configurable aspects.
We would like to suggest to include the aspect “last copy in the IZ (thus: do not delete!)” as well, which would protect the last copy from deletion.
It would also be great to be able to protect the “last copy in the same library" or "last copy in the NZ” during the deletion process, if necessary.
We are familiar with the “Retention Information - committed to retain: yes” feature, but it is too troublesome for us to use, because we would have to actualize…
92 votes -
Enable conversion of English vocabulary in NOTE field to 336/337/338 fields for records with 040 $$b eng
Currently, the system supports conversion of Japanese vocabulary in the NOTE field (e.g., "Content Type: text (ncrcontent)") into structured 336/337/338 fields for records with 040 $$b jpn,. However, a similar conversion is not applied to records with 040 $$b eng, even when the NOTE field contains English vocabulary in the same format.
We request that the same conversion logic be extended to records with 040 $$b eng, so that:
Example:
NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)
-->
336 $$a text $$2 ncrcontent
337 $$a unmediated $$2 ncrmedia
338 $$a volume $$2 ncrcarrierThis enhancement would ensure consistency in metadata mapping between Japanese and English cataloging languages and improve the quality of bibliographic records in Alma.
Currently, the system supports conversion of Japanese vocabulary in the NOTE field (e.g., "Content Type: text (ncrcontent)") into structured 336/337/338 fields for records with 040 $$b jpn,. However, a similar conversion is not applied to records with 040 $$b eng, even when the NOTE field contains English vocabulary in the same format.
We request that the same conversion logic be extended to records with 040 $$b eng, so that:
Example:
NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)
-->
336 $$a text $$2 ncrcontent
337 $$a unmediated $$2 ncrmedia
338 $$a volume $$2 ncrcarrierThis…
3 votes -
NACSIS-CAT Could App: Enable English output in NOTE field when converting 336/337/338 fields for records with 040 $$b eng
Currently, when converting 336/337/338 fields to a NOTE field in Alma --> NACSIS-CAT mappings, the output uses Japanese vocabulary regardless of the cataloging language. For records with 040 $$b eng, we request that the NOTE field be generated using English vocabulary to match the cataloging language.
Example:
Expected output for 040 $$b eng:
336 $$a text $$2 ncrcontent
337 $$a unmediated $$2 ncrmedia
338 $$a volume $$2 ncrcarrier
→ NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)Current output:
→ NOTE: 表現種別: text (ncrcontent), 機器種別: unmediated (ncrmedia), キャリア種別: volume (ncrcarrier)This enhancement would ensure consistency between cataloging language and output vocabulary, improving metadata quality and usability for English-language records.
Currently, when converting 336/337/338 fields to a NOTE field in Alma --> NACSIS-CAT mappings, the output uses Japanese vocabulary regardless of the cataloging language. For records with 040 $$b eng, we request that the NOTE field be generated using English vocabulary to match the cataloging language.
Example:
Expected output for 040 $$b eng:
336 $$a text $$2 ncrcontent
337 $$a unmediated $$2 ncrmedia
338 $$a volume $$2 ncrcarrier
→ NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)Current output:
→ NOTE: 表現種別: text (ncrcontent), 機器種別: unmediated (ncrmedia), キャリア種別: volume (ncrcarrier)This enhancement would ensure consistency…
3 votes -
Add/remove public notes for electronic collection notes in bulk
If there are known access issues with one specific provider, it would be useful to add / remove a note to all electronic collections, which an institution may have for this provider / interface at once. At present, we have to edit all collections for providers individually if we want to add the same public note for all.
15 votes -
Expand SIP2 message support to include patron birth date
Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.
For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).
We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age
This enhancement would enable safer and more autonomous self-service environments, particularly in low-staffed libraries, while ensuring compliance with age-based borrowing restrictions and institutional policies.
Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.
For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).
We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age
This enhancement would enable safer and more autonomous self-service environments, particularly…
59 votes -
Allow prioritization of item requests based on library proximity and capacity
In our consortium, several libraries are linked through relationships. However, these libraries differ in distance, staffing levels, and delivery times.
We would like Alma to provide a way to prioritize the fulfillment of requests based on configurable criteria such as library proximity, staff availability, or delivery speed (as actual transit time rules are not efficient enough).
This enhancement would enable the system to route requests for multiple available items to the most suitable library — ideally the closest or best staffed — thereby streamlining daily operations and improving service efficiency across the consortium.17 votes -
Primo Analytics Mixpanel Data Integrated Into Alma Analytics as External Data Resources
As stated in the Alma Roadmap 2025-2026, "Analytics will support integrations with external data sources, allowing users to analyze data from multiple systems within the Analytics platform." (https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2025-2026)/Analytics_and_Insights#Integration_with_External_Data_Resources )
This new feature is expected to simplify workflows and save time by eliminating the need to access multiple systems, thereby improving staff efficiency and effectiveness.It would be highly valuable if Primo Analytics Mixpanel data were considered a priority candidate for inclusion within this consolidation initiative.
11 votes -
Visibility of Patron Blocks in Alma
Not all patron blocks are visible under the "Blocks" tab in Alma, depending on the type of block and how it is generated. For example, the maximum cash limit block does not appear in the tab but can be seen as a pop-up notification when using the Manage Patron Services screen.
It would be extremely helpful if all blocks were displayed in the "Blocks" - tab, making it easier for staff to get a complete overview of a patron’s status and blocks.
16 votes -
Keep patron physical requests active even if “deliver to” relationships are temporarily interrupted
Our consortia has several libraries connected through “deliver to” relationships, allowing patrons to request and pick up physical items from different sites.
Currently, when these relationships are interrupted — for example, due to maintenance, or temporary closures — all related patron requests are automatically cancelled, and patrons receive cancellation notifications. That makes them angry.
We would like Alma to preserve these requests in an active or pending state during such interruptions, so they can be fulfilled automatically once the relationship is restored, without requiring patrons to place new requests.
This would improve the user experience and reduce administrative workload for library staff.
Our consortia has several libraries connected through “deliver to” relationships, allowing patrons to request and pick up physical items from different sites.
Currently, when these relationships are interrupted — for example, due to maintenance, or temporary closures — all related patron requests are automatically cancelled, and patrons receive cancellation notifications. That makes them angry.
We would like Alma to preserve these requests in an active or pending state during such interruptions, so they can be fulfilled automatically once the relationship is restored, without requiring patrons to place new requests.
This would improve the user experience and reduce administrative workload for…
33 votes -
Add more information to the Couse tab on the user profile I Alma
The course tab only provides information about the course code and course section.
If you, like in our case, have a non-descriptive course code containing only numbers you have zero information about what the course is.If a user has multiple courses and you need to remove a course with name *** you have to look up every course to identify which course code is the one you need to delete.
The following columns should be added: Name, start date, end date, Year, Term, academic department, faculty/school – and make them sortable.
2 votes -
To be able to remove the LOCAL marking of marc fields
Now, if a field in a record is to be 'un-local', you must delete the field and recreate the field without the local indication. An option to de-localize from the menu in MDE would make a better workflow.
1 vote -
Patron last activity date updated by leganto use in Alma.
Leganto use is an important information of use. A patron could have zero library use but use leganto and be assigned to multiple courses.
The information is highly relevant for purging users – if you want to purge inactive users there is no way to known if there is leganto activity – and leganto activity is an important reason to not purge a user as library activity is.
1 vote -
Put related holdings in its own tab not displayed among the actual holdings in Alma
Add the option to turn off the display of related records holding in the holding display for a title in Alma. Having it among the 'true' holdings is very confusing and for most part not relevant when needing to locate the title at hand - In that case I'm not interested in a completely different title just because they share a relation to that title in our collection.
A tab with the related records information would make a less cluttered view6 votesHi all,
This idea was mistakenly closed. It has now been reopened, and we apologize for any inconvenience caused.
-
A temporary location that’s ended by item return/scan in
For exhibitions in the library it would be great to be able to add an item to a temporary location and have the item restored to its permanent location upon return or scan in.
Using a temporary location would make it possible to keep better track of where the item is currently at. Primo would show that an item is used in a display/exhibition and staff could perform better service to patrons and ease the pick-from shelf task.
But there shouldn’t be a need for process restore it to the permanent location. A loaned item taken from a display typically shouldn’t be returned to the display after the loan has ended but just back to its permanent location.
For exhibitions in the library it would be great to be able to add an item to a temporary location and have the item restored to its permanent location upon return or scan in.
Using a temporary location would make it possible to keep better track of where the item is currently at. Primo would show that an item is used in a display/exhibition and staff could perform better service to patrons and ease the pick-from shelf task.
But there shouldn’t be a need for process restore it to the permanent location. A loaned item taken from a display typically…
2 votes -
Alma Split View Hides Main Menu, Affecting Cloud App Access
After rolling out the new UI for the “All Titles Search” with split-view functionality, the main menu is no longer persistent. The menu (which contains location, notifications, cloud apps, etc.) disappears when entering split view.
This is particularly problematic for institutions that frequently use cloud apps in their workflows—for example, when editing physical items. While cloud apps can be pinned before entering split view, this workaround is not satisfactory. Pinning apps adds unnecessary clicks and is easy to forget, resulting in frequent toggling in and out of split view.
As a consequence, many staff members have stopped using cloud apps and instead revert to more manual and time-consuming options (often using Run a Job). In these cases, the new UI is not perceived as an improvement.
To improve usability and maintain workflow efficiency, the main menu should remain visible in split view, similar to the Quick Links menu.
After rolling out the new UI for the “All Titles Search” with split-view functionality, the main menu is no longer persistent. The menu (which contains location, notifications, cloud apps, etc.) disappears when entering split view.
This is particularly problematic for institutions that frequently use cloud apps in their workflows—for example, when editing physical items. While cloud apps can be pinned before entering split view, this workaround is not satisfactory. Pinning apps adds unnecessary clicks and is easy to forget, resulting in frequent toggling in and out of split view.
As a consequence, many staff members have stopped using cloud apps…
35 votes -
pick from shelf Ability to see multiple libraries
Make it possible to see and pick from shelf options from multiple libraries without changing physical location in Alma. Currently, to view pick-from-shelf options from multiple libraries, you must change your physical location. It would be better if we could see all pick from shelf requests in one place.
3 votes -
New option to 'Linking level' menu for Electronic service
I would like to add a new option to the 'Linking level' dropdown menu in the Electronic Service Editor (e.g. Working paper)
This feature will enable you to benefit when searching in Discovery using the 'Resource Type' filter.12 votes -
Make it possible to mark items as "unavailable"
Please make it possible to mark items as "unavailable". This marking can be used in two situations: when an item or a set of items becomes temporarily unavailable to readers, and when items are withdrawn permanently.
Marking should be both manual and by running the job "Change Physical items information".
Ex Libris' advice to use a process is inappropriate because neither a process nor a process-related request is required in these cases.93 votesDear colleagues,
Thank you for raising this idea.
This idea is related to another one - https://ideas.exlibrisgroup.com/forums/308173/suggestions/48370850, which was part of the CERV cycle in 2025, but did not make it to the final list.
During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:
Option 1: New dedicated process type
- It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
- Items marked as "unavailable" will be considered as "not in place"
- The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules
Option 2: Mark a location as "unavailable"
- It will be possible to mark a location as "unavailable"
- All items in this location will be considered as "not in place"
- The difference from option 1 is that when an item is in an "unavailable" location, it can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
- The existing options for location based configuration can be used
Option 3: A new "unavailable" field in item level
- It will be possible to mark specific items as "unavailable", similar to the availability status of portfolios
- Items marked as "unavailable" will be considered as "not in place"
- Similar to option 2, "unavailable" item can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
- As this is a new attribute, relevant configuration options will need to be enhanced to take this attribute into consideration. Further analysis will be needed here
The description here, on this idea, is actually option 3.
During the analysis we identified that
although option 3 might give more flexibility, it is super complicated and would require huge effort. Therefore, the recommended option is option 2: Mark a location as "unavailable".
Do you think that implementing option 2 is enough? in that case, a dummy location "Unavailable" can be utilized for marking specific items by assigning them this location.
I want to share with you the analysis and discussion - you can see it in: https://public.3.basecamp.com/p/ERLrkhNUHtTYerEiaQAsG2uT
Please let me know your thoughts.
Thanks,
Tamar Fuches
Alma product team
Dear colleagues,
Thank you for raising this idea.
This idea is related to another one - https://ideas.exlibrisgroup.com/forums/308173/suggestions/48370850, which was part of the CERV cycle in 2025, but did not make it to the final list.
During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:
Option 1: New dedicated process type
- It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
- Items marked as "unavailable" will be considered as "not in place"
- The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules
Option 2: Mark a location as "unavailable"
- It will be possible to mark a location as "unavailable"
- All items in this location will be considered as "not in place"
- The…
-
Decouple temporary item policy and temporary location
Sometimes we have to set a temporary item policy for items that stay in their permanent location. This requires setting "Item is in a temporary location" = yes and setting the temporary location to the permanent location for the temporary item policy to apply. We would like the ability to set the temporary item policy without needing to set a temporary location.
Furthermore, no warning message is given when "Item is in a temporary location" = no and a temporary item policy is selected. This can lead to confusion because the temporary item policy is not emptied after the setting is saved.
Sometimes we have to set a temporary item policy for items that stay in their permanent location. This requires setting "Item is in a temporary location" = yes and setting the temporary location to the permanent location for the temporary item policy to apply. We would like the ability to set the temporary item policy without needing to set a temporary location.
Furthermore, no warning message is given when "Item is in a temporary location" = no and a temporary item policy is selected. This can lead to confusion because the temporary item policy is not emptied after the setting…
11 votes
- Don't see your idea?