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

1771 results found

  1. Allow cost per use reports for TR reports, not just TR_B1 and TR_J1

    We would like the ability to create cost per use reports based on the Cost Usage Measure TR, not just TRB1 and TRJ1 reports.

    4 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)
  2. Vendors management

    "The process that sends purchase requests to vendors sometimes does not work correctly.

    The error is only detected when the vendor notifies you that they have not received the purchase request.

    To check the error, you must go to the Job (scheduled task).

    Shouldn't there be a way in Alma to report these failures more visibly?"

    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)
  3. Customization on the background color of universal viewer (for 3D Objects)

    Some 3D objects with dark textures are poorly displayed with universal viewer (as the background color was default as "Black").
    Enhancing the background color customization feature in the universal viewer would help improve the visual experience.

    4 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)
  4. Overdue lending requests - sort by overdue-date

    In regards to overdue lending requests, it would be very beneficial to have the option of sorting by due date. By sorting this way, you could tackle the documents that have been kept out of circulation the longest first, with one (or two) clicks.

    Per 13.05.24, the options we can choose from in the "sort by" drop-down menu are:

    • Last interest date
    • Update date
    • Creation date
    • Title
    • Shelving location

    There are toggleable due-date spans in the facet menu. A sorting function would still be beneficial.

    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)
  5. The Provenance field in the physical item editor

    We would like the Provenance field in the physical item editor to be mandatory.
    It is possible to have a default for the list but that is not the same thing. We are afraid people will be not so attentive, and the default option will be the one they always choose. We want it to be mandatory and default to nothing. The user then has to choose something in order to save the item.

    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)
  6. Update expiration on roles in bulk

    We expire the roles for our student workers each semester, since they don't always come back to us after breaks. It would be nice if there was a way to update the expiration date of selected roles in bulk. I can see the benefit of having granularity of control on individual roles, like if someone's job function was changing after a certain point, but that's not a common scenario. It would be a lot easier if we could change a selection of them all at once, on both the user management screen and in the profile configurations. Even if I'm…

    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)
  7. expected receipt date

    Is it possible to display the expected date of receipt for each copy as an additional category in the list of copies?
    In this way, when booking the receipt of issues, one can immediately see whether, for example, the forecast pattern still fits or whether a journal has changed its publication date, for example. I think it's helpful. Thank you, Monika Lange, UB Paderborn

    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)
  8. Support file exchange via Odyssey

    While we are able to send and receive files with other Alma, Rapido, and RapidILL libraries via RapidX, the resource sharing world is much larger than these three systems. While ExLibris talks about supporting interoperability, we are not yet able to receive files using the file sharing method dominant among our peers, even though its platform is open source. Odyssey is a major player in the library secure file exchange world, and while we stress to our partners that they need to send non-returnables to us via other methods, often folks forget, deliver via Odyssey, and assume the request is…

    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)
  9. Add ability to sort by due date

    In certain circumstances, such as when working with renewals or overdue books, we are looking specifically for books with certain due dates. However, currently the system does not allow us to sort sets by due date, and this can make the requests we need to work on hard to find. Adding the ability to sort by due date will save staff time and frustration.

    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)
  10. Job to build relationships between host item and component parts to be run 3 times daily

    The Monograph in Series team is experiencing delays in checking that host items and component parts have successfully linked. The Job using the 773 field (Host Item Entry) and related record : 'MMS - Build Record Relations' currently only runs once a day at 22:00. We suggest this Job should be run 3 times per day to facilitate more speedy checking and prevent delays in the workflow.

    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. Alma - Standardize Cross-Field Validation Across Configuration Dialogs

    Request:
    Implement dynamic dependency handling within Alma "Add Row" dialog boxes to support Proactive Error Prevention.

    The interface should only present users with valid input field combinations, ensuring that logically impossible configurations cannot be constructed.

    While this request originated from a ticket regarding the Exclude Process Types from Publishing dialog, it identifies a broader need for platform-wide consistency in how Alma handles field relationships.

    Functional Gap:
    Currently, the "Exclude Process Types from Publishing" dialog treats [Process Type] and [In Process Type] as independent fields.

    • The Problem: Users can construct combinations that the system knows are invalid.

    • The Result: The user…

    2 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)
  12. provide means to access our Alma and Primo data via our own analytics tools

    we need to analyse and combine our data with data from other systems that are in use at the university. extracting data from Alma in a meaningful way is way too cumbersome to be useful. all methods that I am aware of are based on an Analytics report, and have restrictions on numbers of rows that can be exported at one time. E.g. we would need to compare data from our reading list system (which we can access using an ODBC connector despite the system being SaaS) with print and electronic holdings in Alma and their usage. I do not…

    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)
  13. "Interface name" field separate from Vendor records

    Have an option for the "Interface name" field in local electronic collections to be independent of Vendor records. Our vendor records are itegrated with multiple systems outside of Alma (such as our HR software, Workday). We would like to use the "Interface name" field for display purposes/logic, and possibly reporting in Analytics, but we're limited with it only be populated by Vendor records.

    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)
  14. From my assigned purchase requests, allow selection of multiple requests to be assigned to someone. Doing it line by line is cumbersome.

    From my Assigned Purchase Requests, allow assigning multiple requests at once to someone else. Going in line by line is cumbersome.

    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)
  15. Improve access to Developer Network by consortial staff

    Currently the Developer Network requires unique email addresses for accounts, even across different institutions. This prevents our central office staff from having one developer network account, with their real email address, to use across our consortium.

    Instead, they're forced to create multiple accounts, with bogus email addresses or no email addresses at all, in order to have access to multiple institutions Developer Network accounts. And, as we understand it, bogus or missing email addresses mean that the Multi Factor Authentication can not be used.

    We believe a single account for an individual, tied to a single real email address, should…

    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)
  16. List of possible CZ electronic collection types are inadequate

    According to Alma documentation and the answer from ticket 08300011 CZ electronic collection types can be characterised as:

    Abstract & Index
    Book
    Journal
    Mixed
    OPAC
    Web Service

    Our library has linked to CZ collections which only have streaming video, or streaming audio portolios. We think it would be better if there were more content types available to CZ collections to better reflect their contents

    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. Add an API endpoint to send email via Alma

    Library Open Workflows support sending email using the Alma Mail node, but this uses an internal API that is not usable outside of LOW. It would be really useful if this could be made generally available so that other applications and scripts integrated with Alma could benefit from sending emails through the Alma mail setup instead of having to configure email separately via SMTP, etc with all the resulting spam-filtering issues.

    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)
  18. Display access model in All-titles basic search results

    When you are performing a market search, the access model shows up on the holdings records if they are either attached to the POL or have been manually added to the record. This is incredibly useful and time-saving for searching! When doing an All-titles search, you have to click into the record in order to access that information. This line for access model can be easily added to the listed metadata in the All-titles results page. See attached screenshot

    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)
  19. Support "History" of "Interested User" in POL

    The "Interested Users" area of POLs in Alma currently doesn't have any "History" support; if an operator attempts to determine when or how changes were made to a POL's interested user or the notification settings for an interested user, there is no history to track changes to those fields. Having "History" support for this field would be helpful for maintaining consistency within the POL and for troubleshooting when unexpected changes are made.

    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)
  20. Option to expand "sliding panel" when making an order or viewing order information.

    In the interface that is slated to become standard on August 10, 2025, order information for a title is displayed on a sliding panel that has no option to expand to the entire screen. In this format, the order information that you are seeking takes up a smaller amount of the screen, visually unbalancing the screen and changing focus to one side, while leaving a darkened portion of the search screen visual that adds no helpful information. I have attached a screenshot.

    In the past, this sliding panel had an arrow on the left margin which allowed you to expand…

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