10679 results for "fc coins olx Navštivte Buyfc26coins.com Podpora pro profesionální hráče a týmy..zSiZ"

in 24.94 milliseconds.

• Clinical cancer panel sequencing (UCSF500) analysis of TERT promoter duplication in GBM.

  Dataset contains paired-end clinical cancer panel sequencing (UCSF500) data from 2 samples of an initial tumor and one sample of a recurrence from one GBM patient and one sample from a second GBM patient.

  Dataset EGAD00001009286

• eccDNA in maternal plasma

  We developed a new bioinformatics method for detecting the eccDNA in plasma. We revealed that the biological properties between eccDNA and linear DNA are different. eccDNA could be potentially provided as a new class of circulating biomarker.

  Dataset EGAD00001005286

• Single-cell mRNA-sequencing to generate a transcriptomic atlas of RMS

  Single-cell mRNA-sequencing to generate a transcriptomic atlas of soft tissue sarcoma tumors

  Dataset EGAD00001009385

• RNA-seq data from the tumor samples of a head and neck cancer patient

  This dataset contains paired-end RNA sequencing data (2x50 bp) from the three synchronous primary tumors and the recurrence of a head and neck cancer patient.

  Dataset EGAD00001006654

• Bolleboom-Gao peri-tumoral snRNA-seq glioblastoma dataset 2022/A

  Bolleboom-Gao peri-tumoral snRNA-seq glioblastoma dataset 2022/A

  Dataset EGAD00001009964

• Bam files for a metastatic bladder cancer patient with BAP1 variants

  This dataset consists of three bam files (two cell-free DNA and one germline DNA) from a metastatic bladder cancer patient with BAP1 variants. Bam files were generated from targeted Illumina sequencing data.

  Dataset EGAD00001005520

• WGS and RNA-Seq data from a GBM patient PT-MB9777

  WGS and RNA-Seq data from a GBM patient PT-MB9777

  Dataset EGAD00001004253

• Prognostic factors in prostate cancer: deep sequencing pilot project TAPG

  This is a pilot project to determine whether the TAPG FFPE DNA's are suitable for deep sequencing. If successful an investigation of SNP distribution in a larger cohort will follow.

  Dataset EGAD00001001237

• Single Cell Sperm from fathers of Autistic Children

  Single cell sequencing of fathers who have had children with autism and fathers who have had multiple children, but no children with autism. The data was process on a 10X Chromium and sequenced on a NextSeq

  Dataset EGAD00001006292

• A Phase I/IB Study of Ipilimumab or Nivolumab in Patients With Relapsed Hematologic Malignancies After Allogeneic Hematopoietic Cell Transplantation

  Relapse after allogeneic hematopoietic stem cell transplantation (HSCT) is characterized by poor outcomes and novel therapeutic options are urgently needed. Immune checkpoint blockade using CTLA-4 and PD-1 blocking antibodies are a potential concept for reinstating a dormant graft-versus-leukemia (GvL) effect.This study investigated transcriptomic changes in biopsies obtained from patients who received immune checkpoint blockade for relapsed hematologic malignancy post-HSCT and elucidated transcriptional programs associated with successful reinvigoration of GvL. Differential gene expression analysis showed evidence of increased T cell infiltration in biopsies of responders to ipilimumab treatment and demonstrated shared gene programs between GvL and GvHD.

  Study phs002377

• Circulating cell-free DNA methylation profiles as noninvasive multiple sclerosis biomarkers: A proof-of-concept study

  In chronic neurodegenerative diseases such as multiple sclerosis (MS), there is a critical unmet need for cost-effective non-invasive blood biomarkers to concurrently classify disease subtypes, monitor disability severity, and predict long-term progression. In this proof-of-concept study, we performed low-coverage whole-genome bisulfite sequencing (WGBS) on 75 plasma cell-free DNA (cfDNA) samples collected from a well-characterized real-world prospective clinic cohort with longitudinal disability outcome measurements. We assessed the clinical utility of cfDNA methylation profile for differentiating MS patients from non-MS controls, classifying MS subtypes, estimating disability severity, and predicting disease trajectories.

  Study EGAS50000001277

