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

1698 results found

  1. Increase download limit on large sets

    The limit on the number of records that can be download to Excel from a set is around 70,000 records. Sometimes it's necessary to download larger sets (200,000+) but this is limited by size. It would be better if there was an option to download in CSV so larger data sets could be exported. Or, the Retrieve Set Members API was improved to include the information that is present in the Excel file downloaded from the set's results page. Or, there was an additional export job that allowed a set to be exported using one of the bulk jobs under…

    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)
  2. PO Line for Standing Orders: Renewal field

    when creating a POL for a standing order, the Renewal field is required before the order can be saved/sent. But the whole point of a standing order is that I don't have to do anything to renew it; the vendor just keeps sending them. This should not be a required field; it's clogging up my renewals because I there is no action needed on my part.

    41 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. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. A purchase request with the status "Approved" can be rejected (NOT deleted) and that this information is updated in My Library

    Our proposal is that a purchase request with the status "Approved" can be rejected (NOT deleted) and that this information is updated in My Library (we want the user can see that their purchase request was rejected). The problem when you try to do this is that Alma warns that requests with status "Approved" can not be rejected.

    Ideally, when the POL associated with the purchase request is canceled, Alma should automatically reject this request and it would be displayed in Primo-My Library. (for example, the provider says the book is out of stock)

    23 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. bulk remove titles from collections (not the electronic type)

    Add the ability to remove titles in a set from a collection (not the electronic type) in bulk, as well as add titles in bulk from a set.

    56 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. Fix $g in 773 / 774 related records

    According to documentation (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/130Configuring_Related_Records_for_Physical_Inventory), $g in linking entry MARC fields (such as 773 or 774) "links to specific items for the record specified in the $w, $x, and $z subfields). According to support " it is outside Alma's current functionality to be able to be separate an item from a collection of related bib records. It would be an enhancement to this functionality."

    I am proposing that Ex Libris fix or enhance this functionality so it will work. My institution has a large collection of 'bound with' physical materials from the 1700s with analytical cataloging. For example, 26…

    39 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. Eliminate the confirmation step when editing item records.

    The process of receiving journal items is unnecessarily slowed down by having to confirm every single edit. Clicking on "Save" should be enough to get the job done. Breaking out Receive as a separate step has already added a step to the process. Please consider any and all ways of reducing the amount of time spent looking at blue spinning circles. Thank you.

    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)
  8. Make Suppressing a location function the same as suppressing a holding in all publishing jobs

    Currently, the general publishing job exports inventory in locations which are ticked "Suppress from Discovery" in Physical Locations config, when "Excluded Suppressed Locations: is ticked in the Publishing Profile.

    Alma should handle this flag as it does for Publishing to Primo and Publishing to Libraries Australia and ignore suppressed locations, otherwise what's the point of setting this at the location level and then providing an option to Exclude suppressed records. It is extra work to set this value for each individual bib/holdings record.

    55 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. 'Release remaining encumbrance' Box To Be Ticked as Default

    When looking at manually created invoices it would be ideal if the 'release remaining encumbrance box' be ticked by default. It currently is left blank and we have to remember to tick it each time.

    33 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. 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…

    97 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. Check out an item to a visiting patron's account at their home institution. Direct Pick-up Resource Sharing

    Instead of creating and managing a visiting patron's record, allow libraries to check items out onto their home institutions record. The patron could validate by choosing the institution and having the patron sign in to their account.

    As a patron I could go to any library in my network and easily check out an item there by signing into my home library and checking out the items. Everything checked out would show up on my home library's record and I could return the item either at the lending library or my home library.

    73 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. rfid: write AFI-value to the tag in item editor

    Please write the secure AFI-Value, if a staff user use the button "write RFID and save" inside item-editor.

    We use empty RFID-Tags. So we have to initialize the AFI-Value for each tag. Now we have to go into fulfillment area and return an item to write the secure value to the tag.

    If in the item-editor the AFI-value would be written it helps a lot and save time.

    30 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)
  13. Vendor Interface > Contact Information > Email addresses

    The default display for Vendor Interface > Contact Information > Email addresses, does not include an option to display the "description" field on the main page. The fields available for display are: Preferred, email address, created by, creation date, and type.

    Since most correspondence with vendors and sales representatives happen by email now, it would be useful to be able to see the description on the main page without having to click on .... and Edit for each email listed to see who is the correct contact.
    Some email addresses do not contain the person's full name, and if you…

    62 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. Move the Level of service facet to the top of the facet list

    Currently the Level of Service facet is at the base of the facet list, almost always hidden by the facets above it. I would like to see it moved to the top of the list as the timely processing of material for Rush or Express requests depends on being able to find those requests and action them quickly. As it is currently unless you specifically scroll down the list, you don't even know those requests have come in.

    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)
  15. Display record format in search results and browse pages

    We catalogue Alma-D material in both MARC and DC formats.
    We would like an easy way to determine which format a record is in when viewing it from either an Alma results page or browsing through a collection.

    This could be done with the addition of the record format field to the brief record display.

    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)
  16. Post-migration portfolio urls remain even if changed afterwards

    Post-migration side effect with created portfolios: the url from the bib is created in the new portfolio. This url remains in the portfolio even after it has been changed at a later date (not in an editable field; the url is also searchable even after it has been changed. So, old urls from a migrated system remain searchable and in the portfolio record even after editing. Change this behavior.

    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)
  17. Ability to Modify Purchase Request Role

    Our Library would like to be able to allow the purchase request form be limited by role, so that only some subset of our staff may begin the purchase request process.

    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)
  18. Overdues

    An alert function when items have gone overdue. Currently the requester will get sent overdue e-mails, but the library is not notified. When you have thousands of requests it is imposisble to search through.

    12 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. Add 880 field to the Bibliographic Details dimension table in Analytics

    In MARC bibliographic records, the 880 field is used for non-Roman script equivalents of other fields in the bib record. CJK (Chinese, Japanese & Korean) libraries, for example, may use the 880 to record the non-Roman script equivalent of the Romanized characters in a 245. We would like the 880 field to be searchable in Analytics so we can create new book lists in the CJK scripts. New book lists are very popular with our users and we would like to be able to present these lists in the CJK scripts.

    52 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 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)
  20. Use Pieces field from item record to trigger a confirmation pop-up at checkout or return

    Use the Pieces field from item records to trigger a confirmation pop-up at item checkout or return when that item has two or more pieces. Taking measures for prompting staff to add notes manually item-by-item or creating sets and running jobs to populate fulfillment notes for items that have 2,3,...9,10,...39,40,... pieces are both impractical. Not having a pieces confirmation at checkout feature is a frequent complaint on the Alma Listserv.

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

Feedback and Knowledge Base