12504 results for ""non-traditional+communal+storytelling+approach"+novel+segment+noted+in+critical+commentary"

in 53.96 milliseconds.

• Adenoma to Carcinoma transition in Colorectal Cancer

  Although colorectal carcinoma development is well accepted as a step-wise and sequential process, it is commonly investigated using non-sequential adenoma and carcinoma samples. Here we compared molecular pathologies of the earliest carcinoma stages with those in their adenomatous precursors to unravel common and divergent genetic traits between matched neoplasms with a shared evolutionary history but different contemporary biology.

  Study EGAS00001003468

• Genomic landscape of signals of positive natural selection in North Eurasia

  We searched for the genomic signatures of positive selection in the genome-wide data of 432 people from eight different northern Russian populations (Russians from the Archangelsky and Vologdsky regions, Izhemski Komi, Priluzski Komi, Veps, Khanty, Mansi and Nenets) who were genotyped using microarrays for 700,000 SNPs (InfiniumOmniExpress-24v1-2_A1) through testing the extended haplotype homozigosity (EHH).

  Study EGAS00001003955

• Analysis of exonic somatic variants in light-chain amyloidosis (ALA) and ALA concomitant with multiple myeloma

  We aim to provide the very first insight into ALA+MM molecular profiles and compare the results with ALA and with MM. Our detailed study of ALA and ALA+MM represents an important step towards improved understanding of their genetic and transcriptomic background, which is a prerequisite for development of optimal treatment strategies in the future.

  Study EGAS00001004214

• Clinical Activity of Combined Telomerase Vaccination and Pembrolizumab in Advanced Melanoma: Results from a Phase I Trial

  Thirty patients with advanced melanoma were recruited to a clinical trial investigating the therapeutic cancer vaccine, UV1, in combination with pembrolizumab. Whole exome sequencing was performed on melanoma biopsies to determine tumor mutational burden and association with response to therapy. RNA sequencing of matched tumor biopsies to evaluate gene expression profiles at baseline and post-treatment.

  Study EGAS00001007210

• Summary Statistics GWAS SSNS

  Column 1 “rsid”: SNP identifier Column 2 “chromosome”: name of chromosome on which the SNP is located Column 3: “position”: base pair position on the chromosome Column 4 “minor_test_allele”: the base that constitutes the minor allele Column 5 “major_allele”: the base that constitutes the major allele Column 6 “maf”: the frequency of the minor allele, indicated as a fraction of 1 Column 7 “allele_freq_cases”: the minor allele frequency in cases Column 8 “allele_freq_controls”: the minor allele frequency in controls Column 9 “regression_pvalue”: the p-value for the difference in allele frequency between cases and controls Column 10 “odds_ratio”: the odds ratio, as calculated using logistic regression under an additive model with adjustment for the first ten principal components of ancestry

  Dataset EGAD00001008782

• Induction Failure in Childhood and Young Adult T-cell Acute Lymphoblastic Leukemia

  We carried out WGS and RNAseq on a cohort of 48 children and young adults with induction failure in T-cell Acute Lymphoblastic Leukemia (T-ALL) to identify genomic drivers of treatment resistance. The study includes WGS for 33 tumour/normal pairs and 15 tumour-only samples. In addition, there is RNAseq data for 37 cases.

  Dataset EGAD00001009058

• Nuclease deficiencies alter plasma cell-free DNA methylation profiles (Mouse samples)

  The dataset contains sequencing data in wildtype, Dnase1-deficient and Dnase1l3-deficient mice. We performed 2 x 75bp paired-end whole genome bisulfite sequencing of pooled plasma cell-free DNA (cfDNA) and buffy coat genomic DNA. The effects of DNASE1L3 or DNASE1 deficiency on cfDNA methylation was explored in plasma of mice deficient in these nucleases.

  Dataset EGAD00001007751

• RNA-seq analysis refines molecular subtypes of hepatocellular carcinoma

  This work aims to identify homogeneous and robust molecular subtypes in HCC based on a large, homogenous and well-annotated cohort. We performed RNA sequencing (RNA-seq) on 529 HCC from 461 patients collected mainly in France. Based on the consistency between genomic and transcriptomic data, we identified 9 robust HCC subtypes mainly based on driver mutations. We further characterized HCC subtypes using transcriptomic and clinicopathological features. Our study provided a robust molecular classification based on a large HCC dataset from a Western country, improving our understanding of the mechanisms of carcinogenesis and facilitating the development of genome-based precision medicine in HCC.

  Dataset EGAD00001015427

