14538 results for "PLOS+ONE+Pennsylvania+German+ACS+language+code+pdc+open+access+study"

in 29.04 milliseconds.

• NEC

  This multi-centre, non-randomized, open-label, phase II trial (NCT03016338), assessed niraparib monotherapy (cohort 1, C1), or niraparib and dostarlimab (cohort 2, C2) in patients with recurrent serous or endometrioid endometrial carcinoma. The primary endpoint was clinical benefit rate (CBR). Secondary outcomes were safety and objective response rate (ORR). Translational research was an exploratory outcome. Potential biomarkers were evaluated in archival tissue by immunohistochemistry and next generation sequencing panel. Feasibility of liquid biopsy by ctDNA was assessed.

  Dataset EGAD00001010056

• Submitting array based metadata

  Submitting array based metadata For further information please check our Submission FAQs, submission quickguide as well as submission terms! The submission metadata required for Array-based submission must be submitted using EGA programmatic submission and by completing the Array-based format (AF) template. The guidelines for this workflow are described on this page. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA Array-based-Format (AF) template. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA-Array-based-Format (AF) template. Metadata Model Registering Metadata Use the EGA programmatic submission to register your Study, Samples, Data Access Committee (DAC) and Policy. This online interface enables you to create new and edit existing submissions. Do not use the Submitter Portal to register the metadata objects for array submissions. Please, go to the EGA programmatic submission. Registering Study Go to the EGA programmatic submission Submit an study XML Take a note of your study accession number (EGASXXXXXXXXXXX) To use the study accession number in a publication, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found on https://ega-archive.org "The European Genome-phenome Archive of human data consented for biomedical research"(https://doi.org/10.1093/nar/gkab1059 ). Registering Samples Go to the EGA programmatic submission Submit a sample XML Save the list of accession numbers. These will be needed for the AF template. Registering Data Access Committee Further information on the role of your DAC. Go to the EGA programmatic submission Submit a DAC XML Take a note of the DAC accession number (EGACXXXXXXXXXXX) Registering Policy Your Data Access Policy provides the terms and conditions of data use. This is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAA) Go to the EGA programmatic submission Submit a Policy XML Take a note of the Policy accession number (EGAPXXXXXXXXXXX) Complete the Array-based format (AF) spreadsheet Once you have completed the registration of your Study, DAC and Policy using the programmatix submission, you must then complete and return the AF spreadsheet The AF spreadsheet consists on four components: Do not use EGA IDs registered using the Submitter Portal. You can easily identify objects registered in the Submitter Portal by their EGA ID pattern: EGA[A-Z]5{10 more digits} (e.g. for a sample EGAN50000002506). For populating an AF spreadsheet, please exclusively use EGA IDs following this specific pattern: EGA[A-Z]0{10 more digits} (e.g. for a sample EGAN00001691542). Tab1) Webin accessions : Provide the accession numbers for your study, DAC and policy. Please, also add your ega-box number. Tab2) Sample & phenotypes: Please, leave this tab blank. Tab3) Dataset: Describe the dataset to be created Tab4) Data files: Define how your data is going to be organised into datasets and packets for distribution (linkage between samples and files). Should further assistance be required after going through the guide below; please do not hesitate to contact the EGA helpdesk Once the AF spreadsheet is populated, please send it to our EGA helpdesk for further validation. AF spreadsheet Should your submission require multiple DAC's or policies, use ' ; ' to separate the accession numbers. Accessions AF spreadsheet: Samples & phenotypes Samples and phenotypes AF spreadsheet: Datasets We suggest that each dataset consists of a common set of data. The example below consists of two datasets, grouped according to shared data type, technology and by case/control. We also like to capture the number of unique samples that make up the dataset and the Data Access Committee (DAC) responsible for providing the named dataset and their policy (EGAP). Datasets AF spreadsheet: Data files What follows is an example of how to map your samples to the array based files added to your upload account (4th tab). Data Files Please, find below some practical examples on how to register the linkage between samples-files Case 1) 1 sample or list of samples in different datasets: Data Files In case you have a list of samples that belong to different datasets, please, repeat the samples accession number/s in the first column and link the sample to the corresponding dataset each time (each row). Each row is one linkage between sample-file-dataset. Case 2) 1 sample links to several files: Data Files In order to add multiple files to one sample you MUST use “ ; “ between filenames. Example: file1.gpg;file2.gpg;file3.gpg In case that you want to add an extra file to the sample (phenotype or .Rdata), please use “Additional files” column. Important note: You MUST upload the encrypted and unencrypted md5sum values of all files uploaded to your submission account using the filename nomenclature (file.gpg, file.md5,file.md5.gpg). Your submission will not be processed without md5values supplied for all files in the CORRECT format. What happens after the submission of a dataset? All datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitted or DAC contact instructs our EGA helpdesk for the study to be released. Finally, your data is archived within our databases and prepared for encrypted distribution upon the request of permitted EGA account holders. We strongly advise you NOT to delete your data until we confirm that your data has been successfully archived.

  Documentation submission/metadata/submission/array

• Genomic profiling of subcutaneous patient derived xenograft models of solid childhood cancer

  The pediatric cancer cohort in this study included 70 PDX models from 65 different individuals. This cohort included a total of 16 different pediatric solid tumor subtypes, including fourteen Wilms tumors, thirteen hepatoblastomas, thirteen osteosarcomas, ten germ cell tumors, four neuroblastomas, three clear cell sarcomas, two adrenal cortical carcinomas, two leydig cell tumors, two medulloblastomas, one embryonal rhabdomyosarcoma (ERMS), one Ewing sarcoma, one pleomorphic sarcoma, one adenocarcinoma, one glioblastoma, one mesothelioma and one ovarian tumor. Notably, we have five samples with multiple PDX models from same patient, including two cases with duplicates (564 and 564-Dup, 1796 and 1796-Dup), one case with two different metastasis (560-SM, 560-LM), one case with two blocks from same tumor (1939 and 1939-Dup), and one case with different primary tumor from same patient (2264 and 1932). We have a total of 353 sequencing data, including 82 RNA sequencing data (RNA-seq), 138 whole-exome sequencing (WES) and 135 low-pass whole-genome sequencing (WGS). For RNA-seq data, we have 61 PDXs and 21 PTs; for WES, we have 67 PDXs, 30 PTs and 40 matched normal germlines; for WGS, we have 64 PDXs, 30 PTs and 40 matched normal germlines. Of which, 19 PT-PDX paired RNA-seq, 28 paired PT-PDX paired WES and WGS were included.

  Dataset EGAD00001009863

• Pilot study of adoptive cell therapy using cultured tumor infiltrating lymphocytes for Japanese melanoma patients refractory to immune-checkpoint inhibitors

  To evaluate feasibility of the adoptive cell therapy (ACT) using tumor infiltrating lymphocytes (TIL) in Japanese melanoma patients who failed the immune checkpoint inhibitors (ICIs) and investigate the immune components and immunologic milieu within the pretreatment tumor and expanded TILs from there.?Three patients whose clinical subtype were mucosal, superficial spreading, and acral melanoma were treated and the all completed the TIL-ACT. Clinical response were one short-partial response, one relatively long-stable disease, and one progression disease. Whole-exome and transcriptional analysis of pretreatment tumor revealed the various?immunophenotypes including tumor mutation burden with immunogenic neoantigens and upregulation of immunosuppressive gene signatures.

  Study JGAS000249

