13856 results for "Buy fc coins Buyfc26coins.com is EA Sports official for FC 26 coins I received very good service today..GnKh"

in 127.69 milliseconds.

• Whole-exome sequencing and microRNA profiling predicted relapse risk of stage I lung adenocarcinomas for the study and all the datasets.

  This dataset contains PAIR files and processed somatic copy number alteration value for array CGH of stage I lung adenocarcinomas from Asian patients. In total, there are 111 patients and 222 samples, including 111 tumor samples and 111 adjacent normal samples.

  Dataset EGAD00010001902

• Impact of Genetic Variation on Response to GO Therapy in COG-AML Trials AAML03P1 and AAML0531

  The 340 de novo Acute Myeloid Leukemia (AML) patients (ages 1 month to 21 years) were enrolled in COG-AAML03P1 (NCT00070174). Everyone received standard chemotherapy regimen of ara-C, daunorubicin and etoposide (ADE) with addition of one 3 mg/m2 dose of Gemtuzumab Ozogamicin (GO) in induction 1 as well as in intensification II phase. The 1022 de novo AML patients (ages 0–30 years) were enrolled in COG-AAML0531 (NCT01407757). They were randomly assigned to receive either the standard ADE regimen (ADE arm, n = 511) or with the addition of one 3 mg/m2 dose of GO, during induction I as well as intensification II phase (ADE+GO arm, n = 511). Detailed study design, treatment regimen, and clinical outcomes of these two trials have been previously published (Cooper TM, Franklin J, Gerbing RB, et al., PMID:21766293 and Gamis AS, Alonzo TA, Meshinchi S, et al., PMID:25092781). The current study used genomic DNA from 1,225 pediatric patients treated in these two trials with 470 patients treated with standard chemotherapy in COG-AAML0531 (ADE arm) and 755 patients treated with addition of GO to standard therapy in COG-AAML03P1 and COG-AAML0531 trials (ADE+GO arm). The 132 SNPs in 42 genes within DNA-damage repair (DDR) pathways or genes implicated in mediating calicheamicin were selected for genotyping. These SNPs were genotyped using the Sequenom platform at the Biomedical Genomics Center, University of Minnesota. All SNPs had a call rate of more than 0.98 and were in accordance with the Hardy–Weinberg equilibrium. These genotypes were used to test for association with clinical endpoints as defined in the COG-AAML03P1 and COG-AAML0531 trials.

  Study phs003490

• Studies of a Targeted Risk Reduction Intervention through Defined Exercise (STRRIDE)

  The STRRIDE study is the combination of three interventional trials to evaluate dose and intensity of physical activity on cardiometabolic health. The three component studies are Peripheral Effects of Exercise on Cardiovascular Health (STRRIDE I, ClinicalTrials.gov Identifier: NCT00200993), Effects of Resistence and Aerobic Exercise on Cardiovascular Health (STRRIDE II, ClinicalTrials.gov Identifier: NCT00275145) and Exercise Dose-Response Effects in Prediabetes (STRRIDE-PD, ClinicalTrials.gov Identifier: NCT00962962).

  Study phs001855

• Frequent germline mutations of HAVCR2 in sporadic subcutaneous panniculitis-like T-cell lymphoma.

  Subcutaneous panniculitis-like T-cell lymphoma (SPTCL) is a rare subtype of peripheral T-cell lymphoma affecting younger cases and associated with hemophagocytic lymphohistiocytosis. To clarify the molecular pathogenesis of SPTCL, we analyzed paired tumor and germline DNAs from 13 patients by whole exome sequencing.

  Dataset EGAD00001004795

• Genome wide association study for early onset coronary disease and related phenotypes (ADVANCE)

  ADVANCE (Atherosclerotic Disease, VAscular functioN, and genetiC Epidemiology) is a large epidemiological study of genetic and non-genetic determinants of coronary artery disease (CAD) that started in 2000 as a collaborative effort between researchers at Stanford University and Kaiser Permanente of Northern California. The overarching goal of the study is to improve our ability to prevent, diagnose and treat CAD. The initial study included recruitment of over 3600 subjects (including 1873 subjects with incident clinically significant coronary disease and 1745 control subjects) from multiple race/ethnic backgrounds. A subset of ~ 500 subjects with very early onset coronary disease (men < 45 and women < 55) and ~ 500 similar aged controls were genotyped using the Illumina 550K platform as part of an NIH funded effort within the STAMPEED consortium.

  Study phs000423

