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
  1. API for managing scheduled jobs configured in integration profiles

    The enhancement described and completed in the idea http://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/9592206-api-to-interact-with-alma-job-scheduler is fine as far as it goes, but the current functionality does not allow us to interact with jobs launched automatically by Alma on a periodic basis; it only supports jobs launched manually by a user.

    Our use case: we have scheduled periodic uploads of SIS student data
    configured in a SIS integration profile. We would like to get a formatted list of rejected users, errors, etc. that happened during the automatic load available as a file on our processing server, so that the list can be parsed by a script…

    84 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Synchronizing XSL templates with external systems

    When customizing XSL letter templates, it would be helpful to be able to import/export these to/from Alma. This could be done for example by webDAV. This should make it possible to use an external version control system, like git. The templates are many and complex, and version control would be useful for managing revisions. This would also enable syncing to templates between production and sandbox environments.

    77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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).

    54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Patron Self Registration

    Make Patron Self Registration possible via Primo. This feature would need to be configurable by libraries and able to be turned off altogether by the library. Configuration options could include: what data elements are required, whether new accounts need to be reviewed before they are active.

    53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Alma to support Hold Information in SIP2 checkin reponse

    We have a sort assistant (RFID equipment) that displays the next step/destination of an item on screen. It also generates a hold slip (with the hold patron name if there's a request for that item) or a transit slip (if it needs to be sent to another library).
    However the hold information is not provided in the SIP2 checkin response which means having to scan in the item again in Alma to get this information.

    Could the following SIP2 extension fields be added to resolve this issue:

    CY - Hold Patron Id
    DA - Hold Patron Name

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Exclude expired users from bursar integration job

    Our bursar is not currently able to collect charges from users who are no longer at the university. So we want to be able to able to exclude these patrons from the reports that are sent to the bursar with bursar integration. The fact that this doesn’t exist now has prevented us from implementing integration.
    We would like this functionality to be an additional filter in the bursar integration settings that would exclude users whose expiration date is in the past. If it could specify an actual or relative date, this would be an additional improvement.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Upload electronic holdings job: Add vendor's name information

    The name of the vendor is missing in the "Upload electronic holdings job" report.
    We can only see the name of the integration type.
    To identify the vendor, we have thus to remember the name of the vendors concerned by this integration profile (at this time, Elsevier or Ovid) and the date of the processing job.
    As new integration profiles are planned for other vendors (Proquest, Springer,...), this will be no more manageable.
    Thus, we would like to see the vendor name in all useful places (reports, "Monitor job" page, "Scheduled job status")

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Provide access to files FTPed to third-parties

    We run a daily scheduled "Publishing to OCLC" job which sends OCLC our new and changed MARC records via FTP.

    From time to time, OCLC email us to let us know that some files were not processed due to errors in the MARC (typically blanks in the leader). To fix these, we need to download the problematic files, correct them, and manually upload to OCLC again.

    However we don't have access to these files in Alma. (OCLC deletes them from their server when their automated process picks them up so we can't get them from there either.)

    We managed to…

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. More API options for Borrowing Requests

    The current API:s for Borrowing Requests are limited to get a list of request for a specific user, get a specific request of a specific user or create a new request.

    To be able to integrate better with other systems, in our specific case the Swedish national ILL broker system "Libris Fjärrlån", we would need to be able to update and delete requests as well.

    We would also want to retrieve lists of requests without knowing the user, for example by status, by external system or other criteria.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Add more options for ILL integration

    Adding ILLiad integration to Alma was welcome but also brings more issues into the system. For example - patrons are shown in their account via Primo that ILL loaned items are not renewable. They are but not via Alma. A customizable message for the Resources sharing library that would display in "My Account" saying "Renewable via ILLiad" would be welcome. We have configured ILLiad to send courtesy notices. Now that we have integrated with Alma patrons get two courtesy and "due today" letters because Alma cannot turn off letters for specific locations. The ability to turn off those two letter…

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. SIP2 over https

    SIP2 further development: To provide ability to develop more versatile and agile self-service concepts and processes for the staff, it would be useful to take into use ‘SIP2 over HTTPS’ in Alma. The basic message between library automation and Alma would still be in accordance with the standard 3M/NISO, but message pairs would be encapsulated in XML.

    http://biblstandard.dk/rfid/dk/rfidsip2over_https.htm

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Limit the IP range that can call the Alma APIs

    I would like to suggest an enhancement in ALMA regarding APIs: in addition to the API keys mechanism we would like to limit the IP range that can call the Alma's APIs.

    This feature can be useful for System Administrators and the main benefit is to increase security and user data protection.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Create item via API addition of parameter to generate description field

    Creating item via API using -POST /almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items

    Addition of a parameter "generate description" , when this flag is set to true in a call Alma would generate the description field from the provided enumeration data based on the description templates set in config.

    Looking for an equivilent ot the create digital representation paramter "generate label".

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Writable Code-Table API

    Code-tables, like UserStatCategories, really demand a writable code-table API.

    As our institution adds departments and majors, the only choice we have today is to assign a human to manually update the table in a regularly occurring, human friendly frequency.

    For a machine, it would be trivial to update and synchronize the UserStatCategories code-table via API, daily, hourly, whatever.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Field creation date by changes via API

    While changing a specific field in a user records via API the "creation date" should be changed only in this field and not in any other fields – which happens now – in order to be able to recognize the newest changes in a user profile.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Allow patrons to request extension of hold shelf period in 'my Library account' list of requests in Primo

    Alma-Primo integration as requires My account functionality to Requests from Alma.

    For Patron physical item requests which have placed on the hold shelf it would be very useful to add the ability for Patrons to Request an extension of the hold shelf expiry. This should only appear if there is no outstanding queue of requests against the item.
    This functionality would save many queries from students who ask the Library helpdesk for an extension. We are often able to extend the hold shelf period where there are no further requests but ti would be nice to automate the requesting/task handling…

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. 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…

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. SRU/SRW: Increase the 10,000 record retrieval limit

    The usefulness of the SRU service is reduced substantially by the 10,000 record limit.

    If removing the limit is not an option, it would still help a lot if the limit could be increased to, say, 100,000.

    My use case is that I'm using the SRU service in combination with the Bibs API to do batch processing of catalog records.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base