• Characterization of High-Grade Serous Ovarian Cancer Subtypes via Single-Cell and Spatial-Transcriptomics Profiling

  We measured gene expression in single-cell RNA sequencing samples from patients with high-grade serous ovarian cancer (HGSOC), for a study on improving HGSOC subtype definition by taking into account varying cell type proportions within tumors. The initial dataset (added October, 2020) contains 3 samples (3 individuals). The next dataset (added November, 2022) contains 34 samples from 8 individuals. The samples in the second dataset were sequenced in five different ways: 1) rRNA depletion and bulk RNA sequencing of tumor chunks, 2) rRNA depletion and bulk RNA sequencing of dissociated cells, 3) poly-A capture and bulk RNA sequencing of dissociated cells, 4) poly-A capture and scRNA sequencing of dissociated cells, 5) barcoding and pooling cells and scRNA sequencing (2 pools of 4 samples each). The third dataset (added June, 2024) contains data from one spatially resolved transcriptomics experiment (4 samples, one per Visium capture area, describing one tumor from one individual) and scRNA sequencing on 5 samples (5 individuals).

  Study phs002262

• NHLBI's Collection of Datasets for General Research Use (Public Posting of Genomic Summary Results: Allowed)

  This collection contains all of NHLBI's authorized individual-level genomic datasets currently in dbGaP that are approved for General Research Use (GRU) and have no further limitations beyond those outlined in the model Data Use Certification Agreement. Genomic Summary Results (GSR) sharing is allowed (unrestricted) or not applicable. To request access to this study collection, select phs003132 in the dbGaP Authorized Access System.

  Study phs003132

• National Eye Institute Glaucoma Human Genetics Collaboration (NEIGHBOR) Consortium Glaucoma Genome-Wide Association Study: Whole Exome Resequencing in Glaucoma

  This is a study of primary open angle glaucoma (POAG) conducted through exome sequencing of cases and comparison of variant frequencies with general population frequencies available in dbGAP and controlled for sequencing platform artifact to minimize false positives. POAG is an intraocular pressure (IOP) related progressive optic neuropathy that ultimately leads to blindness. This study builds upon the efforts of an on-going collaborative consortium that studied 2,170 POAG cases and 2,347 controls with a unified definition of POAG (the NEIGHBOR consortium: NEI Glaucoma Human genetic collaBORation). The case definition for NEIGHBOR was harmonized with an additional 976 cases and 1140 controls from the NHGRI supported GENEVA (gene-environment) study of glaucoma (GLAUGEN) (NIH/NHGRI U01HG004728, Pasquale PI). In NEIGHBOR, cases and controls were recruited from ophthalmology clinics and were examined by ophthalmologists. For cases, the clinical exam included intraocular pressure measurements, optic nerve assessment and visual field evaluation. Controls had no family history of glaucoma, normal intraocular pressure and normal optic nerves. Cases and controls were also drawn from two clinical trial populations: Advanced Glaucoma Intervention Study (AGIS, NEI U10EY006827, D. Gaasterland PI) and Collaborative Initial Glaucoma Treatment Study (CIGTS, NEI U10 EY009149, P. Lichter PI). The Glaucoma Exome Sequencing study has one Principal Investigator: Theresa Gaasterland (UCSD) and two Co-Investigators: Robert Weinreb, MD, and Kang Zhang, MD, PhD, all of whom are part of the NEIGHBOR, subsequently NEIGHBORHOOD, consortium, which in turn has two Co-Principal Investigators: J. Wiggs (Harvard, MEEI), and M. Hauser (Duke). NEIGHBOR collaborators who contributed samples and/or expertise to the Glaucoma Exome Sequencing study included the following: Harvard Medical School (Massachusetts Eye and Ear Infirmary) (J. Wiggs, L. Pasquale); Duke University Medical Center (M. Hauser, E. Hauser, R. Allingham, S. Schmidt); University of Michigan (J. Richards, S. Moroi, P. Lichter); University of Miami (M. Pericak-Vance, R. Lee, D. Budenz); Vanderbilt University (J. Haines); University of California San Diego (K. Zhang, R. Weinreb; T. Gaasterland); University of Pittsburgh (J. Schuman, G. Wollenstein); University of West Virginia (A. Realini, J. Charlton, S. Zareparsi); Johns Hopkins University (D. Friedman); Stanford University (D. Vollrath, K. Singh), Eye Doctors of Washington (D. Gaasterland), Marshfield Clinic (Cathy McCarty). Hemin Chin serves as the NEI Staff Collaborator. This national collaborative study is supported by multiple NIH grants: NEI R01 EY015543 (Allingham); NEI U10 EY006827 (D. Gaasterland); NHLBI R01 HL073389 (E. Hauser); NEI R01 EY13315 (M. Hauser); NEI U10 EY009149 (Lichter); NEI R01 EY015473 (Pasquale); NEI U10 EY012118 (Pericak-Vance); NEI R03 EY015682 (Realini); NEI R01 EY011671 (Richards); NEI R01 EY09580 (Richards); NEI R01 EY013178 (Schuman); NEI R01 EY015872 (Wiggs); NEI R01 EY009847 (Wiggs); NEI R01 EY010886 (Wiggs); NEI R01 EY144428 (Zhang); NEI R01 EY144448 (Zhang); NEI R01 EY18660 (Zhang). Funding support for genotyping through exome sequencing, which was performed at the University of California, San Diego, was provided by the National Eye Institute (RC2 EY020678-01).

  Study phs000558

• Genetic Epidemiology of Lung Cancer Consortium GWAS of Familial Lung Cancer

  Familial lung cancer cases were collected by the Genetic Epidemiology of Lung Cancer Consortium (GELCC) recruitment sites: University of Cincinnati, Karmanos Cancer Institute at Wayne State University, Louisiana State University Health Sciences Center-New Orleans, Mayo Clinic, and Medical College of Ohio. Familial cases for this study came from three sources: 1) one case each from families (at least 3 affected lung cancer cases in the family) included in the linkage analysis; 2) one case from linkage-eligible families (at least 3 affected lung cancer cases in the family) but where there were insufficient biospecimens available to make them informative for linkage analysis; and 3) one case from families not eligible for the linkage study with a family history of at least one first or second degree relative affected with lung cancer. Unrelated controls were selected from 1) among the spouses of family members, thus matching on socio-economic status (SES) and ethnicity (typically) of the cases or 2) from case-control studies of lung cancer conducted in the same location in which the linkage families were collected and matched on age, sex, and race. All cases and controls self-reported as European American. Biospecimens used for normal DNA extraction included blood, saliva or mouthwash. Some samples underwent whole genome amplication.

  Study phs000629

• The PRIME-AIR Study: Positive End-Expiratory Pressure, Recruitment, Incentive Spirometry, Muscle Relaxant Optimization, Preoperative Education, Postoperative Early Ambulation, Individualized, and Reinforced

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions.The PRIME-AIR study ("Positive end-expiratory pressure, Recruitment, Incentive spirometry, Muscle relaxant optimization, preoperative Education, postoperative early Ambulation, Individualized, and Reinforced") was a prospective multi-center randomized controlled pragmatic trial, with a blinded assessor, to compare post-operative pulmonary complications (PPCs) in patients with an individualized anesthetic-centered intervention (including individualized mechanical ventilation positive end-expiratory pressure (PEEP) management to maximize respiratory system compliance and minimize driving pressures, a neuromuscular agent and subsequent reversal, and post-operative lung expansion and early mobilization) versus usual care.

  Study phs003926

• Resolving complex duplication variants using long read genome sequencing in autism spectrum disorder

  The goal of the study is to resolve complex genomic rearrangements in individuals diagnosed with autism spectrum disorder (ASD). Families were identified where at least one individual had previously been diagnosed with ASD, and carried a complex genomic rearrangement as determined by short-read whole genome sequencing. In this study the parents, proband and additional siblings, a total of 20 individuals, were analyzed using Oxford Nanopore Technologies long-read sequencing. Each individual was sequenced on one PromethION flow-cell, providing approximately 25-30X coverage of the genome. The data is deposited as nanopore BAM files with methylation information included.

  Study EGAS50000000390