• Youth-GEMs, the project using data to define the mental health trajectories of young people

  Mental health trajectories are shaped by genetic, cognitive, social, and environmental factors that are particularly influential during human development. How exactly the interplay between these factors is impacting mental health, however, is yet unknown. The project “Gene Environment interactions in Mental health trajectories of Youth (Youth-GEMs)”, funded by the European Commission under the Horizon Europe programme, aims to help reducing mental suffering among European youth. How do Youth-GEMs contribute to bettering mental health in young people? Youth-GEMs aims to identify specific neurological, (epi)genetic and environmental drivers on mental health trajectories of young people. To do so, the project is working on a public knowledge base on functional genomics of the developing human brain, between birth and 24 years old. Reliable predictive models for trajectories of onset and course of mental illness in young people of the general population in Europe will be developed. Additionally, a secure and FAIR data infrastructure in mental health is being produced. Engaging and empowering young people Youth-GEMs is also working on the engagement of young people in the scientific field of Psychiatry. For that, the project is developing initiatives such as Science Café, intended to create a learning community where ideas and stories are shared. The 10th Science Café will take place today, with the participation of Lauren Fromont from the EGA. How do the EGA contribute to Youth-GEMs? The contributions require careful data management and harmonisation: we are dealing with an extraordinary amount of data types, sources, and time points (since the studies are longitudinal). To analyse them together and to determine which factors and interactions are truly key to account for mental health trajectories, the variables need to be transformed in a common “language”, i.e., harmonised under a common data model. Further, to guarantee FAIRness of data storage and sharing for future projects that will further advance our knowledge in the mental health field, we are ensuring that data are processed securely but can also be discovered easily. Find out more information about the project in the Youth-GEMs website.

  Blog youth-gems-mental-health

• GOSH_Childhood_Leukemia_Behjati_WellcomeCore_RNA

  Paediatric single-cell archival project This project is taking sequential samples of children with B-cell acute lymphoblastic leukaemia (B-ALL) treated at Great Ormond Street Hospital (GOSH) between 2011 and the present day. Patients selected, are those that have done badly (e.g. had to escalate treatment, relapsed or died) despite having apparently ""good"" or ""intermediate"" risk cytogenetics, and often also had immunotherapy (e.g., the bi-specific T-cell engager blinatumomab) because of this. Using samples from key treatment-points, we hope to better characterise their disease and treatment response, to re-define understandings of risk for patients who did unexpectedly poorly. Additionally, we hope to define the disease/immunological factors that determine response to increasingly used immunotherapies within the field of paediatric B-ALL. Each of the samples will be viably frozen bone marrow-derived mononuclear cells. They will come in Eppendorf's, frozen and de-anonymised, from GOSH. We plan to primarily do single cell analysis (GEX, BCR +/-TCR), and then tumour-only WGS and bulk-RNA expression on left-over

  Study EGAS00001007616

