1427 results for "600k fc points Navštivte Buyfc26coins.com Společnost s dobrou pověstí v české komunitě..MIpb"

in 14.91 milliseconds.

• Genome-Wide Association Study of Patients with Coccidioidomycosis

  BackgroundValley Fever is typically an infection of the lungs caused by the fungi Coccidioides immitis and Coccidioides posadasii. The incidence of Coccidioidomycosis (CM), or infection with Coccidioides, has dramatically increased over the last 20 years. This is particularly true in the Southwest of the United States, where people often breathe fungal spores that arise from the soil. Reasons for increased infection rates are thought to include population growth and construction in these endemic regions, an increase in the number of people whose immune systems are compromised due to infection or treatment with drugs required for organ transplants, climate change, as well as improved testing practices and greater physician awareness. Mild CM most commonly presents itself with flu-like symptoms and rashes, which can last weeks to months. Individuals with compromised immune systems, specifically-- substantial suppression of the immune cells known as T cells, can develop severe pulmonary and disseminated disease. Infection that remains localized to the lungs is referred to as pulmonary disease, but when the infection spreads out of the lungs into other parts of the body it represents a more serious condition referred to as a disseminated disease, or disseminated CM. In nature, Coccidioides spp. exists as mold and lives in dust and soil. When the contaminated soil or dust is disturbed by human activity, animals, or weather, the Coccidiodies spores are released into the air. Airborne spores are taken up by breathing and settle in the lungs. Once in the moist and warm environment of the lung, spores transform into spherules, which divide and become filled with smaller spores, called endospores. When the spherules get large enough, they rupture and release these endospores, which can spread and disseminate to surrounding tissue. The cycle then repeats itself as these endospores develop into new spherules3. Different ethnic groups have been described to vary in their susceptibility to developing disseminated CM after initial infection with Coccidioides. For example, evidence suggests that African-American and Filipino patients suffer the disseminated disease at a greater rate than other ethnicities. The suggestion that race plays a role in the clinical expression of the disease is still a source of debate amongst the scientific community and any genetic mechanisms responsible for these differences have yet to be fully elucidated. If our genetic makeup influences our ability to limit the spread of infection, finding which DNA differences cause these variances could provide clues to how the body successfully fights infection, and provide opportunities to boost the body’s ability to do this. Further, if we are able to identify the specific genetic risk factors that correlate with the development of disseminated infection, physicians could perform genetic screenings to identify high-risk patients and provide them with preemptive antifungal therapy prior to developing disseminated disease.The genome, made up of DNA, contains all of the information needed for humans to develop and grow. Genome-wide association studies (GWAS) allow us to look for inherited differences that are more common between people who share a particular trait, for example, height or susceptibility to certain diseases, compared to those who do not share the trait. Although some traits and diseases are controlled by a single gene, the majority are influenced by contribution from several, or even many, different genes. To find evidence of genes that contribute to specific traits, GWAS typically compares genome information from large numbers of people who have a particular disease (referred to as “cases”) looking for DNA sequences that are common among these samples, and are different from DNA sequences seen in large numbers of people who lack the trait, but are as much like the cases as possible (referred to as “controls”). The DNA sequence data from each group, cases versus controls, are analyzed to see if there are specific genomic differences that tend to be associated with the disease. MethodsTwo separate GWAS approaches were taken to look for genetic differences that could be responsible for the observed differences between the different patient populations we are studying. The first method, known as genotyping, scans for differences at a set of positions across the genome, which includes both the genes that encode our proteins and the larger amount of DNA that does not. The second method, known as exome sequencing, allows us to compare the entire sequence of the portion of the genome that codes for proteins.  For this study, DNA from patients with either pulmonary or disseminated CM were genotyped and exome sequenced to look for DNA differences that are associated with one condition or the other. All patients were at least 18 years old, had no evidence of immunosuppression, and had proven or probable pulmonary coccidioidomycosis according to established diagnostic criteria. Of these patients, a subset demonstrated disseminated disease, i.e., they showed evidence of coccidioidal infection outside of the thorax by biopsy/aspiration, had radiographic imaging, and show positive coccidioidal serology. Our criteria for including patients with the pulmonary disease were that they must not require ongoing antifungal treatment or show evidence of active CM (in skin test positive patients), show no evidence of extrapulmonary dissemination, and have no evidence of ongoing pulmonary infection (pulmonary nodules are accepted) beyond six months from diagnosis.Patient DNA was purified from blood or from sputum samples by the labs of our collaborators, Drs. George Thompson (UC Davis School of Medicine) and John Galgiani (University of Arizona Health Sciences). Genome-wide association (GWAS) analysis was carried out to look for candidate loci associated with pulmonary versus disseminated disease, taking into account the population structure of the samples. Single nucleotide or insertion/deletion variants were identified from whole-exome sequences (WES) using the Picard/BWA/GATK pipeline. ResultsTable 1. Pulmonary versus Disseminated Cases of Coccidiomycosis for GWAS, Sorted by EthnicityEthnicityPulmonary CasesDisseminated CasesAsian85Black/African American1664Caucasian/White4015Filipino03Hispanic/Latino3414Indian21Mexican American1039Pacific Islander01Samoan03Vietnamese10Unknown16917More than one race02Total373134Table 1 shows the number of samples analyzed from patients with pulmonary versus disseminated disease, and patient ethnicity, where known. In all, we worked with 507 samples, including 134 samples from patients with disseminated disease and 373 samples from patients with pulmonary disease. Of these, 505 samples were genotyped using the Multi-Ethnic Global Array from Illumina Inc. In addition, we were able to generate whole-exome sequence from 498 patient samples. No significant associations were detected that differed between samples from patients with pulmonary versus disseminated disease; that is, no particular DNA sequences were found to be significantly enriched in patients with disseminated disease compared to patients with pulmonary disease. The ability to detect genetic association between specific sequences and genetically determined traits is influenced by several factors, including how many patient samples are available to compare, how many different genes contribute to the trait and how strong their contributions are. When the number of genes is small and the contribution of each gene is great, smaller numbers of patient samples are needed to detect an association. When more genes are involved, or the contribution from each gene is more modest, larger numbers of patient samples must be examined. While we were not able to detect any associated within this study, it does not mean that subsequent studies would not find this connection. Our study suggests significantly more samples should be analyzed in further studies.Whole-exome sequences were generated from 498 samples and were aligned to reference sequences to identify positions where the sequences differed from the reference. These data are being analyzed to determine if any variants are associated with pulmonary, versus disseminated, disease. 

  Study phs002170

