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

116 results found

  1. Option to publish new set with Publishing Profiles

    Currently, when you change the set in a publishing profile, the previous set is first published as deleted, and then the new set is published by the job. This behavior means that we have to duplicate an existing publishing profile each time we want to publish a new set with an existing publishing profile in order to get a "clean" output and to avoid overly long processing times publishing the old set as deleted. This results in the needless duplication of institutional publishing profiles and extra staff time to duplicate the publishing profiles to publish new sets. The current publishing…

    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)
  2. Add warning for active title-level-requests when relinking or deleting holding records or items

    When relinking holdings and items to new bib records or deleting holdings or items, requests can get lost. This is the case if they are on the titel level instead of on the item level.
    (Cf. https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Physical_Resource_Management/015_Managing_Physical_Resources#Relinking_Items_to_Another_Bibliographic_Record)

    Staff with the role Cataloger Extended or similar roles which allow for relinking and deleting of records, holdings, and items, would benefit from a warning that an active request is present on the title level (e.g. a pop-up) before a holding record or item is relinked or deleted.

    80 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. Make Push Selected to MDE button available for Itemized Sets

    'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…

    28 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. 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,…

    60 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. Report list of records changed after abort job

    After a user was running a discovery suppression job, and aborted they assumed nothing was changed. It would be very useful if the records that were changed before the abort were reported to the user.
    Here's an example showing an abort that occurred and the user running the job assumed since they aborted the job, nothing was changed:

    https://www.screencast.com/t/PoFqKwEjHIuH

    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)
  6. 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…

    128 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 an option to search the repository by "Assign to" cataloger / operator

    Currently there is no way to know which records are assigned to a certain user except for the "assigned to" note indication. We need a way to retrieve the records that were assigned in order to restore them back to the users' MDE, in case they dissappeard from the opened records pane. See full usecase in SFC#00957311.

    26 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 create sets from "Manage Deleted Repository" search

    We would like the ability to create a set from a "Manage Deleted Repository" search.

    Some vendors cannot use the "delete" files currently generated by Publishing Profiles. We would like to create sets (especially logical ones) from a "Manage Deleted Repository" search so that they can be attached to a Publishing Profile and help automate delete processes for these vendors rather than using an external script with the API and analytics.

    This way, someone would only have to update the deleted date range of the set periodically, or even better, more search options and filters could be created for "Manage…

    14 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. Reading lists - notification on Alma if an attempt is made to delete an item on a Leganto reading list

    We would like there to be a notification on Alma if any attempt is made to delete an item that is on a Leganto reading list, whether it is deleted individually or as part of a batch-job. The deletion could be because the physical item is in poor condition or has been lost by a user, in which case we would need to know to purchase another copy. Alternatively, we may be deleting because we have purchased a newer edition, and would need to make sure that our reading lists are updated. This would apply to both physical and e-resources.…

    15 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. Please add the ability to use the facets for Archival Materials according to LDR pos. 8 = a

    Hello,

    Most archival materials are cataloged as follows:
    LDR pos. 6 = p
    LDR pos. 8 = a
    Currently, the facet in Alma show these kind of materials as "Undefined".
    Adding a facet of "Achieve Material" according to LDR pos.8 = a, would be very useful.

    Thanks.

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

    Hi. 1. Are you stating that you want a new “Resource Type”?
    2. The definitions of the resource types are explained in the table titled “Rules Used to Create the Resource Type Field – MARC 21/KORMARC and UNIMARC” at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/Searching_in_Alma#The_Resource_Type_Field
    3. Do you want a new row in this table which would be as follows?
    Archival materials. LDR pos. 8 = a
    4. The table is read top to bottom and as soon as match is found it stops. Where in the table would you like this new row to appear?
    5. How come the title of this suggestion states “LDR pos. 8 = a” but the comment from Feb. 2 also has “LDR pos. 6 = p”? We do not think “LDR pos. 6 = p” is a good idea. That is used for “mixed materials”. On the other hand “LDR pos. 8…

  11. "Display in Discovery" from any screen in Alma

    Make the Display in Discovery action available in any screen/view of a record in Alma, not just in a repository search or in portfolio lists. There is often the need to see how a resource displays in Primo when working in an item, orders, and other areas of records.

    60 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. Create a Set of Inventory from a Title Set

    It would be very useful to be able to take a set of titles, and convert it into a set of inventory attached to those titles. Specifically, I would like to create a Portfolio set from a set of Electronic Titles. I have regular need to move groups of portfolios from one local e-collection to another. I have only a list of ISBNs to start with, which I use to create an itemized Electronic Titles set. However, moving portfolios requires a Portfolio set, which can only be created with Portfolio IDs. It is very cumbersome to arrive at the appropriate…

    52 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. Authority linking issue with bibliographic field 240

    We'd request that when Alma links up bib field 240 with a uniform title entered in authority record, it should take into account of bibliographic contents in field 240 PLUS field 100 ALTOGETHER, and link these combined contents with uniform titles entered in authority records.

    Currently, it links up the uniform title in field 240 only with authority record. So, those generic uniform titles e.g. Works, Poetry, etc. will be ambiguous, and do not have proper linking with their authority records established with author's name.

    Details, please refer to Salesforce case # 823121

    19 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. Option to export Alma search results and sets as CSV

    Right now Alma search results and sets can only be exported in XLSX-format. For performance (and other) reasons it would be good to have the option to export in CSV format.

    (Publishing this as an enhancement request was suggested by Ex Libris in public Salesforce case #00825531)

    26 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. Make approved Purchase requests searchable in Primo

    By default, Purchase Requests are suppressed from search and discovery in Primo, whatever their status (In review, Approved, Rejected).
    We would like the library to have the possibility to automatically unsuppress Purchase Requests and to make them searchable once they have been Approved.

    21 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. Add the NOT Boolean operator to the Advanced Search in Alma

    Advanced Search in Alma contains currently only AND and OR Boolean operators - it would be very useful to have the NOT operator included, so that we can exclude particular records from Logical Sets, rather than creating 2 Logical sets and then combining them with NOT, resulting always in an Itemized set.

    21 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. Multiple Quick-Cataloging Templates

    Scenario:
    There are multiple workflows and purposes for which the Quick Cataloging interface is used. For example, in course reserves, staff frequently need to create records for different resource formats beyond book and article. Staff at the circulation desks need to create records any time an item brought to the desk is not found in Alma, and these resources can take any form - from sound recordings on CD to equipment like laptop chargers.

    Problem:
    Not all of these materials fit the current “book” and “article” templates provided for Quick Cataloging. To enable efficient use of the Quick Cataloging feature,…

    163 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. Display the date a work order is created

    When a work order is created to put an item in process internally ("Technical Services (CAMS)" or "Show to supervisor" or "Preservation") it would be helpful to have Alma display the date this status change happened.

    It could be in the "item history", and/or the "In process" display, and /or in the "list of items." Currently, the receipt date is the last date displayed in these locations, which does not help with locating an in-process item.

    88 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. Use of parentheses in advanced search

    Currently advanced search does not allow the use of parentheses. We'd like to suggest the capability of using parentheses in doing some complicated search logic. This can shorten the search query a lot. Currently, we have to repeat the search queries, and apply a combination of AND/OR search logic. The attachment explains the situation with a screen shot of current search logic.

    24 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. Show orders and requests in repository search regardless of role

    Every staff member should be able to see if there are orders or requests for a title regardless of their roles.
    It's important e.g. for staff at info/circulations desks to see why a title without items is found - as well as for receiving operators to see if there are any patron physical item requests...

    Still, of course, one should only be able to edit orders or requests with the respective privilege.

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

Feedback and Knowledge Base