15138 results for "cancer studies using rna-seq"

in 25.34 milliseconds.

• UK10K NEURO ASD BIONED

  In the UK10K project we propose a series of complementary genetic approaches to find new low frequency/rare variants contributing to disease phenotypes. These will be based on obtaining the genome wide sequence of 4000 samples from the TwinsUK and ALSPAC cohorts (at 6x sequence coverage), and the exome sequence (protein coding regions and related conserved sequence) of 6000 samples selected for extreme phenotypes. Our studies will focus primarily on cardiovascular-related quantitative traits, obesity and related metabolic traits, neurodevelopmental disorders and a limited number of extreme clinical phenotypes that will provide proof-of-concept for future familial trait sequencing. We will analyse directly quantitative traits in the cohorts and the selected traits in the extreme samples, and also use imputation down to 0.1% allele frequency to extend the analyses to further sample sets with genome wide genotype data. In each case we will investigate indels and larger structural variants as well as SNPs, and use statistical methods that combine rare variants in a locus or pathway as well as single-variant approaches. The BioNED (Biomarkers for Childhood onset neuropsychiatric disorders) study has been carrying out detailed phenotypic assessments evaluating children with an autism spectrum disorder. These assessments included ADI-R, ADOS, neuropsychology, EEG etc. There are 56 DNA samples from this study (25 extracted from blood). For further information with regard to this cohort please contact Patrick Bolton (patrick.bolton@kcl.ac.uk).

  Study EGAS00001000111

• UK10K NEURO ASD GALLAGHER

  In the UK10K project we propose a series of complementary genetic approaches to find new low frequency/rare variants contributing to disease phenotypes. These will be based on obtaining the genome wide sequence of 4000 samples from the TwinsUK and ALSPAC cohorts (at 6x sequence coverage), and the exome sequence (protein coding regions and related conserved sequence) of 6000 samples selected for extreme phenotypes. Our studies will focus primarily on cardiovascular-related quantitative traits, obesity and related metabolic traits, neurodevelopmental disorders and a limited number of extreme clinical phenotypes that will provide proof-of-concept for future familial trait sequencing. We will analyse directly quantitative traits in the cohorts and the selected traits in the extreme samples, and also use imputation down to 0.1% allele frequency to extend the analyses to further sample sets with genome wide genotype data. In each case we will investigate indels and larger structural variants as well as SNPs, and use statistical methods that combine rare variants in a locus or pathway as well as single-variant approaches. This is an Irish sample set of individuals with ASD (approximately 50% with comorbid intellectual disability). Individuals have been diagnosed with ADI/ ADOS, measures of cognition/ adaptive function. They represent a more severe, narrowly defined cohort of ASD subjects. Family histories are available for some with measures of broader phenotype. For further information on this cohort please contact Nadia Bolshakova (bolshakn@tcd.ie).

  Study EGAS00001000112

• Performance comparison of three DNA extraction kits on human whole-exome data from formalin-fixed paraffin-embedded normal and tumor samples

  We generated 42 human whole-exome sequencing data sets from fresh-frozen (FF) and FFPE samples. These samples include normal and tumor tissues from two different organs (liver and colon), that we extracted with three different FFPE extraction kits (QIAamp DNA FFPE Tissue kit and GeneRead DNA FFPE kit from Qiagen, Maxwell\textsuperscript{TM} RSC DNA FFPE Kit from Promega). Variant calling analysis shows a very high rate of concordance between matched FF / FFPE pairs and equivalent performance for the three kits we analyzed. We find a significant variation in the difference of total number of variants called between FF and FFPE samples for the three different FFPE DNA extraction kits. Coverage analysis shows that FFPE samples have less good indicators than FF samples, yet the coverage quality remains above accepted thresholds. We detect limited but significant variations in coverage indicator values between the three FFPE extraction kits. Globally, the GeneRead and QIAamp kits have better variant calling and coverage indicators than the Maxwell kit on the samples used in this study, although this kit performs better on some indicators and has advantages in terms of practical usage. Taken together, our results confirm the potential of FFPE samples analysis for clinical genomic studies, but also indicate that the choice of a FFPE DNA extraction kit should be done with careful testing and analysis beforehand in order to maximize the accuracy of the results.

  Study EGAS00001002631