• Botensilimab, an Fc-enhanced Anti-CTLA-4 Antibody, is Effective Against Tumors Poorly Responsive to Conventional Immunotherapy

  This study explores the genomic landscape associated with a novel Fc-engineered anti-CTLA-4 antibody (botensilimab) in advanced solid tumors. We seek to understand if enhancing the Fc-region affinity of anti-CTLA-4 antibodies can improve anti-tumor efficacy and expand clinical benefit to tumors poorly responsive to conventional immunotherapy. As part of an ongoing open-label, Phase 1, multicenter study, we conducted an exploratory sub-analysis of genomics data. The primary study evaluates the safety, tolerability, pharmacokinetics, and pharmacodynamics of botensilimab monotherapy and in combination with an anti-PD-1 antibody (balstilimab) in participants with advanced solid tumors. RNA from formalin-fixed paraffin-embedded (FFPE) tumor biopsies and matched normal blood samples were isolated and subjected to RNA-sequencing using the Personalis ImmunoID NeXT Platform. We demonstrated that anti-CTLA-4 engineered for enhanced FcγR affinity leverages FcγR-dependent mechanisms to potentiate T cell responsiveness, reduce intratumoral Tregs, and enhance antigen presenting cell activation. This genomic analysis contributes to our understanding of the molecular mechanisms underlying patient responses to Fc-engineered anti-CTLA-4 therapy and may inform future strategies to expand the clinical benefit of immune checkpoint blockade in cancer immunotherapy.

  Study phs003704

• AmsterdamUMC Data Access Committee for the study entitled "Carboxylesterase 1 mediates a distinctive metabolic profile of dendritic cells to attain an inflammatory phenotype"

  The current data access committee reviews and assesses data requests of researchers that seek to gain access to data presented in the manuscript entitled "Carboxylesterase 1 mediates a distinctive metabolic profile of dendritic cells to attain an inflammatory phenotype" as performed at the AmsterdamUMC, Amsterdam, Netherlands.

  Dac EGAC50000000178

• Base-excision repair pathway shapes 5-methylcytosine deamination signatures in pan-cancer genomes

  Transition of cytosine to thymine in CpG dinucleotides is the most frequent type of mutation in cancer. This increased mutability is commonly attributed to spontaneous deamination of 5-methylcytosine (5mC), which is normally repaired by the base-excision repair (BER) pathway. However, the contribution of 5mC deamination in the increasing diversity of cancer mutational signatures remains poorly explored. Here, we integrate mutational signatures analysis in a large series of tumor whole genomes with lineage-specific epigenomic data to draw a detailed view on 5mC deamination in cancer. We uncover tumor type-specific patterns of 5mC deamination signatures in CpG and non-CpG contexts. We demonstrate that the BER glycosylase MBD4 preferentially binds to open chromatin domains, which correlates with lower mutational burden in these domains. We validate our findings by modelling BER deficiencies in isogenic cell models. Overall, we establish MBD4 as the main actor responsible for 5mC deamination repair in humans.

  Study EGAS50000000536

• Evolving epigenomics of immune cells in type 1 diabetes at single nuclei resolution

  The appearance of diabetes-associated autoantibodies is the first detectable sign of the disease process leading to type 1 diabetes (T1D). Evidence suggests that T1D is a heterogenous disease, where the type of antibodies first formed imply subtypes. Here, we followed 49 children, who subsequently presented with T1D and 49 matched controls, profiling single-cell epigenomics at different time points of disease development. Quantitation of cell and nuclei populations as well as transcriptome and open-chromatin states indicated robust, early, replicable monocyte lineage differences between cases and controls, suggesting heightened pro-inflammatory cytokine secretion early among cases. The order of autoantibody emergence in cases showed variation across lymphoid and myeloid cells, potentially indicating cellular immune response divergence. The strong monocytic lineage representation in peripheral blood immune cells before seroconversion and the weaker differential coordination of these gene networks close to clinical diagnosis emphasizes the importance of early life as a critical phase in T1D development.

  Study EGAS50000000863

• RNA-seq from human embryonic tissues (additional samples 2018)

  How the genome activates or silences transcriptional programmes governs organ formation. Little is known about this in human post-implantation embryos undermining our ability to benchmark the fidelity of in vitro stem cell differentiation or cell programming, or interpret noncoding variation as potential causes of disease. Here, by studying histone modification we identified genome-wide open chromatin states and active repression across thirteen tissues during human organogenesis. We integrated the data with transcription to build the first view of how promoter states from nearly 20,000 genes differentially regulate alternative organ fates, arguing against bivalency during human organogenesis. The data illustrate tissue-specific as well as complex patterns of enhancer activity functional in zebrafish and impute master transcription factors. Overlaying 739 noncoding de novo mutations in patients allowed phenotypic correlation of developmental disorders to unanticipated target genes. Taken together, the data provide a comprehensive genomic framework for understanding normal and abnormal human development.

  Study EGAS00001003738

• Framingham Heart Study-Cohort (FHS-Cohort) - BioLINCC

  Data Access NOTE Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Related Studies Other Framingham data available include: Imaging studies (Framingham Heart Study-Cohort (FHS-Cohort)-Imaging, phs003593), Genetics and genomics (Framingham Cohort, phs000007), Collaborative Cohort of Cohorts for COVID-19 Research (C4R): (Framingham Heart Study, phs002911), and as a component of the Sleep Heart Health Study (SHHS-BioLINCC, phs003637). Available Data Original cohort: data now include examination data from the first 32 clinical exams, selected ancillary data, and event follow-up through 2018. Offspring/Omni1 cohort: Data available include Framingham Offspring examination data from the first 9 clinical exams and selected ancillary data and event follow-up through 2019. Also included are the first 4 exams from the OMNI 1 cohort. Third Generation/Omni2/New Offspring Cohort: Data available include Framingham Generation 3 examination data from the first 3 clinical exams, selected ancillary data and event follow-up through 2019. Also included are the OMNI 2 and New Offspring (NOS) cohorts. A genetic pedigree is not provided for the Framingham phenotype only data. Objectives The objectives of the Framingham Study are to study the incidence and prevalence of cardiovascular disease (CVD) and its risk factors, trends in CVD incidence and its risk factors over time, and familial patterns of CVD and risk factors. Other important objectives include the estimation of incidence rates of disease and description of the natural history of cardiovascular disease, including the sequence of clinical signs and systems that precede the clinically recognizable syndrome and the consequences and course of clinically manifest disease. Background Original cohort: The original cohort of the Framingham Study began in 1948 under the U.S. Public Health Service and was transferred under the direct operations of the new National Heart Institute, NIH, in 1949. Participants were sampled from Framingham, Massachusetts, including both men and women. This was the first prospective study of cardiovascular disease and identified the concept of risk factors and their joint effects. Offspring/Omni1 cohort: With the aging of the Framingham cohort and with interest in familiar aggregation and heritability, a new cohort consisting of the offspring of the original cohort was sampled. Spouses of offspring were also included. This new sample, began enrollment in 1971 and constituted a second generation of participants, permitting new assessment of risk factors and outcomes, and provided a resource for the genetic analyses which were yet to come. The Offspring participants have had repeated examinations, though at typically longer intervals than the original cohort. Third Generation/Omni2/New Offspring Cohort: Thirty-one years after enrollment began for the second generation of the Framingham Heart Study (Framingham Offspring Study), Framingham investigators began enrolling adults with at least one parent enrolled in the Offspring study into the Framingham Generation 3 cohort. The addition of the third generation was expected to facilitate investigation of secular trends in risk factors and indicators of health and disease within families, to enhance statistical power to detect genetic and environmental determinants of complex diseases, and to clarify how subclinical cardiovascular disease predicts occurrence of overt clinical events. Participants Original cohort: At entry to the study in 1948-1952, the study recruited 5,209 men and women, ages 28-62 years, living in Framingham, MA. Offspring/Omni1 cohort: 5,124 men and women, ages 5-70 years at entry consisting of offspring of the original Framingham cohort (and spouses of the offspring). In 1994, the Omni Cohort 1 enrolled 507 men and women of African-American, Hispanic, Asian, Indian, Pacific Islander and Native American origins, who at the time of enrollment were residents of Framingham and the surrounding towns. Third Generation/Omni2/New Offspring Cohort: 4095 men and women, almost all who self reported their ethnicity as white, ages 19+ years at entry, with at least one parent in the Framingham Offspring study, participated in the Gen III cohort. The New Offspring Cohort enrolled spouses of Offspring participants that were not otherwise enrolled and had at least two biological children participating in Gen III. 103 New Offspring Spouses (47 men and 56 women) participated. The OMNI 2 cohort enrolled additional ethnically diverse participants, including many individuals related to the participants of Omni Cohort 1 and also individuals unrelated to Omni Cohort 1 members for a total of 410 new participants. Design The cardiovascular disease conditions under investigation include coronary heart disease (angina pectoris, myocardial infarction, coronary insufficiency and sudden and non-sudden death), stroke, hypertension, peripheral arterial disease and congestive heart failure. Original cohort: The Framingham Study is a longitudinal investigation of constitutional and environmental factors influencing the development of CVD in men and women. Examination of participants has taken place every two years and the cohort has been followed for morbidity and mortality over that time period. Offspring/Omni1 cohort: By 1975, a sample of 5,124 men and women, consisting of offspring of the original Framingham cohort (and spouses of the offspring) had participated in the study. Additional studies of these subjects have continued under research contracts. Third Generation/Omni2/New Offspring Cohort: The children of Offspring Cohort participants were initially identified who would be 20 years of age or older by the end of the enrollment period. A higher priority for recruitment was assigned to individuals who belonged to large extended families, in order to complement phenotypic and genotypic information already obtained from prior generations. The baseline examination was begun in 2002 and completed in 2005.

  Study phs003594

