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.

  • or

1014 results found

  1. Show a confirmation/warning about completing a lending request when using scan in items

    It would be a good enhancement to get a warning or a confirmation that a request is about to be set to completed, when we scan in an item that is currently in a resource sharing process. Because we use RFID, we have had multiple occurences of scanning in a document that already has the status Shipped Physically again by mistake, only to have the lending request irreversibly set to Request Completed, without the item ever being received by the Borrowing library. This means we have to contact the owning library and ask them to resubmit the request.

    When…

    279 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Add a function to automatically notify users when a Resource Sharing Request converted to an ILL request via ALMA API

    We implemented the ALMA API to convert Resource Sharing Request to Illiad ILL request. Currently, we can't find a way to automatically notify users when their requests being converted/transferred to Illiad. Since processing the ILL requests usually take longer than processing a regular consortium wide Resource Sharing Request, it will be very helpful to notify users automatically about this information.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

  3. Add more flexibility in Request TOU Pickup Locations policy

    We’d like more flexibility in Request TOU Pickup Locations policy.

    We have more than 20 libraries and most of them are located within walking distance. Therefore, we want our patrons to go directly to those libraries instead of placing pickup requests and limit the patrons who can place such requests. Otherwise, the number of requests will become too large to handle and logistics and management cost will become enormous. Moreover, it’s not time efficient. If users go directly, they can borrow immediately, but it may take 1-2 days to deliver since there is no direct route between…

    213 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. Alma TPRS integration Resource Sharinng - request bib / request fields missing

    Currently there are a number of fields not mapped correctly for TPRS-ALMA integration.

    We would like this to be enhanced. See #08113211

    ====ISSUES==============
    Subtitle field data entered in TPRS not appearing on the Alma side.

    Missing values for Author initials and Additional Person Name.

    (Borrowing) Book Request (Alma borrows from TPRS) - Alma sends Data "Place of publication", this value did not land on (TPRS)?

    13 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. Request Access Type in Title Report harvest

    In COUNTER R5.1, title reports are getting more important as the list of data type has been expanded. A lot of non-journal and non-book usage (e.g. conference proceedings, reports, newspapers, theses, etc.) can only be found in title reports. However, in R5.1, while data type is a mandatory attribute that vendors have to send in title reports when the reports are requested, Access type is not. Access type includes: Controlled, Open Access and Free to Read. In order to get Access type to be included in title reports, the request queries must include the request for Access type. Otherwise,…

    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,

    This idea was accepted and will be part of February Release 2026.

    We will add the option to select additional attributes to request in SUSHI harvest, for COUNTER R5/R5.1 reports:

    DR

    IR

    PR

    TR

    These attributes could be set by default setting for the institution level, and also for each report type individually within the SUSHI account.

    Thank you,

    Zohar Shemesh

    Alma Product Team

  6. Trial : request of a Trial viewer role

    There are 3 roles about Trials : administrator, operator and participant.
    But none gives access to the Trials and all information with only option to view (and not delete neither modify datas).
    A license viewer role exists in ALMA ; we request a similar Trial viewer role.

    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)
  7. Add mandatory choices for Digitization Request page

    For the Get It option of Digitization Request page in Primo, we want to be able to set some fields in the form as mandatory on demand, as a digitization request without specifying the detail is invalid. Only if we can set the following fields as mandatory, the number of invalid requests could get reduced.

    *calculateDigitButton
    *calculateQueueButton
    *chapterArticleAuthor
    *chapterArticleTitle
    *comment
    *endPage
    *fullChapter
    *generalUseLabel
    *issue (For future use)
    *manualDescription (For future use)
    *notNeededAfter
    *part (For future use)
    *partial
    *publicationDate (For future use)
    *startPage
    *volume (For future use)

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

  8. 'Not Needed After' date should be mandatory on patron physical request form.

    It would be helpful if the 'Not Needed After' date is mandatory on the patron physical request form to improve the requesting process for Patrons when there is a high demand for physical items.

    394 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hi,

    An approach we’ll be looking at is that an optional ‘Last Interest Period’ request policy will, if set, be used to set a default the last interest date (Primo and Alma). This way every request will have a last interest date set by the policy and overridable by the patron.

  9. Not "Notify user" when canceling a "Patron physical item request"

    In most situations we don’t want a request cancellation to be sent to users when we cancel a patron physical item request (Ful Cancel Request Letter). But since the checkbox “Notify user” is checked by default, the letter often gets sent by mistake, resulting in users thinking they will not receive the requested material, when in fact they will. We want the checkbox to be unchecked by default. Maybe this could be a configurable option in Alma (whether the checkbox is checked or not) so that each library can decide this for themselves?

    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)
  10. Fix Analytics request creator field to stop it changing to Alma staff primary ID when request cancelled on Alma

    When a user places a request on Primo, the ‘creator’ field in the Analytics requests table shows as ‘System’. When a request is placed by a staff member on Alma, the staff member’s primary ID shows in the creator field.

    If a request placed by a user on Primo is subsequently cancelled by a staff member on Alma, the creator field changes from System to the staff member’s primary ID. This means reporting on requests placed on Primo vs. requests placed by staff members on Alma is not accurate and the field is misleading (creator should refer…

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 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)
  11. Force article request form for ebooks

    When patrons place a resource sharing request on eBooks, we would like the article request form to appear. Currently the request form type by genre cannot accomodate this for eBooks because both eBooks and print books share the genre type book. If Ex Libris could assign eBooks a different genre type, we could easily force the correct form. However, any way to accomplish the same thing would be great! Don't care how it happens.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

  12. Keep suppressed records without items that have received more than one purchase request

    We have detected this case that we consider is an incorrect behavior of Alma.

    When a purchase request is generated, a non-visible bibliographic record is created. The problem is that if a second purchase request for the same document is generated, Alma automatically makes the bibliographic record visible, even though we still do not have copies of it. Therefore this record appears visible in Polibuscador but without funds.

    We request that the bibliographic record should only be visible when the issue or copies are available to the user, meanwhile, even if more than one purchase request has been made, it…

    38 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. 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

    68 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. Adding a lending request 'from search'

    Small thing: when choosing 'from search' for adding a lending request, can the cursor be active in the keywords search field automatically, please. Thanks.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

  15. Add a request cancellation code & reason in the Request webhook

    The current Request webhook doesn't seem to include the Request Cancellation reason. Currently it just says:

    'event' => {
    'desc' => 'Request canceled',
    'value' => 'REQUEST_CANCELED'
    },

    The comment field refers to the request, but not the cancellation reason here:

    'userrequest' => {
    'request
    time' => '2022-05-11T23:42:26.191Z',
    'managedbycirculationdeskcode' => 'EASTCIRC',
    'mms
    id' => '993815723607636',
    'taskname' => 'Rejected',
    'author' => 'Ferguson, J.',
    'item
    id' => '2365452260007636',
    'issue' => '',
    'pickuplocationlibrary' => 'ABC',
    'dateofpublication' => '',
    'managedbylibrary' => 'State Library',
    'requesttype'

    3 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  ·  Webhooks  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Modifying a partner after recieving a borrowing request should be possible

    In the SNLP workflow the partner changes from the own partner code to the partner who ships the request automatically. Therefore most of the requests have the correct partner when the item arrives at the library.
    So most of the time there is no need to modify a partner and the staff's attention to this attribute is not as high as it is to other attributes of the request. If we observe this AFTER receiving the item, there is no possibility to do so.
    Because we don't know to which partner we have to send back the item…

    78 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. Send patron a confirmation email once a hold request is submitted

    Patrons are expressing confusion as to whether their request was actually submitted. We propose that a request confirmation email be sent to the patron as soon as the request is submitted, as is done with other online order forms.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

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

    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)
  19. "Request re-indexing" option for withdrawn items

    There is a re-occurring indexing error in Alma when withdrawing items, where these items sometimes do not disappear from the Alma instance and a re-indexing job must be performed to correct it. These items often cannot be re-activated from "Manage deleted repository" and can't be interacted with. (See attachment)

    Ideally, it should be possible to request a re-indexing of the Alma-instance directly in Alma. This could be for a single record or the instance as a whole.

    51 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Automatic printing of ILL lending (pick-up) request slips

    A Pick From Shelf request (for physical or digital item requests) automatically generates an email (slip) and, through an automatic email manager, a printed request slip as well. We would like the same for incoming Lending Requests (RapidILL). For now, there is no option to print this Ful Incoming Slip Letter automatically. The only option is manual printing.

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

Feedback and Knowledge Base