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

52 results found

  1. Prevent 9xx local fields from being saved to Community Zone (CZ) records

    There is a known issue of some sites not adhering to the Community Zone (CZ) Contribution Guidelines and Community Catalog Standards.
    An example of this is the addition of local 9xx fields to CZ records.
    Ex Libris already uses a normalization routine to validate CZ records which are changed by customers.
    However, this routine does not specifically prevent the addition of local 9xx fields, even though the guidelines are clear that only changes which benefit the broader community should be made.

    Use case:
    This has been a longstanding issue, but has been fixable in the Primo Back Office to an…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Add a F3 functionality in the dropdown menu of the MDE

    In the Metadata Editor, F3 is used in order to look up to the authority headings from a specific bib heading. This is a crucial feature of the MDE, yet it is not available in the dropdown menus. As our librarians sometimes work with tablets, with no function keys, this lack is troublesome. Adding the look up functionality in the dropdown menus would be a welcome improvement of the MDE.

    78 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Create a Physical Titles or Physical Items set from a list of MMS IDs

    It is possible to create an All Titles set from a list of MMS IDs, but not a Physical Titles or Physical Items set. To run certain jobs – like Change Holdings Information – a Physical Titles set is required. In order to run this job on a list of MMS IDs, you must first create an All Titles set, then extract some other key like OCLC #, then create a Physical Titles set from that list, and only then can you run your job. Since all physical titles and items DO have MMS IDs, it should be possible to…

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Make configurable pop-up assistance in metadata editor

    Currently the po-up assistance in metadata editor for subfields 260$a$b$e$f, 264$a$b, 505$r$t and 561$a is hardcoded and it can not be deactivated. Activation/Deactivation should be configurable. We have many queries from our catalogers about that.

    303 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hi all,

    Starting from the May 2026 release, catalogers can customize their workflow by toggling the pop-up assistance on or off for selected subfields.

    Read more in the release notes: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2026/Alma_2026_Release_Notes/2026_RN_05_Main?mt-draft=true


    Best, Alma Product

  5. Suggestions for Normalization Rules (NR) functions

    Hello,

    Please see the attached file.
    We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.

    Thanks

    218 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

  6. Create a task that orders the 6xx (subject) fields

    Alma currently does not have a way to mass resequence the 6xx subject fields, at least into consecutive order. This is an issue in analytics if subject is the field you organize your results by, as the initial subject field (600) may no longer be the first subject displayed and therefore searched on.

    25 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, enhancing its capabilities beyond the existing DROOLS-based rules. This new functionality enables more advanced and sophisticated data normalization processes.

    A blog post has been published demonstrating how to use an XSL normalization process to address the request described in this idea. You can read it here: https://developers.exlibrisgroup.com/blog/how-to-re-sequence-all-marc-fields-using-xsl-normalization/

  7. Add OCLC number to physical item export

    Large scale weeding projects would be made much more efficient if Alma offered the ability to include OCLC numbers in the physical items set export details. Currently, we are in the position of using a work-around where we must create a title-level set based on the same items. There are bib-level elements present in the physical item export, so we assume this is possible. Ultimately, we would prefer the option to select which fields export for every export we perform, but the addition of OCLC number to physical item exports would be a great first step. 

    94 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Preferred term correction should flip headings that change tag number

    Alma authority control does not handle cases where the bib heading is linked to an authority via a cross-reference, but the preferred and non-preferred terms are in different fields, e.g. preferred term is in authority field 130 and cross-reference in authority is in 410.

    Alma should be able to handle this scenario. Currently when the bib heading matches the authority cross-reference, Alma won't correct these and instead puts them on this report: Preferred Term Correction - Bib Heading found no authorized term.

    Example bib heading that Alma won't correct:

    110/2_ $$a Allied and Associated Powers (1914-1920). $$t Treaties, etc. $$g…

    249 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Create a "natural language" editor to create Normalization rules

    The process for creating Normalization rules is unnecessarily complex and difficult, particularly for those of us who are not familiar with Drools logic. Our previous LSP had an intuitive interface which made creating rules to change details in MARC records much less time consuming. Ex Libris would do well to create such an interface.

    16 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

    Additionally, we are currently exploring the integration of AI assistance within the MD Editor. This feature would enable users to generate XSL rules using natural language input, with the help of AI.

  10. offer true author/creator browse

    Currently Alma offers browsing bib headings with using "names" type - which includes also headings from 600/610/611.
    We find it more useful to have a way to browse by author/creator headings without the subject name fields (relevant 1xx and 7xx without 6xx).

    263 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

    Alma enables you to browse bibliographic headings to support various cataloging workflows. You can browse by author name, subject, series, and title.
    As of November release for cases when a person appears both as a creator and as a subject (i.e., ‘Agatha Christie’ might be both the subject and an author), you can select between the following methods of mapping the MARC 21 fields 600, 610, 611:
    Names – (existing options) When browsing bibliographic headings using this option, the 6XX fields appear under Names.
    Subjects – (existing options) When browsing bibliographic headings using this option, the 6XX fields are not found.
    Names (without MARC21 600/610/611) – (new option) When browsing using this option, the 6XX fields are not found.
    Subjects (with MARC21 600/610/611) – (new option). When browsing using this option, the 6XX fields appear under Subjects.

    For more information please see Alma November Release Notes:
    https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes

  11. Generate accession number by using keystroke combination

    Generation an accession number in 852$$h can only be done by using the menu (tools -> MARC21 holdings -> generate accession number), we would prefer a keystroke combination. It would reduce the clicking enormously!

    142 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. add security levels to norm rules

    Because all norm rules can be edited by all staff with cataloger roles, there is great room for erroneous changes for rules that are applied to batch jobs. For example, the norm rule that is applied to records being brought in from Z39.50 targets can be edited by any staff member. A single error in the rule can break the z39.50 import process for all staff until the source of the error is identified. Likewise, if we have a rule applied to import profiles and a staff member inadvertently changes it and we load 50,000 records, that could cause huge…

    275 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, enhancing its capabilities beyond the existing DROOLS-based rules. This new functionality allows for more advanced and sophisticated data normalization processes.

    As part of this enhancement, a new privilege has been introduced and added to various cataloger user roles, providing controlled access to the Normalization Rules functionality.

    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. Put full 100 field information in search results

    Please put the full 1XX field in the search results.

    We have many people with the same or similar names which are distinguished by dates or other information from the 100 field. It would be very useful to have all the personal name information this display in the metadata editor and also to be available in the Excel download of the search results.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Increase size of MD Editor main panel

    The Metadata editing window (main panel) is really small compared to the rest of the screen. Dragging and dropping the panes does not have much effect. There is also the Full Screen functionality which only widens the editing screen. The problem is that it should extend the view of the fields in the length. We would like to see more fields of the record at one time. The panels at the top and bottom of the screen are very wide, so there is plenty of space to make more room for the actual editing.

    52 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Ability to limit Authority Control task list to only Institution zone records

    It is overwhelming to have hundreds or thousands of records listed in the Authority Control task list every day, especially when most of them are Community Zone records that we're not supposed to change. We need to have the option to get a list of only our Institution Zone records that need to be worked on. This would save a lot of time and frustration from having to weed through the morass of Community Zone authority issues.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. cataloging level defaults

    We have cataloging levels enabled in Alma. We would like the default for imports to be higher than the lowest level. Currently, all imports from import and integration profiles are assigned the lowest level, and the only way to change them is to run a job after importing.

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Use the same font and formatting in the MD Editor and View Versions pane

    Alma currently uses a different font in the View Versions display than that used in the MD Editor. The records are also formatted differently, with the field number being center justified against the corresponding field, rather than the number appearing at the beginning of the field. Line spacing is also different between the two versions.

    These design issues make comparing two versions of a record side-by-side much more difficult than it should be.

    Please use the same font and formatting in both the MD Editor and the View Versions record display. The use of shading in alternate fields (as in…

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Provide ability to "Catalog set" and "Filter set" on sets of authorities

    Under 'Manage Sets' we are able to send sets of less than 30 bibliographic records directly to the Metadata Editor by clicking 'Catalog set'. We can also filter sets of less than 30 bibliographic records using indication rules by clicking "Filter set". These functionalities are not available for sets of authority records.

    Existing authorities often will not be available to cataloguers using F3 if there are any coding mismatches from what Alma expects. This is much too big of a job to handle manually.

    It would greatly improve authority control, especially cleaning up old authorities, to be able to filter…

    32 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

    For better management of local authority records, the following new options are now available:

    Catalog Set – A set of local authorities records can be opened in the MD Editor for cataloging.
    Filter Set – You can filter a set of local authority records using indication rules to create a subset of records with only the records that pass the indication rules conditions.
    For more information please see Alma November Notes:
    https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes

  19. Identify headings linked to authority records in Simple Record View

    I frequently consult the Simple Record View page of bibliographic records when working on the Authority Control Task List. This view, however, does not indicate which headings are linked to authority records and which are not. The only place in Alma to confirm this is through the Metadata Editor.

    This proposal recommends adding a marker (such as the binoculars icon found in the Metadata Editor) to those fields in the Simple Record View with headings linked to authority records. This would save a step in the Task List review process, not to mention being helpful to any Alma user looking…

    100 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Delete multiple MARC fields after they are highlighted / selected in Metadata Editor

    At the moment, you can select multiple MARC fields when you hold down CTRL, as can be seen by the fields highlighted in BLUE in the attached screenshot.

    However, when one attempts to remove them (CTRL+F6), only the first field is deleted.

    This is a request to delete all highlighted fields

    117 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?