11865 results for "coin buying fc 26 Visit Buyfc26coins.com for latest FC 26 coins news..2Dtf"

in 27.05 milliseconds.

• RNA-Seq data for the paper titled "Orthotopic Patient-Derived Xenografts of Pediatric Solid Tumors"

  RNA-Seq data for the paper titled "Orthotopic Patient-Derived Xenografts of Pediatric Solid Tumors"

  Dataset EGAD00001003433

• Sputum fungal microbiota in an overall healthy population in Guangdong province, China

  This repository contains raw sequencing data for sputum fungal microbiota in an overall healthy population in Guangdong province, China. The aim of the study is to provide a comprehensive insight on the multi-kingdom airway microbiome, how it may underlie the interplay between exposure and healthy outcomes, and whether it can be employed to inform airway health and diseases.

  Study EGAS00001006720

• RNA-sequencing of ex vivo exhausted human antigen-specific T cells

  Tumor-specific T cells are frequently exhausted by chronic antigenic stimulation. To explore new pathways for reinvigoration of anti-tumor immune functions, we developed a human ex vivo exhaustion model by repetitive antigenic stimulation of primary CD8 T cells. This results in T cells that resemble patient-derived T cells in tumors on a phenotypic and transcriptional level.

  Study EGAS00001006794

• Single cell RNA sequencing of bone marrow mononuclear cells

  Bone marrow aspirates were obtained from patients with relapsed/refractory large B cell lymphoma (rrLBCL), mononuclear cells isolated by ficoll density-gradient centrifugation, and loaded onto a 10X Chromium for single cell RNA-sequencing using 5’ chemistry without prior cryopreservation. Healthy donor bone marrow mononuclear cells were obtained from healthy allogeneic stem cell transplant donors and analyzed following viable cryopreservation.

  Study EGAS00001006836

• Pre-neoplastic somatic mutations including MYD88L265P in lymphoplasmacytic lymphoma

  Normal-cell counterparts of solid and myeloid tumors accumulate mutations years before disease onset; whether this occurs in B-lymphocytes prior to lymphoma remains uncertain. In this study, we sequenced multiple stages of the B-lineage in elderly individuals and patients with lymphoplasmacytic lymphoma, a singular disease for studying lymphomagenesis because of high-prevalence of mutated MYD88.

  Study EGAS00001005656

• Molecular profiling of MBD4-deficient acute myeloid leukaemia

  We describe two cases of MBD4-deficient acute myeloid leukaemia (AML). Clinical samples were used for molecular analysis, including genomic profiling (genome and exomes), methylation analysis (RRBS) and transcriptional profiling (RNA-sequencing). An analysis and methodological description has been published: “MBD4 guards against methylation damage and germline deficiency predisposes to clonal hematopoiesis and early-onset AML” [PMID: 30049810]

  Study EGAS00001002581

• RNA-seq following TBL1XR1 KD in human CD34+CD38- cord blood cells

  We performed RNA-seq on CD34+CD38- human cord blood (CB) cells transduced with sh_Control or sh_TBL1XR1 lentiviruses to identify differentially expressed genes. Sorted CD34+CD38- cells from 3 independent cord blood pools were transduced with lentiviruses containing BFP reporter gene. BFP+ cells were sorted 3 days post-transduction and RNA was harvested for library preparation and sequencing.

  Study EGAS00001005869

• Investigating_the_impact_of_MBD4_on_the_mutability_of_the_germline

  We will be testing the hypothesis that MBD4 PTV germline carriers also show an increased number of C toT germline mutations in their offspring. 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 EGAS00001002861

• Chronic myelomonocytic leukemia

  Chronic myelomonocytic leukemia is an aggressive hematological malignancy with dismal outcomes, with the pCMML subtype in particular having median OS of <2 years and high rates of AML transformation (Patnaik et al., 2014). Given limited therapeutic options for affected patients, we carried out this study to define the genetic and epigenetic landscape of pCMML and identify therapies that could modify disease biology.

  Study EGAS00001005107

