Story #8851
CN sends error doc with "pid" to v2 endpoint
Start date:
2019-11-06
Due date:
% Done:
0%
Story Points:
Sprint:
Description
Error XML type with "pid" is correct re. 2.0 arch docs but not 2.0 schemas. Let's discuss in maint. call.
- 2.0 arch doc says 'pid': https://releases.dataone.org/online/api-documentation-v2.0/apis/Exceptions.html#Exceptions.SynchronizationFailed
- 1.1 schema says 'pid': https://releases.dataone.org/online/d1-schemas-1.1.1/dataoneErrors.xsd
- 2.0 schema says 'identifier': https://releases.dataone.org/online/d1-schemas-2.0.1/dataoneErrors.xsd
- Presumably because it can be a PID or a SID
- GMN expects "pid" in /v1 and "identifier" in /v2
Example error sent to GMN v2 MNRead.synchronizationFailed() by the CN:
<?xml version="1.0" encoding="UTF-8"?>
Synchronization task of [PID::] https://pasta.lternet.edu/package/data/eml/edi/443/1/0271719552fcd1ce830fcb2ee8efae71 [::PID] failed. Cause: InvalidSystemMetadata: The checksum for pid: https://pasta.lternet.edu/package/data/eml/edi/443/1/0271719552fcd1ce830fcb2ee8efae71 does not match the actual checksum supplied by the member node: urn:node:EDI. Actual checksum: null. System metadata checksum: eaaac8b49e6e8c13d30005a69e3600e7e17c9b3a