Search Results - EGA European Genome-Phenome Archive

Poland Podlaskie Voivodeship WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 12 samples (6 female, 6 male of Podlaskie Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000125

Poland Lubusz Voivodeship WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 19 samples (8 female, 11 male of Lubusz Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000127

Poland Holy Cross Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 6 samples (6 female of Holy Cross Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000162

Poland Warmian-Mazurian Voivodeship WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 15 samples (8 female, 7 male of Warmian-Mazurian Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000128

Poland Lublin Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 24 samples (14 female, 10 male of Lublin Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000155

Poland Lodz Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 41 samples (20 female, 21 male of Lodz Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000165

Poland Lesser Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 32 samples (14 female, 18 male of Lesser Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000166

Poland Mazovia Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 43 samples (16 female, 27 male of Mazovia Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000164

Poland Greater Poland Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 37 samples (19 female, 18 male of Greater Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000161

Poland Subcarpathian Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 22 samples (11 female, 11 male of Subcarpathian Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000157

Poland Pomeranian Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 25 samples (14 female, 11 male of Pomeranian Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000160

Poland Lower Silesian Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 30 samples (15 female, 15 male of Lower Silesian Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000156

Poland Silesian Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 47 samples (23 female, 24 male of Silesian Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000163

Poland Kuyavian-Pomeranian Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 22 samples (11 female, 11 male of Kuyavian-Pomeranian Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000158

Poland West Pomeranian Voivodeship - WGS

This project used NGS (next generation sequencing), using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner. The dataset includes BAM and BAM.BAI files from Whole Genome Sequencing of 17 samples (7 female, 10 male of West Pomeranian Voivodeship, Poland from POPULOUS collection). Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

Dataset EGAD50000000129

Integrative Single-Cell Analysis of Transcriptome, Epigenome, and Lineage in HIV Latency and Activation

With the development of triple combination antiretroviral therapy, routine HIV treatment eliminates nearly all actively infected cells. Nevertheless, the small reservoir of latently infected cells, which can remain dormant for long periods of time before becoming active and producing new virus particles, represents a crucial barrier to completely curing the disease. Identifying markers that identify latently infected cells or the biochemical factors that control latency activation could enable the effective use of a “shock and kill” strategy, where specific targeting or activation of latently infected cells eliminates the viral reservoir. Our recent work suggests that the global transcriptomic and epigenomic changes during hematopoietic differentiation affect viral latency and activation. Additionally, we recently found that global inhibition of histone deacetylase activity increases viral activation in these cells, further implicating epigenomic changes during activation. These results raise fundamental questions: What are the markers of latently infected cells? How do the transcriptomic and epigenomic states of a cell affect latency and activation? How does the differentiation state relate to viral latency? Here, we leverage our experimental platform for identifying latently and actively infected cells, single-cell transcriptome and epigenome sequencing, and our recently developed computational integration methods to investigate these questions. Our interdisciplinary team combines expertise in HIV basic science, HIV clinical treatment, and bioinformatics to develop an experimental and computational framework for integrated gene expression, chromatin accessibility, and lineage into a single picture of viral latency and activation. Specifically, this project will (1) use single-cell RNA-seq and single-cell ATAC-seq to map the diversity of infected cells, (2) investigate the relationship between hematopoietic differentiation state and viral activation, (3) determine viral integration sites through single-cell RNA-seq, (4) computationally integrate single-cell transcriptome and epigenome profiles, and (5) computationally infer cell lineage relationships among viral genomes and infected cells. To accomplish these goals, we will carry out the following aims: (1) Characterize lineage, transcriptomic and epigenomic diversity of single latently and actively infected primary cells. (2) Investigate latency and activation during in vitro differentiation. (3) Survey single cell diversity of re-activated and in vitro infected cells from cART-suppressed patients. Together, these aims will produce a comprehensive, integrated transcriptomic and epigenomic atlas of the HIV reservoir, identify DNA and RNA biomarkers of latency, and characterize clonal expansion patterns. Our work also develops a broadly applicable experimental and computational framework, laying a foundation for the discovery of novel insights into HIV latency and activation.

Study phs002915

Center for Common Disease Genomics [CCDG] - Inflammatory Bowel Disease (IBD) - Global Microbiome Conservancy Host Exomes

The human body is a complex ecosystem, hosting tens of billions of bacteria, primarily in the gut. This community, known as the 'gut microbiome', is vital to human health, affecting functions ranging from metabolism, immunity, and development, to behavior. Conversely, reduced microbiome diversity and other imbalances of the gut community (dysbiosis) are associated with many diseases of the industrialized world, such as metabolic syndrome, asthma, and inflammatory bowel diseases among others. Microbiome-based interventions thus hold the potential to revolutionize our understanding of, and therapeutic approaches to, many aspects of human health and disease. Despite many advances, current understanding of the human microbiome is largely limited to majority ethnic groups in industrialized nations, and does not reflect the full diversity of human commensal microbiota. In addition to the scientific ramifications of minority underrepresentation, there are significant translational and ethical implications as well: First, failing to capture the full diversity of healthy human microbiota may limit our ability to understand and generate effective therapeutics for many microbiome-associated diseases. Second, underrepresented groups are less likely to benefit from microbiome-based medical advances tailored to well-studied populations, propagating healthcare inequities. The window of opportunity to characterize human microbiome diversity is closing rapidly. Human gut microbial diversity is diminishing around the globe, due to the spread of Westernized diets and lifestyles, which are associated with reduced microbiome biodiversity. The Global Microbiome Conservancy (GMbC) is a non-profit collaboration between scientists and communities around the world that aims to 1) preserve the full biodiversity of the human gut microbiome, 2) characterize its evolution across populations and host lifestyles and 3) investigate its interactions with the human host. We are collecting gut microbiome and human DNA samples from diverse populations around the world, from isolated groups to urbanized populations, to culture and study this essential biodiversity and to preserve it in a living "seed bank" as a long-term safeguard against future extinctions. The National Human Genome Research Institute (NHGRI) has funded a collaborative large-scale genome sequencing effort to comprehensively identify rare risk and protective variants contributing to multiple common disease phenotypes. Called the Centers for Common Disease Genomics (CCDG), this initiative will explore a range of diseases with the ultimate goal of: Undertaking variant discovery for enough different examples of disease architectures and study designs to better understand the general principles of the genomic architecture underlying common, complex inherited diseases. Understanding how best to design rare variant studies for common disease. Developing resources, informatics tools, and innovative approaches and technologies for multiple disease research communities and the wider biomedical research community. The initial focus of the CCDGs will be in cardiovascular disease (early-onset coronary artery disease, atrial fibrillation, hemorrhagic stroke), neuropsychiatric disease (epilepsy, autism), and autoimmune/inflammatory disease (type 1 diabetes, inflammatory bowel disease). The Broad Institute is one of four selected CCDG project centers. Both exome and genotyping information of GMbC participants will help understanding how recruited human populations are structured and genetically related. This human genetic structure will be analyzed in light of gut microbiome compositional and genomic differences to illuminate associations between specific microbiome traits and human groups and the evolutionary processes involved in the co-evolution of human hosts and their gut microbiome. It will also provide variant information for critical genes shaping the composition of microbiomes, such as genes involved in innate and adaptive immunity (e.g. antimicrobial peptides) or in the regulation of the immune response (e.g. Nod2). Association studies between specific variants in these genes and microbiome features will be performed, which will then be validated with in vitro and in vivo experiments. Human data from GMbC cohorts will also increase the genetic diversity of human populations, providing additional variant information for many susceptible loci that were found to be associated with Crohn's disease and ulcerative colitis. The whole genome sequencing data generated is comprised of samples from diverse and indigenous populations. Raw sequencing data, metadata, vcf and phenotype data at the individual level for a subset of the cohort's samples are available at https://anvilproject.org/data. For questions about availability, contact help@lists.anvilproject.org. Microbiome data for the samples sequenced in this study can be found in phs002235 Global Microbiome Conservancy Sequence Data.

Study phs002205

Impact of germline pathogenic variants in 27 cancer-predisposing genes on the risk of lymphoma

The application of advanced molecular technology has significantly expanded lymphoma classification, allowing risk stratification and treatment optimization. Limited evidence suggests the presence of a genetic predisposition in lymphoma, indicating the potential for better individualized clinical management based on a novel lymphoma classification. Herein, we examined the impact of germline pathogenic variants in 27 cancer-predisposing genes with lymphoma risk and explored the clinical characteristics of pathogenic variant carriers. This study included 2,066 lymphoma patients and 38,153 cancer-free controls from the Japanese population. Following quality control of sequencing data, samples from 1,982 lymphoma patients and 37,592 controls were further analyzed. Sequencing data of controls were obtained from JGAD000721. Germline pathogenic variants in some cancer-predisposing genes were associated with a high risk of lymphoma. Furthermore, germline pathogenic variants in these genes were especially associated with the higher risk of a certain subtype. These results would provide novel insights concerning monogenic form into lymphoma classification. Some lymphoma patients may benefit from surveillance and targeted treatment like other neoplasms.

Study JGAS000347

Distinct genomic profiles and clinical outcomes in constitutional mismatch repair deficiency-associated high-grade gliomas: insights into mutational signatures and clonal evolution

Constitutional mismatch repair deficiency (CMMRD) is a rare cancer-predisposition syndrome, yet the mutational processes and clonal evolution of CMMRD-associated high-grade gliomas (HGGs) remain incompletely understood. In this study, mutational signatures and tumor evolution were analyzed in 25 CMMRD-associated HGGs. Germline biallelic mutations were most frequently identified in MSH6 (56.0%), followed by PMS2 (36.0%) and MLH1 (8.0%). Affected patients showed very early disease onset (mean 5.8 years) and poor clinical outcomes, with a mean progression-free survival of 16 months. Distinct genomic and clinical differences were observed between MSH6- and PMS2-associated tumors. MSH6-deficient HGGs were enriched for SBS6, whereas PMS2-deficient tumors showed predominance of SBS21, and these mutational signatures were correlated with prognosis. Clonal evolution analyses revealed early involvement of POLE/POLD1 mutations and persistence of the founding clone at recurrence. Overall, the study highlights the importance of mutational signatures and clonal evolution in shaping tumor behavior and clinical outcomes in CMMRD-associated HGGs.

Study EGAS50000001506

MethCORR: DNA Methylation-based Characterization, Classification and Prognostication of Colorectal Cancer using Archival Formalin-fixed, Paraffin-embedded Tissue

Transcriptional characterization and classification has potential to resolve the inter-tumor heterogeneity of colorectal cancer (CRC) and improve patient management. Yet, robust transcriptional profiling is difficult using formalin-fixed, paraffin-embedded (FFPE) samples, which complicates testing in clinical and archival material. We present MethCORR, an approach that allows uniform molecular characterization and classification of fresh-frozen and FFPE samples. MethCORR identifies genome-wide correlations between RNA expression and DNA methylation in fresh-frozen samples. This information is used to infer gene expression information in FFPE samples from their DNA methylation profiles. MethCORR was applied to methylation profiles from 877 fresh-frozen and FFPE samples and comparative analysis identified the same two major subtypes in four independent cohorts. Furthermore, subtype-specific prognostic biomarkers that better predicted relapse-free survival (HR=2.66, 95% CI [1.67-4.22], P<0.001) than TNM staging and MSI status were identified and validated using DNA methylation-specific PCR assays. The MethCORR approach is general, and may be similarly successful for other cancer types.

Study EGAS00001004293

FASTQ files of total RNA-Seq data of POPS control samples

Placental biopsies (n = 64 female placentas, n = 67 male placentas) were selected from healthy pregnancies from the POPs cohort. These patients had no evidence of hypertension at booking and during pregnancy, did not experience pre-eclampsia, Hemolysis, Elevated Liver enzymes, and Low Platelets (HELLP) syndrome, gestational diabetes, or diabetes mellitus type I or type II and other obstetric complications. They delivered live babies with a birth weight percentile in the normal range (20-80th percentile), with no evidence of slowing in fetal growth trajectory. Chorionic villi from the corresponding placentas (free from decidua, visible infarction, calcification, hematoma, or damage) were collected and processed within 30 minutes of separation from the uterus. After repeated washes in chilled phosphate buffered saline, the samples were placed in RNA later (Applied Biosystems) and stored at -80°C. Total placental RNA was extracted using mirVana Isolation Kit (Ambion). For each placenta, approximately 5 mg of tissue were homogenized in the Lysis/Binding solution for 20 sec at 6 m/s using a bead beater (FastPrep24) and Lysing Matrix D Tubes (MP Biomedicals). The samples were then spun at 13,000 rpm for 5 min at 4°C and the supernatants recovered. Afterwards, the manufacturer's instructions were followed. Immediately after the RNA extraction, placental RNA samples were DNase-treated using DNA-free DNA Removal Kit (Ambion), aliquoted, and stored in -80°C. Quantity and quality of the RNA samples were assessed using the Agilent 2100 Bioanalyzer, the Agilent RNA 6000 Nano Kit (Agilent Technologies), and Qubit fluorometer. Libraries were prepared starting with 300-500 ng of good quality total RNA (RIN ≥7.5) using the TruSeq Stranded Total RNA Library Prep Kit with Ribo-Zero Human/Mouse/Rat (Illumina), according to the manufacturer's instructions. The kit contains 96 uniquely indexed adapter combinations in order to allow pooling of multiple samples prior to sequencing. After determining their size (with the Agilent 2100 Bioanalyzer and the Agilent High Sensitivity DNA Kit by Agilent Technologies) and concentration (by qPCR with the KAPA Illumina ABI Prism Library Quantification Kit, Kapa Biosystems), libraries have been pooled and sequenced (single-end, 125 bp) using a Single End V4 Cluster Kit and an Illumina HiSeq2500 or HiSeq4000 instrument.

Dataset EGAD00001003457

Similarity and diversity of the tumor microenvironment in multiple metastases: critical implications for overall and progression-free survival of high-grade serous ovarian cancer.

The tumor microenvironment is pivotal in influencing cancer progression and metastasis. Different cells co-exist with high spatial diversity within a patient, yet their combinatorial effects are poorly understood. We investigate the similarity of the tumor microenvironment of 192 local metastatic lesions in 61 ovarian cancer patients. An ecologically inspired measure of microenvironmental diversity derived from multiple metastasis sites is correlated with clinicopathological characteristics and prognostic outcome. We demonstrate a high accuracy of our automated analysis across multiple sites. A low level of similarity in microenvironmental composition is observed between ovary tumor and corresponding local metastases (stromal ratio r = 0.30, lymphocyte ratio r = 0.37). We identify a new measure of microenvironmental diversity derived from Shannon entropy that is highly predictive of poor overall (p = 0.002, HR = 3.18, 95% CI = 1.51-6.68) and progression-free survival (p = 0.0036, HR = 2.83, 95% CI = 1.41-5.7), independent of and stronger than clinical variables, subtype stratifications based on single cell types alone and number of sites. Although stromal influence in ovary tumors is known to have significant clinical implications, our findings reveal an even stronger impact orchestrated by diverse cell types. Quantitative histology-based measures can further enable objective selection of patients who are in urgent need of new therapeutic strategies such as combinatorial treatments targeting heterogeneous tumor microenvironment.

Study EGAS00001002065

eIMPACT Trial: Modernized Collaborative Care to Reduce the Excess CVD Risk of Older Depressed Patients

Cardiovascular disease (CVD) is the #1 killer of American men and women, and its economic burden is substantial and on the rise. Adults with depression are at elevated risk of CVD events and poor CVD prognosis. Unfortunately, past clinical trials of depression treatments have not observed the anticipated cardiovascular benefits. A novel explanation for these null results is that the depression interventions in these trials, which all involved patients with preexisting CVD, were delivered too late in the natural history of CVD. Accordingly, the objective of this single-center, parallel-group, assessor-blinded randomized controlled trial was to determine whether successful depression treatment before, versus after, the onset of clinical CVD reduces CVD risk in depression. Primary care patients with depression and elevated CVD risk from a safety net healthcare system (N = 216, Mage = 59 years, 78% female, 50% Black, 46% with income <$10,000/year) were randomized 1:1 to 12 months of the eIMPACT intervention (a modernized collaborative stepped care program involving internet cognitive-behavioral therapy [CBT], telephonic CBT, and/or select antidepressants) or usual primary care for depression (primary care providers supported by embedded behavioral health clinicians and psychiatrists). The primary outcome was endothelial dysfunction (brachial flow-mediated dilation) at 12 months, and the secondary outcomes were self-reported depressive symptoms (Hopkins Symptom Checklist-20), autonomic dysfunction (high-frequency heart rate variability), systemic inflammation (interleukin-6 and high-sensitivity C-reactive protein), and platelet activation (β-thromboglobulin and platelet factor 4) at 12 months. The central hypothesis was that the eIMPACT intervention would improve endothelial dysfunction in depressed adults by decreasing depressive symptoms, autonomic dysfunction, systemic inflammation, and platelet activation. Primary results are posted to ClinicalTrials.gov at NCT02458690. The de-identified limited dataset available on BDC consists of only the individual phenotypic data needed to confirm this trial’s primary results – i.e., randomization status, primary and secondary outcome variables, and participant characteristics utilized in the hypothesis-testing models (age, sex, race, education, income, and systolic blood pressure). We also provide the SAS code to replicate the results of the hypothesis-testing models reported in Table 4 and Supplemental Tables 1-3 in the main outcomes paper (#2 in Selected Publications). Of note, the user will need to specify the file path for the dataset to run the SAS code. Instructions for requesting individual-level data are available on BDC at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BDC. For questions about availability, you may contact the BDC team at https://biodatacatalyst.nhlbi.nih.gov/contact.

Study phs003283

Programmatic submission based on XML

Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

Documentation submission/metadata/submission/programmatic-submission-xml

University of Illinois at Chicago (UIC) Autism Centers of Excellence (ACE) Exome Sequencing Analysis

Autism spectrum disorder (ASD) is highly heritable with recent sibling recurrence risk estimates of 19% overall and 26% in males. The heritable phenotype of hyperserotonemia, or elevated levels of platelet serotonin (5HT), in ~35% of people with ASD is a well-established biomarker. The efficacy of drugs like risperidone and potent serotonin transporter inhibitors at treating behaviors related to Insistence on Sameness, along with evidence of the contribution of hyperserotonemia to autism susceptibility collectively support the hypothesis that dysfunction in the 5HT system is a significant etiological target for investigation of the genetic component to autism. ASD genetic architecture is complex; common variants of large effect do not contribute substantially to overall ASD risk, but there are clearly common variants with small effects and rare genetic/genomic variation of larger effect among ASD genetic risk factors. The NIH ARRA Autism Sequencing Consortium, including Dr. Sutcliffe and Dr. Cook among others, has initiated exome sequencing studies to identify more of the rare variants contributing to ASD. Data from our group and others reveal numerous rare de novo and inherited sequence mutations, and the number of de novo and other functional mutations that are found to affect molecules encoding 5HT signaling and its regulation further reinforces our hypothesis that regulation of serotonin levels is important in autism genetic susceptibility. Integrin receptor signaling pathways were prominently featured among identified de novo mutations, thus defining a set of interrelated gene networks that control 5HT signaling. We propose to extend our findings to date by conducting exome sequencing on ACE subjects, for whom we also have 5HT biochemical data, to identify rare variants (including CNVs) in 5HT-related gene networks. In total we propose to have exome sequencing completed on 523 samples. The purpose of the proposed research is two-fold: 1) we will conduct more extensive investigations to determine the support for the hypothesis that genetic variation at genes regulating platelet serotonin levels affect susceptibility to ASD and 2) we will combine the exome sequence data from these studies with sequence data for autism being accumulated in a variety of other research projects to further the goal of identifying and characterizing the genetic component to ASD.

Study phs000712

12255 results for "free coins ultimate team Visit Buyfc26coins.com for latest FC 26 coins news..G9vn"

in 39.39 milliseconds.