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

107 results found

  1. 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)
  2. 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…

    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)
  3. 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…

    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. 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)
  5. 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)
  6. 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.

    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)
  7. Changing Invoice Export approved_by API

    In the approved_by API for Invoice Export, we would like it changed from first and last name of the user to the primary identifier or another identifier, to enable unique matching to our finance system and Audit requirements.

    2 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. Enable additional types of requests via API

    The API documentation for the Create User Requests endpoint notes that "is currently NOT possible to create GENERALDIGITIZATION, MOVE or WORKORDER request." Enabling this functionality would facilitate batch processing of items for various workflows.

    2 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 filter for status to Get-Uers API

    Please add a filter for status to the Get-Users API so we can retrieve users who are either active or inactive. Currently, our integration gets all users using the API and it takes about 30 mins but more than half of the users are inactive.

    2 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. More user statistics

    Hi,

    currently the user object (https://developers.exlibrisgroup.com/alma/apis/xsd/rest_user.xsd?tags=GET) contains information regarding the total number of requests and loans as well as the total sum of fines & fees.

    It would be great to have more of these - maybe even outsourced to an own resource e.g. /almaws/v1/users/{user_id}/statistics

    Possible candidates could be:

    (1) Total loans broken down by status (e.g. renewable, not renewable, overdue)
    (2) Total loans due in n days (preferably with n configurable)
    (3) Total requests broken down by type
    (4) Total requests broken down by status and by type
    (5) Total sum of fines and fees broken down…

    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)
  11. Integration through AWS Simple Storage

    Our consortium currently maintains an SFTP server exclusively for transfering files from our student information system to Alma. The server must be maintained and monitored at a cost to us.

    I would like to be able to configure Alma to retrieve the files from Amazon Simple Storage Service (AWS S3). File transfer would be over secure HTTPS and would cost us only a few pennies annually. Implementing this would allow us to retire the dedicated server and simplify our internal IT dependencies.

    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)
  12. Allow API to set PO Line's Associated PO line

    POST&PUT /almaws/v1/acq/po-lines/{polineid}

    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)
  13. Add Signature Verification to Online Import

    Currently when configuring a Student Information System (SIS) for Online Import, you are only able to use basic authentication with an API. It would be nice to also send a signature to ensure that Alma is actually sending the message.

    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)
  14. Rapid ILL

    Add License option for "Authorized Users" for Electronic Title sets. Currently, there is no way to completely automate the Rapid ILL integration because you cannot exclude collections that we are not able to lend out.

    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)
  15. Payment integration - Supporting the import of detailed line payment information to a finance system

    Currently only the total amount paid for fines etc. can be imported to our Finance System. Can the ability to identify and import various payment types & amounts be developed. This would allow us to match payments to differing fundcodes on our finance system. Further supporting the idea of moving to cashless

    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. Add more scheduling options for Integration Profile

    In Alma Configuration > General > External Systems > Integration Profiles > Actions Tab > Synchronize > Schedule,
    is it possible to add an additional schedule time, such as "Every day at 08:00" ?

    In order to meet our daily operations, many of our colleagues request integration profile job runs between 7:30 to 9am. The options right now doesn't work for us. I am wondering if we can add a schedule option at 8am or offer a drop-down list where users can choose a certain day/hour for integration profile job?

    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. Add API for returning on-the-fly calculated blocks

    Currently the API returns only blocks which are written to the database (shown under each user's block tab). However, this does not show a full picture of those who are blocked on-the-fly such as those who have reached max cash before being automatically blocked. So the suggestion is to make sure whatever is pulled from API is the full list of all users who are blocked.

    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. Webhook events for withdrawn items should include MMS-ID

    I would like to suggest that webhook events for withdrawn items should include the MMS-ID the item was associated with. Why does this matter? We've created a custom solution for locations in Primo VE, and to save on the number of API requests to Alma and speed up the loading, we're caching the results. We're using webhooks to update the cache as needed, based on MMS-ID. However, as withdrawn items does not include information on MMS-ID, we cannot automatically update the cache when items are withdrawn.

    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)
  19. Provide sort order information for AVE (portfolio) fields in BIBs API

    When there are multiple portfolios from the same e-collection associated with the same bib record, the Alma Link Resolver (and Primo) displays them in the same order that they appear in Alma. When AVE (portfolio) information is retrieved using "expand=e_avail" in the BIBs API’s Retrieve Bib or Retrieve Bibs service, the AVE fields are returned in no particular order. AVE fields returned for a particular bib record should include an element giving the sort order of the portfolio within that e-collection, as it appears in Alma. This would allow custom discovery interfaces to display Online Access links in the order…

    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)
  20. Allow API update action of License in POLine record

    Currently, License field in POLine record cannot be updated via Acquisition API. There are no effective way to link up POLine record and License record without manual update one by one. The field were mentioned in the restpoline.xsd as

    "The license code. Relevant for electronic orders only, and is not supported for PUT. "

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

Feedback and Knowledge Base