• Whole Exome Sequencing of High grade T1 non-muscle invasive bladder cancer

  High-grade T1 (HGT1) bladder cancer (BC) is the highest risk subtype of non-muscle-invasive BC with unpredictable outcome and poorly understood risk factors. Here we performed whole exome sequencing across 61 HGT1 samples to identify genomic predictors of good outcome, recurrence or progression. This study includes somatic mutation calls and clinical data for 61 HGT1 tumors.

  Study EGAS00001004603

• RNA-sequençing of 21 inflammatory hepatocellular adenomas

  The French ICGC project on liver tumors is coordinated by Pr Jessica Zucman-Rossi and funded by Inca (French Institute for Cancer). The aim of the present project is to identify the catalog of somatic and germline mutations in liver tumors.The present series corresponds to 21 RNA-seq of IHCA samples. Aligned bam files correspond to hg38 human reference.

  Study EGAS00001003685

• CAR_T_cell_Study

  CAR-T cell Study The aim of this study is to understand single cell transcription and chromatin accessibility in CAR-T cells. 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 EGAS00001004718

• Transcriptome sequencing of myelodysplasia

  Transcriptome sequencing was performed on 214 patients with myelodysplasia in this study. RNA was obtained from bone marrow CD34+ cells (n=100) and/or bone marrow mononuclear cells (n=165). Transcriptome sequencing was performed for both cell fractions in 51 patients. We also studied bone marrow CD34+ cells and bone marrow mononuclear cells obtained from three healthy adults each.

  Study EGAS00001002346

• Transcriptomic analysis of TFEB overexpression in LT-HSC, ST-HSC and MEP

  Long-term hematopoietic stem cells (LT-HSC), Short-term hematopietic stem cells (ST-HSC) and Megakaryocyte-erythrocyte progenitors (MEP) were sorted from human cord blood and cultured overnight before transduction with lentivirus to overexpress GP91 (CTRL) or TFEB. Three (LT-HSC ans ST-HSC) or six (MEP) days later, BFP+ transduced cells were sorted for RNA extraction and sequencing.

  Study EGAS00001004969

• Targeted sequencing of paired tumour/blood of 78 Ta stage bladder cancer patients

  In continuation of our whole-exome and targeted sequencing study on non-muscle-invasive bladder cancer, we carried out this targeted paired tumour/blood sequencing study including 78 Ta stage bladder cancer patients. Agilent’s SureDesign tool was used to design a 1.133 Mb SureSelect custom capture for all coding exons of the 140 selected candidate genes.

  Study EGAS00001005766

• Multiple esclerosis and mixed microbial infections

  This Project deals with the sequencing of ITS1 region, which is highly variable both in length and in nucleotide sequence for different yeast using yeast-specific primers ITS1 and ITS2. A total of 19 samples involving different brain regions from patients with different conditions were analysed. Of these, 10 are controls-healthy patients and 9 multiple sclerosis (MS) patients.

  Study EGAS00001002957

• Next Generation Children project - WGS study of patients in NICU and PICU and their families

  With growing evidence that rare single gene disorders present in the neonatal period, there is a need for rapid, systematic, and comprehensive genomic diagnoses in ICUs to assist acute and long-term clinical decisions. This study aimed to identify genetic conditions in neonatal (NICU) and paediatric (PICU) intensive care populations. Whole genome sequencing data.

  Study EGAS00001003002

• FAM50A_Disruption_in_TOV21G_Cells___RNAseq

  In this project we aimed to assess the transcriptional consequences of disrupting FAM50A in TOV21G cells in vivo. To do this we generated a dox inducible FAM50A gRNA allele such that we could conditionally inactivate FAM50A by feeding mice a diet containing doxycycline. Tumour masses were harvested from mice when they reached the ethical limit and RNA was extracted for RNA-Seq analysis.

  Study EGAS00001004156

