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. Acquisitions API - Interested in user – add other identifiers in addition to Primary ID

    Currently Alma allows multiple identifiers to identify ALMA Users, however the Acquisitions API (Interested In users) mapping only allows “primary_ID”.

    We’d like any other identifiers used in Alma also be allowed in the mapping (e.g. Email Type). If this is added on the API parameter, staff can use the less sensitive info instead on vendor site.

    Noting that adding other identifiers in the Interested_User api parameters - is only doing what EOD acquisition workflow/mapping can already do.

    It is cumbersome for staff having need to search the requester’s primary id to be able to use this feature.

    Ref #06652820 –…

    23 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. Add ability to customize the data exported by Bursar integration profile using System = Other

    When creating an integration profile of type Bursar which uses a ‘System’ setting of ‘Other’ there should be more granular control over what data is included in the export.

    If a ‘System’ setting of ‘Other’ is selected, then a 'Data' tab should be made available which will allow you to select via checkbox what fines/fees and user data is included in the exported file. The data available should at minimum include, but not necessarily be limited to, what is accessible via API.

    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)
  3. Add export start/effective date to Bursar integration profile configuration settings

    When creating a new Bursar integration profile, we want to be able to limit the transactions being exported to only those generated after a specific date. This is in addition to ‘Time before export (days)’ setting. We've never used an integration profile to export fines/fees to be transferred to our bursar office and have instead used the API. We're now stuck in a situation where we can't switch to using an integration profile because without a start/effective date there's no way to prevent the exported files from creating double billing of transactions that have already been transferred to our bursar…

    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)
  4. Bursar integration: Additional fee statuses in Alma & Allow fee status change with job Import from Bursar

    Currently there exist in Alma only the fee statuses “open”, “transferred” and “closed”. Transferred means fee was exported to external Bursar system. When the fee is imported back to Alma, it is automatically Closed. For staff it is not possible to tell if the closed fee was paid, waived, unpaid etc. without consulting the 3rd party Bursar system.
    To give the librarians and end users more transparency about the (invoice) status of a fee, we would need more differentiated fee statuses. Also, we need to be able to set this status when importing the fees back to Alma using the…

    373 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. Improve Shelf Report functionality and responsiveness

    Alma’s “Shelf Report” tool is a cumbersome, involved “inventory” process that requires users to populate a spreadsheet with barcode values, feed it to Alma, and then track down and manually identify any items that come back as an error (without Alma providing a timely or clear explanation for where a problem item might have been found if it was detected, or not detected). We’re aware of Dean Lingley’s API for “shelf inventory” and the WRLC “AlmaInventory” tool that attempt to cover some of these gaps, but neither of these replicate the same mass-scan-immediate-feedback-fix-it-and-move-on utility (without involving spreadsheets, macros, etc.) that…

    58 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. provide means to access our Alma and Primo data via our own analytics tools

    we need to analyse and combine our data with data from other systems that are in use at the university. extracting data from Alma in a meaningful way is way too cumbersome to be useful. all methods that I am aware of are based on an Analytics report, and have restrictions on numbers of rows that can be exported at one time. E.g. we would need to compare data from our reading list system (which we can access using an ODBC connector despite the system being SaaS) with print and electronic holdings in Alma and their usage. I do not…

    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)
  7. Retrieve associated collections by MMS ID

    In the Alma API there should be an end point to input an mms id number and return all collection ids associated with that ID number.

    This functionality already exists for e-collections (GET /almaws/v1/bibs/{mms_id}/e-collections) but no such functionality exists for regular collections.

    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)
  8. schedule job api support "Reload & Delete"

    Currently there are api interface to trigger running of schedule job. However there are situation where OAI repositories does not support tracking deleted items, therefore, the current solution is to update import profile harvest start date and run "Delete & Reload" manually from time to time. We would like to suggest to include support to update import profile parameter and running of "Delete & Reload" job.

    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)
  9. Add API support for licenses with type Negotiation

    We are trying to update the license terms on our licenses in the Network Zone. However, when trying to update a license with type Negotiation, the API returns an error:

    "errorCode": "69002",
    "errorMessage": "Updating negotiations by API is currently not supported",
    "trackingId": "E01-0703094132-MPLRX-AWAE786493119"

    Please add support for updating Negotiation licenses through the API.

    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)
  10. Reverse Bursar Export and Restore State of Items and Fines/Fees

    Have the ability to immediately reverse a Bursar Export and restore the state of items and fines/fees. This would be a good quick thing to have in case you have made an error.

    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)
  11. Add support for System for Cross-domain Identity Management (SCIM) standard

    System for Cross-domain Identity Management (SCIM) is a standard for automating the exchange of user identity information between identity domains, or IT systems. Supporting this standard would allow for better automation and SIS integration for institutions using Alma.

    https://en.wikipedia.org/wiki/System_for_Cross-domain_Identity_Management

    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)
  12. Address issue with incorrect fiscal period in Update PO Line API when accrual mode configured

    When activating ledgers for the current and upcoming fiscal years in Alma during API creation, there is an issue where the selected ledger (FY cycle) consistently defaults to the future financial year instead of the current one. As a consequence, the team is compelled to manually adjust the funds to ensure accurate registration against the correct fiscal year. This manual intervention hinders the full automation of the API for DDA activation, and continuous orders renewals via API, thus requiring reliance on manual checks and interventions.
    We experience this with Rialto/Alma API integration and EBSCOnet/Alma API integration.

    For Rialto we utilize…

    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)
  13. Add the ability for users to view current AFN checkout information via the My Account feature on self-check machines.

    Currently, when a user accesses My Account via a self-check machine, they are unable to view any information pertaining to their active AFN checkouts. We opened a support case with Ex Libris, reporting these findings and providing details provided by our self-check vendor (mkSolutions), and their final decision was that this functionality is not currently supported, requiring an enhancement request.

    Enhancement Request: Add the ability for users to view current AFN checkout information via the My Account feature on self-check machines.

    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)
  14. API allow quantity for pricing in POL creation

    We use the adquisitions API to duplicate POLs. When we are creating a new POLs based on a existing ones.

    We get the original POLs json and we make some changes on it to send it again in order to create a new one.
    If the POL has more than one items to be ordered (quanity for pricing field), the api ignore it and put always a 1.
    The problem is that the Alma make some calculations with the amount field and the fun percentage changes, so the POL amount increases and is not the correct amount.

    In order to…

    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)
  15. Integrate Primo VE with Generative AI techology

    The searching capabilities of Primo VE (SearchPlus) can be enhanced by using natural language processing, semantic analysis, etc. Use natural language processing to understand user queries and provide relevant search results.
    Recommend books, articles and other library resources based on input keywords, patron’s previous search history, etc. This can improve the discoverability of library resources and make it easier for patrons to find what they are looking for.

    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. Support full SIP2 protocol

    For the communication between selfcheck kiosks and Alma, the SIP2 protocol is needed.
    The full protocol can be found here: https://developers.exlibrisgroup.com/wp-content/uploads/2020/01/3M-Standard-Interchange-Protocol-Version-2.00.pdf

    Unfortunately, Ex Libris does not support all fields that would be available in the protocol (marked as 'not supported' in this document): https://developers.exlibrisgroup.com/alma/integrations/selfcheck/sip2/

    Please make the whole SIP2 protocol available for Alma.

    94 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. Warn before regenerating the SFTP Service private key

    There is a «Regenerate private key» button under Alma configuration » General » S/FTP definitions.

    This button is too efficient. This idea is to make the button a little less efficient, but in doing so make it safer.

    Clicking the «Regenerate private key» button immediately regenerates the private key for the Ex Libris Secure FTP Service. In the process it invalidates any previously generated private key and breaks all integrations with the SFTP Service. More so, the button in Alma (Premium) Sandbox does the same as in Alma Production, including breaking all production integrations.

    All it can take is one…

    35 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. 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)
  19. Alam API retrieve bibs from collection => sort by created date

    Currently the order of records from this API function is unknown.
    We should be able to sort the records by creation date/new records facet so we can retrieve only the n newest ones.

    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. 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)
← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base