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

118 results found

  1. Allow for an authority file to be addressed by different codes in $2 of various BIB fields

    In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.

    In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2,…

    89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Save certain subfields from being overwritten via F3 and PTC

    When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.

    One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.

    Since different subfields…

    99 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Implement Checks on the Authority Heading Type for Institutions Using ID-based Authority Control

    Currently, when authority linking in Alma is based on ID rather than text, Alma does not check whether the authority heading type in the bibliographic record matches the heading type in the authority record. For example, Alma will link a 600 tag in the bib record for personal names with an authority record whose heading is in tag 110 for corporate names if their ID matches, even though Alma would not offer that option if F3 were pressed.

    We would like Alma to (1) avoid linking in such cases and (2) flag these instances in the authority control task list.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. linked-data-powered sets and collections

    TL;DR: populate existing ALMA sets / collections infrastructure using retrieval of a list of LCCNs from an external URL to allow linked-data-powered sets and collections.

    Problem

    We've all seen the book displays that most physical libraries have in their high-traffic areas. These might be works by the in-house press, topical events, anniversaries of author's birth, etc, etc.

    In the digital space, there are shallow-functionality RSS feeds and then a yawning gap out to things that are typically called 'digital exhibitions' which are resource-intensive glossy displays.

    ALMA Collections can be used for digital exhibitions, but populating them is labour-intensive and slow.

    46 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. All MARC records in the Alma Community Zone should be sorted chronologically between MARC fields 500 - 899.

    The fact that the MARC fields between 500 and 899 are not sorted chronologically for all Alma Community Zone MARC records makes it difficult for us to use the “Collections” function in Primo.
    In the Collections function in Primo, we display the author on the overview page in addition to the title. The author is displayed via a small script in Primo. This script takes the “au” field from the PNX record of the title or, if “au” is not available, the “addau” field and displays the first value from “au” or “addau” in the title overview of the collections.…

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Arrow keys now 'stick' in fields in MDE

    When navigating through records in MDE, if you've previously typed anything in a field, you now cannot move out of that field using the arrow keys. It's not entirely consistent and sometimes does let you move out the field, while other times it 'sticks' randomly in fields you haven't edited at all, but in general it is extraordinarily inconvenient.

    I see using the arrow keys to move within a field was previously suggested as a feature, but even within that suggestion, the idea included the stipulation that if the cursor was already at the start/end of a line hitting up/down…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Add Release Displayed Records in List to Record Actions menu and a keystroke combination

    In the metadata editor, the option to release all displayed records in the record list has only one button which is not accessible by a keystroke. This makes the action less accessible to different users, and is also challenging to document for library staff without including visuals.

    This button, with tooltext "Release displayed records in list," should also appear in the Record Actions menu in the section with other release records options. At minimum, the function should continue the current behavior of releasing the records in the selected records tab. Though it would be useful to have an option to…

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Ability to add labels while creating set

    It would be very useful to be able to add labels to sets when they are created. Currently you have to save your set and only then you can add a label.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add option to batch edit 852 $k and $m in Holdings through the Change Holdings Information Job

    Would love to see the option in the Change Holdings Information Job to be able to apply/remove/change a shared call number prefix or suffix on a set of records. This would greatly improve the efficiency of metadata management for collections of physical items.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. End date confusion

    Inconsistent formatting of dates in different places in Alma leads to confusion. Dates in coverage statements are fomatted mm/dd/yyyy but dates in other places, such as 'Creation date' or 'Modification date' are sometimes formatted dd/mm/yyyy. Ex Libris should start using a standard and consistent date format, namely, the ISO 8601 Date and time format, YYYY-MM-DD, see https://www.iso.org/iso-8601-date-and-time-format.html

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add the option to the item call number in the Table customization list

    Adding "Item Call Number" to the "Table customization" would be very helpful for us. Bib has holding call number, item call number. Item call number is also important to us, by the way, sort by item call number would make our job more easier. Thank you.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add "search internal resources" option to MDE menu

    Our Acquisition staff's workflow is to create brief records at the IZ level for donations etc., when we bring it into the MDE to search for an existing full-level record we are only given the option to "search external resources". We'd like to be able to search internal resources (NZ records) within the MDE (find matches is limited and does not work in most cases--we often discover after we've brought in a record that it did indeed exist in the NZ).

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Add Normalization Process to perform "Expand from Template"

    The "Expand from Template" offers an option to select a template and to expand the currently opened bib record in the Metadata Editor, supporting the options to Override, Add missing and add all.

    As a systems librarian, I would love to have an option to perform this action via a normalisation process.

    Currently, the only way to implement an expand from template via a normalization process is to translate it into normalization rules, which is rather tedious.

    If I could simply use the template in a normalization process, that would save me much time and effort.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. MDE expand from template CZ records

    Alma currently doesn't have the ability to "expand from template" for Community records. The option will enable MDE users to use a template to apply multiple local extension fields to CZ records, minimizing the unintentional error of changing the CZ records for everyone.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add Alma support for microlanguages and language codes recognised by Library of Congress, including Austlang

    Alma’s support for Language for search indexing, facet, and display is hardcoded for 041 to the 3 digit MARC Code List for Languages.
    This excludes languages recognised by Library of Congress, such as Austlang languages which were recognised more than 6 years ago in 2018.
    This issue has been addressed in Primo in 2021 and 2022 with customer advocacy efforts, but remains a glaring omission within Alma.
    See details: https://igelu.org/primo-support-for-austlang-and-iso-639-3/

    The only option currently within Alma for searching this data is to use the keyword field to search by information such as C15, and then use the Language filter to…

    83 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Suppress from Public Displayed on Export

    A field for indicating if records are currently suppressed from discovery should be standard on all exports directly coming out of Alma. Having this information directly available would greatly help in tracking data pulled from Alma without having to go into individual records first, or pulling a list from Analytics first to cross-reference.
    It seems to be a major component missing, especially from the Export (All Fields) list.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Improvements for the MDEs left pane

    The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
    - Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful…

    68 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Make "search" and "sort by" functionality from Browse Bibliographic Headings accessible when binocular icon is clicked.

    The Browse Bibliographic Headings feature allows a user to search in the results list and to sort the list by date, title, creator, etc. When you click the binocular icon for a subject in Alma, it looks like it brings up the Browse Bibliographic Headings feature, but the search and sort features are missing. We'd like them to be added to the results screen when you click the binocular icon.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Improve accessibility of some pop-ups in MDE

    Some pop-ups in Alma cannot be handled with the keyboard (e.g. with the tab and enter keys) but need mouse clicks.
    This makes end-to-end work processes based on keyboard actions and shortcuts impossible.
    For employees with repetitive strain injury (RSI) who should minimize repetitive mouse actions for medical reasons, this is a disadvantage.
    It would be very useful to be able to handle the following pop-ups with the keyboard:

    1. “Expand from template”, the template cannot be selected and confirmed via keyboard (tab, arrow keys, enter).
      (In the similar case of the “Enhance the record” dialogue, key actions are possible.)

    2. “Confirmation…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. The addition of the ability to facet on item format and language in the MDE external resources search.

    It would be really useful to be able to search external resources via the MDE specifically by format and language, or filter the results accordingly. For example, if a cataloguer wants to search principally for records in English and for print format items only.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base