• ATAC-seq data from primary AML samples with t(3;8)

  Open chromatin regions in the MYC super-enhancer region were investigated by ATAC-seq in t(3;8) AML. ATAC-seq was performed as described (Buenrostro et al, 2013) with a modification in the lysis buffer (0.30 M sucrose, 10 mM Tris pH 7.5, 60 mM KCl, 15 mM NaCl, 5 mM MgCl2, 0.1 mM EGTA, 0.1% NP40, 0.15 mM Spermine, 0.5 mM Spermidine, 2 mM 6AA) to reduce mitochondrial DNA contamination.

  Dataset EGAD00001007910

• Genome_Diversity_in_Africa_Project___GemCode_libraries_

  High depth whole genome sequencing from GemCode (10x Genomics) DNA libraries containing long range linkage information for one Baganda trio and one Baganda child (parent already sequenced at high depth). This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/

  Study EGAS00001001828

• Time Lapse to Cancer-Defining the Transition from Polyp to Cancer

  In the US, CRC incidence has declined with uptake in colonoscopy for early detection and removal of polyps, the precursor lesion, can stop a cancer from developing but in spite of this, CRC remains the second leading cause of cancer death in the United States. One third of people who undergo screening colonoscopy will have adenomatous polyps, but less than 5% of the time are these polyps presumed to go on to develop into cancer. Why does one polyp develop into cancer while another one that looks very similar does not. In this proposal we will identify what molecular genetic changes in the genome, in the mRNA expression and genetic methylation patterns will distinguish a polyp that has already transformed into cancer from one that has not.

  Study phs001384

• NextGen Consortium: GENESiPS Study: Identifying the Gene Networks of Insulin Resistance

  Variability in induced pluripotent stem cell (iPSC) lines remains a roadblock for disease modeling and regenerative medicine. Through linear mixed models we have described different sources of gene expression variability from RNA sequencing data in 317 human iPSC lines from 101 individuals. We found that ~50% of genome-wide expression variability is explained by variation across individuals and identified a set of expression quantitative trait loci that contribute to this variation. These analyses coupled with allele specific expression show that iPSCs retain a subject-specific gene expression pattern. Pathway enrichment and key driver analyses, based on predictive causal gene networks, found that Polycomb targets explain a significant part of the non-genetic variability present in iPSCs within and across individuals. These publically available iPSC lines and genetic datasets will be a resource to the scientific community and will open new avenues to reduce variability in iPSCs and improve their utility in disease modeling. SNP array data from individuals included in RNA-seq transcriptome profiling study of human induced pluripotent stem cells to characterize gene expression variation across individuals and within multiple iPSC lines from the same individual. Genotyping was performed on patient blood. Data availability: SNP-genotyping: dbGaP - current study RNA-seq counts: GEO - GSE79636 FASTQ files: SRA - SRP072417

  Study phs001139

• WHOLE GENOME SEQUENCING OF CLEAR CELL RENAL CELL CARCINOMA IN VHL PATIENT

  This submission contains Whole Genome Sequencing data of six ccRCCs, four cysts and one blood DNA sample of a VHL patient.

  Study EGAS50000000295

• A first-in-human clinical study of an allogenic iPSC-derived corneal endothelial cell substitute transplantation for bullous keratopathy

  iPSC-derived corneal endothelial cell substitutes recover pathological corneal edema. No adverse reactions are observed after one year follow-up. Gene mutations may appear despite whole genome sequencing of the master cell bank. This study contains WGS data.

  Study EGAS50000000672

• Multi-Omic Investigation of Beckwith-Wiedemann Syndrome Wilms Tumor

  Wilms’ Tumor (WT), also known as nephroblastoma, is one of the most common malignant kidney tumors diagnosed in children. One of the most common WT predisposition syndromes is Beckwith-Wiedemann Syndrome (BWS, OMIM: 130650), which affects approximately 1/10,000 live births. In this study, we perform Whole Exome Sequencing (WES), DNA methylation array, and messenger RNA-Sequencing (mRNA-Seq), to examine the genomic, methylomic, and transcriptomic signature of BWS WT. We analyzed six tumor-normal paired samples, three BWS tumor only samples, and four non-BWS control samples to identify BWS WT drivers.

  Study phs002769

• DAC for study CMMRD–associated high-grade glioma

  This Data Access Committee (DAC) is responsible for de-identified, summarized somatic variant call data derived from paired tumor–blood Whole-exome sequencing of human samples in a glioma research study. Access requests are approved without additional restrictions and are granted solely for health-related research purposes.

  Dac EGAC50000000855

• Adaptive Therapy Exploits Fitness Deficits in Chemotherapy-Resistant Ovarian Cancer to Achieve Long-Term Tumor Control Open Access

  Drug resistance results in poor outcomes for cancer patients. Adaptive therapy is a potential strategy to address drug resistance that exploits competitive interactions between sensitive and resistant subclones. Here, we showed that adapting carboplatin dose according to tumor response (adaptive therapy) significantly prolonged survival of murine ovarian cancer models compared to standard carboplatin dosing, without increasing mean daily drug dose or toxicity. Platinum resistant ovarian cancer cells exhibited diminished fitness when drug was absent in vitro and in vivo, which caused selective decline of resistant populations due to reduced proliferation and increased apoptosis. Conversely fitter, sensitive cells re-grew when drug was withdrawn. Using a bioinformatics pipeline that exploits copy number changes to quantify the emergence of treatment resistance, analysis of cell‐free DNA obtained longitudinally from ovarian cancer patients during treatment showed subclonal selection through therapy, and measurements of resistant population growth correlated strongly with disease burden. These preclinical findings pave the way for future clinical testing of personalized adaptive therapy regimens tailored to the evolution of carboplatin resistance in individual ovarian cancer patients.

  Study EGAS50000001142