• Single_cell_resolution_of_human_CNV_body_map

  12 tissues from the warm autopsy are selected for this project. Using 10X Chromium technology we will generate ~1000 single cell/nulei genomic libraries per tissue. Each tissue will be whole genome sequenced (~2 lanes per 1000 cells) on hiseq X10. per single cell we will generate CNV profile and we investigate the level of genomic heterogenity with in tissue and across different tissues.

  Study EGAS00001003162

• Analysis of exonic somatic variants in light-chain amyloidosis (ALA) and ALA concomitant with multiple myeloma

  We aim to provide the very first insight into ALA+MM molecular profiles and compare the results with ALA and with MM. Our detailed study of ALA and ALA+MM represents an important step towards improved understanding of their genetic and transcriptomic background, which is a prerequisite for development of optimal treatment strategies in the future.

  Study EGAS00001004214

• Mutant_clone_mapping_in_oesohagus_restricted_bait

  We aim to assess the burden of mutant clones in normal human oesophagus from donors aged 65+. We will do this for a small number of genes which we know to be under positive dN/dS selection. This will allow us to assess the patient to patient variation in mutational burden as well as any changes in selection which may occur with age.

  Study EGAS00001005660

• Amplified EPOR/JAK2 genes define a unique subtype of acute erythroid leukemia

  Acute erythroid leukemia (AEL) is a unique subtype of acute myeloid leukemia characterized by prominent erythroid proliferation, whose molecular basis is poorly understood. To elucidate the underlying mechanism of erythroid proliferation, we performed comprehensive genomic study. The aim of this study is to unveil genotype phenotype correlations and the feasible molecular targets for therapy of AEL.

  Study EGAS00001005810

• whole-genome sequencing of gastric cancer

  Gastric cancer is one of the most common cancers. Genome-wide analysis of genomic signatures might reveal novel mechanisms for gastric cancer tumorigenesis. Here, we analyzed structural variations and mutational signatures via whole-genome sequencing of 168 gastric cancer samples. Our data demonstrates diverse models of complex structural variations operative in GC, which lead to high-level amplification of oncogenes.

  Study EGAS00001003512

• Finding structural variation and functional consequences from the primary leukemia cells (CLL) at the single-cell level

  In this study, we aimed to identify somatic structural variation of chronic lymphocytic leukemia (CLL) at the single-cell level and investigate its direct consequence on the nucleosome occupancy using scNOVA approach. For this purpose, we performed strand-specific single-cell sequencing of primary leukemia samples from 63-year-old female patient.

  Study EGAS00001004925

• Genomic and epigenomic study of Japanese renal cell carcinoma including WGS, RNA-seq, ATAC-seq, and methyl-seq

  We performed whole-genomic and transcriptomic sequencing of more than 100 Japanese renal cell carcinoma (RCC) cases, including clear cell RCC, papillary RCC, chromophobe RCC, and TFE3-translocated RCC. In addition, we conducted epigenome sequencing analyses: the assay for transposase-accessible chromatin sequencing (ATAC-seq) and enzymatic methyl sequencing.

  Study EGAS00001006919

• Sputum bacterial microbiota in an overall healthy population in Guangdong province, China

  This repository contains raw sequencing data for sputum fungal microbiota in an overall healthy population in Guangdong province, China. The aim of the study is to provide a comprehensive insight on the multi-kingdom airway microbiome, how it may underlie the interplay between exposure and healthy outcomes, and whether it can be employed to inform airway health and diseases.

  Study EGAS00001006721

• ALLoreactive T-Cell receptOr RePertoire in kidnEy tranSplantation

  A prospective study for investigating the T-cell receptor (TCR) repertoire in T-cell mediated rejection (TCMR) after kidney transplantation. The pre-formed donor-reactive TCR repertoire was tracked in blood and tissue of patients after kidney transplantation and characteristics of TCR repertoires from patients experiencing a rejection were compared to patients with no histopathological signs of rejection.

  Study EGAS00001005299

