Importing existing samples to another project
Importing existing samples to another project¶
When a sample that finished analysis is required to be processed by another pipeline configuration, this can be accomplished in another project. Uploading the fastq files again and processing them in another project with a different configuration can be tedious. The sample that finished analysis can be imported into another project instead. This process uses the deliverables of the finished sample as a source for the new one. User who does this must have the adequate permissions to manipulate the samples on both the source and destination projects and the samples must not be archived.
Import existing samples¶
--sample-ids can have multiple comma separated values:
$ gencove projects import-existing-samples destination-project-id --sample-ids source-sample-id-1,source-sample-id-2
Import all samples from another project¶
By using --source-project-id is possible to import all available samples in succeeded or failed_qc state that have files from one project into a different one.
$ gencove projects import-existing-samples destination-project-id --source-project-id source-project-id
Note
We automatically batch large project-to-project imports into groups of 100 samples.
Optionally, universal metadata can be assigned to each new sample by adding --metadata-json: