17137 results for "free coins in fc 26 Visit Buyfc26coins.com for latest FC 26 coins news..xwWa"

in 29.84 milliseconds.

• BAM file s of WGS data of Progressive supranuclear palsy patients

  BAM files of healthy controls (3) and Progressive supranuclear palsy (PSP) patients (4). Genomic DNA from donors was fragmented, end-polished, A-tailed, and ligated with Illumina adapters, followed by size selection. Libraries were PCR-amplified (unless PCR-free), purified with AMPure XP, assessed on the Agilent Fragment Analyzer, and quantified using Qubit and qPCR. Qualified libraries were pooled and sequenced on Illumina platforms, and low-quality reads or adapter-contaminated reads were removed. Clean data were then mapped to the hg38 reference genome using BWA.

  Dataset EGAD50000001758

• A Platform Study of Combination Immunotherapy for the Neoadjuvant and Adjuvant Treatment of Patients with Surgically Resectable Adenocarcinoma of the Pancreas

  This is a single-institutional, randomized, open label platform clinical trial testing various immunotherapy combinations. Patients with newly diagnosed and surgically resectable pancreatic ductal adenocarcinoma (PDA) and scheduled to undergo the Whipple procedure at Johns Hopkins Hospital were eligible to participate in this study. Criteria for determining resectability strictly followed National Comprehensive Cancer Network (NCCN) guidelines. The study consisted of 6 parts: parts 1-5 constituted the Prime Phase (see below), and part 6 was the Extended Treatment Phase. Part 1: Participants received one cycle of immunotherapy two weeks prior to undergoing the Whipple procedure. Part 2: Subjects underwent the Whipple procedure. Part 3: Subjects received a second cycle of immunotherapy 4-10 weeks following the Whipple procedure (2-4 weeks prior to adjuvant chemoradiation). Part 4: Subjects underwent chemoradiation. Part 5: Subjects received 4 additional 28-day cycles of immunotherapy beginning 1-2 months after completing chemoradiation for a total of six cycles (two before chemoradiation and 4 following chemoradiation). Eligible subjects were randomized to Arms A and B in a 1:1 ratio, stratified up-front by age (≤65, >65). Arm A participants received Cy/GVAX. Arm B participants received the combination of Cy/GVAX and nivolumab. GVAX Vaccine consists of equal numbers (2.5 x 108 each) of Panc 6.03 pcDNA1GM-CSF and Panc 10.05 pcDNA1GM-CSF combined into a single vaccination. Each vaccination consisted of six total intradermal injections. A single intravenous (IV) dose of 200 mg/m2 Cy (CytoxanR) was given one day prior to GVAX. Anti-PD-1 Therapeutic Antibody Nivolumab 480 mg every 4 weeks was administered as an intravenous infusion. The primary objective for Arms A and B was to compare IL17 expression (Th17) in vaccine-induced lymphoid aggregates between resected PDAs from patients treated with the combination of Cy/GVAX and anti-PD-1 blockade antibody vs. the treatment of Cy/GVAX alone. Secondary objectives were to assess the safety, overall survival (OS), and disease free survival (DFS) of patients treated with each of the study drug combinations, and to assess the effects of each of the immunotherapy study drug combinations on PD-L1/PD-1 associated pathways, vaccine-induced immune regulatory signatures, and peripheral and intratumoral antigen specific T cell responses. The exploratory objective was to explore the effects of therapy on tumor and peripheral blood and tumor infiltrating immune cells, and to explore potential molecular determinants of response, progression and disease stability. To these ends, tumor infiltrating immune cells (TIICs) were obtained from surgically resected tumors following the neoadjuvant treatment of the study immunotherapy. TIICs were sorted into CD3+CD4+ T cells, CD3+CD8+ T cells, CD3-CD19+ B cells, and CD3-CD19-CD11b+ myeloid cells by flow cytometry. The sorted immune cell subtype pellets were sent to the commercial vendor (Eurofins) for RNA extraction and sequencing. SMART-seq v4 Ultra Low Input mRNA Sample Prep Kit was used for library preparation with 100bp paired end reads. FASTQ files, that were returned from the vendor, are deposited here.

  Study phs003002

