As already mentioned, I assume that having a new goal might be more effective than patching RTAC.
One approach could be to expose all relevant Information in the response. In other words, RTAC-2 should just provide all (non classified) attributes of 'holding', 'item', and 'location'. This will allow a library to use all attributes of this objects to pass hints to a discovery system. (e.g. the note fields). The current RTAC provides only a selection of all possible information, which leads into the well documented limitations.
Request
| Task | Method | Path | PostParms |
|---|---|---|---|
| Inquirer information about one instance defined by UUID | GET | /rtac-2/uuid/{instance_uuid} | |
| Inquirer information about one instance defined by HRID | GET | /rtac-2/hrid/{instance_uuid} | |
Inquirer information about multiple instances defined by UUID | POST | /rtac-2/uuid | List of UUIDs |
Inquirer information about multiple instances defined by HRID | POST | /rtac-2/hrid | List of HRIDs |
Notes:
- HRID as query parameter is indispensable for most German libraries
- Providing a batch mode (POST endpoints) seems to be outdated, since clients are capable to do asynchronous concurrent requests.