• Intrapatient tumor heterogeneity and clonal evolution in metastatic salivary gland cancer: an autopsy study: access to data

  Funded by the Radboud Oncology Fund and the Dr. C.J. Vaillant Fund, the Salivary Gland Cancer Autopsy research group (Research Group) has sequenced DNA of 17 salivary gland cancer samples of and three healthy control samples from three patients with salivary gland cancer. This research project is led by Carla M.L. van Herpen from Radboud University Medical Centre in Nijmegen, the Netherlands (“Radboudumc”). The DNA sequencing data have been used for an analysis of intrapatient tumor heterogeneity and clonal evolution of metastatic salivary gland cancer. The Research Group is willing to consider applications from third party researchers for access to the DNA sequence data. Access to the data will be granted to qualified researchers for approved use. Access to DNA Sequencing Data is available by application to the Data Access Committee (DAC). Researchers granted access to DNA Sequencing Data must feedback the results of their research to the Research Group, after publication in accordance with the Research Group publication policy set forth in the Data Access Agreement.

  Dac EGAC50000000792

• Submitter Portal

  Submitter Portal The Submitter Portal does not support array submissions! Please refer to the array documentationAny new objects registered in the Submitter Portal will not be available for use in an array submission For further information please check our Submission FAQs, submission quickguide as well as submission terms! The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. Submitter Portal Index Previous steps Access to Submitter Portal Start a Submission Take The Tour Tutorial Previous steps Create your EGA account To submit data, you first need to create your EGA user. Then, once your account has been verified by the Help Desk team, you will be able to request a submitter role and send the EGA Data Processing Agreement (DPA). In the case you already have an EGA account, or an ega-box (submission account), you can skip this step. Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role and added your public key to your profile, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find relevant information in the DAC Portal Guide. Access to Submitter Portal 1. Request Submitter Role Once you have created your EGA user, request a Submitter Role and complete relevant information such as submission type and size. 2. Signature of the Data Processing Agreement The Data Processing Agreement (DPA) signed by CRG and EMBL-EBI (Joint Data Processors for the EGA) can be downloaded to the submitter for its signature. Further information related to the DPA can be in the Privacy Notice section. The DPA should be signed by a legal representative of the submitter with power of attorney/appointment duly authorised to sign contracts on behalf of the institution. The submitter will return a fully-executed copy of the DPA to us. Please note that due to the high volume of submissions to EGA the DPA is non-negotiable. Once you have completed all the information and attached the DPA signed, send your Submitter request and the EGA Helpdesk Team will validate it and send a confirmation to start submitting your metadata. Start a Submission The steps below will show you how to start a submission and are accompanied with a tutorial and the Take the tour of Submitter Portal. 1. Login Go to the Submitter Portal interface and log in using your EGA account credentials. 2. Create a submission The Submitter Portal interface will show you any already existing open submission. To start a new submission click on “Create a Submission”.In this phase you have the option to add any collaborator(s) as well as their permissions (“Read only” or “Read & Write”). If you want to invite all the collaborators from a previous submission, you can add them by selecting said submission.In the event that the submission has been closed, you will need to reopen it. To do this, you will need to modify one of the objects in the submission, for example, copy and paste the title. Once the submission is open, you can add a collaborator. Further information can be found in the Submission Tour 3. Create Study Click on add Study and complete the form with the relevant information. The fields with an asterisk (*) are mandatory. Further information can be found in the Submission Tour4. Create Sample Sample registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with information about the sequencing samples. Upload the samples.csv and the sample will be created.Add single sample: complete the mandatory fields with the metadata information of your sample.  Further information can be found in the Submission Tour5. Create Experiment Register an experiment with ​information about the sequencing methods, protocols and machines. Experiments generate the connection between samples and study. Further information can be found in the Submission Tour6. Create Run Samples, experiments and files are linked through runs. To register a run, you will be asked to select the appropriate experiment and the file format. Run registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with the sample - file linkage. Upload the run.csv and the runs will register.As the INBOX is a directory, bear in mind to include the file path (/). Example: /filename.c4gh. Add single run: select the file format, sample and experiment from the drop box. For re-using submitted samples, please use the EGA accession ID (EGANXXX). Please note that files must be uploaded in your inbox before linking your files and samples. Further information can be found in the Submission Tour7. Create Analysis Analysis should be only used for BAM/BAI or CRAM/CRAI pair, VCF and phenotype linkage to samples. The analysis is an EGA specific metadata object that links samples to files. This object also stores some metadata about your experiments, such as the experiment type, genome reference, or the platform used. **If only BAM or CRAM alignment files are submitted but not the original unaligned FASTQ files, then please make sure that the BAM or CRAM files also contain the unaligned reads. This is critical to enable primary re-analysis and re-alignment of the dataset using new tools or future genome assemblies.** Start by selecting the samples to be linked to the file, and then populate the required attribute fields. Please be aware of the existence of mandatory fields that must be populated.When populating the chromosome field (mandatory), please select the chromosomes from the checkbox. Please take in consideration that EGA allows for the re-use of any registered metadata. Therefore, a previously registered study or samples can be referenced for the analysis in the current data submission.Further information can be found in the Submission Tour 8. Create Dataset Dataset contains the collection of runs/analysis data files subjected to controlled access by being associated with a Policy. Complete the mandatory fields such as title, description, type and policy. Please, take in consideration that DAC and Policy must be registered in advance in the DAC Portal. Similar to other metadata objects, you can re-use previous runs or analyses, using their EGA accessions IDs (runs - EGAR, analyses - EGAZ). Further information can be found in the Submission Tour 9. Finalise submission Once the files are ingested please delete them from your SFTP INBOX before finalising your submission. This will prevent the files from reappearing in your Submitter Portal Inbox. Once you have completed your submission, click on the Finalise button, and schedule an estimated release date. Afterwards, your submission will be sent to Helpdesk for approval. Please note that once the Helpdesk has approved your submission, you will receive the identifiers for your data. See the Frequently Asked Questions (FAQ) for more information. 10. Update closed submission If you want to append more file to a closed submission, you will need to re-open the submission where the dataset was registered. Find the Submission: go to the Submitter Portal Menu -> Datasets section and find the submission id (EGA0XXX).  Reopen the submission where the dataset is located: to reopen a submission, you must edit any object within the submission. For example, you can copy and paste the title. Take The Tour The Submitter Portal Take The Tour is a visual guidance of all the steps described previously about how to start a submission. Tutorial In this tutorial we will show you how to use the Submitter Portal to register your metadata. Please note the video focuses on the run-based submission (for raw files - fastq - and aligned data - BAM/CRAM) and analysis-based submission (for your BAM/BAI pairs, variation -VCF - and phenotype files).

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal

• NICHD Genomic and Proteomic Network for Preterm Birth Research (GPN)

  We performed genome-wide association studies (GWAS) to study the Spontaneous Preterm birth (SPTB). Maternal and neonatal DNA from 743 SPTB (20 to and less than 34 weeks), and 752 controls (39 to and less than 42 weeks) who fully consented for public research usage were collected from participants in several clinical centers in Alabama, Illinois, New York, North Carolina, Rhode Island, Texas, and Utah. Cases were 1:1-matched with controls according to race/ethnicity (White, Hispanics, African Americans, and Others), maternal age (<20, 20-29, 30-39, 40+), and parity (yes or no). To determine the case-control status for each participant, a Gestational Age (GA) was determined. DNA samples were taken from blood or saliva if blood was not available. Automated DNA extractions were performed on the Qiagen M48 robot, and samples were organized in 96-well plates with barcoding and sample tracking systems. Subsequent manipulations were performed on the Biomek FX liquid handling workstation with 96-channel pipetting. DNA quantitation was performed by dye-based assay on a Molecular Devices SpectraMax Plus plate reader. Samples were genotyped using Affymetrix Genome-Wide Human SNP Array 6.0. This work was conducted at the Microarray Facility at the University of Pennsylvania. Patient data were collected through chart reviews and patient interviews, which included Demographic information (parental age, race, ethnicity, etc.); Medical history (pre-pregnancy weight, height, medications, STD history, medical conditions, etc.); Social history (marital status, years of education, alcohol use and tobacco use); Obstetrical history including outcome of all prior pregnancies and dates of termination; History of preterm labor or premature rupture of membranes symptoms, evaluation or hospitalization for those symptoms in current pregnancy; Medications taken during current pregnancy; History of cervical evaluation (manually or ultrasonographically) or fetal fibronectin measurements; Pregnancy complications; Labor (type, indications, membrane status, and induction method); Delivery type and indications for cesarean section; Neonatal outcome (sex, weight, length, Apgar score, neonatal complications, admission to intensive care unit, etc.); and Maternal family history of SPTB.

  Study phs000714