• ICGC Oesophageal adenocarcinoma - pilot samples

  The oesophageal project will focus on adenocarcinoma which is increasing in incidence in the UK and other developed countries and has a very poor outcome. The primary aims of this project are to deeply sequence tumour and normal genomic DNA (including the precursor condition Barrett's oesophagus when material is available) to provide a comprehensive catalogue of somatic mutations. This will be achieved through a UK-wide network of hospitals involved in a research collaboration called the OCCAMS consortium. The goal of this project is to use high quality clinical material with accurately annotated clinic-pathological, treatment and outcome data.

  Study EGAS00001000559

• ICGC Oesophageal adenocarcinoma - Barrett's samples

  The oesophageal project will focus on adenocarcinoma which is increasing in incidence in the UK and other developed countries and has a very poor outcome. The primary aims of this project are to deeply sequence tumour and normal genomic DNA (including the precursor condition Barrett’s oesophagus when material is available) to provide a comprehensive catalogue of somatic mutations. This will be achieved through a UK-wide network of hospitals involved in a research collaboration called the OCCAMS consortium. The goal of this project is to use high quality clinical material with accurately annotated clinic-pathological, treatment and outcome data.

  Study EGAS00001000726

• Next generation sequencing of diffuse intrinsic pontine glioma samples to identify recurrent mutations, variations, and expression patterns to define novel therapies

  Diffuse intrinsic pontine glioma (DIPG) is an extremely rare (~350 cases/year) and universally fatal childhood brain cancer. Standard clinical strategies such as chemotherapy and radiotherapy show only transient improvement in patient condition and result in negligible change in survival, DIPG remains at below 1% survival after 5 years. Prioritization of panobinostat through previous cooperative work resulted in a phase 1 clinical trial. Nonetheless, new therapies for DIPG must be identified to further dramatically change the statistics for DIPG. To identify novel therapy strategies for DIPG, we performed whole exome(16 new samples, 22 previously published samples, 38 in total with 26 matched normal) and RNA deep sequencing (17 new samples, 11 previously published samples) on a cohort of new patient samples. Sequencing results aid in the identification of recurrent mutations/variations and endotypic expression profiling to identify new therapeutic and treatment strategies for DIPG.

  Study phs001526

• Targeted bisulfite sequencing

  Raw reads from targeted bisulfite sequencing. The SureSelect Methyl-Seq target enrichment system (Agilent Technologies, Inc., CA, USA) was used to prepare bisulfite sequencing libraries from blood DNA samples of lymphoma patients (Ly1, Ly2), healthy family members (Ly8, Ly9, Ly10, Ly11, Ly12, Ly13 and Ly14), baseline controls (Control1-5), DNMT3A mutation carriers (Id5, Id7, Id9, Id11) and their age-matched controls (Id6, Id8, Id10, Id12). In addition, blood DNA sample of a patient (HLRCC_N7) with germline fumarate hydratase (FH) mutation is included. Illumina paired-end sequencing for targeted libraries from Ly1, Ly2, Ly8, Ly9, Ly10 and Ly11 was done at Karolinska Institutet using 100 base-pair read length and the HiSeq2000 platform. Illumina paired-end sequencing for targeted libraries from Ly12, Ly13, Ly14, and DNMT3A mutation carriers and their age-matched controls was done as a service at BGI (BGI Tech Solutions Co., Ltd., China) using 126 base-pair read length and the HiSeq2500 platform.

  Dataset EGAD00001004785

• Genetics of Glucose Regulation in Gestation and Growth (Gen3G) Cohort - Placenta Transcriptomics RNA Sequencing

  The overarching goals of Genetics of Glucose regulation in Gestation and Growth (Gen3G) are to increase our understanding of biological, environmental, and genetic determinants of glucose regulation during pregnancy and their impact on fetal/child development. Gen3G is a prospective cohort study: we initially recruited 1,024 pregnant women between 2010-2013 at Blood Sampling in Pregnancy Clinic during the first trimester of pregnancy (median 9 weeks of gestation) in Sherbrooke, Québec, Canada. We assessed 898 pregnant women at second trimester (median 26 weeks of gestation), when participants completed a 75g oral glucose tolerance test (OGTT) as clinically indicated for screening of gestational diabetes mellitus (GDM). We collected data for 854 mother-child dyads at delivery (from medical records), in addition to placenta and/or cord blood samples in majority of newborns.The overall goal of the grant that supported data that is included in this dbGaP submission was to discover novel placental factors that regulate glucose metabolism in pregnancy and predict GDM by conducting genome-wide transcriptomics (RNA and miRNA) in carefully collected placenta samples from Gen3G.

  Study phs003151

• Single-Cell TCR/BCR Sequencing for Korean COVID-19 Vaccinated and Patient Samples

  We conducted longitudinal single-cell TCR/BCR sequencing for COVID-19 vaccinated cases (297 samples from 112 cases) and COVID-19 infected cases classified as Asymptomatic (26 samples from 12 cases), Mild (82 samples from 37 cases), Moderate (123 samples from 50 cases), Severe (216 samples from 58 cases), and Critical (142 samples from 41 cases) according to the NIH guideline.

  Study phs003341

• 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

• Altered enhancer-promoter interaction leads to MNX1 expression in pediatric acute myeloid leukemia with t(7;12)(q36;p13)

  Acute myeloid leukemia (AML) with the t(7;12)(q36;p13) translocation occurs only in very young children and has a poor clinical outcome. The expected oncofusion between breakpoint partners (MNX1 and ETV6) has only been reported in a subset of cases. However, a universal feature is the strong transcript and protein expression of MNX1, a homeobox transcription factor that is normally not expressed in hematopoietic cells. Here, we map the translocation breakpoints on chromosomes 7 and 12 in affected patients to a region proximal to MNX1 and either introns 1 or 2 of ETV6. The frequency of MNX1 overexpression in pediatric AML (n=1556, own and published data) is 2.4% and occurs predominantly in t(7;12)(q36;p13) AML. Chromatin interaction assays in a t(7;12)(q36;p13) iPSC cell line model unravel an enhancer-hijacking event that explains MNX1 overexpression in hematopoietic cells. Our data suggest that enhancer-hijacking is a more common and overlooked mechanism for structural rearrangement-mediated gene activation in AML.

  Study EGAS50000000130

• Bone marrow single cell genomics from blood cancer samples

  The overall goal of this study was to characterize bone marrow cells based on their transcriptome, surface protein expression and BCR- and TCR VDJ-profile for accurate identification of clinically relevant cell states. This project has received funding from the European Union Horizon 2020 research and innovation programme under grant agreement No 824110 (EASI-Genomics)

  Study EGAS00001007332

• Sensitive detection of tumor mutations from blood and its application to immunotherapy prognosis

  Cell-free DNA (cfDNA) is attractive for many applications, including cancer detection, locating, and monitoring. A fundamental task underlying these applications is the SNV calling from cfDNA, which, however, faces a new challenge, namely, the generally very low tumor content in cfDNA. Thus all existing callers fail to achieve satisfactory performance. Here we present cfSNV, a method incorporating multi-layer error suppression and hierarchical mutation calling, to address this important challenge. Furthermore, by leveraging cfDNA’s comprehensive coverage of clonal landscape, for the first time cfSNV can profile mutations even in subclones. In both simulated and real patient data, cfSNV vastly outperforms existing tools, showing tens of times increase in sensitivity in detecting mutations with low allele frequency while maintaining high precision. cfSNV can enhance the clinical utilities of cfDNA by dramatically reducing the required sequencing depth and therefore reduce the cost by magnitudes, and further make the Whole-Exome-Sequencing of cfDNA a viable option. As an example, we demonstrate that cfDNA-WES allows a new biomarker to effectively select patients for immunotherapy.

  Study EGAS00001004373

• An Advanced Molecular Medicine Case Report of a Rare Human Tumor Using Genomics, Pathomics, and Radiomics

  The associated data of this study is derived from a single female patient with pulmonary sclerosing pneumocytoma (PSP). The aim of this study is to provide the most comprehensive, multi-modality sequencing study of a single case of PSP to-date. To this end, the following sequencing experiments were performed: i) RNA-Seq of the primary tumor and adjacent normal tissues (6 replicates for each tissue type), which was intended to analyze RNA-Seq fusions, gene expression, expression mutations, ii) low-pass DNA whole genome sequencing (WGS) from primary tumor tissue and germline, which was intended to analyze copy number aberrations, and iii) DNA targeted panel sequencing of lung cancer associated genes, using primary tumor tissue and germline from white blood cells, which was intended to analyze somatic mutations. Principal findings: i) the PSP hallmark mutation AKT1 (p.E17K) was detected within both the DNA and RNA, and ii) the TP53 signaling pathway was found to be statistically significant by three different pathway analysis tools of analyzing gene expression and pathway ramifications. Among proteins within the TP53 signaling pathway, the p53 inhibitor encoded by MDM2 was found to be overexpressed (by differential gene expression analysis). The original sequencing data (i.e., FastQ files) from each of the aforementioned samples will be accessible through dbGaP.

  Study phs003154

