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

40 results found

  1. Searchability for MARC 361

    We would like to be able to search MARC-361 in Alma, if possible also specifically in subfields of the 361.

    https://www.loc.gov/marc/bibliographic/bd361.html
    https://www.loc.gov/marc/holdings/hd361.html

    107 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Index 532 field

    MARC21 field 532 should be indexed in Alma and Primo. This is important for accessibility notes.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Add "General Notes" at the collection, service, and portfolio levels to Analytics

    Please add the following note fields to Analytics:

    Electronic Collection:
    - General notes (multiple entries)
    Electronic Service:
    - General notes (multiple entries)
    Electronic Portfolio:
    - General notes (multiple entries)

    Why is this necessary?
    You can search for many fields in Alma itself, but not all of note fields can be exported from Alma. But this is particularly important for note fields!

    Thank you very much in advance!

    Note: this is a follow-up idea to:
    Add "General Notes" at the collection, service, and portfolio levels as indexable/searchable fields
    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46387843-add-general-notes-at-the-collection-service-an

    125 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Analytics  ·  Admin →

    Hi,


    General Notes information is now available in Alma Analytics - E-Inventory subject area, for Electronic Portfolios.


    General Notes for Electronic Collections and Electronic Services will be available in Analytics in 2025 H2.

  4. MARC field 788 should be searchable

    The MARC field 788 ("Parallel Description in Another Language of Cataloging") is used by Library Archives Canada to store information about how to link to record numbers of alternate languages (ie, French to English, and vice versa). This information goes into the $$w (Record number) field.

    Having this field searchable would assist in finding records for the same things in different languages.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Filter OUT cancelled PO Lines

    Provide a facet to filter OUT cancelled PO Lines in the PO Line view. We have a lot of cancelled PO Lines with the same title as existing PO Lines, and it is confusing and time consuming to find the 'active' PO Lines. It would help us tremendously if we could filter OUT cancelled PO Lines, perhaps even by default.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. “Run a job” and “Create itemized set” should be available from the list of Purchase order lines

    When you are in a list of items on a bibliographic post in Alma you have the option to checkmark several items and choose “Manage selected” – “Run a job” or “Add to itemized set”/”Create itemized set”. Now that we have the list “All PO Lines” and can checkmark POLs in the list, it would be practical for these options to also be available for PO lines. Currently you only have the option of creating a logical set (if you add filters to the list) from the list “All PO Lines”. This would make it easier and quicker to run…

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Alma overlap analysis tool to include different identifiers in one comparison

    We would find it useful if the overlap analysis tool compare a list that includes different identifiers. i.e. ISSN, EISSN, ISBN, EISBN, TITLE in one comparison.
    Currently it only allows you to compare overlap within just one identifier. This is very important with collections from vendors that include different kinds of material.
    Being able to conduct this kind of overlap analysis is important for us in terms of making purchasing decisions and we feel that including this kind of feature in the overlap analysis tool would make this a more efficient process within Alma.

    202 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Dear community,

    We began working on this idea,

    Our solution will allow selecting up to 3 matching identifiers to be used in the comparison (in order). This will apply to both Collection Overlap Analysis and Look Up Titles. This is expected in Q3 2025.

  8. Index field 310 for the Alma Repository Search

    It would be useful to be able to search within all records with field 310 not only through the codes in 008 but also via the text in 310. We therefore suggest adding the field to the indexes for the Alma Repository Search.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Index fields 700 $$4 and 710 $$4 for the Alma Repository Search

    As 100 $$4 and 110 $$4 are already indexed and can be very useful for cataloguers for searching records in Alma, we strongly suggest having also the relator codes in 700 $$4 and 710 $$4 indexed for the Alma Repository Search.

    (Follow up of support case 6659197)

    55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Index fields 772 $$w and 830 $$w for the Alma Repository Search

    As these fields are currently not indexed but would be very useful, we strongly suggest adding them to the search indexes which are available for the Alma Repository Search.
    Field 773 $$w is already indexed and we think these two additional fields could be used for similar search queries.

    (Follow up of support case 6659197)

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Index field 773 $$g for the Alma Repository Search

    Our libraries would like to have subfield $$g in field 773 indexed for searching in Alma, because it would allow to have more precise search queries including e.g. the issue number within a journal collection.

    24 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 ISO 639-3 microlanguage names to Alma title search facets

    In Alma titles search facets, display the microlanguage name instead of its code. PCC recently approved the implementation of the ISO 639-3 language codes for use in MARC 008/35-37 and also 546$b.

    Example: where the language facet for a title search shows...

    Language
    Chinese (1)
    wuu (1)

    ...the following would be more useful...

    Language
    Wu Chinese (1)

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Dear all,

    We agree that support for ISO 639-3 languages in 041 is important, and are working on a solution for this.

    Language marc codes are used in several places in Alma, including controlled vocabulary, advanced language search by selecting a language from a list of languages (which are mapped to marc codes in the metadata) and search facet.

    The ISO 639-3 list introduces some complications to several of these workflows, such as languages that are mapped to different codes (e.g. French, which is mapped to fre / fra in the different coding systems). Our solution concept is therefore:

    1. Introducing a new search index, "Language code", which will allow searching for the language code from the MARC record directly, regardless of the source of code - planned for the coming November release (to be fully operational after the November re-indexing).
    2. We are working on future plans to offer more comprehensive…
  13. Suppress bib record when no active portfolios/services

    If a record has zero active services, it should be automatically suppressed in Primo. When we choose to use the CDI records for a collection instead of the CZ records, there is a button to "change to CDI-only full text activation." This suppresses the service, but it does not suppress the bib records. We have to manually run a job on each collection to also suppress the bib records. Most of the time this is fine (even though it's an extra step), but if some of the CZ bib records overlap with other collections, we don't necessarily want to suppress…

    132 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Title search - index the 245 field on its own

    My library catalogs most new material according to the international cataloging standard, Resource Description and Access (RDA). One requirement of RDA is that each work is given a unique access point. When cataloging a new work, our catalogers must search our database to determine if their 245 field value (subfields a, n, p) is unique. This is impossible for them to do with the out-of-the-box search fields in Alma when their title is only one or two words long because the Title field searches 38 MARC fields and over 100 subfields. In our database, a basic title search of the…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Allow to define several local search indexes, including standard MARC fields

    Following the partial implementation of idea "Ability to search via free text MARC tag and subfields" (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/17197337-ability-to-search-via-free-text-marc-tag-and-subfi) under NERS 2020 #6795, here is perhaps a more modest suggestion, that hopefully can be more technically feasible and still provide a large chunk of the missing functionality.

    Similar to the analytics "Local Param" concept, it would be very helpful if institutions were able to define 5-10 "Local Search Indexes", based on each institution's needs. These indexes should be able to include any MARC field or subfield, whether local or standard (and preferably also field combinations).

    Use case: In our institution,…

    64 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Adding the publisher location to the "Keywords" index in Alma

    Currently, the publisher location is not indexed in the general "Keywords" index in Alma. If someone wants to search for a certain publisher location, one must use the specific index because a "Keywords" search won't bring any results.
    This is particularly unpractical when searching for series or periodicals, as they often have similar names but different publishers or publisher locations, or later editions of a certain work which can be identified by the different publisher resp. publisher location.
    What confuses staff users is also that if one wants to search for a book, using the title and/or the author as…

    129 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Bulk waiving by date

    Currently we are unable to do bulk waives within set dates, for example - 01/04/2020 - 02/09/2020. We need to run bulk waives on fines accrued during lockdown periods.

    121 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Allow Fulfillment Network Member (AFN) to lend resources, but not serve as a physical pick-up location for other network members' patrons

    Since some institutions have buildings with perpetual restricted access, we have some AFN fulfillment network member libraries that are willing to send their materials to another AFN member library for pick-up, but, for all functional purposes, they are closed to the public. They don't want patrons from the other AFN institutions to visit their library in person, and thus, don't want patrons from another AFN institution to select their library as a pick-up location.

    This need has been heightened during the pandemic, with more institutions closed to the public.

    We know that turning off all circ desk hold shelves will…

    100 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Batch deleting PO's

    There is currently no system job to delete PO's. These have to be done manually using the Acquisitions>Purchase Order>Delete PO function individually in ALMA.

    We have 1000's of old orders migrated from our legacy system that are no longer required. We also now only keep 7 years worth of orders in line with current financial practice and so would like to be able to set a job to batch delete at rollover into the new fiscal period.

    306 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Dear all,


    I'd like to inform you that this idea will be implemented in a future Alma release. Below is a high level design:

    We will add the possibility to bulk delete Purchase Orders (PO). The "Delete PO" page will be updated to display a full list of all PO's in Alma. Users could select PO's and use the "Delete Selected" and/or "Delete All" actions.

    The deletion logic will be the same as it was until now when deleting only one PO each time. Users could delete a PO when it does not contain PO lines that are received, activated, or linked to an invoice. When deleting a PO, all of its associated PO lines are also deleted

    Full list of PO's that were successfully deleted or not, could be found in the job report.


    Thanks,

    Zohar Shemesh

    Alma Product Team

  20. Dark Mode/Theme

    Like the title suggest, A dark mode/theme for Alma.
    Having the white background can be very sore on the eyes, and many prefer the reverse ( black background / white font ).

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Other  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base