Upcoming use case:
Currently, we expect data to be already extracted from an archive when put into the openBIS dropboxes. (Only exception are the findings from the MTB).
However, for single cell sequencing we have dozens of fastq files coming from the sequencer due to many lanes that have been used. But they belong to one extract sample (one sample code)!
Merging them before an upload is discouraged, as this is part of the analysis pipelines already.
It shall be part of the ETL process, to extract data from an archive and continue with the registration process.
Upcoming use case:
Currently, we expect data to be already extracted from an archive when put into the openBIS dropboxes. (Only exception are the findings from the MTB).
However, for single cell sequencing we have dozens of fastq files coming from the sequencer due to many lanes that have been used. But they belong to one extract sample (one sample code)!
Merging them before an upload is discouraged, as this is part of the analysis pipelines already.
It shall be part of the ETL process, to extract data from an archive and continue with the registration process.