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

1904 results found

  1. 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.

    102 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)

    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…
  2. Allow custom Dewey Classification searches in Consortial Analytics

    In Consortial Analytics, the Dewey Classification search only allows users to select predefined three-digit classifications (as shown in the attached screenshot). This limits the search to broad subject categories. For the purpose of collection development analysis, it would be useful to have the option to search using custom Dewey Decimal numbers, as this would enable more targeted searches.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Make restored CZ electronic portfolios local when using the Manage deleted repository tool

    When using the Manage deleted repository tool to restore deleted CZ electronic portfolios, the restored portfolio should be restored as local, with the blue house icon.

    Currently, the restored portfolio does not become local, but instead appears as linked to the CZ (blue person icon displays), even though the CZ portfolio no longer exists. The result is portfolios in your IZ, that look like they should be CZ linked/managed, aren't. Because the portfolios appear as CZ linked, you are unable to identify the portfolio as local through filtering/reporting and take desired follow up actions. For example, if a CZ portfolio…

    48 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. Add Item‑Level Usage Option to Deselection & Retention Project Scopes

    When determining eligibility for Deselection/Retention Projects, Alma is currently only evaluating title‑level usage rather than item‑level. This means that loans of Lost or Withdrawn items are being considered and the project is actively excluding items that have not circulated for years (because a now lost/withdrawn copy circulated more recently). Further to this, this information is not readily available without going into Alma Analytics.

    Proposal: add an option within the Scope configuration that allows institutions to choose whether usage should be evaluated at:

    Title Level (current behaviour)
    OR
    Item Level (requested enhancement)

    This enhancement would:

    • Improve accuracy of deselection lists
    • Prevent…
    45 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. Community Zone Authorities vs Network Zone Authorities

    When authority records are managed from a Network Zone (NZ) in a cooperative way—that is, when several institutions create and maintain authority records of different types (names, subjects, etc.)—it is confusing for catalogers when authorities from the Community Zone appear.

    For this reason, we would like the possibility to choose from which zone we view authority records, mainly in these two screens:

    • In Browse Authority Headings in the NZ, we would like to have different tabs to choose which zone we want to consult, the NZ or the CZ
    • In Browse Authority Headings in any IZ of the…

    31 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. Allow All MARC21 Fields Valid for Subfield $5 to be Saved as Alma "Local Extensions"

    The Problem:
    Alma’s current "Local Extension" model restricts local data to a hardcoded subset of tags (09X, 59X, 69X, etc.). This forces libraries to choose between keeping standard local data in the Network Zone (where it risks being overwritten) or moving it to non-standard local tags.

    When standard data (like a 700 donor name or a 655 local genre heading) is forced into a 9XX or 69X field, it breaks standard Primo indexing. We lose the ability to have this critical local data indexed in standard Primo indexes.

    The Solution:
    Update the Alma Metadata Editor and bibliographic validation rules to…

    13 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. Include ocn or other 035 as an exportable field for Alma sets

    Currently, 035 fields are not included as viewable or exportable fields in Alma Sets. It would be helpful if we could include 035 fields - specifically OCNs - in an exported list of titles. We use Analytics to gather this information, but it requires an extra few steps. In streamlining our workflows, we want to see as many details about records as possible.

    Thank you for considering this idea!

    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)
  8. File Naming

    Current system behavior replaces user-defined file names with the Rapid request no. and the Cross Ref IDs during the delivery process. To meet ADA Title II standards, we need the system to preserve the original staff-assigned filename when the file is delivered to the patron.

    32 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)
  9. Please get rid of the message notifications that pop up in the top right corner telling people what they just did.

    These inhibit workflow. The collapse-by-default feature is extremely slow, the pop-ups block the tool bar and need to be manually removed before I can continue with my workflow. If there are reasons why people feel this feature needs to be kept, could it please at least be an optional feature that we can turn off? Thanks.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Provide more info on bulk fine waiving confirmation screen

    Bulk fine waiving has been enhanced to allow waiving from a set or from an uploaded file, which is great. However, before running the irreversible job, a moment that is typically a bit fraught for the user, it would be very helpful see the number of fines that the job will waive with the current parameters applied. Currently no info is given by the confirmation screen and this leads to uncertainty as to whether the indicated set / file was being properly recognized. The confirmation screen should be more in line with the standard manual jobs or the portfolio loader,…

    10 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. Search Authority Headings: Mariano Moreno National Library of Argentina. Import BNA10 - Z39.50 protocol

    Implement the import of authority records via Z39.50 from the Mariano Moreno National Library of Argentina. Is not listed in “Authority vocabularies in the Community Zone” https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(Espa%C3%B1ol)/Gesti%C3%B3n_de_metadatos/050Trabajar_con_registros_de_autoridad

    Downloading authority records
    https://www.bn.gov.ar/bibliotecarios/protocoloZ3950
    Z39.50 protocol

    IP: 200.123.191.9
    Port: 9991
    Database: BNA10
    Authentication: YES
    Username: Z39.50
    Password: Z39.50
    Character set: UTF-8
    Format syntax: MARC21
    Contact: dpt@bn.gob.ar

    A Proquest case (10586567) was submitted—Search for Authority Headings: Mariano Moreno National Library of Argentina. It was noted that "Alma currently allows the import of bibliographic records from the Mariano Moreno National Library using the BNA01 database. However, the incorporation of the BNA10 database for authority records…

    22 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)
  12. 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…

    272 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)

    Hello everyone, for those who raised comments about the correction of 830 $v, could you please provide a detailed, step-by-step explanation of the scenario in which this subfield gets overwritten?

  13. Display all assigned PO lines in task list

    With the introduction of the new PO line layout, it became possible to manually assign PO lines, regardless of their status. However, the Alma task list (tasks requiring your attention) still only displays assigned PO lines, when they are in review. Assigned PO lines with different statuses tend to be overlooked.

    It would be very useful for ACQ staff to be able to see all PO lines assigned to them in the task list. This could also encourage more use of the "Assign To" function.

    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)
  14. Prevent resource sharing requests from matching to different formats

    Currently, there is no method of preventing digital article requests from matching with physical items, while keeping the resource sharing library active for lending of digital requests for physical items (e.g. to send book chapters digitally).

    We would like the locate process to exclude certain formats based on the citation type selected in the request form. For example, a request for a book chapter would match only to physical and electronic books and an article request would match to only electronic and physical articles.

    16 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. Improve precision of locate process for digital resource sharing article requests

    Currently, when identifiers are not included in a resource sharing request form, Alma uses a search mechanism based on keywords to guide the locate process. This results in many false positive matches. Additional locate by fields (title, author) selected in the partner’s locate profile and Resource Sharing Library lending setup are not considered in the process. Turning on the Locate only when all fields match setting does not improve the accuracy of the locate for article requests, as article author is not considered in the matching process for article, with the journal title being the main matching element.

    We would…

    18 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. Use Online Ordering to preference ebook multi-user licenses over single user licenses.

    We would like ebook links with unlimited or multi-user licenses to be preferenced (display first) over single user license ebooks in discovery configuration. We would like this to be an option in Configuration > Fulfillment > Discovery Interface Display Logic > Online Services Order

    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)
  17. Automated linking a NZ record to the IZ based on the existence of a parent 773 link

    As a system librarian, I have a problem with linking large amounts of bibliographic records from Network Zone to the Institution Zone. Those are recods that are related to other bib records by the 773 field with $w – links using the record control number and/or with $x – links using the ISSN of the bibliographic record. Those linking records, usually monographic component parts, are created and saved in the Network Zone, and are not automatically linked to their related records in the IZ, every institution has to link them one by one from the NZ to IZ.
    It would…

    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)
  18. Improve cookies on Alma and other Clarivate sites

    Alma-specific:
    * Re-configure the OneTrust settings so that performance cookies default to off
    * Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
    * Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)

    Clarivate-wide:
    * Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off,…

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Expand the character limit for Inventory number field

    The Inventory number field for physical items in Alma is currently limited to 20 characters. We are using RFID tags to track some of our items, and would like to store them in the Inventory number field. Because these codes are generally about 25 characters long, it'd be helpful if the size of the field could be extended to 30 or (preferably) 50 characters.

    20 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. Contributed collections - a Report to Contributor instead of Report to Ex Libris

    There are many collections now that are contributed by the community. Sometimes there are errors within them and as it is now, there is no way to report that and get the linking problem (for an example) fixed and the issues can be so many that a deactivation is necessary, but then the collection becomes dead and just clutter KB. My suggestion is that when a institution contributes a collection, a mandatory field is added to the workflow of contributing. This field contains an email address. That email address is then incorporated into a button so you can report to…

    127 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)
  • Don't see your idea?