Currently a PID resolves to the record URL page (the /records/ID, not /api/records/ID). The endpoint only supports html output, which is not optimal for machines to read. We must find a way to support machine readable formats.
The simplest solution is to add support for json outputs when the Accept header demands it.
Currently a PID resolves to the record URL page (the /records/ID, not /api/records/ID). The endpoint only supports html output, which is not optimal for machines to read. We must find a way to support machine readable formats.
The simplest solution is to add support for json outputs when the Accept header demands it.