• Chicago Infant Mortality Study

  The Chicago Infant Mortality Study (CIMS) was a population-based, prospective, case-control study conducted in metropolitan Chicago, Cook County, Illinois, to examine the risk factors for sudden infant death syndrome (SIDS) among a primarily Black population. Eligible case infants were aged birth to one year where the cause of death was determined to be SIDS while eligible control infants were aged one month to one year who died of other sudden unexpected infant death (SUID) causes. Recruitment occurred between November 1993 and April 1996. The goal of this ancillary multiomics study was to evaluate possible genetic and epigenetic determinates of SIDS and together with metabolomic profiles, identify novel clinical diagnostic tools to enable molecular autopsies and biomarkers to proactively identify and intervene in infants at greater risk of death from SIDS. The multiomics data was generated from medical examiner autopsy specimens and includes: whole exome sequencing genotypes; RNA-seq transcriptome and methylome profiles from autopsy heart tissue; and serum metabolomics profiles. The sample size available varies with the modality of the omics assay, but the total number of unique infants included is about 400.

  Study phs003790

• INCLUDE Data Hub: NDA GUIDs for Down Syndrome Research

  The INCLUDE (INvestigation of Co-occurring conditions across the Lifespan to Understand Down syndromE) Project is an NIH-wide collaboration that seeks to improve health and quality of life for people with Down syndrome. The INCLUDE Project Data Coordinating Center (DCC) and partners created the INCLUDE Data Hub, a centralized data resource that allows access to large-scale clinical and multi-omics datasets specific to Down syndrome and supports collaborative, cloud-based analysis to accelerate scientific discoveries related to Down syndrome and its co-occurring conditions. The INCLUDE Data Hub includes an innovative researcher data repository, a portal, and a cloud-based platform for data analysis. The portal provides access to de-identified demographics and clinical metadata, as well as multi-omics datasets, including whole genome sequences, transcriptomes, proteomes, and metabolomes. The INCLUDE Data Hub uses a 'registered access' model, whereby users can access the portal and associated data after agreeing to terms of use. From the Data Hub, users can also reach 'controlled access' data (e.g., whole genome sequences) only for those studies for which they have obtained approval by an NIH Data Access Committee through the corresponding dbGaP study. A thoughtful linkage strategy to identify duplicate participants across studies enables researchers to merge multiple datasets and data types to create richer datasets and reduce costly redundancies in large-scale data generation (e.g., -omics) while mitigating potential risks introduced by linkage.Based on recommendations from the NICHD Office of Data Science and Sharing, which completed a comprehensive assessment of existing Privacy Protecting Record Linkage (PPRL) and associated data governance solutions, the INCLUDE DCC and the associated NIH Steering Committee have implemented NIMH Data Archive Global Unique Identifiers (NDA GUIDs) in the INCLUDE Data Hub. The NDA GUID Tool is a government-owned and operated PPRL technology that enables researchers to link data from multiple sources to the same individual without revealing personally identifiable information (PII). With the NDA GUID Tool, the same participant information will return the same GUID whenever or wherever it is entered. The GUID itself is not personally identifiable information or protected health information. Sharing data with NDA GUIDs allows approved researchers to link together data on a single participant, even if the data were collected at different locations or through different studies or are distributed from different data repositories. This dbGaP study enables researchers to access an INCLUDE GUID Mapping File that includes all available NDA GUIDs and their associations to study-specific Participant IDs across studies in the INCLUDE Data Hub. This dbGaP study only distributes NDA GUIDs associated with the INCLUDE Data Hub datasets. To access the associated controlled-access datasets, add the corresponding dbGaP studies to your Data Access Request. A list of these studies is available on the INCLUDE Data Hub Portal: https://portal.includedcc.org/studies.

  Study phs003678

• PyEGA3 download client

  PyEGA3 Checks prior to download - Is the dataset available for download? Most datasets are available using the PyEGA3 Download client, except for specific legacy datasets. For these ones, refer to Live Outbox distribution, an alternative way to download these datasets.If the dataset you've been granted access to begins with the ID EGAD5XXXXXXX, please refer to the Live Outbox distribution. If the dataset you have been granted access to contains encrypted data (filename ending in .gpg), contact EGA Helpdesk for detailed information on how to download these files.General Information The PyEGA3 download client is available at its GitHub repository. In its README you will find a step by step guide on how to use it to download files you have been granted access to. PyEGA3 implements the GA4GH-compliant HTSGET protocol supporting requests over genomic ranges. This enables the download of specific regions of interest rather than the entire file. HTSGET is not possible for all the files held by EGA: if the dataset does not contain index files (e.g. filename ending in *.crai), then genomic range requests cannot be performed. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Check out our video tutorial! Frequently Asked Questions General questions How do I download the datasets to which I have been granted access? After setting up your EGA download account, you can proceed to download using the EGA download client – PyEGA3. The pyEGA3 download client is a python-based tool for viewing and downloading files from authorised EGA datasets. This download client is continuously being developed for more user-friendly download experiences. Can I download the dataset’s metadata via the download client? No, the download client cannot be used to download metadata. Registered EGA users can download metadata of an authorised dataset by logging into the EGA webpage and navigating to the dataset of choice. Approximately two thirds down the page you will find the option to download the metadata as a zip file. How do I download large datasets as quickly as possible? The main EGA download client is pyEGA3 download client, a python-based tool for viewing and downloading files from authorised EGA datasets.We could exceptionally consider the option of an Aspera download for users experiencing very slow download rates or facing particular issues.Contact the EGA Helpdesk for further information. Pre-requirement and Installation What are the major requirements for the PyEGA3 download client installation and usage? The PyEGA3 client is compatible with any OS with Python 3.6+ installed. The client requires a connection to the internet, sufficient space on the destination drive, and the EGA download account credentials. Where can I find the PyEGA3 download client installation and download instructions? We strongly recommend checking our video tutorial demonstrating the usage of PyEGA3 from installation to file download. More detailed information is available at PyEGA3 GitHub. What ports are required for the PyEGA3 download client to function? PyEGA3 makes HTTPS calls to the EGA Data API (https://ega.ebi.ac.uk:8443). This port 8443 must be reachable from the location where PyEGA3 is executed to avoid timeouts. PyEGA3 download client How to update the PyEGA3 download client to be on the latest version? Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 --upgrade I do not have an active EGA account. Can I test the download with the PyEGA3 download client? An EGA download test account (ega-test-data@ebi.ac.uk) has been created for troubleshooting and training purposes. The test account does not require an EGA username and password because it contains publicly accessible files from the 1000 Genomes Project. More information about the use of this account and log in details are available at pyEGA3. I lost my connection while the download was in progress. Does this mean that I have to download the file again from the start? The PyEGA3 download client supports automatic resumption of downloads. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the resume feature, downloads will automatically resume if you encounter any errors or if the connection is interrupted. How can I improve the overall download speed of the PyEGA3 download client? Download speeds can be optimised using the --connections parameter which will parallelise download at the file level. If the --connections parameter is provided, all files >100Mb will be downloaded using the specified number of parallel connections. It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Why is my file taking a long time to be saved? Please note that when a file is being saved, it goes through two processes. First, the downloaded file "chunks" are pieced back together to reconstruct the original file. Secondly, PyEGA3 calculates the checksum of the file to confirm that the file was downloaded successfully. Larger files will take more time to reconstruct and validate the checksum. Why is the HTSGET protocol not working with my dataset of interest? PyEGA3 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file, saving both time and storage space. Please note that in order for the genomic range requests to work for a BAM, CRAM or VCF file there must be an associated BAI, CRAI or TBI file, respectively. If the dataset does not contain these index files then genomic range requests cannot be performed. After download Do I need to decrypt data files downloaded through the pyEGA3 download client? Files are transferred over secure HTTPS connections and received unencrypted, thus there is no need for decryption after data download. What is the purpose of an MD5 file? After the download completes, file integrity is verified using checksums. The PyEGA3 download client automatically verifies each file’s unencrypted md5 after download to ensure that the file was downloaded correctly from the EGA. Errors Why do I get a “400 Client Error” while trying to access the download client? Ensure that your credentials are formatted correctly. Please contact the EGA Helpdesk if you are unsure about your account’s username (i.e. your email address). Why do I get a “500 Server Error”? It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Otherwise, 500 server errors are internal server errors from EGA’s end. Retry after some time and, if the 500 error persists: check our homepage or Twitter for any outage information or report it to EGA Helpdesk. Why do I get a “slice error”? This type of error occurs when one slice download was prematurely interrupted. Please re-start the same download. The download client will pick up any partial download and download any missing slices. Why do I get the error “Dataset' EGADXXXXXXXXXXX' is not in the list of your authorised datasets”? Please note that the data access was given to the email (username) provided to the Data Access Committee (DAC) in your official request. Therefore, you shall check that the account that you are using is the same one that you sent to the DAC. Why do I get “ERROR:root:Failed to obtain IP address”? This might mean that the connection ports are blocked. Check that the port 8443 is reachable.In case the port is reachable and the error persists, please try to modify the file pyega3.py on line 44 in the python module installation: Replace endpoint = 'https://ipinfo.io/json' with endpoint = 'https://api.myip.com' Why do I get the error “Invalid username, password or secret key - please check and retry”? Make sure that you are using the correct credentials (username and password) and there is no typo. Contact EGA Helpdesk if the problem persists.

  Documentation access/download/files/pyega3