• cis-eQTL mapping of TB-T2D comorbidity in a five-way admixed SA cohort

  The aim of the study was to identify ancestry-specific genetic variants associated with differentially expressed genes in TB-T2D comorbid patients compared to T2D patients, as well as between TB patients and healthy controls. Both global and local ancestry was incorporated in regression models to account for the genetic heterogeneity in our complex multi-way admixed population.

  Study EGAS00001007059

• Three-dimensional patient-derived models of glioblastoma retain intra-tumoral heterogeneity

  The intra- and inter- tumoral heterogeneity of glioblastoma represents a significant therapeutic challenge, as well as difficulty in generating reliable models for in vitro studies. Here, we quantify the tumor cell composition from matched patient-derived neurospheres (PDN) and organoids (PDO) established from the same primary tumor using a series of multi-omic interrogations, relative to primary tissue

  Study EGAS00001008023

• Induction Failure in Childhood and Young Adult T-cell Acute Lymphoblastic Leukemia

  We carried out WGS and RNAseq on a cohort of 48 children and young adults with induction failure in T-cell Acute Lymphoblastic Leukemia (T-ALL) to identify genomic drivers of treatment resistance. The study includes WGS for 33 tumour/normal pairs and 15 tumour-only samples. In addition, there is RNAseq data for 37 cases.

  Dataset EGAD00001009058

• Summary Statistics GWAS SSNS

  Column 1 “rsid”: SNP identifier Column 2 “chromosome”: name of chromosome on which the SNP is located Column 3: “position”: base pair position on the chromosome Column 4 “minor_test_allele”: the base that constitutes the minor allele Column 5 “major_allele”: the base that constitutes the major allele Column 6 “maf”: the frequency of the minor allele, indicated as a fraction of 1 Column 7 “allele_freq_cases”: the minor allele frequency in cases Column 8 “allele_freq_controls”: the minor allele frequency in controls Column 9 “regression_pvalue”: the p-value for the difference in allele frequency between cases and controls Column 10 “odds_ratio”: the odds ratio, as calculated using logistic regression under an additive model with adjustment for the first ten principal components of ancestry

  Dataset EGAD00001008782

• Immune Response Targeted Panel + B/TCR Profiling + AbSeq + Sample Tag Multiplexing

  Multiomics data for a cohort of 20 COVID-19 patients (10 patients mild, 3 patients moderate, 4 patients severe, 3 patients critical) obtained from peripheral blood mononuclear cells (PBMCs) from longitudinally sampled at hospital admission, discharge, and 1 month thereafter. The data has been obtained a multiwell-based single-cell technology (BD Rhapsody) that includes the targeted expression of BD Immune Response Targeted Panel, the TCR/BCR profiling and a set of 52 surface proteins. The samples of the different patients at different collection times were labelled using a cell hashing strategy with the BD Single-Cell Multiplexing Kit (6 samples for each run).

  Dataset EGAD00001011319

• Single cell sequencing of human normal luminal cells

  The dataset includes 12 paired FASTQ files (6 samples) with single cell transcriptome sequencing data of normal breast luminal cells from ducts and TDLUs derived from reduction mammoplasties from three patients. Chromium Single Cell 3’ Reagent Kit v2 or v3 (10x Genomics) were used for processing of cells, whereafter sequencing was performed using the Illumina® NextSeq500/550 High Output Kit v2. Cell Ranger was used for generating FASTQ files and files from different lanes were concatenated prior to uploading the data to EGA. "R1" files include the feature barcodes and UMIs, while "R2" files include the reads.

  Dataset EGAD00001008499

• Whole exome and transcriptome sequencing of BPDCN

  This data set contains whole exome and transcriptome data from 47 case with BPDCN. For exome data, bam files are provided (mapped against GRCh38), for transcriptome raw fastq-files (paired-end data).

  Dataset EGAD00001008692

