Tar archives can already be piped into the dync client already. The downstream applications at QBiC's servers cannot handle tar archives properly, so I suggest a special handling for incoming tar archives, which makes dync more specialised, but this fits more into the current data upload and pre-processing process at QBiC.
Until we find a more elegant solution, this should do the job.
Tar archives shall be recognised by the tarfile module and all files extracted. In this case, no additional checksum will be written, as for directories, this is already implemented by the dropboxhandler. dync shall just move it into the correct target dropbox, as set in the configuration file of dync.
This dropbox will be an incoming dropbox from the dropboxhandler, which will process the directory properly and prepare it for the openBIS dropbox properly.
sven1103
commented
7 years ago 
Tar archives can already be piped into the dync client already. The downstream applications at QBiC's servers cannot handle tar archives properly, so I suggest a special handling for incoming tar archives, which makes dync more specialised, but this fits more into the current data upload and pre-processing process at QBiC.
Until we find a more elegant solution, this should do the job.
Tar archives shall be recognised by the
tarfilemodule and all files extracted. In this case, no additional checksum will be written, as for directories, this is already implemented by the dropboxhandler. dync shall just move it into the correct target dropbox, as set in the configuration file of dync.This dropbox will be an incoming dropbox from the dropboxhandler, which will process the directory properly and prepare it for the openBIS dropbox properly.