• Genome-Wide Association Study of HCC in Non-Asian USA Population

  This GWAS of HCC relied on existing biological and data resources from 7 USA sites and one Canadian site which allows for the integration of genetic and environmental data. Total of 2199 case patients and 1103 non cancer controls were genotyped. Case patients are defined as patients with pathological or radiological diagnosis of HCC with and without chronic hepatitis C virus infection. Study was restricted to Caucasian population without prior infection with chronic HBV infection. All DNA samples were extracted from peripheral blood. Study population of the participated sites are: Site-1: University of Texas MD Anderson Cancer Center A hospital based-case-control study was initiated at UT MD Anderson Cancer Center in 2000 and approved by the Institutional Review Board of The University of Texas M. D. Anderson Cancer Center. Study design was previously described in detailed (1-3). Written informed consent for an interview and for a biological sample was obtained from each participant. At time of diagnosis prior to treatment exposure. Case patients were recruited from the population of patients with newly diagnosed HCC who were evaluated and treated at the institution's gastrointestinal medical and surgical oncology outpatient clinics. Inclusion criteria were as follows: a pathologically confirmed diagnosis of HCC, U.S. residency, and the ability to communicate in English. Patients with concurrent or past history of other types of cancers were excluded. Control subjects were healthy spouses of patients with cancers other than liver, gastrointestinal, lung, or head and neck (smoking-related cancers) undergoing treatment at our institution. Eligibility criteria for control subjects were the same as those for patients, except that control subjects could not have ever had cancer. A short, structured questionnaire was used to screen potential control subjects on the basis of eligibility criteria. Control subjects and patients were recruited simultaneously. Case patients and control subjects were interviewed by well-trained interviewers who followed a written protocol to guide ascertainment and reduce surveillance, interviewer, and recall bias. No proxy interviews were conducted. The interviewers used a structured and validated questionnaire to collect information about demographic characteristics and potential risk factors for HCC such as personal smoking history, alcohol use, medical history, occupational history, and family history of cancer. Blood samples from cases and controls were tested for HBV and HCV. HCV antibodies, hepatitis B surface antigen, and antibodies to hepatitis B core antigen were detected by use of a third-generation enzyme-linked immunosorbent assay (ELISA) (Abbott Laboratories, North Chicago, IL). Important clinical information were retrieved from patients' medical records. Total of 1188 case patients and 278 controls from MD Anderson study were genotyped. Site-2: Mayo Clinic Case patients and controls included in the study from Mayo clinic were recruited as part of Mayo International Hepatobiliary Neoplasia Register and Biorepository. Only USA patients and controls were participated. All cases and controls signed informed consent indicating their willingness to participate in genetic studies. Epidemiological and clinical data were collected from participants and retrieved from medical records. Total of 522 HCC case patients and 182 controls were genotyped in this study. Site-3: Toronto University Molecular Epidemiology of Hepatobiliary Tumors (HBT study, CAPCR 09-0289) is a hospital-based study that includes 1710 patients diagnosed with liver, bile duct or gallbladder adenocarcinoma (Hepatocellular carcinoma - HCC; cholangiocarcinoma - CCA; and gall bladder adenocarcinoma -GBCa) recruited at University Health Network (UHN) between 2009 and 2018. HBT study is a prospective study of cancer patients that collects self-reported demographic and epidemiological data, medical records/clinical information and blood samples for research purposes. Eligible patients recruited between 2009 and March 15 2016 were selected to participate in the Genome-Wide Association Study in Patients with Hepatocellular Carcinoma (GWAS in HCC, CAPCR 15-9943-CE), a sub-study of the HBT study. Eligible prospective patients recruited after March 15 2016 signed the Addendum to the HBT consent form and became eligible to participate in the GWAS in HCC study. Total of 271 cases and 21 controls were genotyped from Toronto University Site-4: University of Pittsburgh The design of the study has been described previously (4-6). Briefly, this population-based study enrolled 120 HCC patients and 230 matched controls from black, Hispanic, and non-Hispanic white residents of Los Angeles County who were between 18 and 74 years of age at diagnosis from January 1995 through December 2001. HCC Cases were identified through the Los Angeles County Cancer Surveillance Program. We sought to recruit up to two control subjects per case from the neighborhoods where HCC patients resided at the time of diagnosis, who were matched to the index case by sex, age (within 5 years), and race (Hispanic white, non-Hispanic white, black). Blood samples (plasma and buffy coat), medical and lifestyle factors were collected from all consenting participants. Total of 65 cases and 60 controls were genotyped in this study Site-5: South Western Dallas Under IRB approval, HCC Cases and controls were prospectively collected since 2015 from the outpatient Liver clinics from Parkland Health and Hospital System and UT Southwestern Medical Center, two large health systems in Dallas TX. A Total of 31 cases and 29 controls were genotyped from site 5. Site-6: Columbia University HCC patients from Columbia are those recruited as part of the Herbert Irving Comprehensive Cancer Center Database Shared Resource which seeks to recruit all cancer patients for potential future studies. The PI is Dr. Katherine Crew AAAL5871. This resource collects sociodemographic, lifestyle and clinical data on patients as well as a blood sample. Those who indicated on their consent form that they would participate in genetic studies were included. Total of 79 case patients with HCC were genotyped from Columbia University. Site-7: University of Michigan The study population included from University of Michigan were included from a prospective study of with chronic HCV infection recruited in Ann Arbor Patients who had under- gone liver transplantation, known coinfection with HIV, life expectancy <12 months due to extra-hepatic illnesses, or were receiving HCV treatment at enrolment, were excluded. Protocol, surveys, and data forms were developed where each enrolled patient completed the same questionnaire All patients provided written informed consent before enrolment in the study. The study was approved by the institutional review board or ethics committee at the University of Michigan. Detailed study description was previously published (7). Total of 44 cases and 347 controls were genotyped Site-8: Veteran Administration Medical Center in Houston This research including written informed consent form was jointly approved by Institutional Review Boards for the Baylor College of Medicine and the Michael E. DeBakey VA Medical Center in Houston, Texas. Study details have been previously published (8). Briefly, we prospectively recruited consecutive HCV-infected veterans prior to their previously scheduled HCV clinic visit at a large tertiary care VA medical center between May 1, 2009 and December 31, 2012. Patients completed a research assistant (RA) administered survey interrogating medical and risk factor history including lifetime alcohol use, had anthropometric measurements taken, and completed a fasting venipuncture for performance of the FibroSure-ActiTest as a measure of hepatic pathology. We restricted our current analysis to individuals who were: (1) White male veterans between 18 and 70 years; (2) had no history of HCC, liver transplant, decompensated liver disease including ascites, dementia, or psychosis; (3) were serologically-confirmed to have chronic HCV and to be negative for both HIV and active HBV infection; (4) were not currently receiving anti-HCV pharmacotherapy; and (5) had FibroSURE testing shown F3/F4 fibrosis consistent with cirrhosis.

  Study phs001744

