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. API access to Item's edit history

    For rolling back changes in a batch of items, it would be extremely useful to have API access to the Item Changes that are reported in the History tab of each item record.

    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)
  2. Import PO Approvals Job schedule more than 1 time a day

    Currently the Import PO approvals job will only run once a day. Can this be scheduled to run multiple times a day.

    We are using rialto which is supposed to be quick way of ordering but jobs are not sent to vender straight away as it has to wait for the job to run adding delays

    If this could be scheduled multiple times a day it would greatly improve the timeline

    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. 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. 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)
  5. 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)
  6. 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)
  7. 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)
  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. 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)
  10. 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)
  11. 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)
  12. 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)
  13. 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)
  14. 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)
  15. 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)
  16. Update Resource-sharing request through the ALMA API

    Currently with the API, the only update option possible is shipping a resource sharing request. We request the option to perform other updates, e.g. change the status.
    (Updating the resource sharing request through the corresponding user-request does not work.)

    30 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…

    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)
  18. 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)
  19. 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)
  20. Integration with git

    There are many areas of Alma where integration with git would be immensely helpful. For example, Alma rules management makes it impossible to make batch updates to rules and does not offer version control. Likewise, Metadata Configuration extension management in the system leaves too much room for error and, again, does not offer version control. External management in a connected git repository would be highly preferable.

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

Feedback and Knowledge Base