• Bulk RNA-seq dataset of Single cell RNA sequencing reveals induced bifurcated differentiation after RUNX1::RUNX1T1 depletion in patient-derived leukemic blasts

  In this study, we demonstrate that primary AML cells harboring the chromosomal translocation t(8;21) are critically dependent on the corresponding fusion gene, RUNX1::RUNX1T1, to suppress differentiation and maintain stemness. Silencing RUNX1::RUNX1T1 expression using siRNA-loaded lipid nanoparticles induces significant changes in chromatin accessibility, redirecting the leukemia-associated transcriptional network towards a myeloid differentiation program. Single-cell analyses reveal that this transcriptional reprogramming is associated with the depletion of immature stem and progenitor-like cell populations, accompanied by an expansion of granulocytic and eosinophilic/mast cell-like populations with impaired self-renewal capacity.

  Dataset EGAD00001015508

• ENU-CCK-81 cetuximab pilot project

  Cetuximab is a targeted monoclonal antibody against the epidermal growth factor receptor (EGFR) which is used therapeutically for the treatment of KRAS wild-type colorectal cancer (CRC). The Cetuximab sensitive KRAS wild-type CRC cell line NCI-H508 has been treated with a fixed concentration of ENU for 24 hours and then selected with Cetuximab until drug resistant clones were ready to be picked and grown up as sub-clones of the parental cell line. These will have genes causally implicated in cancer sequenced to identify common point mutations in multiple independently derived drug resistant clones as a forward genetic screen for mechanisms of resistance to Cetuximab in CRC.

  Dataset EGAD00001001947

• ENU-NCI-H508-Cetuximab-SecondRound

  Cetuximab is a targeted monoclonal antibody against the epidermal growth factor receptor (EGFR) which is used therapeutically for the treatment of KRAS wild-type colorectal cancer (CRC). The Cetuximab sensitive KRAS wild-type CRC cell line NCI-H508 has been treated with a fixed concentration of ENU for 24 hours and then selected with Cetuximab until drug resistant clones were ready to be picked and grown up as sub-clones of the parental cell line. These will have genes causally implicated in cancer sequenced to identify common point mutations in multiple independently derived drug resistant clones as a forward genetic screen for mechanisms of resistance to Cetuximab in CRC

  Dataset EGAD00001002065

• ENU-NCI-H508 cetuximab fixed concentration project

  Cetuximab is a targeted monoclonal antibody against the epidermal growth factor receptor (EGFR) which is used therapeutically for the treatment of KRAS wild-type colorectal cancer (CRC). The Cetuximab sensitive KRAS wild-type CRC cell line NCI-H508 has been treated with a fixed concentration of ENU for 24 hours and then selected with Cetuximab until drug resistant clones were ready to be picked and grown up as sub-clones of the parental cell line. These will have genes causally implicated in cancer sequenced to identify common point mutations in multiple independently derived drug resistant clones as a forward genetic screen for mechanisms of resistance to Cetuximab in CRC

  Dataset EGAD00001001948

• GWG in T1DM - DAC

  Dac EGAC00001001580

• TCRseq in cancers DAC

  Dac EGAC00001002235

• ID1 in glioblastoma

  Study EGAS00001003711

• CHIP and LOY in AD

  Dac EGAC00001003606

• 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

• Translational Research Investigating Underlying disparities in acute Myocardial infarction Patients' Health status (TRIUMPH)

  The Translational Research Investigating Underlying disparities in acute Myocardial infarction Patients&#39; Health status (TRIUMPH) cohort is a cohort of 4340 patients prospectively enrolled after hospitalization for acute myocardial infarction (AMI) between June 1, 2005, and December 31, 2008 from 24 U.S. hospitals. Consenting patients had detailed chart abstractions of their medical history and processes of inpatient care, supplemented with a detailed baseline interview. Detailed genetic and metabolic data were obtained at hospital discharge in 2979 (69%) and 3013 patients (69%), respectively. Centralized follow-up interviews sought to quantify patients&#39; post-discharge care and outcomes, with a focus on their health status (symptoms, function, and quality of life). Reprinted from [Article Citation], with permission from [Publisher].

  Study phs001518

• Therapeutic Targeting of ATR Yields Durable Regressions in High Replication Stress Tumors

  Patients with relapsed or recurrent small cell lung cancer or extra-pulmonary small cell cancers were enrolled on an investigator-initiated, single-arm, phase 2 trial (NCT02487095) combining an ATR inhibitor M6620 (VX-970, berzosertib) administered at 210 mg/m2 intravenously over 60 minutes on day 2 and day 5, and topotecan 1.25 mg/m2 intravenously over 30 minutes every 23 hours on days 1 through 5, with a support of pegfilgrastim 6mg subcutaneously on day 6 in 21-day cycles. Tumor samples were collected either just before starting the treatment or before starting treatment prior to be enrolled in the trial. Whole exome and RNA were sequenced to evaluate genomic and transcriptomic characteristics associated with the response to the combination treatment.

  Study phs002327