• GCAT | Genomes for life

  The GCAT project is a prospective cohort study that was designed to recruit the general population of Catalonia, the north-east region of Spain. This study is a long-term genomic, environmental and lifestyle cohort project that aims to evaluate and track multiple pathologies as well as biologically related traits. By the end of 2017, the GCAT Study had recruited a total of 20 000 participants aged 40–65 years. Participants who agreed to take part in the study completed a self-administered computer-driven questionnaire, and underwent blood pressure, cardiac frequency and anthropometry measurements. For each participant, blood plasma, blood serum and white blood cells are collected at baseline. The GCAT Study has access to the electronic health records of the Catalan Public Healthcare System. Participants are followed biannually for/during, at least, 20 years after recruitment. Therefore, the GCAT Study offers a unique opportunity to integrate diverse data to allow the identification of novel relations among different biomarkers and conditions. Results may lead to the development of new genetic, genomic, epigenomic and proteomic diagnoses and screening tests, as well as new public health recommendations. The only currently available population-based prospective cohort study in Spain to the date, including more than 4899 genotyped participants and 800 whole genome sequences is now stored in the EGA archive under accession id EGAS00001003018.

  Blog gcat-genomes-for-life

• RNA sequencing of a glioblastoma PDX cohort

  Patient-derived xenograft (PDX) models represent an essential tool for the preclinical evaluation of novel targeted therapies and their combinations. In this project, we molecularly characterized a comprehensive panel of glioma PDX models with well conserved molecular and pathological features over multiple passages. PDX samples were subjected to next generation sequencing (NGS). Characterization of cancer-relevant features including driver mutations or cellular processes was performed using mutational and gene expression data in order to identify potential biomarker or treatment targets in glioblastoma. In summary, we reported a newly established and molecularly characterized panel of glioma PDX models with high relevance for translational preclinical research.

  Study EGAS00001007119

• RNA sequencing data of 257 samples from the CORALLEEN trial

  Early-stage Luminal B breast cancer is frequent and is a major cause of breast cancer death due to its poor prognosis. Our proposal aims to study the biology behind the sensitivity and resistance of Luminal B breast cancer to chemotherapy (CHT) or a non-CHT regimen composed of hormone therapy in combination with ribociclib, a CDK4/6 inhibitor. To accomplish this, we first completed the SOLTI-1402 CORALLEEN phase II trial, a study where 106 patients with early-stage Luminal B breast cancer were randomized to standard neoadjuvant CHT for 6 months, or neoadjuvant letrozole and ribociclib for 6 months. After treatment, patients underwent surgery. The primary results of the study, which showed that the response rate to letrozole+ribociclib was similar to CHT, was reported (Prat et al; Lancet Oncol). Tumor biopsies were available at baseline, week 3 and surgery. A total of 257 samples were analyzed using the Illumina TruSeq Stranded Total RNA w/Ribo Zero Gold with MiSeq in TGL (Sequencer NovaSeq S4/PE/100x)

  Dataset EGAD00001010121

• MorphoITH: A Framework for Deconvolving Intra-Tumor Heterogeneity Using Tissue Morphology

  This study introduces MorphoITH, a framework for deconvolving intra-tumor heterogeneity (ITH) in clear cell renal cell carcinoma (ccRCC) based on tissue morphology from histopathological slides. The study tested MorphoITH's ability to capture different aspects of morphology and to reflect genetic ITH. The data deposited here is derived from a morphology guided multi-regional sequencing dataset used to study the relationship between morphology and genetic evolution. This dataset consists of whole exome sequencing of tumor from multiple sites and adjacent normal samples which were collected from two patients treated in affiliated hospitals of the University of Texas Southwestern Medical Center (UTSW), including Parkland Hospital.

  Study EGAS50000001064

• Sequential single-cell transcriptional and protein marker profiling reveals TIGIT as a marker of CD19 CAR-T cell dysfunction in patients with non-Hodgkin’s lymphoma

  Employed single cell RNA sequencing and protein surface marker profiling of serialCAR-T cell samples from patients with non-Hodgkin’s lymphoma (NHL) to reveal CAR-T cell evolution, identify biomarkers of response, and test for evidence of exhaustion inCAR-T cells of poor responders. At the transcriptional and protein levels, we note the evolution of CAR-T cells toward a non-proliferative, highly-differentiated, andexhausted state that is enriched in CAR-T cells of patients with poor response.Furthermore, we identified the checkpoint receptor TIGIT as a novel prognosticbiomarker and potential driver of CAR-T cell exhaustion.

  Study EGAS00001005356