• 59 CLPD-NK cases WGS & WTS data

  For the cohort of 59 samples, we performed TruSeq DNA PCR-Free whole-genome sequencing library preparation according to manufacturer’s instructions (llumina, ILMN, San Diego, CA) on the automated NGS Star liquid handling platform (Hamilton, Bonaduz, Switzerland) followed by 2x150 bp paired-end sequencing on the HiSeqX or NovaSeq6000 (ILMN). An average coverage of >100x was achieved. For whole transcriptome analysis, the TruSeq Total Stranded RNA kit was used, starting with 250 ng of total RNA, to generate RNA libraries following the manufacturer’s recommendations (ILMN). 2x100bp paired-end reads were sequenced on the NovaSeq 6000 with a median of 50 mio. reads per sample (ILMN).

  Dataset EGAD00001008558

• Cell-free DNA and bone marrow samples from myelodysplastic syndromes

  We have assessed the molecular profile of a cohort of 70 patients with MDS by next-generation sequencing (NGS) using cfDNA and compared the results to paired bone marrow (BM) DNA.

  Dataset EGAD00001008567

• The 5-hydroxymethylcytosine Landscape of Prostate Cancer

  This dataset consists of genome-wide 5hmC methylomes at various stages of prostate cancer, including not only 93 metastases from castration-resistant prostate cancer (mCRPC) patients, but also 5hmC patterns in cell-free DNA (cfDNA). There are 2000 runs in total as fastq files.

  Dataset EGAD00001008462

