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. 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)
  2. 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)
  3. 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)
  4. 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)
  5. 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)
  6. 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)
  7. 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)
  8. 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…

    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)
  9. role scopes in api

    We are trying to build a simple application where our staff can request Alma roles be added to an account.

    We can retrieve a list of all roles from the Alma API for users to choose from; however, this list does not clarify what scopes are available for which roles.

    Can this info be provided via the API?

    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)
  10. Prevent GOBI API from matching activated CZ records in IZ

    Problem - The matching method used in the API will ink to the CZ bib records if it is in the IZ. The match methods are not flexible in the API integration profile when compared to something like import profiles that allow ignoring the record from the Community Zone and creating a local record.

    We would like the API to always create a local bib even if a matching CZ record exists in the IZ. Or, at least make this an optional setting.

    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)
  11. Webhook that runs when a user is updated, to show what information was changed for that user

    I tried setting a webhook to run when a user is updated.

    I wanted to know what information was changed for that user. To me, this is the most obvious use case for the user webhook.

    However, i get what seems like the post-changed user information only. I am unable to tell what information was changed.

    Request for the user webhook to contain information about what information was changed for the user.

    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)
  12. Ability to change an institutions public key for S/FTP setup

    Our institution is requiring us to change the public key we use in Alma every 90 days in the S/FTP integration connections we have set up, to adhere with our Universities tightening of cyber security measures. We would like the ability to change our institutions public key 4 times a year. Currently institutions are only assigned a static key that can not be changed.

    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. User API order response of identifiers

    When a response is received from the users API the identifiers aren't ordered.

    For example our library gates system requests a GET on the user API to retrieve an identifier, in our case <id_type desc="Additional ID 1">OTHERID1</id_type>. it can only read the first hit for this identifier

    I would like the response to order the values by status, with Active coming first.

    This would allow us to read the active value and ignore any subsequent Inactive values

    This is an example what is currently returned
    <user_identifiers>
    <user_identifier segment_type="Internal">
    <id_type desc="Additional ID 1">OTHERID1</id_type>
    <value>1234567890</value>
    <status>INACTIVE</status>
    </user_identifier>
    <user_identifier…

    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. Expand API access to all record fields across all record types

    Libraries frequently use API access to Alma records to complete a variety of tasks, provide services, and support special projects. Currently, the types of records and fields that are accessible via APIs are limited. For example, in bibliographic records, the 024 (UPC) field data is inaccessible via the API. Please Expand API access to all record fields across all record types.

    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. Allow updating Controlled Vocabulary (Form) code tables for Alma Digital via API

    Currently these tables (with codes beginning "FormCV.vocabulary") can be read via API, but attempting to update them throws a "Requested table is hidden" error. It would be useful to update these code tables automatically from upstream data, rather than requiring staff to import a spreadsheet periodically.

    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. SIP2 Kiosks should bundle loan/return notifications to a single notification

    Currently SIP2 connected self service hardware triggers a receipt notification for every single item that is loaned or returned. Would it be possible to package these notifications in to one email after the transaction is finished based on the configuration that it has been conducted on a self service circulation desk?

    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. 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' => 'HOLD',
    'request
    id' => '1419991190007636',
    'pickup…

    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. 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)
  19. Add API support for read/update/add/delete contact e-mails in Organization units: library, Institution Zone

    Use case: Library / IZ contact e-mails are used in many workflows as the e-mail sender for letters generated in Alma. In our network (31 IZs), we are running a consortia mail server. As part of the configuration, we moved the library and IZ contact e-mails to our consortia domain. For example, library@abc.ch is now library-abc@swisscovery.net. This means changing the configuration of each library contact e-mail in the IZ to a different e-mail address and adding a description.
    Initially, we made these changes manually. However, as e-mails can change, we have to maintain these changes. In addition, these e-mails…

    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)
  20. 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.

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

Feedback and Knowledge Base