70 results found

1. role scopes in api

   We are trying to build a simple application where our staff can request Alma roles be added to an account.

   We can retrieve a list of all roles from the Alma API for users to choose from; however, this list does not clarify what scopes are available for which roles.

   Can this info be provided via the API?

   3 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

   Submit Rating

2. API versioning (especially user API)

   API updates should be rolled out with an opt-in and out option. So that developers can test and adopt new versions and roll back if problems occur. Currently we just get a new version and if this new version breaks any of our custom integrations. We have no way to compare to old behaviour or opt out of the update until we can fix this.
   Example of this is the November API changes. The change broke how some of our APIs customizations worked. Our ICT developer team had to make changes to resolve the problems that the November API change made. Then 2 months later Ex libris changed the API to resolve the bug that November had made. This update broke the workarounds that our developers have created. So our ICT developers have then had to work on a second resolution within a very short space of time. This is specifically problematic for our ICT developers as the issue is system critical and therefore needs to be done quickly. Whereas versioning API changes would resolve this.

   API updates should be rolled out with an opt-in and out option. So that developers can test and adopt new versions and roll back if problems occur. Currently we just get a new version and if this new version breaks any of our custom integrations. We have no way to compare to old behaviour or opt out of the update until we can fix this.
   Example of this is the November API changes. The change broke how some of our APIs customizations worked. Our ICT developer team had to make changes to resolve the problems that the November API change… more

   1 vote

   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  ·  Edit…  ·  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

   Submit Rating

3. 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

   20 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

   Submit Rating

