Concepts
| Term | Explanation |
|---|---|
|
Patron |
Library members or other customers in the Wise system. |
|
User |
Library employee with permissions. Users are created in the wise manager. |
|
ApplicationName |
Name of the API-client application. OCLC defines this, and it is used for API-key creation |
|
APP-ID |
Application ID: ID with which the application is known within the Wise system. |
|
APP-KEY |
Unique key with which the Wise-Key is calculated. |
|
WISE-KEY |
Unique key with limited validity for executing requests. |
|
Token |
Unique key with which a patron or user is registered. |
| PatronSystemId (PID) | A unique id of a patron |
| LibraryId |
The identification of the library organization in a Wise system. |
| BranchId | A branch of a library organization |
API technical documentation
Our Swagger documentation can be found here: https://oclc.hostedwise.nl/restapi/doc/index.html
Wise Model
In a Wise system there can be multiple library organizations. Each organization can have a multiple branches. In the image below there are 5 organizations in one Wise system. Libraries A, B and C are working together. The level of collaboration can be configured, e.g. sharing a collection, a holds network or working together financially. The most common part of a collaboration network is allowing patrons of library A to borrow books in library B and C (and vice versa). Libraries D and E are in the same Wise system, but not taking part in any collaboration. A patron who wants to borrow items in library C and D, needs a subscription in library C (or A or B) and a subscription in D.