• Genome-Wide Association Study of Celiac Disease

  Celiac disease (gluten-sensitive enteropathy, celiac sprue) is a common disease with significant morbidity and mortality. It is caused by sensitivity to the dietary protein gluten, resulting in a chronic enteropathy in the small intestine. Celiac disease is now recognized to be a common disease, with reports that the disease frequency is 1:133 in the United States, similar to European estimates. There is recent evidence to suggest that the incidence of the disease is rising. Occult disease is frequently present with minimal classic symptoms or signs. The ratio of symptomatic to asymptomatic celiac disease is estimated to be 1:7. Some complications of celiac disease include lymphoma, osteoporosis, anemia, miscarriages, seizures, vitamin deficiencies, and co-occurrence of other autoimmune diseases. The only treatment is a gluten-free diet, so that recurrence of symptoms and complications may occur after minor dietary indiscretions. Identifying the underlying genetic causes of celiac disease may allow us to identify susceptible individuals, as well as advance new ways to prevent the disease and to treat it once it occurs. Several genome-wide linkage studies and one genome-wide association study of celiac disease have been conducted. Other than the common locus at HLA, few putative celiac disease loci have been replicated between studies, suggesting that the disease is heterogeneous and complex. A portion of the genetic predisposition can be attributed to HLA, but the etiology is likely due to a number of rare, high penetrant genes (as would be identified in linkage analysis) and to more common, low penetrant genes (as would be identified in association studies). The objective of this study is to identify new loci that increase risk to develop celiac disease. We will capitalize on existing North American resources, including three large collections of celiac cases and controls (Aim 1) and an independent set of celiac cases and their families (Aim 3). We propose a comprehensive multi-stage approach, with the following specific aims. In Aim 1, we will conduct a genome-wide association (GWA) study of single nucleotide polymorphisms (SNPs) and copy number variants (CNVs). The GWA will include1900 disease cases and 3400 matched controls, genotyped using the Illumina Human 610-quad chip. Statistical analyses will be performed to test for associations with celiac disease. In Aim 2, we will conduct a combined analysis of our GWA dataset from Aim 1 and a previous GWA dataset to identify additional low-penetrance loci. In Aim 3, we will attempt to replicate significant findings from the GWA study in two independent sample sets. At the conclusion of this study, we expect to have validated a number of SNPs and CNPs from regions in the genome that alter the risk of developing celiac disease. These SNPs may prove useful at both the clinical and research level. The data from the study will be shared with the scientific community.

  Study phs000274

• cfDNA and CDX/PDX methylation profiling in Small Cell Lung Cancer

  This study contains methyl-binding domain sequencing and shallow whole genome sequencing from circulating free DNA (cfDNA) for 79 patients with small cell lung cancer (SCLC) and 78 non-cancer controls. We also sequence genomic DNA (both methyl-binding domain sequencing and shallow whole genome sequencing) from 30 circulating-tumour-cell derived explant models (CDXs, from 23 unique patients with SCLC), 20 patient derived explant models (PDXs, from 10 unique patients with SCLC) and 13 lung tissue samples.

  Dataset EGAD00001008673

• 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

• Genomic signatures define three subtypes of EGFR-mutant stage II-III non-small-cell lung cancer with distinct adjuvant therapy outcomes

  This dataset contains targeted sequencing data of 204 surgical samples from resected NSCLC. Genomic profiling identifies five predictive biomarkers, which is then integrated into the Multiple-gene INdex to Evaluate the Relative benefit of Various Adjuvant therapies (MINERVA) score. The MINERVA score categorizes patients into three subgroups with relative disease-free survival and overall survival benefits from either adjuvant gefitinib or chemotherapy. This study demonstrates that predictive genomic signatures could potentially stratify resected EGFR-mutant NSCLC patients and provide precise guidance towards future personalized adjuvant therapy.

  Dataset EGAD00001008157