Page Comparison

...

1. A user places an interlibrary loan request in an external system.

2. The external system uses the ReShare Shared Inventory API to identify an eligible instance.

   1. Search by bibliographic metadata, such as ISBN, title, author.

   2. Identify a matching instance record.

   3. Confirm that this instance record has at least one holding with an ILL status of “Will lend.”

   4. Return the UUID of the Instance.

3. The external system uses the ReShare OpenURL resolver to create a new request.

   1. The OpenURL must include the Instance UUID identified from the shared inventory.

   2. The OpenURL must include a patron ID of the same type that ReShare is using for verification with a particular library.

   3. The OpenURL resolver will return a confirmation of success and the UUID of the request in the library’s ReShare tenant.

4. The external system uses the ReShare mod-rs API for each individual library tenant to poll for the status of the request using the UUID returned by the OpenURL resolver.

...

$ export TENANT=mytenantshared_inventory_tenant
$ export OKAPI_URL=https://myokapishared_inventory_api_url.example.com
$ export TOKEN=mytoken

...

$ export TENANT=mytenantmod-rs_tenant
$ export OKAPI_URL=https://myokapimod-rs_api_url.example.com
$ export TOKEN=mytoken

...

Both the Shared Inventory and mod-rs run on the Okapi platform and share a common method of logging in. Note that the Shared Inventory and the mod-rs tenant of a specific library have distinct “X-Okapi-Tenant” values. The following example shows how to obtain an API token using cURL.

...