12011 results for "fc 26 switch coins Visit Buyfc26coins.com for latest FC 26 coins news..NhK9"

in 24.95 milliseconds.

• Chracterising cellur pathways underlying CD3/CD28 activation of human CD4+ cells

  We devised an approach to disentangle the TCR and CD28 pathways upon stimulation in naive and memory primary human CD4+ T cells (Tcons) in response to defined stimulatory signals. Sorted Tcons were activated using a titration of anti-CD3 and anti-CD28 in combination as well as individually. As a control we cultured cells in the same conditions but without the stimuli. In total, we defined seven conditions from four individuals for sequencing. 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/.

  Dataset EGAD00001006610

• Single cell RNA sequencing data in "Three-dimensional human alveolar stem cell culture models reveal infection response to SARS-CoV-2"

  This dataset includes a total of 5 single cell RNA sequencing (scRNAseq) data of SARS-CoV-2 infected human alveolar stem cell culture models. Two scRNAseq data were obtained from SARS-CoV-2 infection with MOI of 1.0 (1 for control and 1 for infected case) and the other three were obtained from SARS-CoV-2 infection with MOI of 0.1 in the study entitled "Three-dimensional human alveolar stem cell culture models reveal infection response to SARS-CoV-2". The 10x Chromium Single Cell 3' Reagent kits were used to generate libraries.

  Dataset EGAD00001006242

• TS and WGS data

  The dataset contains the targeted sequencing (TS) and the whole genome low pass (WGS) BAM files of the study. For the TS: Samples: TS_XXX There are normal and tumor DNA samples. Each DNA strand has been sequenced independently (PoolA and PoolB). A TruSeq Custom Amplicon panel of 20 genes frequently mutated in ILC and/or ER-positive BC in general was designed using DesignStudio from Illumina: AKT1, ARID1A, CDH1, ERBB2, ERBB3, ESR1, FOXA1, GATA3, IGF1R, JAK2, MAP2K4, MAP3K1, NF1, PIK3CA, PTEN, RB1, RUNX1, STAT3, TBX3, and, TP53. For the WGS: Samples: WGS_XXX There are normal and tumor DNA samples. Samples were sequenced to an average target coverage of 0.5X.

  Dataset EGAD00001006393

• H3Africa AWI-GEN Phase 1 Phenotype

  The phenotypic data for ~12500 samples of the AWI-Gen Phase 1 Population cross-sectional study of older adults (mostly between 40 and 60 years), men and women. Six study sites in four sub-Saharan African counties including Ghana, Burkina Faso, Kenya and South Africa. Some groups are missing data for specific variables. Data includes questionnaire data (demography, health history, family health history, behaviour and infection data); anthropometry; and laboratory assays on blood and urine.

  Dataset EGAD00001006425

• Chracterising cellur pathways underlying CD3/CD28 activation of human CD4+ cells

  We devised an approach to disentangle the TCR and CD28 pathways upon stimulation in naive and memory primary human CD4+ T cells (Tcons) in response to defined stimulatory signals. Sorted Tcons were activated using a titration of anti-CD3 and anti-CD28 in combination as well as individually. As a control we cultured cells in the same conditions but without the stimuli. In total, we defined seven conditions from four individuals for sequencing. 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/ .

  Dataset EGAD00001006612

• 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

• 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

• 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

• 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

• 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

• 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

• A new subgroup of hepatocellular adenomas with sonic hedgehog pathway activation

  Using sequencing and gene expression analyses, we identified a subgroup of HCA characterized by fusion of the INHBE and GLI1 genes and activation of sonic hedgehog pathway. Molecular subtypes of HCAs associated with different patients’ risk factors for HCA, disease progression, and pathology features of tumors. This classification system might be used to select treatment strategies for patients with HCA. Related Publication: Molecular Classification of Hepatocellular Adenoma Associates With Risk Factors, Bleeding, and Malignant Transformation Nault, Jean-CharlesLaurent, Christophe et al. Gastroenterology , Volume 152 , Issue 4 , 880 - 894.e6 http://dx.doi.org/10.1053/j.gastro.2016.11.042

  Dataset EGAD00001003092

• Identification of drug resistance genes in melanoma

  Our aim is to analyze the genome of human melanoma cell lines and short term culture from human melanoma samples in order to identify genes that confer drug resistance to clinically relevant targeted therapies. We will perform whole-exome sequencing, copy number variation analysis and methylome analysis in a collection of human melanoma cell lines and short term culture that will be then screened for drug sensitivity/resistance through a library of clinically relevant drugs and drug combinations. By the combined analysis of the genomic lesion and the drug sensitivity/resistance profile of different cell lines, we will look for genes whose mutation is associated to the sensitivity or resistance to a specific drug in different samples.

  Dataset EGAD00001001124

• SCLC study George et al. - WGS data set

  Whole genome sequencing was performed with DNA extracted from fresh-frozen tumor and normal material. Short insert DNA libraries were prepared with the TruSeq DNA PCRfree sample preparation kit (Illumina) for paired-end sequencing at a minimum read length of 2x100bp. Human DNA libraries were sequenced to an average coverage of minimum 30x for both tumor and matched normal. Murine DNA libraries of tumor and matched normal were both sequenced to a coverage of 25x.

  Dataset EGAD00001001273

• Tam-Seq of HGSOC samples for fixative comparison study

  Targeted amplicon sequencing of samples as part of the study "Methanol-based fixation is superior to buffered formalin for next-generation sequencing of DNA from clinical cancer samples. The amplicon panel consists of 48 amplicons in TP53, PTEN, EGFR, PIK3CA, KRAS and BRAF genes as described previously [Forshew, STM 2012]. All libraries were pooled and quantify using DNA 1000 kit on Agilent 2100 Bioanalyzer and KAPA SYBR FAST ABI Prism qPCR Kit (KAPA Biosystems) on 7900HT Fast Real-Time PCR System (Applied Biosystems) according to the supplier's recommendations. Reads were aligned using bwa-mem v0.7.12-r1039 to the 1000 genomes version of human genome build GRCh37, retaining duplicate reads.

  Dataset EGAD00001001937

• 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

• 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