• Drug screening of patient-derived organoids from colorectal peritoneal metastases

  Colorectal cancer (CRC) patients with peritoneal metastases (CRPM) have limited treatment options and the lowest CRC survival rates. We trialed the possibility of organoid directed precision treatment for CRPM patients. CRPM organoids (peritonoids) isolated from patients underwent next-generation sequencing and medium-throughput drug panel testing ex vivo to identify specific drug sensitivities for each patient. We measured the utility of such a service including: success of peritonoid generation, time to cultivate peritonoids, reproducibility of the medium-throughput drug testing, and documented changes to clinical therapy as a result of the testing. Peritonoids were successfully generated and validated from 68% (19/28) of patients undergoing standard care. Genomic and drug profiling was completed within 8 weeks and a formal report ranking drug sensitivities was provided to the medical oncology team upon failure of standard care treatment. This resulted in a treatment change for 2 patients, one of whom had a partial response despite previously progressing on multiple rounds of standard care chemotherapy. The barrier to implementing this technology in Australia is the need for drug access and funding for off-label indications. In conclusion, our approach is feasible, reproducible and can guide novel therapeutic choices in this poor prognosis cohort, where new treatment options are urgently needed. This platform is relevant to many solid organ malignancies.

  Study phs002023

• The DNA methylation landscape of glioblastoma disease progression shows extensive heterogeneity in time and space

  Glioblastoma is characterized by widespread genetic and transcriptional heterogeneity, yet little is known about the role of the epigenome in glioblastoma disease progression. Here, we present genome-scale maps of DNA methylation in matched primary and recurring glioblastoma tumors, using data from a highly annotated clinical cohort that was selected through a national patient registry. We demonstrate the feasibility of DNA methylation mapping in a large set of routinely collected FFPE samples, and we validate bisulfite sequencing as a multipurpose assay that allowed us to infer a range of different genetic, epigenetic, and transcriptional characteristics of the profiled tumor samples. On the basis of these data, we identified subtle differences between primary and recurring tumors, links between DNA methylation and the tumor microenvironment, and an association of epigenetic tumor heterogeneity with patient survival. In summary, this study establishes an open resource for dissecting DNA methylation heterogeneity in a genetically diverse and heterogeneous cancer, and it demonstrates the feasibility of integrating epigenomics, radiology, and digital pathology for a national cohort, thereby leveraging existing samples and data collected as part of routine clinical practice.

  Study EGAS00001002538

• Full blood mRNA sequencing of myotonic dystrophy type 1 patients after cognitive behavioural therapy

  Myotonic dystrophy type 1 (DM1) is an incurable multisystem disease caused by a CTG-repeat expansion in the DM1 protein kinase (DMPK) gene. The OPTIMISTIC clinical trial demonstrated positive and heterogenous effects of cognitive behavioral therapy (CBT) on the capacity for activity and social participations in DM1 patients. Here, we performed mRNA sequencing of full blood for 27 patients of the OPTIMISTIC cohort before and after the CBT intervention. We identified 608 genes for which their expression was significantly associated with the disease causing CTG-repeat expansion, as well as with 1176 genes significantly associated with the average clinical response towards the intervention. Remarkably, all 97 genes significantly associated with both returned to more normal levels in patients who benefited most from CBT. This trend was consistent with the difference observed between DM1 patients and controls in an earlier study of blood mRNA expression levels, singling these genes out as candidate biomarkers for therapy response. Together these results highlight the ability to find disease relevant information in full blood of DM1 patients and open new avenues to monitor therapy effects.

  Study EGAS00001005830

• PRPH2-Related Retinal Dystrophies: Mutational Spectrum in 103 Families from a Spanish Cohort

  Various NGS experiments from patients affected by genomic variants at gene PRPH2, one of the most frequently inherited retinal dystrophy (IRD)-causing genes.

  Study EGAS50000000847

• SNP array data for 140 individuals from 5 populations in Pakistan

  We have genotyped 140 individuals from 5 populations in Pakistan, using the OmniExpressExome-8 array, which includes approximately one million autosomal SNP markers.

  Study EGAS00001002965

• Profiling RNA Translation in Pediatric Medulloblastoma

  This study provides RNA-sequencing and ribosome profiling data for patient-derived cell lines and patient tissue samples for children with medulloblastoma. Ribosome profiling is a variant protocol of RNA-sequencing that directly sequences ribosome-bound RNA fragments only. Associated RNA-seq and Ribo-seq data obtained separately for some cancer cell lines can be found on the NCBI SRA as PRJNA957428. Samples were processed for poly-A mRNA sequencing using the Roche Kapa Kit. Ribosome profiling was performed as described in the manuscript referenced below (Hofman et al.) and based on the article by McGlincy et al., Methods (2017). Ribo-seq data were analyzed for sample quality using RiboseQC (Calviello, Nat Struct Mol Biol, 2020). These data were used to quantify P-sites of open reading frames. RNAseq and ribo-seq data were integrated and compared to determine translational efficiency values using TPM (Ribo-seq) over TPM (RNA-seq) as the metric. Ribo-seq data on 14 samples and RNAseq data on 21 samples derived from 16 fresh-frozen surgical samples for medulloblastoma and 5 autopsy samples are available through dbGaP. A second cohort of 4 medulloblastoma samples (RNAseq, Ribo-seq) related to this study can be found on the EGA at EGAS00001007426.

  Study phs003446

• A first-in-human clinical study of an allogenic iPSC-derived corneal endothelial cell substitute transplantation for bullous keratopathy

  iPSC-derived corneal endothelial cell substitutes recover pathological corneal edema. No adverse reactions are observed after one year follow-up. Gene mutations may appear despite whole genome sequencing of the master cell bank. This study contains the RNA-seq data.

  Study EGAS50000000673