• Single-cell omics data for COVID-19 patients

  Single-cell RNA-seq, single-cell ATAC-seq, and genotypes used in the analysis for the study "Altered and allele-specific open chromatin landscape reveal epigenetic and genetic regulators of innate immunity in COVID-19". The RNA-seq and ATAC-seq are raw data in FASTQ format while the genotypes are in the VCF format which was filtered and imputed (more details are available in the main text of the study).

  Dataset EGAD00001009331

• Oxford Nanopore targeted RNA-based amplicon data of 12 classical HLA genes

  The dataset consists of Oxford Nanopore targeted RNA-based amplicon data of 12 classical HLA genes (HLA-A, -B, -C, -DRA, -DRB1, -DRB3, -DRB4, -DRB5, -DQA1, -DQB1, -DPA1, and DPB1) of 50 healthy individuals. The 12 classical genes were sequenced in two separate gene pools on R9.4 flowcells using MinION sequencer. Per individual, gene pool 1 contains HLA-A, -B, -C, -DRB1, -DRB3, -DRB4, -DRB5, and -DPB1 and gene pool 2 HLA-DRA, -DQA1, -DQB1, and -DPA1. The dataset includes 100 fastq files of Oxford Nanopore 2D reads (50 for gene pool 1 and 50 for gene pool 2).

  Dataset EGAD00001006814

• A108768B

  Whole genome sequencing for single cells for library A108768B 1126 cells; filetype=bam

  Dataset EGAD00001007089

• The Primary Open-Angle Glaucoma Genes and Environment (GLAUGEN) Study

  Background Information: Primary open-angle glaucoma (POAG) is an age-related, intraocular pressure (IOP)-dependent progressive optic neuropathy that ultimately leads to irreversible blindness. Vision loss from POAG is a condition of public health significance. Current evidence suggests that POAG is a polygenetic disease modified by environmental influences. Despite the fact that a positive family history of disease is an important risk factor for POAG, conventional linkage and candidate gene approaches have revealed less than 5% of the genetic component of the disease. Furthermore, there is no consensus on environment risk factors for POAG. Elevated IOP is the only modifiable risk factor for POAG; yet, lowering IOP slows, but does not halt the disease process. Study Objectives: The overall goal of our research is to elucidate the pathogenesis of POAG so that cost-effective disease detection and primary prevention strategies can be implemented. The primary aim of the Glaucoma Gene Environment Initiative (GLAUGEN), funded by the Human Genome Research Institute (NHGRI), is to discover genetic loci associated with POAG. The secondary aim of GLAUGEN, funded by NHGRI and the National Eye Institute, is to discover gene environment interactions in POAG. Methods and study populations: For this study, we have assembled cases and controls from three studies: the Nurses' Health Study (NHS), the Health Professionals Follow-up Study (HPFS) and the Genetic Etiologies of POAG (GEP) project based at Massachusetts Eye and Ear Infirmary (MEEI). This case-control group includes 1057 unrelated cases and 1272 controls. Members of the NHS and HPFS also have repeated environmental exposure data collected prior to a diagnosis of POAG. NHS - The Nurses Health Study started in 1976 under the direction of Dr. Frank E. Speizer. With funding from the NIH, registered nurses from 11 US states were invited to complete a detailed questionnaire regarding lifestyle and health biennially. Initially, 121,000 women responded to the baseline questionnaire. Currently, Dr. Susan Hankinson serves as the program director for the NHS. HPFS - The Health Professionals Follow-up Study began in 1986 under the direction of Drs. Walter Willett and Meir Stampfer. Under the auspices of the NIH, they enlisted 51,529 male health professionals from throughout the US to complete similarly designed biennial questionnaires. Beginning in 1990, questions regarding ocular health were added to biennial questionaires completed by health professionals participating in the NHS and HPFS. This allowed us to formulate (PI: S. Hankinson; NEI) and maintain (PI: L. Pasquale; NEI) a cohort at risk for POAG derived from the respective general cohorts who were under ophthalmic care. We then developed a definition of POAG that allowed us to identify cases from a population that was geographically dispersed. The centerpiece of this definition is the presence of reproducible visual field loss consistent with nerve fiber layer (NFL) dropout (the NFL contains the axons that comprise the optic nerve) on reliable tests. Reproducible visual field loss occurred in the context of anterior segment findings that did not suggest a secondary cause of elevated IOP and posterior segment findings that did not suggest a secondary cause of visual field loss. We selected controls from the cohort at risk for POAG on the basis of age, gender and time period when cases were identified. GEP - The Genetic Etiologies of POAG was initiated in 1996 with funding from the National Eye Institute under the direction of Dr. Janey Wiggs. The purpose of this work was to discover novel genetic loci associated with POAG. In the GEP, cases were derived predominantly from the Glaucoma Service at MEEI. The majority of cases had an examination by a glaucoma specialist and met the definition for POAG used in NHS and HPFS. Cases with only one reliable visual field consistent with NFL dropout were included if there was a cup-disc ratio of 0.7 or more. The majority of controls were patients who presented to the MEEI comprehensive ophthalmology service for routine eye examination or from spouses of MEEI patients with secondary forms of glaucoma. Other controls were identified from regional glaucoma screenings held throughout Massachusetts. Members of GEP have detailed ocular phenotype data but limited information on environmental exposures. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to primary open-angle glaucoma through large-scale genome-wide association studies of three well-characterized cohorts of cases and controls, some in matched pairs. Genotyping was performed at the Broad Institute of MIT and Harvard, a GENEVA genotyping center. Data cleaning and harmonization were performed at the GEI-funded GENEVA Coordinating Center at the University of Washington.

  Study phs000308