• Long-Term Oxygen Treatment Trial (LOTT-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. Objectives: To evaluate the efficacy of long-term treatment with supplemental oxygen in people with stable chronic obstructive pulmonary disease (COPD) and resting or exercise-induced moderate desaturation. Background: COPD is the fourth leading cause of death in the United States, with more than twelve million people currently diagnosed with the disease. In 2011, Medicare reimbursements for oxygen-related costs for people with COPD exceeded two billion dollars. The quality of life of a person with COPD decreases as the disease progresses, making treating and managing COPD in the moderate stages important. The benefits of oxygen supplementation were studied in the 1970s, but these benefits were specific to people with COPD who have severe resting hypoxemia. The LOTT trial was designed to address the effectiveness of supplemental oxygen therapy in treating people with COPD who have moderately low blood oxygen levels at rest or who have normal blood oxygen levels at rest, but have low or very low blood oxygen levels during exercise. Participants: There were a total of 1759 people screened for eligibility for the LOTT trial. Of the 1759 screened, 738 people with COPD were selected for randomization with 368 randomly assigned to the supplemental-oxygen group and 370 to the no-supplemental-oxygen group. Of the 738 people with COPD who underwent randomization, 133 (18%) had resting desaturation only, 319 (43%) had exercise-induced desaturation only, and 286 (39%) had both types of desaturation. Furthermore, in the supplemental-oxygen group, 220 people were prescribed 24-hour oxygen and 148 were prescribed oxygen during exercise and sleep only. Design: The LOTT trial was originally designed to test whether the use of supplemental oxygen would result in a longer time to death for people with COPD and moderate resting desaturation. After seven months, the trial design was judged to be infeasible; therefore, the trial was redesigned to include people with exercise-induced desaturation with a primary composite outcome of death or first hospitalization for any cause, whichever occurs first. Other outcomes measured included: death, health care utilization, COPD exacerbation, quality of life measurements, anxiety, depression, and measures of functional status. Potential participants were screened using questionnaires, a breathing test, a brief physical exam, a blood draw, and measurements of resting and walking blood oxygen levels. Based on those results, eligible participants returned for a second screening visit for further evaluations. At the end of the second visit, eligible participants were assigned randomly to supplemental oxygen therapy or no oxygen therapy. Participants assigned to supplemental oxygen therapy received stationary and/or portable oxygen systems. Participants were required to return for a one hour visit to determine how much oxygen to use while walking and to learn how to use the equipment. Participants who had low blood oxygen levels during rest were instructed to use supplemental oxygen 24 hours per day. Participants with normal resting blood oxygen levels, but low or very low blood oxygen levels during exercise were instructed to use it during physical activity and sleep. Throughout the treatment period, participants were asked to keep records of the number of oxygen tanks emptied or pounds of oxygen delivered, meter readings, and changes in equipment. Study officials contacted participants weekly for the first month, monthly for the next five months, and then every two months until the Year 1 study visit. Participants assigned to receive no oxygen treatment were contacted one week after assignment for a check-up. All participants returned for study visits once a year for up to seven years. At each of these visits, participants completed some of the same tests and questionnaires from the screening visit. Participants underwent a blood draw during the one year study visit. Participants in both treatment groups received two phone calls each year to check on status and use of oxygen. In addition, participants in both groups were asked to complete a quality of life questionnaire by mail at four months and sixteen months. Medicare claims were collected for the duration of each participant's enrollment in the study. Conclusions: In participants with stable COPD and resting or exercise-induced moderate desaturation, the prescription of long-term supplemental oxygen did not result in a longer time to death or first hospitalization than no long-term supplemental oxygen, nor did it provide sustained benefit with regard to any of the other measured outcomes. Long-Term Oxygen Treatment Trial Research Group, Albert RK, Au DH, Blackford AL, Casaburi R, Cooper JA Jr, Criner GJ, Diaz P, Fuhlbrigge AL, Gay SE, Kanner RE, MacIntyre N, Martinez FJ, Panos RJ, Piantadosi S, Sciurba F, Shade D, Stibolt T, Stoller JK, Wise R, Yusen RD, Tonascia J, Sternberg AL, Bailey W. A Randomized Trial of Long-Term Oxygen for COPD with Moderate Desaturation. N Engl J Med. 2016 Oct 27;375(17):1617-1627.

  Study phs003933

• National Institute of Mental Health (NIMH) Duke Cognition Cohort

  The overall goal is to identify genetic variants influencing normal variation between humans, with a focus on cognitive and neurosensory traits. Because of the focus of funding agencies on disease, very few studies of the genetics of non-disease traits have been performed. The genetic variation underlying the vast majority of differences between humans therefore remains not only undiscovered, but also unexplored. We have assessed &#62;1,200 healthy volunteers for &#62;70 diverse, non-disease phenotypes, with a focus on cognitive and neurosensory traits that are understudied and seem to have a strong biological basis. Our study includes measurements of face recognition, night vision, cognitive performance, auditory pitch discrimination, contagious yawn susceptibility, time perception, sense of direction, taste preferences, personality, sexual behaviors, sleep habits, acne, headache locations, synesthesia, and teeth sensitivity. This method is very different from the focus of most studies on collecting cohorts of patients with disease and controls with minimal phenotypic information. Because we phenotype the same healthy volunteers for multiple highly variable yet heritable traits, we can perform genetic analyses on a large number of phenotypes by just investing once in sequencing the DNA of these participants. An additional &#62;2,000 participants in our cohort have been measured just for cognitive performance instead of for the more extensive phenotyping. Most of the genetic studies in this cohort have been about cognitive perfromance. The number of participants with genetic data generated who have undergone the more extensive phenotyping is limited. Our studies of the more novel traits like contagious yawning have therefore focused more on correlations between different phenotypes until we have a sufficient sample size to truly attempt to make genetic discoveries. . The dataset also includes two small challenge studies. In one study, the cognitive performance of 150 healthy volunteers was measured before and after an acute dose of the antiepileptic drug topiramate. In the other study, the cognitive performance of 13 healthy volunteers was measured before and after 24 hours of sleep deprivation.

  Study phs001406

• WGS datasets of pediatric glioblastoma

  WGS with linked reads of pediatric glioblastoma. For each patient, blood and tumor tissue were sequenced. For two patients, we also provide sequencing data for the blood of their parents.

  Dataset EGAD00001005212

• WES data from 165 tumor/germline samples with muscle invasive bladder cancer.

  In this study, a total of 300 patients with MIBC receiving chemotherapy were included; 62 received NAC before cystectomy and 245 received first-line chemotherapy upon detection of locally-advanced (T4b) or metastatic disease. Treatment response, defined as pathological downstaging (&lt; pTa,CIS,N0) after NAC or complete or partial response after first-line treatment (RECIST criteria). WES was performed using DNA from 165 tumors (76x median coverage) and associated germline DNA (46x median coverage). Data provided here consist of 5,828 fastq files for WES.

  Dataset EGAD00001006239

• Indonesian methylation data

  DNA methylation data were collected to study patterns of functional variation across the broad geography of Indonesia. The region has extremely diverse populations, with very different demographic histories and multiple genetic ancestries. This dataset reports Illumina Epic methylation chip data for individuals from three islands spanning this geographical region: Mentawai, Sumba and West Papua.

  Study EGAS00001003653

• Orthotopic Patient-Derived Xenografts of Pediatric Solid Tumors

  Pediatric solid tumors arise from endodermal, ectodermal, or mesodermal lineages. Although the overall survival of children with solid tumors is 75%-80%, that of children with recurrent disease is below 30%. To capture the complexity and diversity of pediatric solid tumors and establish new models of recurrent disease, we developed a protocol to produce orthotopic patient-derived xenografts (O-PDXs) at diagnosis, recurrence, and autopsy. Tumor specimens were received from 168 patients, and 64 O-PDXs were established for 12 types of pediatric solid tumors. The origins of the O-PDX tumors were reflected in their gene-expression profiles and epigenomes. Genomic profiling of the tumors, including detailed clonal analysis, was performed to determine whether the clonal population in the xenograft recapitulated the patient’s tumor. We identified several drug vulnerabilities and showed that the combination of a WEE1 inhibitor (AZD1775), irinotecan, and vincristine can lead to complete response in multiple rhabdomyosarcoma O-PDX tumors in vivo.

  Study EGAS00001002528

• Molecular_diagnosis_of_albinism

  Albinism is genetically heterogeneous rare genetic condition affecting 1:17000 in the Western world (but more frequent in Africa) whose main feature is a profound visual impairment, characterised by foveal hypoplasia, abnormal chiasmatic connections, nystagmus and photofobia. All these features result in severly altered visual acuity (&lt;0,1), absent depth perception and poor night vision. People with albinism are primarily visually handicapped. In addition, for some types of albinism, the visual phenotype can be presented with partial or total hypopigmentation, hence resulting in a secondary phenotype which can lead to skin cancer if skin is not adequately protected. Recently a new syndrome has been described, FHONDA, with the same visual abnormalities of albinism but without pigment alteration. The traditional classification differentiates Oculoculatenous albinism (OCA), where hypopigmentation involves hair, skin and eyes versus Ocular Albinism (OA), where hypopigmentation only affects the eyes. These are non-sydrimic types of albinism. Some syndromic forms (Hermansky-Pudlak=HPS, Chediak-Higashi=CHS) affect cells beyond pigment cells, present in the lungs, immune system, platelets and intestines, resulting in more severe phenotypes that can be fatal. Mutations in at least 19 genes are assocaited with the corresponding types of albinism. Most hospitals will only diagnose the most frequent cases using traditional Sanger, MLPA approaches. Some will use CGH arrays. We aim to diagnose all cases of albinism through the Albinochip proposal, which combines a Sequenom first step of known mutations combined with subsequent NGS approaches. In some cases we fail to find a second mutation, these are good candidates for further full exome analyses. 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 EGAS00001002068