• National Heart, Lung, and Blood Institute (NHLBI) Bench to Bassinet Program: The Pediatric Cardiac Genetics Consortium (PCGC) Study

  Multi-center, prospective observational cohort study of individuals with congenital heart defects (CHD). Phenotypic data and source DNA derived from 10,000 probands, parents, and families of interest are being collected to investigate relationships between genetic factors and phenotypic and clinical outcomes in patients with CHD. Phenotype data will be stored at dbGaP, while molecular and sequence data will be stored at BioData Catalyst. The PCGC Cohort is utilized in the following dbGaP substudies. Please click on the following substudies below or in the "Substudies" section of this top-level study page phs001194 PCGC Cohort. phs000571 PCGC: whole exome sequences, whole genome sequences, targeted sequences, MIP sequences, and SNP array data phs001843 PCGC-CMG Collaboration: whole genome sequences The Gabriella Miller Kids First Pediatric Research Program (Kids First) subset of the PCGC project (phs001194) is now accessible through a separate dbGaP study accession: phs001138. To access this dataset, please submit a Data Access Request (DAR) for phs001138. Approval of this DAR will be expedited for approved users of phs001194. To learn about other Kids First datasets visit https://kidsfirstdrc.org/.NHLBI's TOPMed program has provided additional Whole Genome Sequencing for PCGC participants - that data is accessible through a separate dbGaP sudy accession: phs001735. Access to this data set should be requested through a Data Access Request (DAR) for phs001735.

  Study phs001194

• 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

• Autosomal recessive

  To define a genetic syndrome of combined immunodeficiency, severe autoimmunity, and developmental delay, 4 patients from two families who had similar syndromic features were studied. To identify disease-causing mutations, we performed whole exome sequencing for one patient and her healthy parent from Family 1 and also for one patient from Family 2. Disease segregated with novel autosomal recessive mutations in a single gene, tripeptidyl-peptidase II (TPP2) gene. The result defines a new human metabolic immunodeficiency.

  Study phs000848

• Genetic Landscape of Esophageal Squamous Cell Carcinoma Defined by Exome Sequencing on Chinese Patient Cohort and Cell Lines

  Esophageal Squamous Cell Carcinoma (ESCC) is one of the deadliest cancers worldwide. To define the genetic landscape of ESCC, whole exome sequencing was performed on 113 pairs of tumor and normal DNA samples collected from Chinese individuals with treatment-naive primary ESCC, along with 8 cell lines, including 7 from KYSE series ESCC cell lines and one immortalized esophageal squamous epithelial cell line Het-1A.

  Study EGAS00001000932

• Whole_exome_sequencing_of_additional_thyroid_disease_cases

  Whole-exome sequencing of a cohort of families (probands and affected/unaffected relatives) suffering from one of two rare thyroid disorders: congenital hypothyroidism (CH) and resistance to thyroid hormone (RTH).

  Study EGAS00001001114

• 71 Whole-exome sequencing of Esophageal Squamous Cell Carcinoma on Chinese Patients

  Esophageal Squamous Cell Carcinoma (ESCC) is one of the deadliest cancers worldwide. We performed 71 Whole-exome sequencing of Esophageal Squamous Cell Carcinoma on Chinese Patients.

  Study EGAS00001001475

• Genetics of Hypertension Associated Treatment (GenHAT) Study, Genomic Background of Blood Pressure Response to Treatment in African Americans

  The GenHAT study is an ancillary pharmacogenomics study to the Antihypertensive and Lipid Lowering Treatment to Prevent Heart Attack Trial (ALLHAT). ALLHAT was a randomized, double-blind, multi-center trial that enrolled 42,418 participants &#8805;55 years of age with hypertension and at least one additional risk factor for cardiovascular disease (CVD). Participants were randomized to treatment with one of four primary antihypertensive drugs: chlorthalidone (thiazide-like diuretic), amlodipine (CCB), lisinopril (ACE-i), or doxazosin (alpha-adrenergic blocker) in a ratio of 1.7:1:1:1, respectively. Participants were followed for treatment response and CVD outcomes. The original GenHAT study (N=39,114) evaluated the association of candidate hypertensive genetic variants with CVD outcomes for participants consenting to genetic research. The current GWAS study focuses on a subset of African American GenHAT participants (n=6908).&nbsp;&nbsp;

  Study phs002716

• Indonesian Microbiome Ecology and Evolution v1 - Data Access Policy

  This Data Access Policy sets forth the terms, conditions, and limitations governing access to and use of the raw sequencing data of samples in the Indonesian Microbiome Ecology and Evolution (IndoMEE) v1 dataset by individuals who are not part of the Data Producer. The IndoMEE v1 dataset comprises 126 human faecal samples collected across Indonesia between 2015 and 2021, that was collected to study patterns of human microbiome variation across Indonesia’s diverse geography and lifestyles.

  Dac EGAC50000000587

• Integrative_Oncogenomics_of_multiple_myeloma

  We used targeted capture and massively parallel sequencing of exomes of CD138 purified plasma cells and matched somatic DNA from 17 patients with Multiple Myeloma. For each patient, an early tumor sample (at diagnosis) and a late one (at relapse) were available. For few of them, an additional late sample (2nd progression) was present. In total, the study has 52 samples. 1044 variants were validated by 454 sequencing. The present study will validate an additional 4630 variants by targeted pull-down and sequencing. All 52 samples will be indexed and then will be pre-pooled in groups of 5 or 6. The sequence capture will use 10 reactions. All samples will then be pooled and go thorugh one lane of HiSeq.

  Study EGAS00001000244

• Acute Respiratory Distress Network (ARDSNet) Study 02 Late Steroid Rescue Study (LaSRS) (ARDSNet-LaSRS-BioLINCC)

  Data Access NOTE: Please refer to the &#8220;Authorized Access&#8221; section below for information about how access to the data from this accession differs from many other dbGaP accessions. Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from ARDSNet-LaSRS include BAL Slides, Bronchial Lavage, and Plasma. Please note that use of biospecimens in genetic research is subject to a tiered consent.Objectives: Since previous reports suggested that corticosteroids may improve survival, this project was developed as a multicenter, randomized controlled trial of corticosteroids in patients with persistent ARDS.Background: Persistent acute respiratory distress syndrome (ARDS) is characterized by excessive fibroproliferation, ongoing inflammation, prolonged mechanical ventilation, and a substantial risk of death.Participants: There were 180 participants.Conclusions: The results do not support the routine use of methylprednisolone for persistent ARDS despite the improvement in cardiopulmonary physiology. In addition, starting methylprednisolone therapy more than two weeks after the onset of ARDS may increase the risk of death. (NEJM April 20, 2006; Vol 354, No. 16, pp 1671-84).

  Study phs003769

• Genome-Wide Association Study of Amyotrophic Lateral Sclerosis in Finland

  The genetic etiology of amyotrophic lateral sclerosis (ALS) is not well understood. Finland has one of the highest incidence of ALS in the world, making it an ideal population for study. To identify genetic risk factors for this fatal neurodegenerative disease, we undertook a genome-wide association study of 405 Finnish patients diagnosed with ALS and 497 Finnish controls. Two loci that exceeded the Bonferroni threshold for genome-wide significance were identified. One was located on chromosome 21q22, corresponding to the known autosomal recessive D90A allele of the SOD1 gene. The other was detected on the short arm of chromosome 9, which had been previously identified in linkage studies of families with ALS. Together, these two loci account for most of the increased incidence of ALS observed in this population.

  Study phs000344

• Rheumatoid Arthritis Finger Stick RNA Sequence Data

  This is a longitudinal study of 355 blood samples collected weekly from 5 patients with Rheumatoid Arthritis with varying disease activity over the course of one to five years. Blood samples were self collected from finger sticks and mailed from home. RNA was extracted, purified and sequenced.

  Study phs003179