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

134 results found

  1. separate work orders from patron requests

    On the results from a physical titles search, each title shows the number of requests pending for that title. This number includes both patron physical item requests and internal work orders. In order to see what requests fall into which category, you have to click on the Requests link and wait for the information to load in the slider pane (this can take some time if the number of requests is large). Then you can filter by request/process type.
    It would be useful for these two categories of requests to be separated from each other. For example, we circulate laptops…

    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. Block when overdue: add a "days per overdue days" unit of measurement option

    Hello everyone,
    when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
    There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first…

    57 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. Post download links for digtization requests to user's Primo account

    Currently, Alma will post a download link to the user's Primo account when a resource sharing request is filled digitally. Alma does not post a download link to Primo when a digitization request is filled. This difference can be confusing for users, so it would be very helpful if download links for both resource sharing and digitization requests were posted to the user's Primo account.

    43 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 "Send Query to Patron" option to Digitization requests menu

    Currently there is not option to ask the patron about a current Digitization request. These requests are often submitted with little or vague information and a way to contact the patron for clarification is needed. The "Send Query to Patron" option for this purpose is included under "the ellipses" for Resource Sharing requests. Why does it not appear for Digitization?

    8 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. Please add restrict request function for fulfillment network requests in Primo VE between institutions.

    We are a library consortium facilitating interlibrary loans through a fulfillment network with Network Zone, rather than AFN.

    It allows patrons to find items from other institutions directly and request them. Our goal is for patrons of Institution A to use Institution A's Primo VE to request books from Institution B.

    If Institution A has the book available for borrowing, requesting the book from Library B will not be possible.

    Implementing the above feature in Alma to restrict requests in this manner would not only save shipping costs but also reduce waiting times for patrons.

    We previously submitted this requirement,…

    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)
  6. Usability issues with the New Circ UI

    1. When processing items from a cart, if they are scanned at Return items and the item is a Ship physically item, the new UI just brings up the item and in small letters says Next Step - System - and the library its to go to. It also says not on loan (which in this case is not helpful, because there is an active request). The system "ships" the item, but doesn't tell you that it did and in order to print the shipping slip staff have to go back to the lending queue and find it.
    2. We believe if…
    11 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 a "Pick up location" line under the "Pick Up Requested Resources" columns

    For institutions with multiple campuses that share items, there is no way to see what the pick-up location for an item is on the Pickup Requested Resources page. you must export the data to excel, print it out, process the hold, or search for the item's request separately. This creates a lot of unnecessary steps for such simple information and makes it difficult for institutions that track item movement between campuses. My suggestion is to add a line in the columns under each request that states what the pick-up location is. View files to see example. Thank you

    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)
  8. Convert digitization request to purchase request

    I would like to convert a request from a scanning request to a purchasing request, particularly when the permissions cost is high. I am not sure if this is a Alma or Rialto workflow, but it would be nice to do a "search in Market" to find out price and auto-reject the way we can do in Rapido. Additionally, we would like 'Pay-per-use" functionality from Alma digitization requests.

    1 vote
    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. Improve Request Limit configuration to match Loan Limit configuration

    Request limit configuration is currently extremely limited:

    • It applies across the whole instutition
    • It is a single limit which can't be distinguished for different material types, items or kinds of requests
    • It is linked only the user group of the patron.

    We propose that request limit config should match loan limit config and allow for other variables:

    • Application to a specific library
    • Limit by item policy, location, material type, user group, statistical category and job category.

    An additional improvement would be to allow some link up between request limits and loan limits. They are particularly problematic for remote storage integrations…

    6 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. Adding bib- and item-level information like "MMS ID" and "Barcode" to a patron's "Requests"

    When using "Fulfillment -> Manage Patron Services" to view a user's account, the "Requests" tab shows a patron's current requests, but these lack identifying and linked information beyond the title. Being able to view and click on a link to the MMS ID of the record that the request is for would be helpful since a library may have multiple records with the same title; in addition, item-level information like possible Barcodes for items that would fulfill the request would be helpful in visually confirming that a particular item in hand matches a patron’s request.

    Would it be possible to…

    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)
  11. Make all Address Types usable for Personal Delivery

    Only addresses with an Address Type of 'Home' or 'Office' can be used for Personal Delivery. This is a problem for us because the addresses that come through into Alma for each user from our student information system integration are in Address Types ‘Home’ and ‘School’. We don’t use ‘Office’. We are unable to get the systems integration changed for local reasons. We would like to see all Address Types made usable for Personal Delivery, with options in the Request Terms of Use to enable us to show only the Address Types that we use and therefore that we want…

    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)
  12. Improve job "Requests - Handle Expiration steps"

    The job "Requests - Handle Expiration Jobs" updates requests and at present, the output of the job informs only on the number of outputs. The job can block on a request-ID which then must be manually handled.
    In order to save time and better inform the lending libraries, it would be helpful to have at least an information on any Error-causing request, with it's request-ID. Ideally it would be great to also have an output of successfully handled requests in form of a list, which can be exported to Excel.

    Improve the job "Requests - Handle Expiration Jobs" with output…

    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)
  13. Open / Closed Stacks Request Possibilities Priority

    Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.

    In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.

    We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item…

    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. Allow us to create duplicate borrowing requests via the Users API

    The SUNY system has created an ILLiad addon that automatically converts ILLiad borrowing requests into either Alma borrowing requests or Alma hold requests (depending on whether the requested item is locally available). We're using the Users API to create these requests in Alma. We've figured out how to override the Alma function that blocks the creation of duplicate hold requests when necessary, but we there's no way for us to override the function that blocks the creation of duplicate borrowing requests. Please add this feature to the Users API.

    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. 1 vote
    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. Improve integration between 'Place on hold' in Rialto and Tasks widget in Alma

    If the 'Place on hold' option is ticked when placing an order in Rialto, there is no notification in the Tasks widget in Alma to let Library staff know when an item has arrived. This means we are unable to prioritise the processing of those newly arrived, requested items. If we were to use 'Place on hold' in Rialto, then we wouldn't find out an item had been requested until we happened to scan it in. We would like an integration between Rialto and the requests functionality putting in place to make it apparent to Alma users when items received…

    1 vote
    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. Monitor request page

    Currently on the Monitor requests page for the Activity status filter there are the following options:
    Completed; Active, All. It would be useful to have the option that filters requests with status Rejected

    1 vote
    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. Notification on 'Pick from Shelf' link

    Can a notification or flag be added to the 'Pick from Shelf' link to alert us to new requests? Something like the notifications on Announcements and View Recommendations. Our requests are often sporadic, and it would stop us from having to keep checking the 'Pick from Shelf' list and help us be more responsive to requests.

    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)
  19. Request limit

    It will be useful to limit the number of request for a specific library. Likewise for loan limits.
    If an institution has more than one library then it may want, for example, to allow a patron to borrow from several of them. Then the order limit should be correspondingly larger. However, if the loan limit is larger than the request limit, this situation can be confusing for the user. For example - a patron has a request limit of 10, and loan limit 5 in Library A and 5 in Library B. However, for the moment he can request 10…

    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)
  20. Booking request - possibility to configure a blocked period

    We are using the booking request for technical equipment which has to be prepared for lending previously. We want that an item can not be booked shorter than 3 days in advance, so the team is able to prepare everything. This ist not configurable yet.

    27 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)
← Previous 1 3 4 5 6 7
  • Don't see your idea?

Feedback and Knowledge Base