This is a django web-app that provides an internal-api that interfaces with the ILLiad hosted API.
This internal-api allows multiple applications that programmatically interface with ILLiad (the article part of easyAccess, and easyBorrow, for example) -- to continue to work as-is if/when the programmatic interface to ILLiad changes.
And it has.
In April 2019, we changed our programmatic-access to ILLiad from a module that simulated web-requests on behalf of a user -- to, instead, use ILLiad's official api. We made this change as part of a migration from an end-of-life self-hosted version of ILLiad -- to a newer version of ILLiad only available via OCLC hosting.
Useful references...
-
table documentation -- used to apply field-length limits when calling the official-illiad-api
-
check user: better example coming; for now see these tests
-
create user: see sample script
-
request item: see sample script