-
Notifications
You must be signed in to change notification settings - Fork 0
withdrawal
Participants in the MoBa cohort might withdraw their consent/participation and ask for their data to be deleted. This includes all data, including snpArray (GWAS) and methylation data.
MoBa is obliged to remove all information within a reasonable time frame.
Your contract will furthermore force you to exclude these participants from further research - but not from research allready done. The list over samples you need to delete is described below, under What samples have been/will be deleted?
All samples (identified by SentrixId_well) are from individuals that have asked to have their data deleted from MoBa.
You will find one or more files on a TSD directories called
Datasets/withdrawal - this would be a sub-directory of the modality
(p229mobagenetics or p229methylation) Every time we delete, we publish
an (accumulated) list of deleted samples in a file named
modalityDeletionsyymmdd.csv. The file contains
- Name of the set
- Sample id as SentrixID_well
- Approximate delete date (could be up to 10 days later)
When we delete samples we delete:
- Idat files
- References to idat-files in samplesheets
- All results using/containing the samples
We rerun QC on the pruned dataset. The effect of this is that the samples deleted will not contribute to the QC results. In theory, this might change the QC-results of other samples. No data on or including the sample will found under the result directories.
When we delete samples we delete from the raw-data:
- Idat files
- References to idat-files in samplesheets
- The corresponding samples in the bedset (plink files). This also means that some triads will be destroyed - if a father or mother asks for deletion, the child will get that parent as unknown
Since July 2022, Mobagenetics 1.0 does not contain raw data files, since these are the same as the ones in version 1.5.
Empty for now