4. Air bar box

   I am a General Manager of Store Operations and responsible for day to day store operations, including scheduling, training, and supervising employees and assistant manager. Before that, [url=https://cgdistro.com/product/air-bar-box-disposable/]Air bar box[/url] I worked as a casual Customer Service Representative, In - store consultant, and ROC Coordinator.Clear eyes, Eagle torch lighters, Duracell batteries, haze xl disposable vape, recharging puff bar, top shine disposable, supreme hyppe max flow and wax pen batteries are among the items for sale. Managing shop profitability as well as all controllable expenses such as labor, inventory levels,

   1 vote

   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

   Submit Rating

5. Enable additional types of requests via API

   The API documentation for the Create User Requests endpoint notes that "is currently NOT possible to create GENERALDIGITIZATION, MOVE or WORKORDER request." Enabling this functionality would facilitate batch processing of items for various workflows.

   2 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

   Submit Rating

6. Ability to change an institutions public key for S/FTP setup

   Our institution is requiring us to change the public key we use in Alma every 90 days in the S/FTP integration connections we have set up, to adhere with our Universities tightening of cyber security measures. We would like the ability to change our institutions public key 4 times a year. Currently institutions are only assigned a static key that can not be changed.

   3 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  ·  Edit…  ·  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

   Submit Rating

7. User API order response of identifiers

   When a response is received from the users API the identifiers aren't ordered.

   For example our library gates system requests a GET on the user API to retrieve an identifier, in our case <id_type desc="Additional ID 1">OTHERID1</id_type>. it can only read the first hit for this identifier

   I would like the response to order the values by status, with Active coming first.

   This would allow us to read the active value and ignore any subsequent Inactive values

   This is an example what is currently returned
   <user_identifiers>
   <user_identifier segment_type="Internal">
   <id_type desc="Additional ID 1">OTHERID1</id_type>
   <value>1234567890</value>
   <status>INACTIVE</status>
   </user_identifier>
   <user_identifier segment_type="External">
   <id_type desc="Barcode">BARCODE</id_type>
   <value>removed</value>
   <status>ACTIVE</status>
   </user_identifier>
   <user_identifier segment_type="External">
   <id_type desc="University ID">UNIVID</idtype>
   <value>removed</value>
   <status>ACTIVE</status>
   </user_identifier>
   <user_identifier segment_type="External">
   <id_type desc="Additional ID 1">OTHERID1</id_type>
   <value>0987654321</value>
   <status>ACTIVE</status>
   </user_identifier>
   </user_identifiers>

   This is how I would prefer it to be returned
   <user_identifiers>
   <user_identifier segment_type="Internal">
   <id_type desc="Additional ID 1">OTHERID1</id_type>
   <value>0987654321</value>
   <status>ACTIVE</status>
   </user_identifier>
   <user_identifier segment_type="External">
   <id_type desc="Barcode">BARCODE</id_type>
   <value>removed</value>
   <status>ACTIVE</status>
   </user_identifier>
   <user_identifier segment_type="External">
   <id_type desc="University ID">UNIVID</idtype>
   <value>removed</value>
   <status>ACTIVE</status>
   </user_identifier>
   <user_identifier segment_type="External">
   <id_type desc="Additional ID 1">OTHERID1</id_type>
   <value>1234567890</value>
   <status>INACTIVE</status>
   </user_identifier>
   </user_identifiers>

   When a response is received from the users API the identifiers aren't ordered.

   For example our library gates system requests a GET on the user API to retrieve an identifier, in our case <id_type desc="Additional ID 1">OTHERID1</id_type>. it can only read the first hit for this identifier

   I would like the response to order the values by status, with Active coming first.

   This would allow us to read the active value and ignore any subsequent Inactive values

   This is an example what is currently returned
   <user_identifiers>
   <user_identifier segment_type="Internal">
   <id_type desc="Additional ID 1">OTHERID1</id_type>
   <value>1234567890</value>
   <status>INACTIVE</status>
   </user_identifier>
   <user_identifier… more

   3 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  ·  Edit…  ·  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

   Submit Rating

8. API to get and upload Overdue and Lost Loan Profiles

   It would be great to have an API to get a list of all Overdue and Lost Loan Profiles as well as being able to get and upload individual profiles.

   We have 300 libraries, each of which has 3 or more Overdue and Lost Loan Profiles. Being able to manipulate the profiles with an API would be of great help in keeping track of all these profiles.

   1 vote

   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  ·  Edit…  ·  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

   Submit Rating

9. The "maximum renewal date" (max_renew_date) should be part of the fields that are provided by API

   The max-renew_date is viewable in Primo, but if you use another Discovery it can't be displayed because it is not provided by API.

   55 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

   Submit Rating

10. Two-Factor Authentication (2FA) for developer portal

    Currently login to the developer portal https://developers.exlibrisgroup.com/ requires username and password. If a user account associated with an organisation is compromised this gives the malicious actor access to use/create API keys to do anything they want in Alma.

    For example a malicious actor could create an API key which allows them to access all the user information stored in Alma.

    Access to manage API keys should be locked down with 2FA, password login is not sufficient.

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

    Submit Rating

11. SIP2 Kiosks should bundle loan/return notifications to a single notification

    Currently SIP2 connected self service hardware triggers a receipt notification for every single item that is loaned or returned. Would it be possible to package these notifications in to one email after the transaction is finished based on the configuration that it has been conducted on a self service circulation desk?

    3 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  ·  Edit…  ·  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

    Submit Rating

12. Allow API update action of License in POLine record

    Currently, License field in POLine record cannot be updated via Acquisition API. There are no effective way to link up POLine record and License record without manual update one by one. The field were mentioned in the restpoline.xsd as

    "The license code. Relevant for electronic orders only, and is not supported for PUT. "

    0 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

    Submit Rating

13. API access to Item's edit history

    For rolling back changes in a batch of items, it would be extremely useful to have API access to the Item Changes that are reported in the History tab of each item record.

    7 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

    Submit Rating

14. Allow API update action of License in POLine record

    Currently, License field in POLine record cannot be updated via Acquisition API. There are no effective way to link up POLine record and License record without manual update one by one. The field were mentioned in the restpoline.xsd as

    "The license code. Relevant for electronic orders only, and is not supported for PUT. "

    1 vote

    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  ·  Edit…  ·  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

    Submit Rating

15. Import PO Approvals Job schedule more than 1 time a day

    Currently the Import PO approvals job will only run once a day. Can this be scheduled to run multiple times a day.

    We are using rialto which is supposed to be quick way of ordering but jobs are not sent to vender straight away as it has to wait for the job to run adding delays

    If this could be scheduled multiple times a day it would greatly improve the timeline

    6 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

    Submit Rating

16. 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.

    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

    Submit Rating

17. 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

    29 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

    Submit Rating

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

    34 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

    Submit Rating

19. 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 of the premium sandbox for customers who were already using it with the old policy, when we could request refreshes when we wanted. We would like Ex Libris to make it possible to export all configurations in bulk, and then reimport these configurations after the refresh. Ideally these would be exportable in bulk, and then you could pick and choose which configurations to reimport.

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

    32 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…)
    3 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

    Submit Rating

20. Merge Patron Accounts API

    Add an API endpoint that provides a programatic interface to the merging patron accounts functionality.

    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/030User_Management/Merging_Patron_Records

    37 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…)
    4 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

    Submit Rating