After user downloads a set of files belonging to a dataset, see #22, it will be interesting to provide a functionality to check the sizes and adler32 checksums of downloaded files.
This information is available over REST API, here is one example.
The command would go through the given directory, calculate size and adler32-checksum of present files, and compare this with the information obtained from the server via the REST API.
The command would report back to user:
exit code 1 if any of the locally available files is having different size or different checksum
exit code 2 if some of the locally available files is not present on the remote opendata.cern.ch instance
exit code 3 if some of the opendata.cern.ch files are not present locally
exit code 0 if everything corresponds perfectly well
The command will exit with different error codes so that users could plug this command to their harvesting workflows.
After user downloads a set of files belonging to a dataset, see #22, it will be interesting to provide a functionality to check the sizes and adler32 checksums of downloaded files.
This information is available over REST API, here is one example.
The user would launch:
The command would go through the given directory, calculate size and adler32-checksum of present files, and compare this with the information obtained from the server via the REST API.
The command would report back to user:
The command will exit with different error codes so that users could plug this command to their harvesting workflows.