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.

How can we improve Alma?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

    54 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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

    48 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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…

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 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…

    32 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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).

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. make the bunch of XSD publicly available

    We use JAXB to generate classes from the XSDs of the API.
    The only way we know to obtain these XSDs is to click through the developer network and to collect the single files from

    https://developers.exlibrisgroup.com/resources/xsd/

    There is no chance to stay up to date except permanently pulling the resources again and to diff them with what you have already.

    In fact this is what we do but smells like somthing from stone age and has the handicap that we never find out if there is NEW XSDs (as we have to know the name of something for pulling).

    It…

    10 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Create item via API addition of parameter to generate description field

    Creating item via API using -POST /almaws/v1/bibs/{mms_id}/holdings/{holding_id}/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".

    32 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Use sane file permissions on gzipped files from publishing jobs

    When extracting the MarcXML-files from a publishing job, the extracted files by default have unix file permissions set to 060 (u=,g=rw,o=), i.e. only readable and writable by the group, not by the user. This is weird and makes little sense.

    Even worse, it also means that on systems with default umask of 022, which is *very* common, the *effective* permissions will be 040 (u=,g=r,o=) which means that the files can be neither changed nor deleted – even by the user who extracted them – without messing with permissions.

    I can see no reason whatsoever for preferring the current default set…

    2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Display call number and/or barcode in list of fines in Primo

    We like to display the alternative call number in the patron's list of fines in Primo for fees that are attached to an item. As well there should be the permanent call number or at least the item barcode in cases there is no alternative call number. Often, the items title is not sufficient to find the correct item in ALMA, and the staff at the circulation desks have problems to clarify witch items are concerned. In Alma the item barcode is already displayed in the list of fees/fines and this should be reflected in Primo as well.

    This functionality…

    27 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. 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…

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. 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 "overdue_at_change_due_date" 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 overdue_at_change_due_date, 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
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. integration

    We would like the ability to import new funds (from Workday) into ALMA. In other words, we can currently import new patrons into ALMA from Workday. We would like that ability to extend to our Funds data.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. 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.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. 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 …

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Add option to specify electronic collection in Create PO-Line API

    When an electronic portfolio is created by GOBI through the Create PO-Line API, it is automatically set to standalone. The Create PO-Line API has no option to specify that it should be part of a specific electronic collection.

    In our use case we thought we could fix this by using the update inventory import profile when importing a more complete MARC record, but if this profile is configured with a collection a new portfolio will be created if the existing is standalone. (See case #00500768.)

    Allowing an electronic collection to be specified when creating portfolios through Create PO-Line API would…

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. bursar integration - option to export fine/fee credits even if minimum value > 0

    Currently in order for fine/fee credits to be exported in the bursar integration, the minimum value must be set to zero, which means Alma will export fines of any amount even if they are very small.
    We would like to be able to set a minimum value for the fine export, but still export credits. Ideally we'd like a checkbox to tell Alma to apply the minimum value amount to credits as well as to debits. For example if we set the minimum value to $5 and check a box to include credits, Alma would export any fines over $5,…

    13 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base