• 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

• Exome chip analysis file

  This data set includes the following summary level data file used for the exome chip analysis: exome_chip.sv.assoc.txt: results from single variant association analysis in exome chip

  Dataset EGAD00010001187

• Immunochip_genotypes

  Intensity files for Immunochip genotypes from blood

  Dataset EGAD00010001495

• MS-Twins-EPIC-PBMCs

  Genome-wide DNA methylation profiles of MZ twins clinically discordant for MS generated using Illumina’s Infinium MethylationEPIC BeadChip assay (EPIC array)

  Dataset EGAD00010001618

• GR@ACE_StageI.v02

  Binary Plink files for post-GWAS quality control in 7409 samples genotyped using Axiom 815K Spanish Biobank array (Thermo Fisher)

  Dataset EGAD00010001653

• Sequencing data for ICGC Oesophageal Adenocarcinoma tissue samples - pilot normal and pre/post-chemo

  Dataset EGAD00001000704

• uganda_autosomes

  Genotype data (in binary PLINK format) and imputed data (with merged 1000Gp3 and AGVP reference panel in GEMMA BIMBAM dosage format) for 1391 individuals from EMaBS in Entebbe, Uganda.

  Dataset EGAD00010002578

• The CCA Genome Core is responsible for archiving the sequencing data generated by the Cancer Centre Amsterdam (CCA).

  Dac EGAC00001000181

• tRCC UTSW 2024 Cohort

  This submission contains the WES and RNA-Seq raw data for the study titled 'Comparative Genomics of a Translocation Renal Cell Carcinoma Mouse Model Reveals Molecular Mechanisms of Tumorigenesis.

  Dac EGAC50000000105

• bfast CohortD OSPL

  ctDNA sample data (one sample per line) for BFAST Cohort D including sample-level summaries like tumor fraction (cTF).

  Dataset EGAD50000000147

• Walter and Eliza Hall Institute - University of Melbourne

  Data Access Committee for Gocuk, Lancaster et al. 2024: nanopore sequencing data of patients with choroideremia and X-linked retinitis pigmentosa, to determine X inactivation skew.

  Dac EGAC50000000301

• Whole exome sequencing data for two samples

  Whole exome sequencing of two human samples run on the Illumina HiSeq2500 platform. It contains two BAM files aligned to the refrence genoeme GRCh38.

  Dataset EGAD50000000825