• De Novo Characterization of Cell-Free DNA Fragmentation Hotspots in Plasma Whole-Genome Sequencing

  The raw sequencing data deposited here are low-coverage (~1X) whole-genome sequencing (WGS) of plasma cell-free DNA (cfDNA). The purpose is to validate the performance of early-stage cancer diagnosis in the Zhou et al. 2020 BioRxiv paper, mainly for two types of cancer: early-stage liver cancer and breast cancer. The cases and controls are matched with age, gender, smoking history, and alcohol usage. We developed a computational method to identify the cfDNA fragmentation hotspots from pooled low-coverage cfDNA WGS data. We found the cfDNA fragmentation hotspots are highly enriched in regulatory regions, such as open chromatin regions. The signals from these regions can help the diagnosis of early-stage cancers and their tissues-of-origin.

  Study phs003062

• Impaired HLA Class I Antigen Processing and Presentation as a Mechanism of Acquired Resistance to Immune Checkpoint Inhibitors in Lung Cancer

  Mechanisms of acquired resistance to immune checkpoint inhibitors (ICIs) are poorly understood. The purpose of this study was to investigate whether alterations in genes encoding components of the HLA Class I antigen processing and presentation machinery or interferon signaling pathways play a role in acquired resistance to PD-1 or PD-L1 antagonistic antibodies. Whole exome sequencing was performed on tumor samples collected from patients with advanced non-small cell lung cancer at the time of resistance to PD-1 axis inhibitors and on available matched pre-treatment and normal samples. Patient-derived xenografts successfully established from the ICI-resistant samples were also exome sequenced. Additionally, RNA sequencing was performed on cases with sufficient tissue.

  Study phs001464

• RNA sequencing, ATACseq, and TCR-seq of Tfh cells and CXCR5- CD4+ T cells in HIV infected lymph nodes

  The high dimensional analyses of CD4+ T cells in human lymph nodes are case-based analyses of the TCR repertoire, transcriptome, and epigenetic signatures of various CD4+ T cells in human lymph nodes. The study aims to determine clonal overlap between phenotypically distinct CD4+ T cells and the similarities between these populations on transcriptional and epigenetic levels. This study performs TCR repertoire sequencing using Molecular Identifier Clustering-based Immune Repertoire Sequencing (MIDCIRS). We found clonal overlap between a population of CXCR5- T cells and follicular helper T (Tfh) cells. We also show epigenetic and transcriptional similarities between CXCR5-PD-1+ T cells and Tfh cells. This study shares an overlapping set of donors with phs001548.

  Study phs001849

• NGS-based monitoring of the T cell receptor repertoire in living donor kidney transplant patients undergoing combination cell therapy

  Tolerance induction through mixed chimerism is a promising approach to achieve long term graft patency without or only low dose maintenance immunosuppression. In this phase I/IIa academic trial kidney transplant recipients in the case group were co-transplanted with bone marrow from the same donor and received an autologous cell product. The control group did not receive donor bone marrow or an autologous cell product. Peripheral blood mononuclear cells were collected at multiple timepoints before and after transplantation and the recipients native T-cell receptor (TCR) repertoire at time points 0, 1, 3 and 6 months after transplantation as well as their donor reactive TCR repertoire were analysed using NGS-based TCR sequencing.

  Study EGAS50000000210

• Multidimensional and Longitudinal Immune Profiling of Sepsis in Uganda

  We conducted a prospective, observational cohort study of adults (RESERVE-U-2-TOR) admitted to Tororo General Hospital in eastern Uganda with severe, undifferentiated infection (i.e., suspected sepsis). Briefly, whole-blood samples were collected in PAXgene blood RNA tubes (PreAnalytiX, Qiagen, Germantown, MD, USA), from which RNA was extracted using PAXgene Blood RNA Kits (cat. no. 762164) (Qiagen). Sequencing libraries were constructed with the NEBNext Ultra II RNA Library Preparation Kit for Illumina, after which libraries were multiplexed and sequenced on the Illumina NovaSeq X Plus platform (Illumina, Inc, San Diego, CA). Data from this study available through dbGaP include raw RNA-Seq data generated from whole-blood samples collected upon RESERVE-U-2-TOR study enrollment (N=274).

  Study phs003914

• CRISPR-screening identifies mechanisms of resistance to KRASG12C and SHP2 inhibitor combinations in non-small cell lung cancer

  Although KRASG12C inhibitors show clinical activity in patients with KRAS G12C mutated NSCLC and other solid tumor malignancies, response is limited by multiple mechanisms of resistance. The KRASG12C inhibitor JDQ443 shows enhanced preclinical antitumor activity combined with the SHP2 inhibitor TNO155, and the combination is currently under clinical evaluation. To identify rational combination strategies that could help overcome or prevent some types of resistance, we evaluated the duration of tumor responses to JDQ443 �� TNO155, alone or combined with the PI3K�� inhibitor alpelisib and/or the CDK4/6 inhibitor ribociclib, in xenograft models derived from a KRASG12C-mutant NSCLC line and investigated the genetic mechanisms associated with loss of response to combined KRASG12C/SHP2 inhibition.

  Study JGAS000643