scRNAseq and scATACseq of MMR vaccinattion
Dataset containing 48 samples: 12 per timepoint (before or after treatment) and group (MMR vaccine or Placebo). Each sequencing run contains the sequencing data from 4 randomized samples. Genotype data is used to demultiplex sample ids inside of each pool. Phenotype data contains the information per pool.
- 23 samples
- DAC: EGAC00001003058
- Technology: Illumina NovaSeq 6000
Data access policy for the Helmholtz Centre for Infection Research, Centre for Individualised Medicine.
Data access policy Data management refers to processes that guard and maintain the consistency and accuracy of collected data and facilitate the re-use of data. This document provides information about procedures of data management. Responsibilities Researchers have the obligation to provide accompanying metadata. Supervisors (group leaders), together with the data steward, have the responsibility to check and enforce the archiving of appropriate metadata. Included data Two categories of research data are to be distinguished: Published data. Data belonging to research published in peer-reviewed journals Unpublished data. Data belonging to unpublished research. This includes work-in-progress data but also, data that was not selected for publication. Two types of data types are to be distinguished, regardless of data category: Raw data Depending on the platform used for generation of the data this includes data formats according to standards in the field: FASTQ for raw DNA sequencing data BAM for mapped DNA sequencing data RAW for mass-spectrometry data (Thermo RAW) Processed data This includes data resulting from any additional analysis of the raw data. The format of processed data is inherently loosely specified, as it is specific to the analysis conducted. Formats are mostly non-binary (flat-text) files, such as tab-delimited or Microsoft Excel files. Metadata Metadata should include experimental variables that are crucial to repeat the experiment, and to correctly interpret the results of the experiment. Metadata should include at least: Source of biological material (cell line, tissue, organism) Treatment (chemical, biological, compound) Protocol by which the sample was prepared Instrument settings Date Researcher Metadata for published data • Depending on the database used (see below) metadata is included in different ways: • GEO, dbGAP, ENA, and EGA explicitly specify which metadata must be included with data submission to their databases. This includes both experimental and technical (‘machine’) variables. Upon submission, this metadata is linked to the accompanying data files. • PRIDE accepts RAW files, which contain both the raw data as well as the metadata of the corresponding experiment, as such providing an ‘in-file’ metadata-data link. Data storage • For published data, several public databases are used, according standards in our field: o GEO (https://www.ncbi.nlm.nih.gov/gds) for DNA sequencing and array data (USA), open access o dbGAP (https://www.ncbi.nlm.nih.gov/gap) for DNA sequencing and array data (USA), controlled access o ENA (https://www.ebi.ac.uk/ena) for DNA sequencing and array data (EU), open access o EGA (https://www.ebi.ac.uk/ega) for DNA sequencing and array data (EU), controlled access o PRIDE (https://www.ebi.ac.uk/pride) for mass-spectrometry data (EU), open access o Database choice is dependent on data-type (mass-spectrometry vs. DNA sequencing data), and per-project restrictions (e.g. EU/USA) o In publications, the respective data is referenced using unique persistent identifiers provided by the database. These identifiers link to the databases. o At the publishers’ request, processed data is primarily provided either as supplemental data to the publication at the journal’s website. However, some of the databases mentioned above also accept processed data. In case of large processed-data files, these are co-submitted with the raw data to the public database. For instance, GEO has a flexible policy for accepting various file formats (flat-text, Excel). • For unpublished data, data is stored on the institutes’ infrastructure. For integrity reasons, raw data is kept at a designated partition that is write-protected (only writable by the system administrator). Data protection To prevent data loss in case of technical failures, the institutes’ data is stored: • On one of the public databases mentioned above (published data only) • At the institutes’ local infrastructure • In addition, raw sequencing data is mirrored at an independent physical location of the institute’s local infrastructure. • Raw data is write-protected (only writable by the system administrator). Maximum retention period • Both published and unpublished data is kept for a minimum of 10 years. • The public databases mentioned above do not explicitly state a restriction on preservation time of submitted data. Therefore, we regard this as ‘permanent’. Accessibility and re-use • Published data o Raw and processed data is publicly available through one of the databases mentioned above. o According current standards in our field, data of a published studies can be freely downloaded and re-used. Availability in databases is a prerequisite for acceptance of a manuscript; the journals request peer-reviewers to check the availability of both raw and published data. Databases such as GEO provide functionality such as ‘reviewer links’ that allow for anonymized download/viewing of submitted data, prior to publication. o The use of standardized data formats for DNA sequencing and mass-spectrometry (FASTQ, BAM, RAW), allows for re-analysis of the original data by others. • Unpublished data o Unpublished data is not publicly accessible, and is only available to researchers within the institutes’ departments. Privacy of sensitive data • Published data o Sensitive data containing identifiable information (DNA sequence data from donors, patients, healthy volunteers, etc.) is deposited under controlled access, depending on the informed consent of the corresponding project. Both EGA and dbGAP have controlled access mechanisms. As such they are appropriate databases for hosting sensitive patient data under secure standards. Access is controlled by a project-specific Data Access Committee (DAC) and applications are submitted to the Data Access and Compliance Office (DACO) or International Data Access Committee (IDAC). These ensure that potentially identifiable data will only be used by qualified scientists, taken into consideration access policies and restrictions on the purpose of data use. Procedures for identifiable data and controlled access are available via https://www.ebi.ac.uk/ega/about, https://www.ncbi.nlm.nih.gov/projects/gap/cgi-bin/about.html • Unpublished data o Sensitive data containing identifiable information is not publicly available and not accessible to anyone outside of our institute.
Studies are experimental investigations of a particular phenomenon, e.g., case-control studies on a particular trait or cancer research projects reporting matching cancer normal genomes from patients.
Study ID | Study Title | Study Type |
---|---|---|
EGAS00001006787 | Other |
This table displays only public information pertaining to the files in the dataset. If you wish to access this dataset, please submit a request. If you already have access to these data files, please consult the download documentation.
ID | File Type | Size | Located in | |
---|---|---|---|---|
EGAF00007772617 | fastq.gz | 24.2 GB | ||
EGAF00007772618 | fastq.gz | 27.6 GB | ||
EGAF00007772619 | fastq.gz | 20.4 GB | ||
EGAF00007772620 | fastq.gz | 23.3 GB | ||
EGAF00007772621 | fastq.gz | 4.3 GB | ||
EGAF00007772622 | fastq.gz | 33.0 GB | ||
EGAF00007772623 | fastq.gz | 2.5 GB | ||
EGAF00007772624 | fastq.gz | 18.0 GB | ||
EGAF00007772625 | fastq.gz | 3.6 GB | ||
EGAF00007772626 | fastq.gz | 25.9 GB | ||
EGAF00007772627 | fastq.gz | 3.3 GB | ||
EGAF00007772628 | fastq.gz | 24.4 GB | ||
EGAF00007899927 | vcf | 97.5 MB | ||
EGAF00007903080 | csv | 2.8 kB | ||
EGAF00007903081 | fastq.gz | 11.5 GB | ||
EGAF00007903082 | fastq.gz | 13.0 GB | ||
EGAF00007903083 | fastq.gz | 11.2 GB | ||
EGAF00007903084 | fastq.gz | 12.5 GB | ||
EGAF00007903085 | fastq.gz | 19.1 GB | ||
EGAF00007903086 | fastq.gz | 21.4 GB | ||
EGAF00007903087 | fastq.gz | 19.1 GB | ||
EGAF00007903088 | fastq.gz | 21.8 GB | ||
EGAF00007903089 | fastq.gz | 26.6 GB | ||
EGAF00007903090 | fastq.gz | 30.6 GB | ||
EGAF00007903091 | fastq.gz | 21.3 GB | ||
EGAF00007903092 | fastq.gz | 24.5 GB | ||
EGAF00007903093 | fastq.gz | 20.0 GB | ||
EGAF00007903094 | fastq.gz | 22.9 GB | ||
EGAF00007903095 | fastq.gz | 24.0 GB | ||
EGAF00007903096 | fastq.gz | 1.9 GB | ||
EGAF00007903097 | fastq.gz | 24.0 GB | ||
EGAF00007903098 | fastq.gz | 26.9 GB | ||
EGAF00007903099 | fastq.gz | 21.1 GB | ||
EGAF00007903100 | fastq.gz | 23.8 GB | ||
EGAF00007903101 | fastq.gz | 3.2 GB | ||
EGAF00007903102 | fastq.gz | 23.0 GB | ||
EGAF00007903103 | fastq.gz | 3.8 GB | ||
EGAF00007903104 | fastq.gz | 29.1 GB | ||
38 Files (667.1 GB) |