• Identification of a Fumarate-Hydratase Deficient-like RCC Subtype with Convergent Pathway Alterations

  The development of molecularly targeted therapies builds upon the identification of tumor clades with shared molecular abnormalities. Hereditary leiomyomatosis and renal cell carcinoma (HLRCC) is a familial syndrome resulting from germline mutation of the two-hit tumor suppressor gene, Fumarate Hydratase (FH). HLRCC renal tumors present often in young adults, exhibit unique histological features and are particularly aggressive. HLRCC is uncommon and poorly understood, and whether there are sporadic renal tumors with similar characteristics, is unclear. Notably, FH can also be inactivated somatically in RCC, and should be included among FH-deficient (FHD) kidney tumors. We identified a tumor clade without FH mutations but with similar morphological and molecular characteristics as well as aggressive clinical behavior, which we name FHDL (FHD-like). We show that FHD/FHDL tumors represent a unique subtype of CIMP (CpG Island Methylator Phenotype) with the highest levels of overall genome methylation and CDKN2A silencing. FHD/FHDL tumors are characterized by convergent activation of the Hippo pathway as determined by frequent and mutually exclusive mutations in NF2 and PTPN14. AKR1B10, an NRF2 target, was upregulated in FHD/FHDL tumors as well as GATA3, which suggests a shared origin in the renal medulla and is consistent with topological studies. There is loss of 5-hydroxymethylcytosine in both FHD and FHDL tumors. These data define a group of particularly aggressive renal cancers with shared molecular features and potential targets for therapeutic intervention.

  Study EGAS00001002646

• Initial whole genome sequencing of plasma cell neoplasms in First Responders exposed to the World Trade Center attack of September 11, 2001

  The World Trade Center (WTC) attack of September 11, 2001 created an unprecedented environmental exposure to known and suspected carcinogens. High incidence of multiple myeloma (MM) and precursor conditions has been reported among first responders to the WTC disaster. To expand on our prior screening studies, and to characterize the genomic impact of the exposure to known and potential carcinogens in the WTC debris, we were motivated to perform whole genome sequencing (WGS) of WTC first responders and recovery workers who developed a plasma cell disorder after the attack. PATIENTS AND METHODS: We performed WGS of 9 CD138-positive bone marrow mononuclear samples from patients who were diagnosed with plasma cell disorders after the WTC disaster. RESULTS: No significant differences were observed in comparing the post-WTC driver and mutational signatures landscape with 110 previously published WGS from 56 patients with MM and the CoMMpass WGS cohort (n=752). Leveraging constant activity of the single base substitution mutational signatures 1 and 5 over time, we estimated that tumor-initiating chromosomal gains were windowed to both pre- and post-WTC exposure. CONCLUSIONS: Although limitations in sample size preclude any definitive conclusions, our findings suggest that the observed increased incidence of plasma cell neoplasms in this population is due to complex and heterogeneous effects of the WTC exposure that may have initiated or contributed to progression of malignancy.

  Study EGAS00001004467

• The Southern African Human Genome Programme

  The Southern African Human Genome Programme (SAHGP) is a national and regional initiative that aims to unlock the unique genetic character of southern African populations. Its vision is to improve quality of life through understanding human genetic diversity. It is timely to advance the SAHGP initiative since global genomic initiatives are increasingly pointing to populations in Africa, more specifically the San and Khoe from southern Africa, as harbouring the most ancient genetic signatures among the living populations of the world. Studies on African populations have already generated a wealth of information upon which the SAHGP can build. This information will be used to promote and support genomic research programmes both nationally and regionally to address critical questions that would benefit the people of our region. The SAHGP aims to make a significant contribution to the understanding of DNA variation among southern Africans and how this impacts on the health of the people of this region. Aims of the SAHGP: To develop capacity for genomic research in southern Africa; To establish sustainable resources for genomic research in the region; and To translate knowledge and information into improvements in human health in the region. The objective is to derive the maximum benefit from the SAHGP, and that the data should be widely shared with the scientific community for the benefit of the people of the sub-continent and beyond.

  Study EGAS00001002639

• 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

• Transcriptome atlas of brain organoid developent

  Single-cell Cut&Tag of three histone modifications and chromatin accessibility over a timecourse of brain organoid development from pluripotency. We profiled 5 time points of brain organoid development and 2 time points of retinal organoid development. We used scRNA-seq to profile transcriptome. Library preparation was carried out with the 10x genomics platform.

  Dataset EGAD50000000223

• BIOMIROX

  This dataset regroups RNAseq of paired primary colorectal cancers and liver metastases extracted from 113 patients In Paris and Besançon University Hospitals. 216 FASTQ files from single-end 3' PolyA (QuantSeq 3′mRNA-Seq Kit FWD for Illumina (Lexogen)) RNAseq samples were generated On NOVASEQ 6000 (ILLUMINA).

  Dataset EGAD50000000443