• Framingham Cohort

  Startup of Framingham Heart Study. Cardiovascular disease (CVD) is the leading cause of death and serious illness in the United States. In 1948, the Framingham Heart Study (FHS) -- under the direction of the National Heart Institute (now known as the National Heart, Lung, and Blood Institute, NHLBI) -- embarked on a novel and ambitious project in health research. At the time, little was known about the general causes of heart disease and stroke, but the death rates for CVD had been increasing steadily since the beginning of the century and had become an American epidemic. The objective of the FHS was to identify the common factors or characteristics that contribute to CVD by following its development over a long period of time in a large group of participants who had not yet developed overt symptoms of CVD or suffered a heart attack or stroke. Design of Framingham Heart Study. In 1948, the researchers recruited 5,209 men and women between the ages of 30 and 62 from the town of Framingham, Massachusetts, and began the first round of extensive physical examinations and lifestyle interviews that they would later analyze for common patterns related to CVD development. Since 1948, the subjects have returned to the study every two years for an examination consisting of a detailed medical history, physical examination, and laboratory tests, and in 1971, the study enrolled a second-generation cohort -- 5,124 of the original participants' adult children and their spouses -- to participate in similar examinations. The second examination of the Offspring cohort occurred eight years after the first examination, and subsequent examinations have occurred approximately every four years thereafter. In April 2002 the Study entered a new phase: the enrollment of a third generation of participants, the grandchildren of the original cohort. The first examination of the Third Generation Study was completed in July 2005 and involved 4,095 participants. Thus, the FHS has evolved into a prospective, community-based, three generation family study. The FHS is a joint project of the National Heart, Lung and Blood Institute and Boston University. Research Areas in the Framingham Heart Study. Over the years, careful monitoring of the FHS population has led to the identification of the major CVD risk factors -- high blood pressure, high blood cholesterol, smoking, obesity, diabetes, and physical inactivity -- as well as a great deal of valuable information on the effects of related factors such as blood triglyceride and HDL cholesterol levels, age, gender, and psychosocial issues. Risk factors have been identified for the major components of CVD, including coronary heart disease, stroke, intermittent claudication, and heart failure. It is also clear from research in the FHS and other studies that substantial subclinical vascular disease occurs in the blood vessels, heart and brain that precedes clinical CVD. With recent advances in technology, the FHS has enhanced its research capabilities and capitalized on its inherent resources by the conduct of high resolution imaging to detect and quantify subclinical vascular disease in the major blood vessels, heart and brain. These studies have included ultrasound studies of the heart (echocardiography) and carotid arteries, computed tomography studies of the heart and aorta, and magnetic resonance imaging studies of the brain, heart, and aorta. Although the Framingham cohort is primarily white, the importance of the major CVD risk factors identified in this group have been shown in other studies to apply almost universally among racial and ethnic groups, even though the patterns of distribution may vary from group to group. In the past half century, the Study has produced approximately 1,200 articles in leading medical journals. The concept of CVD risk factors has become an integral part of the modern medical curriculum and has led to the development of effective treatment and preventive strategies in clinical practice. In addition to research studies focused on risk factors, subclinical CVD and clinically apparent CVD, Framingham investigators have also collaborated with leading researchers from around the country and throughout the world on projects involving some of the major chronic illnesses in men and women, including dementia, osteoporosis and arthritis, nutritional deficiencies, eye diseases, hearing disorders, and chronic obstructive lung diseases. Genetic Research in the Framingham Heart Study. While pursuing the Study's established research goals, the NHLBI and the Framingham investigators has expanded its research mission into the study of genetic factors underlying CVD and other disorders. Over the past two decades, DNA has been collected from blood samples and from immortalized cell lines obtained from Original Cohort participants, members of the Offspring Cohort and the Third Generation Cohort. Several large-scale genotyping projects have been conducted in the past decade. Genome-wide linkage analysis has been conducted using genotypes of approximately 400 microsatellite markers that have been completed in over 9,300 subjects in all three generations. Analyses using microsatellite markers completed in the original cohort and offspring cohorts have resulted in over 100 publications, including many publications from the Genetics Analysis Workshop 13. Several other recent collaborative projects have completed thousands of SNP genotypes for candidate gene regions in subsets of FHS subjects with available DNA. These projects include the Cardiogenomics Program of the NHLBI's Programs for Genomics Applications, the genotyping of ~3000 SNPs in inflammation genes, and the completion of a genome-wide scan of 100,000 SNPs using the Affymetrix 100K Genechip. Framingham Cohort Phenotype Data. The phenotype database contains a vast array of phenotype information available in all three generations. These will include the quantitative measures of the major risk factors such as systolic blood pressure, total and HDL cholesterol, fasting glucose, and cigarette use, as well as anthropomorphic measures such as body mass index, biomarkers such as fibrinogen and CRP, and electrocardiography measures such as the QT interval. Many of these measures have been collected repeatedly in the original and offspring cohorts. Also included in the SHARe database will be an array of recently collected biomarkers, subclinical disease imaging measures, clinical CVD outcomes as well as an array of ancillary studies. The phenotype data is located here in the top-level study phs000007 Framingham Cohort. To view the phenotype variables collected from the Framingham Cohort, please click on the "Variables" tab above. The Framingham Cohort is utilized in the following dbGaP substudies. To view genotypes, analysis, expression data, other molecular data, and derived variables collected in these substudies, please click on the following substudies below or in the "Substudies" section of this top-level study page phs000007 Framingham Cohort. phs000342 Framingham SHARe phs000282 Framingham CARe phs000363 Framingham SABRe phs000307 Framingham Medical Resequencing phs000401 Framingham ESP Heart-GO phs000651 Framingham CHARGE-S phs000724 Framingham DNA Methylation phs001610 Framingham T2D-GENES phs002558 Framingham ADSP phs002559 Framingham BRIDGET phs002560 Framingham Cholesterol phs002611 Framingham Post-Mortem Brain Tissue phs002938 Framingham Molecular QTL The unflagging commitment of the research participants in the NHLBI FHS has made more than a half century of research success possible. For decades, the FHS has made its data and DNA widely available to qualified investigators throughout the world through the Limited Access Datasets and the FHS DNA Committee, and the SHARe database will continue that tradition by allowing access to qualified investigators who agree to the requirements of data access. With the SHARe database, we continue with an ambitious research agenda and look forward to new discoveries in the decades to come.

  Study phs000007

