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

68 results found

  1. Add support for System for Cross-domain Identity Management (SCIM) standard

    System for Cross-domain Identity Management (SCIM) is a standard for automating the exchange of user identity information between identity domains, or IT systems. Supporting this standard would allow for better automation and SIS integration for institutions using Alma.

    https://en.wikipedia.org/wiki/System_for_Cross-domain_Identity_Management

    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)
  2. Institutions working in a Campus level generate a monthly Alma Collection Report with InCites

    Please allow institutions working in a Campus level to use the institution’s electronic holdings with InCites to generate a monthly report in Web of Science. Per Ex Libris tech support (case #07213024), the JRC Cloud App is not designed to work when an institution has campuses configured. These reports would provide institutions with multi-faceted collection development and utilization analyses for journal titles.
    Documentation: https://developers.exlibrisgroup.com/appcenter/journal-citation-reports-jcr/

    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)
  3. Check box option to disable Alma from appending file names in publishing profiles

    We publish files to many third party vendors. Some vendor systems must have their files named with a certain convention and CANNOT process them if that filename convention is altered in any way.

    Alma publishing profiles are current configured to append "_new" to the end of files it publishes, even if you specify a file name already. We would like the option to either enable or disable each publishing profile from appending the filenames it sends. They can be enabled by default, or not, but the option would be helpful.

    Use case: We are publishing files of electronic holdings to…

    5 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. Retrieve associated collections by MMS ID

    In the Alma API there should be an end point to input an mms id number and return all collection ids associated with that ID number.

    This functionality already exists for e-collections (GET /almaws/v1/bibs/{mms_id}/e-collections) but no such functionality exists for regular collections.

    5 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. 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)
  6. API access to suspend realtionships among libraries

    Currently, there is no API access to manage the suspension of relationships between libraries in Alma, which requires manual intervention to suspend them at the appropriate time when there is an interruption in the logistics shuttle between libraries. This process can be time-consuming and requires staff to handle it during off-hours, such as early mornings or late nights.
    We propose implementing an API endpoint that would allow libraries to schedule the suspension of relationships at a given date and time. This feature would help streamline operations, reduce manual intervention, and ensure that interruptions in logistics are handled efficiently and at…

    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. API allow quantity for pricing in POL creation

    We use the adquisitions API to duplicate POLs. When we are creating a new POLs based on a existing ones.

    We get the original POLs json and we make some changes on it to send it again in order to create a new one.
    If the POL has more than one items to be ordered (quanity for pricing field), the api ignore it and put always a 1.
    The problem is that the Alma make some calculations with the amount field and the fun percentage changes, so the POL amount increases and is not the correct amount.

    In order to…

    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. Mail Handling Integration - In September 2025 Microsoft Exchange Online to retire Basic auth for Client Submission (SMTP AUTH)

    Are there plans for supporting more modern authentication methods (e.g., oauth2)?

    I imagine that there are quite a few customers that use Microsoft Exchange (office365) as a relay and will be affected by the retirement of basic auth for Client submission. What, if any, are your plans for handling this?

    Thank you

    Related article:

    https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-to-retire-basic-auth-for-client-submission-smtp/ba-p/4114750#:~:text=Today%2C%20we%20are%20announcing%20that,SMTP%20AUTH)%20in%20September%202025.

    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. Reverse Bursar Export and Restore State of Items and Fines/Fees

    Have the ability to immediately reverse a Bursar Export and restore the state of items and fines/fees. This would be a good quick thing to have in case you have made an error.

    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. 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)
  11. 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)
  12. 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)
  13. Allow loans/requests APIs to override blocks and limits

    When using the Alma UI staff are able to override user blocks and loan/request limits when loaning an item or creating a request. With the API this is not possible. It would be helpful if the APIs had a parameter to perform a staff override in the same manner. This would allow automated loans and requests to work in scenarios where staff would have overridden the block/limit, and where it is desirable that the loan/request always succeeds.

    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)
  14. Add MARC namespace to Alma OAI feed

    In our Alma OAI feed, tags lack the marc namespace prefix, where the same prefixes are present in our current Voyager OAI. That is:

    Alma OAI: <controlfield tag="005">20231016143437.0</controlfield>
    Voyager OAI: <marc:controlfield tag="005">20231016143437.0</controlfield>

    Can we add the namespace prefix?

    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)
  15. Address issue with incorrect fiscal period in Update PO Line API when accrual mode configured

    When activating ledgers for the current and upcoming fiscal years in Alma during API creation, there is an issue where the selected ledger (FY cycle) consistently defaults to the future financial year instead of the current one. As a consequence, the team is compelled to manually adjust the funds to ensure accurate registration against the correct fiscal year. This manual intervention hinders the full automation of the API for DDA activation, and continuous orders renewals via API, thus requiring reliance on manual checks and interventions.
    We experience this with Rialto/Alma API integration and EBSCOnet/Alma API integration.

    For Rialto we utilize…

    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)
  16. More options for scheduling integration profile jobs

    For our local purchasing processing, we really need to be able to schedule invoices to be exported to the FTP server every Monday evening at 5:00 pm. This is not currently an option. This is specifically the Export Invoices For Payment job in the Integration Profiles.

    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)
  17. Output Location External Name in z39.50 OPAC format

    Alma provides the ability to specify an External Name for a location and this is used in PrimoVE instead of the location Name. However, when item information is exposed via the z39.50 OPAC format the "shelvingLocation" contains the location Name and not the External Name. The External Name should apply in all cases where the location name is exposed outside of ALMA including z39.50.

    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. Integrate Primo VE with Generative AI techology

    The searching capabilities of Primo VE (SearchPlus) can be enhanced by using natural language processing, semantic analysis, etc. Use natural language processing to understand user queries and provide relevant search results.
    Recommend books, articles and other library resources based on input keywords, patron’s previous search history, etc. This can improve the discoverability of library resources and make it easier for patrons to find what they are looking for.

    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)
  19. Alam API retrieve bibs from collection => sort by created date

    Currently the order of records from this API function is unknown.
    We should be able to sort the records by creation date/new records facet so we can retrieve only the n newest ones.

    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)
  20. Optimizing Library Operations Through Alma API Integration

    Hello everyone,

    I am seeking expert guidance on effectively harnessing Alma’s API capabilities to elevate our library’s operational efficiency. As we strive to streamline processes and strengthen system integration, including mulesoft API integration. I am eager to learn from the collective wisdom of this community.

    I am particularly interested in insights on:

    Best Practices: Proven methods for seamlessly integrating Alma APIs with external systems to ensure optimal data flow and mitigate potential challenges.
    Overcoming Obstacles: Common hurdles encountered during Alma API integration and successful strategies for resolution.
    Performance Enhancement: Techniques and tools for optimizing Alma API performance, especially when…

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