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

    10 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. Make modification date of user account available in the User API (v2)

    In the earlier SOAP-based version of the Alma User API, the last modification date of a user account was an available field. However, in the current REST-based API, that field is no longer available.

    This piece of information is very important to us when we synchronize Alma data to ILLiad via our custom ILLiad login script. That allows to us update ILLiad as needed and insert an accurate modification date into a user's ILLiad account.

    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. Statistics for Cloud Apps

    We would like to be able to see some statistics within our IZ regarding Cloud Apps:

    • Which user has activated which Cloud App
    • How often is a Cloud App used
    • When did a user use a specific Cloud App
    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. 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)
  5. Provide all User Profile data via API

    Please provide at least GET API access to user profile data (Config -> User Management -> Roles and Registration -> Profiles). This should be full data: for each profile, include full roles and parameters.

    Currently, there is no good way to export user profile data from Alma. It does not seem to be available in Analytics; it's not in any of the code or mapping tables available via "config" APIs.

    We can use the Alma UI to export each profile to Excel individually... but that is not practical at scale, and the role data we can extract from Excel is…

    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)
  6. 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)
  7. 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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)
  12. 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)
  13. 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)
  14. 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)
  15. 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)
  16. 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)
  17. Allow copy of BURSAR file to be exported to email

    Bursar files are currently just exported to S/FTPs. It would be good if there was an option to have the files also exported to an email as a way to backup and save these files in the event they file is accidentally lost or runs into errors upon trying to upload.

    Users who manage different aspects of the billing process may not all have access to the SFTP drop in order to troubleshoot issues.

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

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

Feedback and Knowledge Base