Researching errors reported in the CRS

API errors from the CRS are being logged in the Data Service Center in a table stored in AWS.

To research errors, you need login access to https://aws.oit.duke.edu

Currently this is LSIS staff only, access is managed by Jeff.

From Services, choose DynamoDb

On the left hand side, click “Explore items”

From the table list, choose “alma-integrations-logging”

Paging through the results is time-consuming and not efficient since it defaults to the oldest results, not the newest.

To search results, under Scan or Query items, choose Query

Set the app (Partition key) to CRS

Then you can use the timestamp to search by time, or under filters, search by individual attributes

Here’s an example screenshot if you were searching the data field (which should be the actual error from the Ex Libris API):

Problem: Patron has already requested item
Solution / Workaround: Patron may have clicked multiple times, especially if the page is responding slowly. No action is needed; they have a request in. You can verify this in Alma.

Problem: The patron’s record could not be looked up.
Solution / Workaround: The cause can be varied, but is often found when an account is not being loaded from identity management - like an alum, or a visiting scholar. Things to check include - does the account have the unique ID? if the patron has ever had a netid, does the account have the netid? is the patron using onelink?

Problem: According to Alma, the item either can’t be located to be requested, or the particular patron who is requesting the item is not able to request it.
Solution / Workaround:

Problem: Patron has a loan for the title, and they can’t request another copy while they have the copy out.
Solution / Workaround: Patron