• 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 of Chronic Pain and Disease

  The Functional Genomics Section (FGS) is a part of the National Institute of Dental and Craniofacial Research (NIDCR) within the National Institutes of Health (NIH). Research at the FGS focuses on understanding the mechanics involved in nociception through both clinical samples from patients with chronic pain and mouse models of pain. Pain is relayed from the periphery to the central nervous system through specialized sensory neurons known as nociceptors. The cell body of nociceptors resides in neuronal structures that branch off of the spinal cord known as dorsal root ganglia (DRG). The DRG is a heterogenous tissue containing not only sensory neurons like nociceptors, but also glial cells, capillaries, fibroblasts, and resident macrophages. The interaction between the nociceptors and these DRG cell types can have a significant role in affecting neuronal hyperexcitability and downstream pain sensitivity. To better understand the cellular factors involved in producing conditions of chronic pain, DRGs from consenting organ donors were collected from individuals experiencing pain disorders such as painful diabetic neuropathy and rheumatoid arthritis. A multi-omics approach is being used to identify molecular mechanisms that lead to pain hypersensitivity in patients with chronic pain.&nbsp;&nbsp;

  Study phs002548

• Whole Exome Sequencing in Alopecia Areata Identifies Rare Mutations in KRT82

  Alopecia areata (AA) is an autoimmune disorder, in which the body's own immune cells attack hair follicels resulting in hair loss. It is a complex genetic disease with 14 associated loci previously identified in our genome-wide association study (GWAS). In the study, we performed the whole-exome sequencing (WES) on 849 AA patients with the aim to identify the novel rare variants in genes contributing to AA susceptibility. We performed gene-collapsing analyses and identified keratin 82 (KRT82 Gene ID: 3888) as the highest associated AA gene in the three rare damaging collapsing models with p&lt;6.7E-07 in one of the models. The KRT82 gene is a hair-specific type II keratin expressed in the hair shaft cuticle during the anagen phase of the hair cycle. We reported the lower expression of KRT82 in AA hair follicles, compared to controls, and the KRT82 expression is absent from the bulb region, the site of AA immune attack. This study emphasizes the significance of using WES and gene collapsing analyses to identify rare variation in a functionally relevant risk gene using a moderate sample size.&nbsp;&nbsp;

  Study phs002632

