Open nichtich opened 5 years ago
Suggestion: extend PAIA with an additional part PAIA info in addition to PAIA core and PAIA auth.
Return an JSON object with information about the PAIA server. Minimum information should be base URL of PAIA core and PAIA auth, if available, for instance:
{
"core": "https://example.org/core/",
"auth": "https://example.org/auth/"
}
Return a JSON array with storages supported by the PAIA server or HTTP 501 if this list is not supported. Storages are found in document field storageid
Return a JSON object describing a storage if this storage is known to the PAIA server or HTTP 501 if storage lookup is not supported or HTTP 404 if the storage is not known. Example:
https://example.org/info/storage/http://uri.gbv.de/organization/isil/DE-999@xxx
{
"id": "http://uri.gbv.de/organization/isil/DE-999@xxx",
"description": "Magazin",
"href": "...optional URL..."
}
Return a JSON array with fee types supported by the PAIA server or HTTP 501 if this list is not supported. Fees are found in fee field feeid
.
https://example.org/info/fee/de-999:fee-type:123
{
"id": "de-999:fee-type:123",
"description": "Mahngebühr",
"amount": "1.00 EUR"
}
Return a JSON array with user types supported by the PAIA server or HTTP 501 if this list is not supported. User types are found in patron field type
https://example.org/info/user-type/de-999:user-type:42
{
"id": "de-999:user-type:42",
"description": "Studierende"
}
See also #70 for conditions (this includes delivery places aka desks).
patron types can be arbitrary URIs defined anywhere but the ILS backend will likely know best about user types, so it should also make information about it available. Example:
https://example.org/paia/info/patrontype/42
=>
Similar information could be made available for storageid and feeid