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

    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)
  3. FTPS box

    Currently ALMA merely supported SFTP (SSH ftp), not FTPS(FTP over SSL). Please add the function to support FTPS(FTP over SSL) provided by BOX.com so that our ALMA integration profile could use it.

    Best!

    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)
  4. 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)
  5. Payment integration - Supporting the import of detailed line payment information to a finance system

    Currently only the total amount paid for fines etc. can be imported to our Finance System. Can the ability to identify and import various payment types & amounts be developed. This would allow us to match payments to differing fundcodes on our finance system. Further supporting the idea of moving to cashless

    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. Allow institutions to export and import all configurations from Alma

    Ex Libris has the new policy of forcing a refresh of the sandbox for all customers on the premium sandbox twice a year. This presents a significant challenge for institutions that use the sandbox actively, because it means that before every refresh, we have to go through the largely manual process of exporting all configurations out of the sandbox so we can keep record of them. Then if we want to recreate the old configurations, we have to do this manually.

    Ex Libris offers no way to export or import these configurations in bulk. This policy change reduces the value…

    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)
  7. Payment on Self Check Kiosk SIP2

    SIP2 protocol is over 20 years old. More payment types should be allowed (2-char, fixed-length field (00 thru 99)) and not restricted to those only specified from 00 to 02.

    Value Payment Type
    00 cash
    01 VISA (this is not even relevant anymore)
    02 credit card

    Other LMS systems are able to configure extensions to the payment type using the 03 up to 99 to link payment types that are used in their LMS.

    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. Rapid ILL

    Add License option for "Authorized Users" for Electronic Title sets. Currently, there is no way to completely automate the Rapid ILL integration because you cannot exclude collections that we are not able to lend out.

    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)
  9. 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)
  10. 34 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. Empty User Roles via API

    We would like to be able to empty all user roles using an API call. Currently, User_Roles is the only segment that keeps untouched when the API call object does not contain any roles. This makes it necessary to keep at least one role as a parameter and it makes no sense from the API usability as it actually always returns the full user objets including empty roles arrays when we delete all roles from Alma end-point.

    135 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. SIS Import/Synchronise: improve invalid character handling

    When the Alma SIS Import/Synchronise job runs, if any of the files contain an invalid XML character, the entire job is aborted. The consequence of this is that user data held in Alma might be out-of-date, depending on whether it has recently changed in central systems. I assume this behaviour occurs because one of the initial steps when the import runs is to parse the input files as a whole, rather than parsing each user record individually.

    This Ideas Exchange ticket requests that the SIS job is improved so that the job does not abort, but instead skips over the…

    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)
  13. Changing Invoice Export approved_by API

    In the approved_by API for Invoice Export, we would like it changed from first and last name of the user to the primary identifier or another identifier, to enable unique matching to our finance system and Audit requirements.

    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)
  14. Add Signature Verification to Online Import

    Currently when configuring a Student Information System (SIS) for Online Import, you are only able to use basic authentication with an API. It would be nice to also send a signature to ensure that Alma is actually sending the message.

    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)
  15. SRU (Search/Retrieve via URL) for item records

    Currently, SRU can be used to retrieve Alma bibliographic and holdings record data. In the documentation below, there are "bibliographic options" and "holdings options".

    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/190SRU_SRW_Search

    Our institution needs data from Alma on the item record level. Use case: we'd like to use SRU to count the number of items with the same item call number.

    Currently if we use the "marcxml" record schema, the <numberOfRecords> returns the total number of bibliographic records. The "isohold" schema returns the number of holdings records.

    Neither schema returns the total number of item records with the same item number (especially in situations where 2…

    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. BIBFRAME support for UNIMARC

    Currently, Alma can expose bib records in Linked Data in BIBFRAME format, but for MARC21 records only. I ask to develop the support for UNIMARC too, in order to expose UNIMARC records in BIBFRAME format through APIs, Publishing and the Alma Resource management UI.

    17 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. Alma to DOCLINE OAI-PMH Integration

    Integration for automated harvesting of eJournal and pJournal holdings from Alma to Docline (National Library of Medicine's automated interlibrary loan (ILL) request routing and referral system).

    79 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 "Authenticate or refresh user" - Working for all user account types, not only for internal user accounts

    API "Authenticate or refresh user" - Working for all user account types, not only for internal user accounts

    Now the "Authenticate or refresh user" works only for internal users where Alma is the identity provider.
    It would make things a lot easier in many applications around alma if it would also work for external user.
    Like:
    Internal user -> no change
    External user ->
    * Take the ID in the URL als ID in the external IDM and the passwort like in case of internal user.
    * Check ID and password against the external IDM, just as in case of…

    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. Allow part payments to be sent from Alma to WPM for online payments

    Allow a user to choose the sum they wish to pay when making an online payment via WPM. At the moment it is only possible to pay the total fine/fees owed, no option is given to enter and pay a lesser amount.

    While WPM will accept whatever amount is sent from Alma, and Alma will handle whatever payment is sent from WPM back to Alma (closing fees as possible, and partially closing fees if the paid amount does not exactly match the owed amount), Alma can only send WPM one payment element with the total amount the user owes (as…

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

Feedback and Knowledge Base