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

1106 results found

  1. Print slips in lc call number order

    In the resource request management area when printing the pull slips it would be helpful to have the option to print these in LC Call Number Order.

    3 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

  2. Acquisitions API - Interested in user – add other identifiers in addition to Primary ID

    Currently Alma allows multiple identifiers to identify ALMA Users, however the Acquisitions API (Interested In users) mapping only allows “primary_ID”.

    We’d like any other identifiers used in Alma also be allowed in the mapping (e.g. Email Type). If this is added on the API parameter, staff can use the less sensitive info instead on vendor site.

    Noting that adding other identifiers in the Interested_User api parameters - is only doing what EOD acquisition workflow/mapping can already do.

    It is cumbersome for staff having need to search the requester’s primary id to be able to use this feature.

    Ref #06652820…

    34 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. Add the ability for users to view current AFN checkout information via the My Account feature on self-check machines.

    Currently, when a user accesses My Account via a self-check machine, they are unable to view any information pertaining to their active AFN checkouts. We opened a support case with Ex Libris, reporting these findings and providing details provided by our self-check vendor (mkSolutions), and their final decision was that this functionality is not currently supported, requiring an enhancement request.

    Enhancement Request: Add the ability for users to view current AFN checkout information via the My Account feature on self-check machines.

    3 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. 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)
  5. DARA

    Add an option to create a purchase request from the current drop down or after hitting the "implement" button. Sending us to the title view doesn't help us to implement the recommendation.

    3 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. Make documentation more gender inclusive

    Can we please increase inclusivity by changing to gender-non-specific language in both documentation and descriptions in coding tables?

    The Primo and Alma documentation uses very gendered terms, particularly his / him. End users and library staff are mostly referred to as he / his / him, despite libraries being an overwhelmingly female workforce. We also need to recognise the increasing numbers of non-binary users within our institution.

    I propose the following changes:
    Him or her -> them
    His or hers -> theirs
    She or he -> they

    As one example, a search on Alma documentation shows 3324 results for he,…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  3 comments  ·  Other  ·  Admin →
  7. Expose valid pickup locations and digitization departments via API

    Problem:
    The API endpoint for creating requests currently requires mandatory information such as pickup locations (physical item requests) or digitization departments (digitization request). BUT: The API does not provide a way to determine valid values for these mandatory(!) parameters.

    Impact:
    That means, every application using this API (discovery systems, mobile apps, ...) has to implement its own logic to determine valid pickup locations or digitization department. This is cumbersome, error-prone and violates the DRY-principle ("don't repeat yourself") paradigm of programming.

    Solution:
    Since Alma already has that logic built-in, it would be a very easy solution, if the…

    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)
  8. Why no 'last edit' history with operator and date in User Notes?

    We would like to query why there is currently no way to tell who has edited a User Note; rather only the Created By and Creation Date are recorded?
    Are there plans to improve this? Or if not, can this be considered for an enhancement request, in order that Fulfillment staff may add and edit notes and be able to follow the progress of such amendments from the data logged.
    Currently the only way to see a trail of updates is to add freetext in the notes themselves, or else recreate a note each time an update occurs.
    An…

    8 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

  9. Add a print server or other local print option so that slip letters can be printed locally

    As it is all Resource Request Slip Letters, Transit Letters, etc., are sent to network printers through a more convoluted process than is necessary, and has caused more pain than it is worth in some departments. This could all be solved by introducing a print server or something similar so that these slips may be printed on locally connected printers as opposed to network-only printers. Instead of having emails sent to accounts that route these print jobs to appropriate printers "in theory", the option could exist to instead print to a hard-wired printer. As it stands, print jobs are hectic…

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Completed  ·  3 comments  ·  Other  ·  Admin →
  10. Copyright Work Percentage Rule

    It should be possible to apply the Copyright Work Percentage Rule for:
    1. Patron Digitization Requests
    2. RS Borrowing requests

    And not just for:
    1. Staff Digitization Requests
    2. Library Physical Digitization 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)
  11. Keep deleted Alma objects in Analytics

    When I delete Alma objects such as PO lines, Purchase orders, course requests, invoices, purchase requests, they are deleted in Analytics as well. On the contrary, even if deleted in Alma, objects like bibliographic records or physical items are still accessible in Analytics.
    It would be great if other Alma objects were also accessible in Analytics even if deleted.

    20 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)
  12. Reactivate deferred order POLs in bulk

    For Legal Deposit we create deferred PO Lines (POLs) linked to pre-publication information supplied by publishers. When the deferral reminder date is reached and the publication has not yet been received, staff reactivate the POL. Functionally, this returns the POL to In Review, where it is validated and, if there are no issues with the POL or vendor record, a publication request is sent to the publisher.

    We typically reactivate 100-150 deferred POLs per month. Before reactivation, the relevant POLs are gathered and exported to a spreadsheet, where metadata is reviewed and any issues are resolved. We then use a…

    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)
  13. Pick From Shelf Notification for Staff

    We would like to have the ability to have "Pick from shelf" send email notifications to certain staff members when a patron requests a book be put on the hold shelf for them to pick it up. This would be easier and more efficient for us, than periodically logging into Alma and clicking on "Pick from shelf" to see if anything is there. Thank you.

    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)
  14. Preferred language visible handling requests

    Preferred language visible handling requests:

    When handling requests it would be timesaving to have patrons preferred Language visible as well as if you need to contact the user. So to have an option to choose to include Language in the Administration > User Management Configuration > Configuration Menu > General > Contact Information Pop-Up

    4 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. Metadata editor Browse Shelf List forward/back buttons should be bigger or easier to distinguish.

    The browse shelf list / call number browse feature is very difficult to use for actual browsing because the forward and next buttons are minuscule. They are not actually buttons, just the less than or greater than sign without borders. I frequently hit the wrong part and end up going back when I wanted to go forward. It's a really small target that calls for high-precision mousing.

    Requested improvements:
    1) Allow keyboard shortcuts for navigating to previous and next sections of the browse list.
    2) Create borders/margins around those buttons.
    3) Add mouse-over text showing previous/next so that if…

    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)
  16. Improve reorder functionality in Fulfillment Unit Rules

    Right now, if you add a new fulfillment unit rule, it goes to the bottom of the list. If it needs to be elsewhere, you have to use the reorder arrows to quite tediously move the rule up and down (click ... reload page ... scroll to find where rule is ... click ... reload page ... ad nauseum.)

    It would be SO much better if we could either
    1) Drag and drop the rules (and then require clicking a save button to save the new order, and/or
    2) Reorder using the row number by exporting to an external spreadsheet,…

    35 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. Making the temporary location change before the loan

    We would like the temporary location change to be made before the loan, to enable us to exclude the temporary location from the loan count using a Loan limit rule.
    Thank you for considering this request.

    3 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. Collection-level authentication method options for CDI Link in Record links

    Please provide an option to configure the authentication method applied to CDI Link in record links at the collection level. As it stands, we are able to set a preference at the institution level that is applied to all CDI collections. Our selection to apply the default proxy (in our case, the OpenAthens redirector) is not appropriate for some collections and cannot be overridden. This is especially important as more providers move to federated authentication.
    Ex Libris has configured exceptions for ProQuest legacy collections upon request, but not for other providers.
    Mintel is a good example. When the OpenAthens…

    10 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)
  19. Automatically add specific blocks to a patron record by type of fine

    We would like to be able automatically add a specific block to a patron record by a type of fine once it as reached a specified amount.

    We have recently set up a new block for oustanding resource sharing borrowing request charges (we charge our patrons for renewals). We would like this to be automatically added to the patron record once the fines `active balance' reaches £13.95 which is the equivalent of 3 renewals.

    5 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

  20. Add block information box on patron’s account landing page

    Currently, when accessing a patron’s account through the “Manage Patron Services” tab, the patron’s account landing page does not show the block information (a pop-up does show up but with incomplete information, as recorded in a SF case). In order to access block information, one has to click on the patron’s name, and then navigate to the block tab.
    The suggested idea would be that a box containing block information be added in the left-hand column of the patron’s account information, under the box containing loans, returns, requests and fines and fees information. Block types could be described with…

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