94 results found

1. API for Bibliographic record versions

   Currently, only the latest version of a Bib record is available from the Bibs API. There should be some way to retrieve older versions of the record.

   19 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Support automatic weeding of holdings in the Swedish national catalogue

   The Swedish national Ex Libris user group (ElugSWE) would like Alma to integrate with the Swedish national catalogue (Libris), so that when a bibliographic record is deleted in Alma, the corresponding holding record is deleted in Libris.

   (We have discussed this idea with the local Ex Libris representative and also a customer success manager, and were recommended to submit it to Idea Exchange.)

   This integration exists for multiple other library systems, and it would be really welcomed if Alma could match them on this.

   The integration would need to make use of Libris API:s, documented here:

   https://github.com/libris/librisxl/blob/master/rest/API.md

   The sections most interesting for the "weeding" use case are:

   Delete – https://github.com/libris/librisxl/blob/master/rest/API.md#deleting-a-record---requires-authentication
   Findhold – https://github.com/libris/librisxl/blob/master/rest/API.md#_findhold---find-holding-records-for-a-bibliographic-record
   Authentication – https://github.com/libris/librisxl/blob/master/rest/API.md#authentication

   The Swedish national Ex Libris user group (ElugSWE) would like Alma to integrate with the Swedish national catalogue (Libris), so that when a bibliographic record is deleted in Alma, the corresponding holding record is deleted in Libris.

   (We have discussed this idea with the local Ex Libris representative and also a customer success manager, and were recommended to submit it to Idea Exchange.)

   This integration exists for multiple other library systems, and it would be really welcomed if Alma could match them on this.

   The integration would need to make use of Libris API:s, documented here:

   https://github.com/libris/librisxl/blob/master/rest/API.md

   The sections most… more

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Accession number available by API

   Hello,
   To be able to develop several external tools (relabelling, cataloging, ...) we need to access the "Accession number" table by API (read and write).
   This would probably give many other clients oportunities in developing external tools for managing physical collections.
   Best regards.

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. 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 individual user record(s) that contains the invalid character(s).

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

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. 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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. 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 Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. API conf/sets - Always add member/@link

   Currently not all calls to conf/sets will return member-elements with links. This will make a call to e. g. electronic portfolios close to useless, as there is no API-call that can be done with the portfolio's ID only.

   Ceterum censeo I don't think that this is an enhancement, but Case 00874282 was not interpreted as this being a bug.

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Display “Created by” field for all Notes tab notes

   When we use the APIs to update a record, the “Updated On”, and “Updated By” fields on the Notes tab are overwritten with today’s date and “API, Ex Libris”. (This behaviour occurs regardless of the record type.) While we love the ability to use the API to update fields in our Alma records, we feel it’s misleading for these fields to show as having been updated when no update actually occurred.

   Per Ex Libris, this is the expected behavior: when we have a list of something, the PUT API replaces them all by deleting them and then recreating them according to the info in the PUT payload. If you remove the notes from the body, then the API will remove any existing data and since there is nothing to replace it with in the body then it remains empty (i.e., the notes will be deleted entirely).

   Since we cannot stop the notes from being deleted & replaced nor the “Updated On” and “Updated By” fields from being changed, it would be very helpful if the “Created By” field would display in the Alma User Interface. Even if we cannot see which operator originally updated the note, it’s very useful for us to be able to see who originally created the note. In a large, decentralized system, where many staff might be touching or updating records, seeing who created the note can provide additional context as to why the note was added.

   Please consider displaying the “Created by” field for all notes in all record types.

   When we use the APIs to update a record, the “Updated On”, and “Updated By” fields on the Notes tab are overwritten with today’s date and “API, Ex Libris”. (This behaviour occurs regardless of the record type.) While we love the ability to use the API to update fields in our Alma records, we feel it’s misleading for these fields to show as having been updated when no update actually occurred.

   Per Ex Libris, this is the expected behavior: when we have a list of something, the PUT API replaces them all by deleting them and then recreating them according… more

   •  

   14 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. 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, as well as any credits over $5.

   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,… more

   13 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. API for terms of use

    An API to retrieve the terms of use would allow us to display borrowing rules on our website which are completely synced to our Alma configuration.

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. 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 login in Alma for external user.

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

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Browzine : Journals with multiple sources

    Libraries who are using Browzine are exporting our journals holdings file using a Google Scholar XML schema. For titles that have multiple sources, Browzine will based on their own algorithm to determine one source to be made available to the users in the Browzine interface. According to Third Iron, this "choosing algorithm" is designed to pick the source that has the widest coverage. This is fine in most of the cases but if we want to override this "decision", we will need to write in to Third Iron.

    Suggestion: To consider having a designated field in the portfolio record for libraries to indicate as “preferred source in Browzine”? This would allow libraries to easily flag out titles that we want to be visible in Browzine.

    Thank you.

    Libraries who are using Browzine are exporting our journals holdings file using a Google Scholar XML schema. For titles that have multiple sources, Browzine will based on their own algorithm to determine one source to be made available to the users in the Browzine interface. According to Third Iron, this "choosing algorithm" is designed to pick the source that has the widest coverage. This is fine in most of the cases but if we want to override this "decision", we will need to write in to Third Iron.

    Suggestion: To consider having a designated field in the portfolio record for… more

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Allow Z39.50 and other search results to include the barcode

    Alma's APIs need to provide greater flexibility in fields searched. Too often the MMSID must be used but this is not a particularly useful ID as it is internal. It's also not particularly helpful as it does not integrate with other systems like Remote Storage management systems, Bindery, NCIP, and the like. Yet Primo displays the barcode so clearly it's not difficult to pull out of a record.

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Allow more information to be included in the Webhook Failure letter

    As things stand, the Webhook Failure letter cannot be customised to include a reason for the failure, forcing recipients to trawl through the opaque and confusing logs to work it out. Allowing administrators to add more information to this letter (such as information from the webhook response body) would simplify the process of dealing with webhook issues.

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Alma “scan-in” API: Marc21 field 852 - call number prefix and suffix

    We are using the Alma “scan-in” API
    /almaws/v1/items?itembarcode={itembarcode}
    which redirects to
    /almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items/{item_pid}
    to print book labels.

    Some sublibraries also use call number prefixes or suffixes in some cases.
    
    Please see the following example record:
    - Marc21 field 852 in the Holding record
    - XML output

    (1) Example: Call number with prefix 852 $$k
    852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix

    XML output:
    item/holdingdata/permanentcallnumber: Präfix G-1234567
    item/holdingdata/callnumber: Präfix G-1234567
    item/holdingdata/accession_number: G-1234567

    item/itemdata/parsedcallnumber:
    <parsedcallnumber>
    <callno/>
    <call_no>Präfix</call_no>
    <call_no>G-1234567</call_no>
    </parsed_call_number>

    (2) Example: Call number with suffix 852 $$m
    852 8_ |b XHOG |c XGRY |h G-1234567 |m Suffix

    XML output:
    item/holdingdata/permanentcallnumber: G-1234567 Suffix
    item/holdingdata/callnumber: G-1234567 Suffix
    item/holdingdata/accession_number: G-1234567

    item/itemdata/parsedcallnumber:
    <parsedcallnumber>
    <callno>G-1234567</call_no>
    <call_no/>
    <call_no>Suffix</call_no>
    </parsed_call_number>

    (3) Example: Call number with prefix 852 $$k and suffix 852 $$m
    852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix |m Suffix

    XML output:
    item/holdingdata/permanentcallnumber: Präfix G-1234567 Suffix
    item/holdingdata/callnumber: Präfix G-1234567 Suffix
    item/holdingdata/accession_number: G-1234567

    item/itemdata/parsedcallnumber:
    <parsedcallnumber>
    <callno/>
    <call_no>Präfix</call_no>
    <call_no>G-1234567</call_no>
    <call_no/>
    <call_no>Suffix</call_no>
    </parsed_call_number>

    and after some tests the <parsed_call_number> section looks like this:

    <parsed_call_number>
    <call_no/>
    <call_no>Präfix</call_no>
    <call_no>G-1234567</call_no>
    <call_no/>
    <call_no>Suffix</call_no>
    </parsed_call_number>

    Conclusion:
    - Marc21 subfields 852 $$k and $$m are not listed sperately in the XML :-(
    - In <parsed_call_number> section the content of <permanent_call_number> or <call_number> is splitted up into the content of 852 $$k, $$h and $$m. The order of the <call_no> tags is correct (call number prefix / call number / call number suffix) but there are also empty <call_no/> tags.

    Please provide us a XML output with Marc21 852 content in seperate fields. The important call number fields for us are:
    - 852 $$k ... call number prefix
    - 852 $$h ... call number (classification part)
    - 852 $$m ... call number suffix
    - <accession_number> includes 852 $$h only if the call number has been generated via a call number (accession number) counter.

    Other libraries may be interested also in other subfields of Marc21 852:
    https://www.loc.gov/marc/holdings/concise/hd852.html
    $h - Classification part (NR)
    $i - Item part (R)
    $j - Shelving control number (NR)
    $k - Call number prefix (R)
    $l - Shelving form of title (NR)
    $m - Call number suffix (R)

    Having the content of 852 $$k, $$h and $$m in separate XML fields gives us the possiblity to handle the call number parts in a different way on the book label (if desired).
    Having two <call_no> tags in the <parsed_call_number> section is not clear enough. It could mean that you have:
    - 852 $$k ... call number prefix / 852 $$h ... call number (classification part)
    - or 852 $$h ... call number (classification part) / 852 $$m ... call number suffix

    Thank you in advance!

    We are using the Alma “scan-in” API
    /almaws/v1/items?itembarcode={itembarcode}
    which redirects to
    /almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items/{item_pid}
    to print book labels.

    Some sublibraries also use call number prefixes or suffixes in some cases.
    
    Please see the following example record:
    - Marc21 field 852 in the Holding record
    - XML output

    (1) Example: Call number with prefix 852 $$k
    852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix

    XML output:
    item/holdingdata/permanentcallnumber: Präfix G-1234567
    item/holdingdata/callnumber: Präfix G-1234567
    item/holdingdata/accession_number: G-1234567

    item/itemdata/parsedcallnumber:
    <parsedcallnumber>
    <callno/>
    <call_no>Präfix</call_no>
    <call_no>G-1234567</call_no>
    </parsed_call_number>

    (2) Example: Call number with… more

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Allow API clients to include/exclude fields in the response data

    It would be great if API clients could include/exclude fields of the response data of API calls.

    The rational behind this stems from a use case of our own:

    When making calls to the Alma and also Primo APIs we get a huge chunk of data back from which we only need a small portion. If we were able to make an API request in which we could specify upfront which fields we would and/or wouldn't need would: (1) prevent all that overhead data, (1) reduce the network traffic and (3) increase the response speed.

    The functionality that is necessary to filter the response could be implemented once on the API endpoint server. After that every possible client (also those developed by ExLibris) could then customize the response format of the APIs according to its needs.

    It would be great if API clients could include/exclude fields of the response data of API calls.

    The rational behind this stems from a use case of our own:

    When making calls to the Alma and also Primo APIs we get a huge chunk of data back from which we only need a small portion. If we were able to make an API request in which we could specify upfront which fields we would and/or wouldn't need would: (1) prevent all that overhead data, (1) reduce the network traffic and (3) increase the response speed.

    The functionality that is necessary… more

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. 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 can't be too difficult to bundle the XSDs every week (for example) and place them somewhere for download.

    It can

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

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Improve z39.50 tab in ILLiad to search individual volumes of serials/monographs

    Improve z39.50 tab in ILLiad to search individual volumes of serials/monographs. Currently searching z39.50 will turn up one random volume from multi-volume set

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. 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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. 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 Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close