Skip to content

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

72 results found

  1. Add the 'Not contains', 'Not contains phrase', 'Not equal', 'Is not empty' search logic to Keywords, Creator, Subject etc. search indexes

    Please add the 'Not contains', 'Not contains phrase', 'Not equal', 'Is not empty' search logic to as many search indexes as possible, and particularly to Keywords, Creator, Subject search indexes.

    The 'Not contains', 'Not contains phrase', 'Not equal', 'Is not empty' search logics are very essential to advanced searches.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Remove 246 $a from title matching

    When fuzzy and extended fuzzy tests for title matches, they include 246 $a. This allows too many mismatches. When testing for title matches, match should not evaluate on 246 $a at all. For example, the current routine considers these two titles a match (due to 246 $a), even though they are in different languages (both have Plato as an author), have different ISBN, publishers, etc.:

    Title: Ion, oder, Über die Ilias
    Published: Göttingen ; Bristol, CT, U.S.A. : Vandenhoeck et Ruprecht, [2017]

    Title: Ion.
    Published: Paris, Les Belles Lettres, 2018.

    36 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  Dana Moshkovits responded

    Thank you for the idea.
    Extended Fuzzy Serial Match Method now supports the same functionality as the Extended Fuzzy Serial Match Method, except that when matching against the title, this profiles matches only by 245 a,b,k,n,p and not by 245 a,b,k,n,p, 245 a, 210 a, 246 a.
    for more information please see:
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/060Record_Import/020Managing_Import_Profiles

  3. Index the Marc 546 field in Alma Repository Search

    Libraries have expressed the need to search the Marc 546 language note field in Alma repository search. https://www.oclc.org/bibformats/en/5xx/546.html

    Use cases:
    to search for specific languages that do not have a Marc language code in the 041 field.
    Or to search for closed-captioning or subtitle info in the 546 field. (Example: "English, Spanish, French or Mandarin dialogue with optional English for the hearing impaired; closed-captioned."

    https://www.oclc.org/bibformats/en/0xx/041.html

    Like how other 5xx fields are indexed in the Notes search index, could the 546 be indexed as well?

    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/180Search_Indexes/MARC_21_Search_Indexes

    Voters: If you would like additional 5xx fields indexed please add them as a comment…

    56 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Full PCRE Regular Expressions in Normalization rules

    Supporting full PCRE regular expressions would make Normalization rules so powerful. Allow capturing data in one place and re-using it somewhere else, checking for substrings, etc.

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Alma now supports XSL normalization rules, expanding its capabilities beyond the existing DROOLS support. This addition enables more advanced and intricate data normalization. For detailed information on using XSL normalization rules, please refer to the May 2025 release notes available at: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes

  5. Add the ability to delete multiple sets from the "my sets" view

    In the course of our relegatuion and withdrawal work we create a large number of itemised sets. A while after the work has been carried it is useful to delete these sets (especially as many contain items which are no longer in our stock). Presently the only way to delete sets is on a set-by-set basis. We would like to be able to delete multiple sets in one go. I envisage this functioning much like the "task list" - that is, have a checkbox next to each set. This could then be checked and a "delete set" command applied to…

    79 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    This requirement is already taken care of in the new Manage Sets structure, which went into effect in August 2023.

    The bulk Delete button appears in the toolbar when one or more sets are chosen. See the screenshot that is attached.

  6. In Advanced Search, allow filtering OUT specific locations. For example, allow use of the filer: Physical Location "IS NOT" X.

    Many searches do not allow for an "IS NOT" operator, and in some cases it is greatly missed. For example, when trying to assemble large sets of records where you want to exclude just a few locations, or filter out a single library. Please allow for an "IS NOT" operator when doing an advanced search and filtering by location or library. I'm sure there are other search filters also missing the "IS NOT" operator. Please feel free to add more suggestions via a comment! :)

    596 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Ability to schedule manual jobs on a regular basis

    At our institution, we have some manual jobs we would like to schedule on a regular basis (daily, weekly, etc.). For example, after we purchase a physical title and a PO line is created in Alma, we run the manual job, change holding information on a logical set. This job updates the holding call number (852 $h and $i) from the bibliographic record and also updates the library and location (852 $b and $c) based on the Library of Congress call number in 852 $h.

    We are aware that there is an Alma Jobs API (https://developers.exlibrisgroup.com/blog/Working-with-the-Alma-Jobs-API) that could…

    140 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Add the option to expand both physical and electronic inventory simultaneously rather than having to choose one or the other

    For people who work with both physical and electronic items, it is frustrating to continually have to toggle the Expand option back and forth between the two inventory types in order to see associated items or portfolios in the brief results lists. This makes collections work burdensome and requires multiple additional clicks. We'd like the option to have inventory information for both types display automatically by default, in addition to the existing options to display one type or the other.

    206 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Allow user to specify number of items to display (and select) per page

    Currently, only 20 items may be displayed and selected at a time. Most commercial websites offer a widget that allows the user to specify display of, for example, 25, 50, 100, or "all" matches when searching. (The widget option would be useful for other search types as well, but I'm concerned primarily with items here.) Adding such an option in Alma would be welcomed. Displays could still default to 20 per screen, but allow the user to display more on a single screen if desired.

    The current limit has a serious impact on our productivity when units are transferring large…

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  Dana Moshkovits responded

    As of November release you can now select the number of results appearing on any list of results (previously, only a few lists had this feature). For some lists, the range is between 10 and 50 results. For other lists, it is between 20 and 100 results.

  10. Add Previous and Next buttons to various screens

    After conducting a search and selecting a record to view, it would be nice to have Previous/Next buttons for navigation, rather than needing to always go "Back" and then select the next record in the list for viewing. This could also be useful in other areas, like the physical item editor, and perhaps in some Fulfillment functions.

    119 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. search in a specific library

    We would appreciate having a tab "library" as existing tabs "Institution zone", "Network zone", "Community zone". Indeed, currently, it's tiresome to use facet "library" each time we launch a search in Alma.

    Is it possible?

    247 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Allow **** or Python plugins for normalization rules

    The Drools framework in place for normalization rules is very limited compared to real programming script languages like **** or Python. Live would be way easier, much more efficient and some things impossible with Drools would be possible with **** (like in SFX parsers) or Python for those who can use these languages.

    54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Alma now supports XSL normalization rules, expanding its capabilities beyond the existing DROOLS support. This addition enables more advanced and intricate data normalization. For detailed information on using XSL normalization rules, please refer to the May 2025 release notes available at: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes

  13. Z39.5 MARC field filtering

    Alma's current settings on integration profile do not have the functionality to prevent exposure of specific MARC field. It will create problem if some of the MARC content are licensed and are not supposed to be shared easily.

    134 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Raise the limit to total number of rejections ( currently 1000) for exporting records that are not imported (due to import profile setup)

    There is currently no limit to the number or records that can be imported into Alma (as far as I am aware).. there is however a limit of 1000 when needing to export the rejected data.. Workflows would be much better managed if this limit was raised to the total number of rejected records

    174 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Add to General Publishing profile the ability to include holdings details for related inventory

    We have large numbers of "bound with" titles e.g. pamphlets. These have MARC Bibliographic records but no Holdings or Items - they are linked to the parent volume, which has the Holdings and Inventory information. When the "bound with" records are published using a General Publishing profile, the Holdings information is not added from the related (parent) record, and the records appear to have no Holdings. We would like the option to include Holdings and Items for Related records in these cases, so that the library and location of the title can be included in the published records.

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  Dana Moshkovits responded

    Related records can now be republished to external systems, so that the external catalog has a full representation of the catalog and inventory of your library. You can include the related record information (bibliographic and physical inventory). If the institution is part of a consortium, then when publishing bibliographic records from the Network Zone to an external system, the related records information can also be published to the external system.

    For more information please see Alma December Release Notes:
    https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2021/Alma_2021_Release_Notes

  16. "Select All" checkbox for In Process Items

    When changing the status of In Process Items there is no “Select All” box at the head of the column, often there are multiple copies and we want to apply the same status change to all the items on the list.

    Instead of having to check the box next to each item in a list we would like to suggest that on this page (and other pages where applicable) that a “Select All” checkbox* be added.

    *as is the case on some lists such as “Patron Loans” and “List of Items”.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Need ability to search 79X fields

    We plan to implement use of the 790 field for local tracings (such as former owners) to be used for special collections materials, and have set up a separate search field in Primo. Now we see that we can't search that field at all in Alma, only Primo. Since Alma does index 59X fields as "local notes" and 69X fields as "local subjects" we propose that the 79X be indexed as well.

    58 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Produce a Publishing Profile for BrowZine

    The idea is to create a specific publishing profile for sending data to BrowZine on a scheduled basis. The presently used data format (Google Scholar XML with Sources) could be better served as a CSV file for numerous reasons. Additionally, the Publishing Profile should be able to accommodate the scenario of a library's holdings being made up of a combination of NZ and IZ holdings.
    Please contact john@thirdiron.com for full technical guidelines for the best and most reliable data exporting configuration. Thank you!

    Note:
    Over time we have come to understand a number of limitations in the approach suggested here…

    268 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Allow reactivation of withdrawn items

    It would be very useful to be able to easily reactivate/reinstate withdrawn items. For example, an item that has been made missing, not found, and deleted may turn up later. This is happening more frequently as we are carrying out large scale stock projects, and will increase when we begin regular stock taking.

    Ideally when a deleted item is returned or scanned in a message box would alert the user:

    "This item was withdrawn on dd/mm/yyyy.

    Would you like to reactivate it?

    Proceed/Cancel"

    All the necessary data appears to be retained (and can be seen in Analytics), and I am…

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Share GES configurations from the NZ to the IZ

    Would like to set up GES configurations in the NZ and be able to share those configurations with the IZ. Example, ERIC, Amazon, Google Scholar, and ProQuest Dissertations.

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?