68 results found

1. 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 accruals, with multiple ledgers activated in the system. To mitigate ongoing issues, we find it necessary to deactivate the ledgers for future fiscal years and activate them only when the payment in question necessitates the accrual mode.

   For EBSCOnet we are unable to deactivate the ledgers for future fiscal years due to the need to use those ledgers for other continuous orders. Manual updating of the fiscal period is required in the EBSCOnet POLs to ensure expenditure is recorded correctly in Alma

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

   3 votes

   Vote 0 votes 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

2. 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 0 votes 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. 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 0 votes 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. Statistics for Cloud Apps

   We would like to be able to see some statistics within our IZ regarding Cloud Apps:

   • Which user has activated which Cloud App
   • How often is a Cloud App used
   • When did a user use a specific Cloud App
   23 votes

   Vote 0 votes 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

5. 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 slip of a mouse click on this Alma page.

   Library staff and Ex Libris support staff both have fallen into the trap of regenerating the private key on sandbox without knowing that doing so breaks production.

   The idea is to:
   1. Show a warning dialog after clicking the regenerate private key that emphasises that continuing will: a) stop any previously generated private key from working; and b) affects both Alma Production and Alma Sandbox.
   2. Show a second «Regenerate private key» button, along with a «Cancel» button.

   It is important that regenerating the private key becomes a deliberate two-step process to avoid accidently regenerating the 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… more

   •  

   31 votes

   Vote 0 votes 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

6. 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 not directly applicable / compatible with what's needed for the "user_role" data in the "user" APIs.

   Having accurate and complete user profile data available via API would make it much easier and safer to manage our staff permissions programmatically.

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

   9 votes

   Vote 0 votes 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

7. 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 0 votes 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. 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 OCLC because the current OCLC Data Sync profiles as they exist within Alma do not handle electronic materials (see https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/110Publishing_to_OCLC#Publishing_Electronic_Holdings_to_OCLC ). OCLC asks for a specific file naming convention, and that name cannot be altered. The profile adds "_new" to the end of the file name, which prevents their system from processing the file entirely. As a result, we have to either manually download these incredibly large files, change the file name, the put them on OCLC's server, or write a script to do this for us with no coders on staff.

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

   5 votes

   Vote 0 votes 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

9. Prevent GOBI API from matching activated CZ records in IZ

   Problem - The matching method used in the API will ink to the CZ bib records if it is in the IZ. The match methods are not flexible in the API integration profile when compared to something like import profiles that allow ignoring the record from the Community Zone and creating a local record.

   We would like the API to always create a local bib even if a matching CZ record exists in the IZ. Or, at least make this an optional setting.

   11 votes

   Vote 0 votes 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. 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 0 votes 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

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

    9 votes

    Vote 0 votes 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

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

    61 votes

    Vote 0 votes 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

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

    8 votes

    Vote 0 votes 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

14. 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 0 votes 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

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

    52 votes

    Vote 0 votes 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. 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 0 votes 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. 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

    53 votes

    Vote 0 votes 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

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

    43 votes

    Vote 0 votes 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

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

    88 votes

    Vote 0 votes 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…)
    5 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. 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

    27 votes

    Vote 0 votes 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