• MissionBio single cell DNA and protein seq for 2 samples

  This dataset contains MissionBio Targeted single-cell DNA and Protein sequencing data from a primary sample and a patient-derived xenograft (PDX) model, which is used to investigate the clonal evolution in the FOXF1/FENDRR ALL subtype. All the 2 samples are in bam file type.

  Dataset EGAD50000001793

• Sequencing data

  WES: (7 samples, BAM files), scRNA-Seq (4 samples, BAM files), TruSight (56 samples, BAM or FASTQ files)

  Dataset EGAD00001007749

• KCL PRECSION Mutations targeted-seq

  105 Normal, DCIS and recurrences samples target-sequenced

  Dataset EGAD00001008376

• Mixture of 4

  Mixture of 4 unrelated individuals sequenced by 10x as a scRNA-seq. The dataset was then processed by Cell Ranger and deconvoluted to yield each individuals genetic profile. The clustering of SNPs is submitted as the processed file. The Sequencing fastqs are submitted as unprocessed files.

  Dataset EGAD00001008724

• Mixture of 3

  Mixture of 3 unrelated individuals sequenced by 10x as a scRNA-seq. The dataset was then processed by Cell Ranger and deconvoluted to yield each individuals genetic profile. The clustering of SNPs is submitted as the processed file. The Sequencing fastqs are submitted as unprocessed files.

  Dataset EGAD00001008729

• Anonymized germline variants of prospectively characterized clinical cancer specimens

  These clinical specimens represent solid tumors and matched blood controls that were collected as part of patients&#39; routine care at Memorial Sloan Kettering Cancer Center. They were sequenced on the targeted platform MSK-IMPACT. Here, we performed germline variant calling on the normal blood specimens and assessed their zygosity in the concomitant tumor specimens for comprehensive exploration of the landscape of pathogenic germline variants in patients with advanced cancer.

  Study phs001858

• Circulating tumour DNA (ctDNA) data of High Grade Serous Ovarian Cancer Patients

  This study contains circulating tumour DNA (ctDNA) data derived from longitudinal plasma samples of High Grade Serous Ovarian Cancer (HGSC) patients belonging to the DECIDER study (NCT04846933). Ovarian cancer kills more than 40 000 women in Europe each year, and HGSC is the most common and most difficult to treat subtype of this disease. This study contains different sequencing datasets with samples from different stages during the treatment of the patients.

  Study EGAS50000000674

• Matched_breast_cancer_fusion_gene_study

  Genomic libraries (500 bps) will be generated from total genomic DNA derived from 40 breast cancer samples and subjected to total of eight lanes of 37 bp, paired end sequencing on the llumina GA. Paired reads will be mapped to build 37 of the human reference genome to facilitate the generation of genome wide copy number information, and the identification of novel rearranged cancer genes and gene fusions.

  Study EGAS00001000031

• Understanding Determinants of Racial Disparities in Lung Cancer Incidence

  This is a nested case-control study designed to evaluate the association between common genetic variants and the risk of lung cancer. The study included 1258 cases and 1252 controls selected from the Southern Community Cohort Study (SCCS), a large, prospective observational cohort. Cases were identified from cancer registries across the catchment area of the SCCS. Cases and controls were frequency matched on age, sex, race, and enrollment site (community health center vs general population).

  Study phs003789

• MOSAIC - Multi-Omics Spatial Atlas In Cancer

  MOSAIC is a collaborative initiative founded by Owkin, Lausanne University Hospital (CHUV), Charité Universitätsmedizin Berlin, University Hospital Erlangen (UKER), Gustave Roussy Institute in Paris, and University of Pittsburgh. The goal of MOSAIC is to build the largest collection of spatial omics data in cancer. By integrating comprehensive high quality clinical annotations with advanced deep profiling techniques, MOSAIC aims to uncover novel cancer subtypes and identify key drug targets and biomarkers within them.

  Study EGAS50000000689

• Genome- and epigenome-driven evolutionary dynamics of tumour-immune coevolution within primary colorectal cancers

  This data includes targeting sequencing of the immunopeptidome from 94 samples, usually individual laser microdissected cancer glands, from 11 cases of colorectal cancer. The data were used to test for evidence of immunoediting (antigen depletion) in colorectal cancers. The full data description is provided in the original manuscript https://pmc.ncbi.nlm.nih.gov/articles/PMC10888923/. The 11 colorectal cancers had been previously multiomic profiled with data described in the parts of this disposition.

  Study EGAS50000001154