Perform a code review of all dataone methods in order to:
improve fault tolerance for
failed or timed out DataONE service calls
incorrect arguments to method calls
unexpected arguments to method calls
unavailable services or DataONE objects
corrupted objects
improve ease of use
improve consistency between different calls
improve ability to use data obtained from DataONE
i.e. ability to download an object directly to disk in the correct format, file extension
In order to fully test any built in fault tolerant capabilities, it may be necessary to stand up a mock server or test D1 MN that produces errors or corrupted data as responses to certain D1 service calls.
Some potential errors might include well known but sporadically occurring errors such as:
sysmeta checksum doesn't agree with calculated data object checksum
"Hazelcast not initialized" error
authorization errors
certificate expired
member node not available
CN or MN timeout
"Request Entity Too Large" error - what http code is returned for this?
Thie review will also include the datapack package.
Perform a code review of all
dataonemethods in order to:In order to fully test any built in fault tolerant capabilities, it may be necessary to stand up a mock server or test D1 MN that produces errors or corrupted data as responses to certain D1 service calls. Some potential errors might include well known but sporadically occurring errors such as:
Thie review will also include the
datapackpackage.