61 results found

1. provide means to access our Alma and Primo data via our own analytics tools

   we need to analyse and combine our data with data from other systems that are in use at the university. extracting data from Alma in a meaningful way is way too cumbersome to be useful. all methods that I am aware of are based on an Analytics report, and have restrictions on numbers of rows that can be exported at one time. E.g. we would need to compare data from our reading list system (which we can access using an ODBC connector despite the system being SaaS) with print and electronic holdings in Alma and their usage. I do not particularly want to go down the route of duplicating our Alma holdings in a local repository. When I contacted ExLibris support about possible solutions I was asked to add this to the ideas exchange.

   we need to analyse and combine our data with data from other systems that are in use at the university. extracting data from Alma in a meaningful way is way too cumbersome to be useful. all methods that I am aware of are based on an Analytics report, and have restrictions on numbers of rows that can be exported at one time. E.g. we would need to compare data from our reading list system (which we can access using an ODBC connector despite the system being SaaS) with print and electronic holdings in Alma and their usage. I do not… 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  ·  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. API allow quantity for pricing in POL creation

   We use the adquisitions API to duplicate POLs. When we are creating a new POLs based on a existing ones.
   
   We get the original POLs json and we make some changes on it to send it again in order to create a new one.
   If the POL has more than one items to be ordered (quanity for pricing field), the api ignore it and put always a 1.
   The problem is that the Alma make some calculations with the amount field and the fun percentage changes, so the POL amount increases and is not the correct amount.

   In order to solve the problem we ask to accept the "Quantity for pricing" information when the order is created by API.

   We use the adquisitions API to duplicate POLs. When we are creating a new POLs based on a existing ones.
   
   We get the original POLs json and we make some changes on it to send it again in order to create a new one.
   If the POL has more than one items to be ordered (quanity for pricing field), the api ignore it and put always a 1.
   The problem is that the Alma make some calculations with the amount field and the fun percentage changes, so the POL amount increases and is not the correct amount.

   In order to… 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

3. Reverse Bursar Export and Restore State of Items and Fines/Fees

   Have the ability to immediately reverse a Bursar Export and restore the state of items and fines/fees. This would be a good quick thing to have in case you have made an error.

   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

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

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

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

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

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

   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

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

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

11. Add a request cancellation code & reason in the Request webhook

    The current Request webhook doesn't seem to include the Request Cancellation reason. Currently it just says:

    'event' => {
    'desc' => 'Request canceled',
    'value' => 'REQUEST_CANCELED'
    },

    The comment field refers to the request, but not the cancellation reason here:

    'userrequest' => {
    'requesttime' => '2022-05-11T23:42:26.191Z',
    'managedbycirculationdeskcode' => 'EASTCIRC',
    'mmsid' => '993815723607636',
    'taskname' => 'Rejected',
    'author' => 'Ferguson, J.',
    'itemid' => '2365452260007636',
    'issue' => '',
    'pickuplocationlibrary' => 'ABC',
    'dateofpublication' => '',
    'managedbylibrary' => 'State Library',
    'requesttype' => 'HOLD',
    'requestid' => '1419991190007636',
    'pickuplocation' => 'Redmond Barry Reading Room',
    'materialtype' => {
    'desc' => 'Book',
    'value' => 'BOOK'
    },
    'requestsubtype' => {
    'desc' => 'Patron physical item request',
    'value' => 'PATRONPHYSICAL'
    },
    'volume' => '',
    'managedbylibrarycode' => 'ABC',
    'part' => '',
    'barcode' => '30328504468884',
    'expirydate' => '2022-05-19Z',
    'description' => undef,
    'pickuplocationtype' => 'CIRCULATIONDESK',
    'comment' => undef,
    'userprimaryid' => '12345678',
    'pickuplocationcirculationdesk' => 'DEFAULTCIRCDESK',
    'managedbycirculationdesk' => 'East Retrieval',
    'requeststatus' => 'HISTORY',
    'title' => 'Life.',
    'requestdate' => '2022-05-12Z',
    'additional_id' => '141-999-119'
    }

    The current Request webhook doesn't seem to include the Request Cancellation reason. Currently it just says:

    'event' => {
    'desc' => 'Request canceled',
    'value' => 'REQUEST_CANCELED'
    },

    The comment field refers to the request, but not the cancellation reason here:

    'userrequest' => {
    'requesttime' => '2022-05-11T23:42:26.191Z',
    'managedbycirculationdeskcode' => 'EASTCIRC',
    'mmsid' => '993815723607636',
    'taskname' => 'Rejected',
    'author' => 'Ferguson, J.',
    'itemid' => '2365452260007636',
    'issue' => '',
    'pickuplocationlibrary' => 'ABC',
    'dateofpublication' => '',
    'managedbylibrary' => 'State Library',
    'requesttype' => 'HOLD',
    'requestid' => '1419991190007636',
    'pickup… 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

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

    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

13. Add filter for status to Get-Uers API

    Please add a filter for status to the Get-Users API so we can retrieve users who are either active or inactive. Currently, our integration gets all users using the API and it takes about 30 mins but more than half of the users are inactive.

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

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

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

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

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

18. 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…)
    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. Add API support for licenses with type Negotiation

    We are trying to update the license terms on our licenses in the Network Zone. However, when trying to update a license with type Negotiation, the API returns an error:

    "errorCode": "69002",
    "errorMessage": "Updating negotiations by API is currently not supported",
    "trackingId": "E01-0703094132-MPLRX-AWAE786493119"

    Please add support for updating Negotiation licenses through the API.

    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

20. Retrieve associated collections by MMS ID

    In the Alma API there should be an end point to input an mms id number and return all collection ids associated with that ID number.

    This functionality already exists for e-collections (GET /almaws/v1/bibs/{mms_id}/e-collections) but no such functionality exists for regular collections.

    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