• Whole Genome Sequencing in the Inner City Asthma Consortium (ICAC) Cohorts

  We performed whole-genome sequencing on individuals from the Asthma Phenotypes in the Inner City (APIC) and Urban Environment and Childhood Asthma (URECA) study cohorts, which consist of children with asthma who live in low-income neighborhoods across 10 U.S. cities. APIC was a one-year, prospective, observational study of children ages 6-17 with asthma. URECA was a prospective, observational study featuring a birth cohort of children with a high risk of developing asthma based on family history. We performed whole-genome sequencing on 1,035 individuals (ages 5-17 yrs; 67% Black, 25% Hispanic; 66% with MD-diagnosed asthma; APIC=508, URECA=527). Sequence read processing, quality control, and variant calling were performed using the Genome Analysis Toolkit suite (GATK v4). Variant call sites were annotated according to the filters applied in our common variant (minor allele frequency &#8805; 1%) association studies, based on predicted false positive rates, genotype quality and depth, and population-adjusted Hardy-Weinberg equilibrium. Principal components of ancestry were calculated using high quality, linkage-disequilibrium-pruned single-nucleotide variants, accounting for subject relatedness, using PC-Air and PC-Relate.

  Study phs002921

• Whole Genome Association Study of Systemic Lupus Erythematosus

  The goal of this collaborative study was to identify new genetic risk factors for Systemic Lupus Erythematosus (SLE). To do this we conducted a genome-wide scan by combining the resources and expertise from a number of SLE researchers to establish a large sample set comprising 1311 SLE cases and 3340 controls. The SLE case samples were genotyped from the following collections: 338 subjects from the Autoimmune Biomarkers Collaborative Network (ABCoN), an NIH/NIAMS funded repository, 141 subjects from the Multiple Autoimmune Disease Genetics Consortium (MADGC), 613 subjects from the University of California San Francisco (UCSF) Lupus Genetics, and 335 subjects from the University of Pittsburgh Medical Center (UPMC), plus 8 samples collected at The Feinstein Institute for Medical Research. A total of 3583 control samples were examined in the association analyses. As part of this project, 1861 control samples were selected and then genotyped from the New York Cancer Project (NYCP), based on self-described ethnicity, gender and age. In addition, genotype data from 1722 control samples (all self-described North Americans of European descent) were obtained from the publicly available iControlDB database (http://www.illumina.com/pages.ilmn?ID=231).

  Study phs000122

• Genetic Epidemiology of Ovarian Cancer Histotypes

  Epithelial ovarian cancer is a highly fatal malignancy with known genetic etiology; however, it is estimated that a substantial portion of narrow sense heritability remains to be discovered. The goal of this research was to use genetic information from distantly related ovarian cancer cases to identify regions of the genome that may harbor rare risk variants for epithelial ovarian cancer. The study was conducted in the setting of the Utah Population Database, a statewide data resource in which extensive ancestry data are linked to Utah Cancer Registry records. Focusing on families with a statistically significant excess risk of epithelial ovarian cancer, we used the Infinium Global Screening Array v.3.0 to generate germline genotyping data for distantly related cases. We then applied Shared Genomic Segment Analysis to each set of related cases to identify genomic regions that may harbor ovarian cancer risk variants. Eleven regions were identified. Genotype data are available through dbGaP for one case from each pedigree. Genotype data from other ovarian cancer cases within the high-risk pedigrees as well as the pedigrees' corresponding structures can be requested and made available with approval from the Utah Resource for Genetic and Epidemiologic Research (RGE).

  Study phs003140

• HTAN Pilot Project: Single-Cell Transcriptomics Toolbox for Fresh and Frozen Human Tumors (Lung, Breast, Ovarian, Melanoma, Neuroblastoma, Sarcoma, Glioblastoma, Glioma, and Leukemia)

  Single cell transcriptomics is a powerful tool to map the complex tumor microenvironment, providing unprecedented resolution into cell types, cell states, cell interactions, and tumor heterogeneity. Depending on their tissue site and whether processing begins from a fresh or frozen sample, different tumors require different optimizations in order to obtain high quality single cell transcriptomic data. In this study, we profiled a range of tumor types, varying in cell-of-origin, solid and non-solid forms, patient ages, and transitions. The tumors also further varied in their tissue site and in their sample collection method. To enable profiling of such diverse samples, we developed a systematic toolbox for single cell RNA-Seq and single nucleus RNA-Seq of fresh and frozen clinical tumor samples. We validated this toolbox for 216,490 cells and nuclei extracted from 39 samples across 23 tumors (some tumors were split into multiple samples). The 23 tumors represented eight unique tumor types. This toolbox comprises both experimental and computational protocols as well as guidelines for comparing and selecting protocols for the biological problem of interest.

  Study phs001983

• Molecular Determinants of Esophageal Cancer in Tanzania

  We describe the genomic profiles of 61 esophageal squamous cell carcinoma (ESCC) cases from Tanzania and compare them to profiles from an existing cohort of ESCC cases from Malawi. We also provide a comparison to ESCC tumors in The Cancer Genome Atlas Program (TCGA). Despite a high burden of ESCC in Eastern Africa, investigations into the genomics in this region are nascent. This represents the largest comprehensive genomic analysis of ESCC from sub-Saharan Africa to date. We observed substantial transcriptional overlap with other squamous histologies via comparison with TCGA PanCan dataset. DNA analysis revealed known mutational patterns, both genome-wide as well as in genes known to be commonly mutated in ESCC. TP53 mutations were the most common somatic mutation in tumors from both Tanzania and Malawi but were detected at lower frequencies than previously reported in ESCC cases from other settings. In a combined analysis, two unique transcriptional clusters were identified: a proliferative/epithelial cluster and an invasive/migrative/mesenchymal cluster. Mutational signature analysis of the Tanzanian cohort revealed common signatures associated with aging and cytidine deaminase activity and an absence of signature 29, which was previously reported in the Malawi cohort.

  Study phs003217

• Whole-Exome Sequencing Study of Diabetic Nephropathy

  To identify rare variants of diabetic kidney disease (DKD), we conducted a whole-exome sequencing (WES) study. This study employed an extreme case&#8211;control design, which included a selection of the 593 most rapidly progressing DKD cases from the Chronic Renal Insufficiency Cohort (CRIC) Study (phs000524). In this two-stage WES study of DKD, participants with DKD from the CRIC were compared with control groups of participants without DKD from another cohort in the first stage. Suggestive signals identified in the first stage were confirmed in the second stage analysis among a diverse population with existing whole-genome sequencing (WGS) data. Generalized linear mixed models, which accounted for genetic relatedness and adjusted for age, sex and ancestry, were used to test associations between single variants and DKD. Gene-based aggregate rare variant analyses were conducted using an optimized sequence kernel association test implemented within our mixed model framework. As a result, we identified four novel gene loci, DIS3L2, KRT6B, ERAP2 and NPEPPS, that achieved exome-wide significance and may play an important role in the DKD disease course. This large WES study provides novel insights into DKD's molecular mechanisms.

  Study phs003429