Concepts
The following table lists terms used throughout the Wise Rest-API documentation:
| 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
For more information on the API technical documentation, see our Swagger documentation.
Wise Model
There can be multiple library organizations in a Wise system, and each organization can have multiple branches. In the image below, there are 5 library organizations in one Wise system. Libraries A, B, and C are working together. The level of collaboration between these libraries 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 from Library B and Library C (and vice versa).
Libraries D and E are in the same Wise system, but do not take part in any collaboration. A patron who wants to borrow items from Library C and Library D still needs a membership with Library C (or A or B) and a membership with Library D.
