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

108 results found

  1. 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)
  2. To support retrieving / updating of Portfolio "Internal Description" field via API call

    We recently migrate to Alma. Since there was no data migration for E-Portfolio fields for the Alma implementation, we need to use the API calls to update various portfolio fields with the data from the old library system.

    In particular, the Portfolio "Internal Description" field is not supported by the API call. We strongly recommend to add back this field for the API call.

    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. Allow more information to be included in the Webhook Failure letter

    As things stand, the Webhook Failure letter cannot be customised to include a reason for the failure, forcing recipients to trawl through the opaque and confusing logs to work it out. Allowing administrators to add more information to this letter (such as information from the webhook response body) would simplify the process of dealing with webhook issues.

    11 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. 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)
  5. API UPDATE Single Tag in the record (PATCH)

    Currently if I want to update a Bibliographic record I have to use a "PUT" command, but using this replace all tag in the record. So you have to pay attention if you don't put a tag this will be lost.
    So we would like to have the possibility to update only one tag in the bibliographic record for example using another command, in Rest API usually is used a PATCH command that allow to change a single element of the resource. So I ask to implement a real UPDATE command (PATCH for example) so we could change single or…

    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)
  6. The "maximum renewal date" (max_renew_date) should be part of the fields that are provided by API

    The max-renew_date is viewable in Primo, but if you use another Discovery it can't be displayed because it is not provided by API.

    50 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 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. FTPS support for SIS integration

    Add support for FTPS protocol for the SIS patron load integration

    8 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. Send ebook access models through the autoholdings integration profile

    It would be very helpful if vendors could send ebook access models (1U, 3U, UA), and Exlibris could load them into the portfolio information, as part of the autoholdings integration profile, especially for Ebook Central. Updating this manually is difficult, especially given that ebooks are added to this collection continuously through many different feeds and not all of them have PO lines where access models can be added. We want to take full advantage of this great new feature, and it would be great if it could be automatically managed for us.

    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)
  10. 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)
  11. Remove all items from Collection with single API call

    When editing a Collection in Alma, there is an option to "Remove All" items, emptying the collection. This is very useful, for example, when updating a rotating collection such as the New Books shelf. Unfortunately, doing this via API requires issuing a separate call to remove each individual item--potentially hundreds of calls just to empty a single collection so that it can be updated. There should be a single call that will empty the Collection.

    9 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. NCIP request security

    Currently a valid NCIP request from anywhere can retrieve information about a given library's patrons. In order to exploit this, the attacker would need to know server address, institution code, code of the profile for ILL, all of the correct metadata, and the correct message type/formatting. It's not trivial to gather up all that information for a given institution, but much of the information is publicly available (e.g. NCIP message formatting is a public standard), and none of it is generally treated as a secret.

    Given the continuously evolving state of library systems security, it would be good to prevent…

    81 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. Alma Users API Web Service Result - Reference User Role Description instead of Number

    When updating a User via the API, if there is an issue with a User Role Parameter, the Web Service Result contains an error message like the following:
    | errorMessage: Mandatory field is missing: user_role parameters [ServiceUnit] for role number 37

    Would it be possible to reconfigure the error message template to return a message like this?
    | errorMessage: Mandatory field is missing: user_role parameters [ServiceUnit] for role [Receiving Operator]

    This would save time in looking up the description in code table HFrUserRoles.roleType.

    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)
  14. API - Fines & Fees Function - Single Email Receipt with Line-Item Summarization for Partial-Payments

    Howdy,

    Our organization has given our patrons the ability to submit bulk (line-item) full/partial-payments on individual fines & fees.

    When processing these transactions, we must send individual line-item transactions to the API which results in individual payment-receipt emails being sent to the patron.

    /almaws/v1/users/{userid}/fees/{feeid}

    Conversely, the API’s pay-all function sends out a single payment-receipt email with a summary of the fully-paid line-items.

    /almaws/v1/users/{user_id}/fees/all

    We would like a function which can transact an array of line-item payments and generate a single payment-receipt email like that of the /fees/all function.

    Something like:

    /almaws/v1/users/{user_id}/fees/partial

    Parameter:
    fees (array) [{fee_id, amount}…]

    Thank you,…

    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)
  15. Accession number available by API

    Hello,
    To be able to develop several external tools (relabelling, cataloging, ...) we need to access the "Accession number" table by API (read and write).
    This would probably give many other clients oportunities in developing external tools for managing physical collections.
    Best regards.

    18 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. WebHooks for Orderlines

    We would like to have WebHooks, that are triggered by acquisition events.

    For example sending of POs shall trigger a Web Hook (similar to a finished job) to start subsequent processes via the Alma-API. In principle, we could also use the packaging job, however, if orders are sent directly, this does not work.

    Use case: Extrenal setting of call numbers, inventory counters, setting of item properties within multiple item orders.

    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. Support automatic weeding of holdings in the Swedish national catalogue

    The Swedish national Ex Libris user group (ElugSWE) would like Alma to integrate with the Swedish national catalogue (Libris), so that when a bibliographic record is deleted in Alma, the corresponding holding record is deleted in Libris.

    (We have discussed this idea with the local Ex Libris representative and also a customer success manager, and were recommended to submit it to Idea Exchange.)

    This integration exists for multiple other library systems, and it would be really welcomed if Alma could match them on this.

    The integration would need to make use of Libris API:s, documented here:

    https://github.com/libris/librisxl/blob/master/rest/API.md

    The sections most…

    24 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. Webhook for holdings

    We have webhooks from Alma that can notify an external system when changes to items or bibs happen. We would like to have a webhook for changes to holdings. This would be helpful as we have an offsite storage system and we would like to update it as soon as items are switched to that location in Alma, so that when the items arrive there the external system has that update.

    0 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. ALMA Cloud apps; can we enable this feature role-based

    with lots of interest we have followed the Igelu presentations about ALMA Cloud Apps.
    For now we have not enabled this feature though we would like to use it.
    We do not want all our ALMA users to be able to use all these apps.
    It looks as now the only choice is 'enable or disable'.

    Is it possible to add Alma Cloud apps role based?
    For example for our users who have a General Administrator role or to the meta data experts in our library?

    Kind regards, Hiltje
    Leiden University Library, The Netherlands

    48 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)

    Dear community,

     

    Thanks for raising this idea.

    I would like to better understand the requirement:

    Do you want to limit users to be able to install/use only cloud apps that they have the proper roles for operating? Meaning - users will not be able to install/use a cloud app they do not have the required roles to operate it.

    or

    Do you want to allow the use of cloud apps only for users that you specifically choose (by giving them a dedicated role for that)? Meaning - users will be able to install/use cloud apps only if they were given a dedicated role for that (for example, a new role "CLOUD_APP_OPERATOR")?

    or

    Both?

    or

    Other?


    I would be happy to hear your thoughts and clarifications.

     

    Thanks,

    Uri Beladev

    Platform Product Management team

  20. API conf/sets - Always add member/@link

    Currently not all calls to conf/sets will return member-elements with links. This will make a call to e. g. electronic portfolios close to useless, as there is no API-call that can be done with the portfolio's ID only.

    Ceterum censeo I don't think that this is an enhancement, but Case 00874282 was not interpreted as this being a bug.

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

Feedback and Knowledge Base