• HBCC Postmortem Psychiatric Molecular Studies

  This postmortem study examines molecular, genetic and epigenetic signatures in the brains of hundreds of subjects with or without mental disorders conducted by the DIRP NIMH Human Brain Collection Core (HBCC). The brain tissues are obtained under protocols approved by the CNS IRB (NCT00001260), with the permission of the next-of-kin (NOK) through the Offices of the Chief Medical Examiners (MEOs) in the District of Columbia, Northern Virginia and Central Virginia. Additional samples were obtained from the University of Maryland Brain and Tissue Bank (contracts NO1-HD-4-3368 and NO1-HD-4-3383) (http://www.medschool.umaryland.edu/btbank/ and the Stanley Medical Research Institute: http://www.stanleyresearch.org/brain-research/). Clinical characterization, neuropathological screening, toxicological analyses, and dissections of various brain regions were performed as previously described (Lipska et al. 2006; PMID: 16997002). All patients met DSM-IV criteria for a lifetime Axis I diagnosis of psychiatric disorders including schizophrenia or schizoaffective disorder, bipolar disorder and major depression. Controls had no history of psychiatric diagnoses or addictions. SNP array: Array-based genotyping was performed on most samples published in this collection. The number of SNPs assayed via Illumina chips varied between 650,000 and 5 Million. Cerebellar tissue was generally used for genotyping studies. # Diagnosis SNP Array 1 Anxiety Disorder 1 2 Autism Spectrum Disorder 13 3 Bipolar Disorder 114 4 Control 387 5 Eating Disorder (ED) 2 6 Major Depressive Disorder (MDD) 186 7 Obsessive Compulsive Disorder (OCD) 5 8 Post-Traumatic Stress Disorder (PTSD) 0 9 Schizophrenia 220 10 Other 7 11 Tic Disorder 3 12 Undetermined 1 13 Williams Syndrome 2 Table: Numbers of samples in each diagnostic category. DNA extraction: 45-80 mg of cerebellar tissue was pulverized for DNA extractions. The QIAamp DNA mini Kit (Qiagen) method was employed for tissue DNA extraction. The tissue was initially lysed using Tissue Lyser (Qiagen) and extractions were accomplished according to manufacturer's protocol. The DNA was captured in 500uL elution buffer. The concentrations were measured using Thermo Scientific's NanoDrop 1000/NanoDrop ONE. The mean yield was 128.85 uG (+/- 79.48), the mean ratio of 260/280 was 1.87 (+/- 0.105), and the mean ratio of 260/230 was 2.48 (+/-1.75). Genotyping methods: Three types of Illumina Beadarray chips were used: HumanHap650Y, Human1M-Duo, and HumanOmni5M-Quad (San Diego, California). The genotyping was done according to the manufacturer's protocol (Illumina Proprietary, Catalog # WG-901-5003, Part # 15025910 Rev.A, June 2011). Approximately, 400ng DNA was used and each DNA sample was QC tested for 260/280 ratio by nanodrop and DNA band intactness on 2% agarose gel. Briefly, the samples were whole-genome amplified, fragmented, precipitated and resuspended in appropriate hybridization buffer. Denatured samples were hybridized on prepared Bead Array Chips. After hybridization, the Bead Chip oligonucleotides were extended by a single fluorescent labeled base, which was detected by fluorescence imaging with an Illumina Bead Array Reader, iScan. Normalized bead intensity data obtained for each sample were loaded into the Illumina Genome Studio (Illumina, v.2.0.3) with cluster position files provided by Illumina, and fluorescence intensities were converted into SNP genotypes. Microarray: We generated RNA expression data using array technology for psychiatric subjects compared to non-psychiatric subjects as controls. We used tissues from three different brain regions i.e. hippocampus, dorsolateral prefrontal cortex (DLPFC), and dura mater for a large cohort of individuals (total number 552 subjects for hippocampus, 800 for DLPFC and 146 for dura). Total RNA was extracted from ~100 mg of tissue using the RNeasy kit (Qiagen) according to the manufacturer's protocol. RNA quality and quantity were examined using the Bioanalyzer (Agilent, Inc) and NanoDrop (Thermo Scientific, Inc), respectively. Samples with RNA integrity number (RIN) # Diagnosis DLPFC Hippo Dura 1 Anxiety Disorder 1 0 0 2 Autism Spectrum Disorder 14 6 0 3 Bipolar Disorder 90 49 0 4 Control 336 270 75 5 Eating Disorder (ED) 2 1 0 6 Major Depressive Disorder (MDD) 144 87 0 7 Obsessive Compulsive Disorder (OCD) 5 3 0 8 Post-Traumatic Stress Disorder (PTSD) 6 0 0 9 Schizophrenia 192 125 71 10 Other 5 6 0 11 Tic Disorder 3 3 0 12 Undetermined 1 1 0 13 Williams Syndrome 2 1 0 Table: Numbers of samples in each diagnostic category. RNA-Seq of Dorso-lateral prefrontal cortex: All brains were collected and the dorsolateral prefrontal cortical (DLPFC) samples dissected at the HBCC, DIRP, NIMH. Dorsolateral prefrontal cortex (DLPFC) specimens were dissected from right or left hemisphere of frozen coronal slabs. The study was funded by the DIRP, NIMH under contract (#HHSN 271201400099C) with Icahn School of Medicine at Mount Sinai,1106402 One Gustave L. Levy Place, Box 3500, New York NY 10029-6574. RNA extraction, library preparation and sequencing were performed under contract at Icahn School of Medicine. The Common Mind Consortium (CMC) provided project management support. RNA isolation: Total RNA from 468 HBCC samples was isolated from approximately 100 mg homogenized tissue from each sample by TRIzol/chloroform extraction and purification with the Qiagen RNeasy kit (Cat#74106) according to manufacturer's protocol. Samples were processed in randomized batches of 12. The order of extraction for schizophrenia, bipolar, and MDD disorders and control samples was assigned randomly with respect to diagnosis and all other sample characteristics. The mean total RNA yield was 24.2 ug (+/- 9.0). The RNA Integrity Number (RIN) was determined by 4200 Agilent TapeStation System. Samples with RIN DLPFC RNA-Seq quantified expression data are provided for 364 samples. Data were generated, QC'd, processed and quantified as follows: RNA library preparation and sequencing: All samples submitted to the New York Genome Center for RNAseq were prepared for sequencing in randomized batches of 94. The sequencing libraries were prepared using the KAPA Stranded RNAseq Kit with RiboErase (KAPA Biosystems). rRNA was depleted from 1ug of RNA using the KAPA RiboErase protocol that is integrated into the KAPA Stranded RNAseq Kit. The insert size and DNA concentration of the sequencing library was determined on Fragment Analyzer Automated CE System (Advanced Analytical) and Quant-iT PicoGreen (ThermoFisher) respectively. Schizophrenia Bipolar Control 89 65 210 Table: Numbers of samples in each diagnostic category. RNA-Seq of subgenual anterior cingulate cortex (sgACC): All the 200 post-mortem brain samples (61 controls; 39 bipolar disorder; 46 schizophrenia; 54 major depressive disorder) were collected by the HBCC, DIRP, NIMH. RNA Extraction and Quality Assessment: Tissue from sgACC was pulverized and stored at -80°C. Total RNA was extracted from 50-80 mg of the tissue using QIAGEN RNeasy Lipid Tissue Mini Kit (QIAGEN, Cat. # 74804) with DNase treatment (QIAGEN, Cat. # 79254). The RNA Integrity Number (RIN) for each sample was assessed with high-resolution capillary electrophoresis on the Agilent Bioanalyzer 2100 (Agilent Technologies, Palo Alto, California). The concentration of RNA and their 260/280 ratio (2.1+/- 0.032 SD) were determined with NanoDrop (Thermo Scientific). RNA sequencing: Stranded RNA-Seq libraries were constructed after rRNA depletion using Ribo-Zero GOLD (Illumina). RNA sequencing was performed at National Institute of Health Intramural Sequencing Center (NISC). Schizophrenia Bipolar Control MDD 46 39 61 54 Table: Numbers of samples in each diagnostic category. Whole Genome Sequencing: All brains were collected and dissected at the HBCC, DIRP, NIMH. This study generates whole genome sequencing data using sequencing of DNA in the dorsolateral prefrontal cortex (DLPFC), anterior cingulate cortex (ACC) or cerebellum of 443 individuals with schizophrenia, bipolar disorder and major depressive disorder and non-psychiatric controls. The study was funded by the DIRP, NIMH under contract (#HHSN 271201400099C) with Icahn School of Medicine at Mount Sinai,1106402 One Gustave L. Levy Place, Box 3500, New York NY 10029-6574. DNA extraction, library preparation and sequencing were performed under contract at Icahn School of Medicine. The Common Mind Consortium (CMC) provided project management support. All specimens were dissected from right or left hemisphere of frozen coronal slabs. DNA Library Preparation and Sequencing: All samples submitted to the New York Genome Center for WGS were prepared for sequencing in randomized batches of 95. The sequencing libraries were prepared using the Illumina PCR-free DNA sample preparation Kit. The insert size and DNA concentration of the sequencing library was determined on Fragment Analyzer Automated CE System (Advanced Analytical) and Quant-iT PicoGreen (ThermoFisher) respectively. A quantitative PCR assay (KAPA), with primers specific to the adapter sequence, was used to determine the yield and efficiency of the adaptor ligation process. Performed on the Illumina HiSeqX with 30X coverage. Schizophrenia Bipolar Control 115 78 230 Table: Numbers of samples in each diagnostic category. ChIP-Seq: All brains were collected and the dorsolateral prefrontal cortical (DLPFC) samples dissected at the HBCC, DIRP, NIMH. This study generates epigenetic data using sequencing of DNA after chromatin immunoprecipitation (ChIP-Seq) for marks H3K4me3 and H3K27ac in the dorsolateral prefrontal cortex (DLPFC). Dorsolateral prefrontal cortex (DLPFC) specimens were dissected from right or left hemisphere of frozen coronal slabs. The study was funded by the DIRP, NIMH under contract (#HHSN 271201400099C) with Icahn School of Medicine at Mount Sinai,1106402 One Gustave L. Levy Place, Box 3500, New York NY 10029,6574. Chromatin precipitation, library preparation and sequencing were performed under contract at Icahn School of Medicine. The Common Mind Consortium (CMC) provided project management support. Chromatin immunoprecipitation (ChIP) assays for histone marks H3K4me3 and H3K27ac were carried out using Native ChIP. Micrococcal Nuclease (MNase) (Sigma, N3755) treatment was used to digest chromatin into mononucleosomes. The following antibodies were used for chromatin pull-down: anti-H3K4me3 (Cell Signaling, Cat# 9751BC, lot 7) and anti-H3K27ac (Active Motif, Cat# 39133, Lot # 31814008). Histone modification-enriched genomic DNA fragments were recovered using Protein A/G magnetic beads (Thermo Scientific, 88803-88938 or Millipore 16-663), and then washed, eluted, and treated with RNAse A and proteinase K. Final ChIP DNA products were isolated using phenol-chloroform extraction followed by ethanol precipitation. The efficiency of each ChIP assay was validated using Qubit concentration measurement and qPCR for positive (GRIN2B, DARPP32) and negative (HBB) control genomic regions. Only ChIP assays that passed quality control were further processed for library preparation and sequencing; this included ChIP DNA that was not detectable on Qubit but showed a good signal and expected enrichment patterns in qPCR. HISTONE_MARK H3K27ac H3K4me3 Input Bipolar 56 4 7 Control 158 11 24 Schizophrenia 79 11 12 Table: Numbers of individuals in each assay grouped by histone mark or input.Long-Read Whole-Genome Sequencing (WGS) Cohort Description: Brain specimens were obtained from the Human Brain Collection Core (HBCC), part of the NIH NeuroBioBank. Samples were collected under protocols approved by the NIH CNS Institutional Review Board (IRB) (NCT03092687), with informed consent from next-of-kin (NOK). Collection was coordinated through the Offices of the Chief Medical Examiners (MEOs) in Washington, D.C., Northern Virginia, and Central Virginia. Clinical metadata and documentation are publicly available via the NIMH Data Archive (NDA) (Collection #3151) https://nda.nih.gov/edit_collection.html?id=3151 Eligibility Criteria No clinical diagnosis of major neuropsychiatric or neurodegenerative diseaseNo diagnosis of cognitive impairment during life All individuals were confirmed to be neurologically normal at time of deathDemographics Initial cohort size: 155 individuals Ancestry: All individuals self-identified as African or African-admixed Mean age at death: 44.2 years (range: 18–85 years) Sex distribution: 36.4% femaleSample Processing: Frozen frontal cortex tissue was dissected and processed according to the public protocol: https://www.protocols.io/view/processing-human-frontal-cortex-brain-tissue-for-p-kxygxzmmov8j/v2. High-molecular-weight DNA was extracted and libraries were prepared using the Oxford Nanopore Technologies (ONT) LSK-114 kit. Sequencing was performed using ONT PromethION flow cells (R10.4.1 chemistry) Data Processing and Quality Control: Basecalling: Conducted using Guppy v6.38 Read Alignment: Reads were aligned to the GRCh38 reference genome using minimap2 Sample Identity Verification: Sample identity was validated by comparing ONT-derived SNP calls with matched short-read WGS genotypes to ensure concordance and prevent sample swaps Variant Calling and Phasing: Reads were base-called with Guppy v6.38. Reads were aligned to GRCh38 using minimap2. We verified sample identity by cross-checking ONT SNV calls with the existing short-read WGS genotypes, confirming no sample switches. The napu pipeline (https://github.com/nanoporegenomics/napu_wf) produced; haplotype-resolved assemblies, joint small-variant (SNV/indel) calls, and multi-caller structural-variant sets, all reported on GRCh38 and phased where possible. Raw signal data were basecalled to obtain 5-methyl-cytosine (5mC) status; methylation tags were added to the phased BAM files. Genome-wide methylation summaries are provided in BED format.Dataset Filtering and Exclusions: All 155 samples underwent sequencing and SNP-based ancestry inference 8 samples were excluded due to ancestry inconsistent with African or African-admixed background 1 sample was excluded due to insufficient sequencing quality Final Sample Set: 146 high-quality samples from individuals of African or African-admixed ancestry were retained for downstream analyses See PMID: 39764002 for further analysis detailsDiagnosis#SamplesControl155Table: Diagnostic Summary.Note: The data derived from HBCC resources were removed from dbGAP and are now available in the NIMH Data Archive (NDA). They include genotypes, short read whole genome sequencing (WGS), epigenetics (DNA methylation, ChIP-seq for histones), RNA expression (qPCR, microarray, RNA-seq, single nucleus RNA-seq) of various brain regions in cases with schizophrenia, bipolar disorder, major depression, substance use disorders and normative controls. Please access our NDA collection (https://nda.nih.gov/edit_collection.html?id=3151) for further detail.

  Study phs000979

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• Submitter Portal

  Submitter Portal The Submitter Portal does not support array submissions! Please refer to the array documentationAny new objects registered in the Submitter Portal will not be available for use in an array submission For further information please check our Submission FAQs, submission quickguide as well as submission terms! The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. Submitter Portal Index Previous steps Access to Submitter Portal Start a Submission Take The Tour Tutorial Previous steps Create your EGA account To submit data, you first need to create your EGA user. Then, once your account has been verified by the Help Desk team, you will be able to request a submitter role and send the EGA Data Processing Agreement (DPA). In the case you already have an EGA account, or an ega-box (submission account), you can skip this step. Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role and added your public key to your profile, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find relevant information in the DAC Portal Guide. Access to Submitter Portal 1. Request Submitter Role Once you have created your EGA user, request a Submitter Role and complete relevant information such as submission type and size. 2. Signature of the Data Processing Agreement The Data Processing Agreement (DPA) signed by CRG and EMBL-EBI (Joint Data Processors for the EGA) can be downloaded to the submitter for its signature. Further information related to the DPA can be in the Privacy Notice section. The DPA should be signed by a legal representative of the submitter with power of attorney/appointment duly authorised to sign contracts on behalf of the institution. The submitter will return a fully-executed copy of the DPA to us. Please note that due to the high volume of submissions to EGA the DPA is non-negotiable. Once you have completed all the information and attached the DPA signed, send your Submitter request and the EGA Helpdesk Team will validate it and send a confirmation to start submitting your metadata. Start a Submission The steps below will show you how to start a submission and are accompanied with a tutorial and the Take the tour of Submitter Portal. 1. Login Go to the Submitter Portal interface and log in using your EGA account credentials. 2. Create a submission The Submitter Portal interface will show you any already existing open submission. To start a new submission click on “Create a Submission”.In this phase you have the option to add any collaborator(s) as well as their permissions (“Read only” or “Read & Write”). If you want to invite all the collaborators from a previous submission, you can add them by selecting said submission.In the event that the submission has been closed, you will need to reopen it. To do this, you will need to modify one of the objects in the submission, for example, copy and paste the title. Once the submission is open, you can add a collaborator. Further information can be found in the Submission Tour 3. Create Study Click on add Study and complete the form with the relevant information. The fields with an asterisk (*) are mandatory. Further information can be found in the Submission Tour4. Create Sample Sample registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with information about the sequencing samples. Upload the samples.csv and the sample will be created.Add single sample: complete the mandatory fields with the metadata information of your sample.  Further information can be found in the Submission Tour5. Create Experiment Register an experiment with ​information about the sequencing methods, protocols and machines. Experiments generate the connection between samples and study. Further information can be found in the Submission Tour6. Create Run Samples, experiments and files are linked through runs. To register a run, you will be asked to select the appropriate experiment and the file format. Run registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with the sample - file linkage. Upload the run.csv and the runs will register.As the INBOX is a directory, bear in mind to include the file path (/). Example: /filename.c4gh. Add single run: select the file format, sample and experiment from the drop box. For re-using submitted samples, please use the EGA accession ID (EGANXXX). Please note that files must be uploaded in your inbox before linking your files and samples. Further information can be found in the Submission Tour7. Create Analysis Analysis should be only used for BAM/BAI or CRAM/CRAI pair, VCF and phenotype linkage to samples. The analysis is an EGA specific metadata object that links samples to files. This object also stores some metadata about your experiments, such as the experiment type, genome reference, or the platform used. **If only BAM or CRAM alignment files are submitted but not the original unaligned FASTQ files, then please make sure that the BAM or CRAM files also contain the unaligned reads. This is critical to enable primary re-analysis and re-alignment of the dataset using new tools or future genome assemblies.** Start by selecting the samples to be linked to the file, and then populate the required attribute fields. Please be aware of the existence of mandatory fields that must be populated.When populating the chromosome field (mandatory), please select the chromosomes from the checkbox. Please take in consideration that EGA allows for the re-use of any registered metadata. Therefore, a previously registered study or samples can be referenced for the analysis in the current data submission.Further information can be found in the Submission Tour 8. Create Dataset Dataset contains the collection of runs/analysis data files subjected to controlled access by being associated with a Policy. Complete the mandatory fields such as title, description, type and policy. Please, take in consideration that DAC and Policy must be registered in advance in the DAC Portal. Similar to other metadata objects, you can re-use previous runs or analyses, using their EGA accessions IDs (runs - EGAR, analyses - EGAZ). Further information can be found in the Submission Tour 9. Finalise submission Once the files are ingested please delete them from your SFTP INBOX before finalising your submission. This will prevent the files from reappearing in your Submitter Portal Inbox. Once you have completed your submission, click on the Finalise button, and schedule an estimated release date. Afterwards, your submission will be sent to Helpdesk for approval. Please note that once the Helpdesk has approved your submission, you will receive the identifiers for your data. See the Frequently Asked Questions (FAQ) for more information. 10. Update closed submission If you want to append more file to a closed submission, you will need to re-open the submission where the dataset was registered. Find the Submission: go to the Submitter Portal Menu -> Datasets section and find the submission id (EGA0XXX).  Reopen the submission where the dataset is located: to reopen a submission, you must edit any object within the submission. For example, you can copy and paste the title. Take The Tour The Submitter Portal Take The Tour is a visual guidance of all the steps described previously about how to start a submission. Tutorial In this tutorial we will show you how to use the Submitter Portal to register your metadata. Please note the video focuses on the run-based submission (for raw files - fastq - and aligned data - BAM/CRAM) and analysis-based submission (for your BAM/BAI pairs, variation -VCF - and phenotype files).

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal

• 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