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

94 results found

  1. API for backdate an item

    Alma provides an API for library to build up application to do circulation operation, such as renew, change due date. However, since Nov release 2018, a parameter "overdueatchangeduedate" has been introduced and shall charge overdue fine to patron if it has been already overdue during the change due date API operation is executed. If library do not want to disable the overdueatchangeduedate, it has no way to check-in an overdue item without creating fine.

    SIP2 and offline circulation is suggested from EXL but API operation is always preferred.

    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)
  2. 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)
  3. Add additional error code to Renew loan API when an item has been renewed but the due date hasn't changed

    The Users / Renew Loan API (https://developers.exlibrisgroup.com/alma/apis/users/POST/gwPcGly021r0XQMGAttqcPPFoLNxBoEZNUiGwQUr+MuAI+35dTBcVUmYayAq/vUq/0aa8d36f-53d6-48ff-8996-485b90b103e4) currently only returns two errors - "Loan ID XXX does not exist." or "Cannot renew loan: Loan ID XXX." This API should return an additional status of "renewed, but due date didn't change" when that applies to the item in question. This would allow our locally developed catalog, which uses the Alma APIs for requesting items, to provide more complete information on why certain requests fail.

    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)
  4. Allow MarcEdit Alma Integration to update Community Zone records (via API)

     Ex Libris has allowed us to edit Community Zone records, except 022 field.  Currently, we can only open the records in the metadata editor and add a MARC field one at a time.  Using MarcEdit Alma Integration to update a record one at a time results in an error, because the Alma API documentation states that “…updating a linked Community Zone record is currently not supported.”
    
      I am requesting Ex Libris to allow updating Community Zone records via MarcEdit Alma Integration., so that we can update records one at a time, instead of adding MARC fields to a record one
    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)
  5. 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)
  6. Include "External Name" in Bib API results when returning the location of an item

    We're using the Bib API for several Alma integrations and have noticed that Bib API calls are returning just the "Location Name" for the location of items. We're of the opinion that the "External Name" should also be included in the Api results, as this is the location text that should be presented in public interfaces. Please include the "External Name" field in addition to the "Location Name" when returning the location in Api calls.

    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)
  7. Make Jobs API deal with JobNames instead of IDs

    When you want to use Jobs API to trigger a job you have to give the JobID.
    When you define the job (integration profile) the ID is invisible. The definition of one integration profile leads to the creation of several jobs with several IDs.

    To define an API trigger you have to search the ID of the wanted job manually by calling "GET /almaws/v1/conf/jobs" from here

    https://developers.exlibrisgroup.com/console/?url=/wp-content/uploads/alma/wadl/conf.json#/Jobs/get/almaws/v1/conf/jobs

    To make it all worse the ID of all jobs inside an intergration profile changes when you save a profile after changing a part of it. As one profile contains several jobs you…

    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)
  8. Include Public Notes associated with electronic collection and electronic service in the BIBs API Retrieve Bibs service

    The BIBs API Retrieve Bibs service provides electronic inventory information equivalent to that in the Primo View It display, except it only includes Public Notes at the portfolio level, not those associated with the portfolio’s electronic collection or electronic service. Up to three additional API calls are needed to retrieve the complete set of Public Notes for a single portfolio using the Electronic Resources API, and many bibs have multiple portfolios associated. We would like to retrieve the complete set of public notes for each portfolio when making a single API call to the Retrieve Bibs service.

    We're not able…

    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)
  9. sru

    The SRU does not support the exact operator (==) only the contains (=) in alphanumeric indexes. This would mean that when we search for for instance an ID, we also get in return documents where the ID searched for is part of another ID. This gives us problems if we want to for example updated the bibliographic records based on the result. Then we need to be sure that we get the correct result-list.

    Example: Searching for this ID: 20522 returns two books that are linked to the authority 20522 , but also a document with this ID in 650$$0…

    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)
  10. 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)
  11. Make Mapping Tables Available Via API

    It would be very helpful to have Alma mapping tables available through the API, similar to how code tables are available.

    Many code tables are mostly useless without their associated mapping tables, making their API exposure pointless. For example, the UserStatCategories and UserStatisticalTypes code tables need the Statistical Categories/Types mapping table to be of any use (unless you are using a single category).

    Making mapping tables API-accessible would go a long way towards making Alma more developer-friendly.

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

    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)
  13. Two-Factor Authentication (2FA) for developer portal

    Currently login to the developer portal https://developers.exlibrisgroup.com/ requires username and password. If a user account associated with an organisation is compromised this gives the malicious actor access to use/create API keys to do anything they want in Alma.

    For example a malicious actor could create an API key which allows them to access all the user information stored in Alma.

    Access to manage API keys should be locked down with 2FA, password login is not sufficient.

    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)
  14. Granular permissions for Alma API functions

    (The idea title is copied from a NERS suggestion (5311) that didn't make it to the second round.)

    When working with third parties it is problematic that granting access to the Alma API for the necessary functionality will often also open up for access to other information that we might not want to share with the same third party.

    An example is that allowing a vendor to create PO Lines via the API will also give the vendor access to the complete financial data of our institution, potentially giving them insights that could be used against us when negotiating prices.

    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. Webhook for Library Hour Changes

    It would be great if a event could be created that would fire a webhook when a librarys hours change.

    The use case for this is when we use a 3rd party system that pulls hours out of Alma, we want to be able to know the hours have changed and perform a sync sooner than say 72 hours later (or whatever interval) when the outside system refreshes automatically.

    This would be useful when we close do to inclement weather or something, so we could trigger updating our 3rd party system after the hours are updated in Alma.

    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)
  16. API for Alma requests

    As it is possible in Alma to convert an Alma request into a Alma Resource Sharing Request (a good workflow), we would like to explore creating a form for users to submit Alma requests outside of Primo and for these to be created in Alma through an Alma requests API.

    Please could an Alma Requests API be created to enable this.

    If a submitted request was not in stock, we would then convert it to an Alma Resource Sharing request (a good workflow).

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

    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)
  18. Allow patron load integration using v2 to implement override so internal elements are preserved

    Under General Administration when setting up a user record integration using v2 of the user.xsd, there appears to be some missing functionality to bring it in line with the REST user APIs.

    The suggestion is to add additional options to the synchronize method so that under Synchronization type where it currently only has 'Swap All' as the only radio button, you could toggle between this and 'Override' as per the User APIs. This would allow internal notes and other internal attributes to be preserved.

    It might also be useful to add the list of fields via selection that the Override…

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

Feedback and Knowledge Base