10968 results for "fc 26 best way to get coins Visit Buyfc26coins.com Gyors és hatékony szolgáltatás. Hamarosan visszatérek több FC 26 érmeért..4w1a"

in 38.01 milliseconds.

• Center for Common Disease Genomics [CCDG] - Inflammatory Bowel Disease (IBD) - Global Microbiome Conservancy Host Exomes

  The human body is a complex ecosystem, hosting tens of billions of bacteria, primarily in the gut. This community, known as the 'gut microbiome', is vital to human health, affecting functions ranging from metabolism, immunity, and development, to behavior. Conversely, reduced microbiome diversity and other imbalances of the gut community (dysbiosis) are associated with many diseases of the industrialized world, such as metabolic syndrome, asthma, and inflammatory bowel diseases among others. Microbiome-based interventions thus hold the potential to revolutionize our understanding of, and therapeutic approaches to, many aspects of human health and disease. Despite many advances, current understanding of the human microbiome is largely limited to majority ethnic groups in industrialized nations, and does not reflect the full diversity of human commensal microbiota. In addition to the scientific ramifications of minority underrepresentation, there are significant translational and ethical implications as well: First, failing to capture the full diversity of healthy human microbiota may limit our ability to understand and generate effective therapeutics for many microbiome-associated diseases. Second, underrepresented groups are less likely to benefit from microbiome-based medical advances tailored to well-studied populations, propagating healthcare inequities. The window of opportunity to characterize human microbiome diversity is closing rapidly. Human gut microbial diversity is diminishing around the globe, due to the spread of Westernized diets and lifestyles, which are associated with reduced microbiome biodiversity. The Global Microbiome Conservancy (GMbC) is a non-profit collaboration between scientists and communities around the world that aims to 1) preserve the full biodiversity of the human gut microbiome, 2) characterize its evolution across populations and host lifestyles and 3) investigate its interactions with the human host. We are collecting gut microbiome and human DNA samples from diverse populations around the world, from isolated groups to urbanized populations, to culture and study this essential biodiversity and to preserve it in a living "seed bank" as a long-term safeguard against future extinctions. The National Human Genome Research Institute (NHGRI) has funded a collaborative large-scale genome sequencing effort to comprehensively identify rare risk and protective variants contributing to multiple common disease phenotypes. Called the Centers for Common Disease Genomics (CCDG), this initiative will explore a range of diseases with the ultimate goal of: Undertaking variant discovery for enough different examples of disease architectures and study designs to better understand the general principles of the genomic architecture underlying common, complex inherited diseases. Understanding how best to design rare variant studies for common disease. Developing resources, informatics tools, and innovative approaches and technologies for multiple disease research communities and the wider biomedical research community. The initial focus of the CCDGs will be in cardiovascular disease (early-onset coronary artery disease, atrial fibrillation, hemorrhagic stroke), neuropsychiatric disease (epilepsy, autism), and autoimmune/inflammatory disease (type 1 diabetes, inflammatory bowel disease). The Broad Institute is one of four selected CCDG project centers. Both exome and genotyping information of GMbC participants will help understanding how recruited human populations are structured and genetically related. This human genetic structure will be analyzed in light of gut microbiome compositional and genomic differences to illuminate associations between specific microbiome traits and human groups and the evolutionary processes involved in the co-evolution of human hosts and their gut microbiome. It will also provide variant information for critical genes shaping the composition of microbiomes, such as genes involved in innate and adaptive immunity (e.g. antimicrobial peptides) or in the regulation of the immune response (e.g. Nod2). Association studies between specific variants in these genes and microbiome features will be performed, which will then be validated with in vitro and in vivo experiments. Human data from GMbC cohorts will also increase the genetic diversity of human populations, providing additional variant information for many susceptible loci that were found to be associated with Crohn's disease and ulcerative colitis. The whole genome sequencing data generated is comprised of samples from diverse and indigenous populations. Raw sequencing data, metadata, vcf and phenotype data at the individual level for a subset of the cohort's samples are available at https://anvilproject.org/data. For questions about availability, contact help@lists.anvilproject.org. Microbiome data for the samples sequenced in this study can be found in phs002235 Global Microbiome Conservancy Sequence Data.

  Study phs002205

• 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

• Submission FAQ

  Submission FAQ Before Submission Is the EGA the right archive for my data? TThe most suitable archive for your data is dependent on the type of data you are wishing to submit and whether the data require public or controlled access. Public access is defined as complete and open access to all submitted data. On the contrary, controlled access, exerted by the EGA, requires formal applications to be made to access the submitted data files and metadata. EGA only accepts human-derived data subject to controlled access. If your submission contains other types of data, please choose the appropriate repository for it (see image below): ENA, EVA, ArrayExpress, BioSD and GWAS catalog.  Should your submission be subjected to controlled access? Data access conditions are normally defined in the original informed consent agreements signed by the participants involved in your study. All data submitted to the EGA is subject to controlled access. These consents prevent the derived data files, potentially identifiable, from being dispersed by open and public access. Controlled access data often refers to human data derived from medical research and consortium projects. If in doubt, consult the informed consent agreements that apply to your study The EGA enables you to hold a submission before publication. What data types can be submitted to the EGA? Data types accepted by the EGA can be split into three categories: Sequences: both in generic and platform-specific formats. Array-based: from raw signal files to processed matrices. Phenotypes: all possible phenotype formats are accepted. All manufacturer-specific raw data formats derived from major next generation sequencing platforms are accepted. Also generic sequence formats: flat reads in a FASTQ file, aligned sequences (BAM or CRAM files) as well as sequence variation files in VCF format. All array-based technologies are accepted, including raw data, intensity and analysis files, without any restriction on data formats accepted. We also accept and distribute phenotype data (associated to the samples) in almost any format: from an image to a README file. How long does a submission take? Submissions to EGA come in a variety of formats and sizes, thus it is difficult for us to exactly predict how long a submission will take. We, therefore, advise all of our submitters to allow as much time as possible to make a submission. Based on previous records, we anticipate that the submission process may take at least one month. The submitter’s familiarity with the procedures, possible technical issues that may arise during submission and the amount of data that is being submitted are the main factors that will affect the length of the submission process. However, each step of a regular submission should be considered when estimating the time it would take: Encryption of the files Upload of the files Metadata submission Archival of the files Release of the study and datasets to EGA webpage For example, the upload of the files depends on the submission size, while metadata submission mainly relies on each submitter’s expertise. Further, some steps (e.g. answering to inquiries) depend on the EGA Helpdesk team, which may take some days to be processed during busy times Is data deposited in the EGA secure? The EGA set-up consists of a secure computing facility for data processing, a shared EBI set-up for data submissions and distribution of data via data requests made through the EGA website. Data is also copied in the Barcelona Supercomputing Center (BSC) infrastructure, where all stored and distributed data is encrypted Data is encrypted along the submission process and stored securely, granting its access to authorised users exclusively. During the download process, through our Python Client or Aspera, all requested data is downloaded over secure https connections. All data at the EGA is encrypted, and only accessible (for log-in and download) through secure protocols. For further information please, visit our security overview. What documentation do I need to provide? All submissions require policy’s documentation: 'Data Access Agreement (DAA)', 'Data Processing Agreement (DPA)' and 'Authorized Submitters Formulary'. The data processors (EGA) and the data owners will also sign the DPA. Will all metadata be public? Among the submitted metadata we need to make the distinction between identifiable and unidentifiable metadata: (1) the former may allow the identification of the human the sample derived from (e.g. detailed geographical providence, personal name, family ancestry…); (2) while the latter can be used to interpret the data without compromising the anonymity of the patients. The majority of the metadata submitted to the EGA corresponds to the unidentifiable category (e.g. sequencer's model). This type of metadata is publicly available on the EGA website and other EBI resources/partners’ websites. On the other hand, some parts samples’ metadata are subject to being identifiable, and thus only accessible by authorized data requesters, with the exception of: 5 submitter-defined attributes of the sample: alias, title, subject_id, gender and phenotype. It is the submitter’s responsibility not to submit sensitive metadata in these public fields. 3 anonymised fields that pinpoint the sample record in archivals: sample’s EGA stable ID (EGAN…), BioSample ID (SAMEA…) and submitter’s center name. During Submission Are there any sample specific requirements for EGA? All samples submitted to the EGA must include the attributes of biological sex, subject ID (anonymised individual identifier) and phenotype information. These are critical for data findability and its analysis, and we highly recommend using controlled ontology terms where applicable. For example: defining tumour and non-tumour samples and/or defining disease state. The EGA recommends using the Experimental Factor Ontology Database to find ontologized terms that describe your sample phenotypes. How do I get an accession number to use in my publication? You will receive your study accession number (EGAS…) upon complete your submission, either: Programmatically. As soon as the metadata is submitted and validated your study will be assigned an accession number that will be given in the submission’s response. Manually registering your study and relevant metadata using the online metadata submission tool: the EGA submitter Portal. How are files uploaded to the EGA? Data files are uploaded into private submission drop boxes (i.e. environments to which you are granted access and where you can transfer your files) using INBOX or FTP. These spaces are provided as part of the submission procedure. Before uploading any file, you must encrypt your files, . Only encrypted files shall be uploaded to the drop boxes. Why does data need to to encrypted for my submitted files? It is one of the security steps the EGA has implemented. In case of a security breach, people without the proper encryption key will not be able to read or use the information that could have been leaked. This measure is essential when working with sensitive data, such as controlled access human data. All submitters must use crypt4gh to create EGA compliant files prior to uploading them. This encryption is GPG-based, using EGA’s public key. Why are my files not available if I see them in the INBOX? There exists a time window between the data upload and the availability of such files via the Submitter Portal. For this reason, some metadata (run and analysis objects) cannot be registered until at least 24 hours after the files have been uploaded to your box. Why are MD5 sum values generated for my submitted files? We require pre- and post- encryption MD5 (message-digest) checksum values to be provided for all submitted files. These 128-bit values are computed using the content of each file, creating unique sequences that allow us to ensure that file integrity has been maintained during the transfer process. In other words, if the MD5 checksums we generate and those you generated match, we infer that the content of the transferred files is correct (i.e. files are not corrupted or truncated). MD5 checksums are computed automatically using the crypt4gh tool provided. Your submission will not be accepted and may be significantly delayed if you do not provide MD5 checksum values for all data files in the required format. How can I check if my files are correctly uploaded to the inbox? It is important to check the status pf your file so you know whether your files are in the inbox, being processed, or if there is any issue with one of them. In order to check this, you should: Look for the file locally. Drag and drop it to the file table. Then bars will appear on the table, which means that we are processing it. Green: The files checksum are correct and your file will move to “ingested files”. No further actions are needed from your end.. Red: The files checksum does not match and your file needs to be re-uploaded. Please re-upload relevant files to your inbox using the same path. After Submission How do I use my accession number in my publication? We suggest the use of the below template, using your study accession ID (EGAS…) : Data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found at https://ega-archive.org and "The European Genome-phenome Archive of human data consented for biomedical research" Your study ID will be the one that groups your whole submission, and thus its usage is recommended as such. Nevertheless, all metadata submitted to EGA hold a unique and persistent identifier (starting with EGA…) that can be used to identify specific records. For example, you could reference a specific dataset (EGAD…) or sample (EGAN…) in your publications (see full list of identifiers). How do I make my data searchable? Once you have finalized your submission, you can schedule the data release. Please take into account that the release process needs time for the files to be archived in our system, and for the Helpdesk team to validate your submission. Can I withdraw (meta)data from the EGA? We have methods in place for the secure removal of deposited (meta)data. Contact EGA-helpdesk for further details. EGA complies with FAIRness of (meta)data, and thus, even when the data is removed we keep an entry for their identifiers in our system. In other words, we execute a soft delete on canceled objects (e.g. a study): metadata is still stored in our systems, but it loses all links, cannot be queried and data files cannot be retrieved anymore. The reason behind this behaviour is so that queries using withdrawn data properly respond back (see example of a canceled study). What happens to the data once it has been submitted to the EGA? When the data is submitted, the submitter can choose either keep their data private or schedule the release of their data.

  Documentation submission/metadata/submission/FAQ

• How to request data

  Request Data Access If you're looking to access data from the EGA for your research, you are in the right documentation page! In this page you will find a step by step guide on how to request data archived at the EGA, as well as some frequently asked questions you might find useful. When requesting data, you'll need to provide information about your research project and intended use of the data. Keep in mind that your data access request may require additional approvals or agreements depending on the datasets and data providers involved. Step by step guide Register yourself as an EGA user. Validate your account. A validation link will be sent to your email to activate your EGA user account. Log into the EGA page. Search the dataset of interest from the dataset catalogue or search bar. Click on “Request access” Add a comment requesting these files and send your request Your request is successfully registered, and the DAC will receive a notification about your request In addition to submitting your request, you should also contact the DAC directly via e-mail. You can access the DAC's contact information from the relevant dataset page. Frequently Asked Questions (FAQ) Which is the role of the EGA in the data access process? The European Genome-phenome Archive (EGA) facilitates the secure distribution under controlled access of personally identifiable genetic and phenotypic data. Data Access Committee (DAC) is a body of one or more individuals who are responsible for data release to external requestors, based on participant consent and/or National Research Ethics terms. How do I request access to multiple datasets? To request access for multiple datasets managed by the same Data Access Committee (DAC), please start by visiting the DAC catalogue to locate the DAC of your choice. Once you've found the relevant DAC, proceed to its dedicated page where you'll find a "Request access" button. After logging in to the EGA website, you'll be presented with a comprehensive list of datasets under the chosen DAC. Select the datasets you're interested in, and then compose a message indicating your access request. Click the "Send" button to submit your request, which will include the chosen datasets. Please be sure to review the data usage policies for the requested datasets, as policies can vary among datasets managed by the same DAC. I am a co-applicant. Will I be given a joint access account? Each applicant needs to create an EGA account themselves, with unique login details. User log-in details are for individual use only and should never be shared, under any circumstances. EGA services are only provided to EGA account holders. Therefore, the co-applicant will send a formal request to the DAC. What happens if a co-applicant leaves or a new member needs to be added to an existing DAC application? The appropriate Data Access Committee (DAC) should be contacted and informed about the required changes so that the application can be updated. I have changed my place of work since my EGA account was created. Can I still have access to data? You must contact the relevant Data Access Committee (DAC). The DAC did not reply to my data access request. How should I proceed? There is no estimated time for DAC response. Please allow up to four weeks for a response. In the meantime, please send them a weekly reminder of the status of your request by emailing them directly.If the DAC becomes unresponsive, meaning that they fail to communicate with a requestor within the specified time frame, please contact the EGA Helpdesk team. I have an account with the EGA and would like access to further datasets. How should I proceed? You need to reapply to the relevant Data Access Committee (DAC). Once the DAC has approved your application your account will be updated and an email will be sent to notify you of a change made to your account. How do I download files of the datasets I have been granted access to? The preferred method for data download and decryption is the EGA Secure Download Client. Please carefully review the provided documentation. How do I download metadata? Metadata is retrieved from the EGA webpage; you will not need to use any download client. Be informed that you will only be able to download metadata of your approved datasets. For such download, you should first log in the EGA webpage with your credentials. Then browse the metadata's dataset you have gained access and you will find a metadata download button. You may also want to have a look our metadata schema. I have forgotten or misplaced my user account password; how do I get a new one? Click on “Log in”, located in the top right corner of the EGA homepage. Then click “Forgot password”, type in your registered institutional email address, and instructions for resetting your password will be sent to you. Please check both regular and junk/spam folders. I was sent a link to set a password for my download account, but it seems like the link has expired. What should I do? The procedure is the same as the one for a forgotten password, explained in the previous question.

  Documentation access/request-data/how-to-request-data

• Prevention and Early Treatment of Acute Lung Injury (PETAL) Crystalloid Liberal or Vasopressors Early Resuscitation in Sepsis (CLOVERS) (PETAL CLOVERS-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from PETAL CLOVERS include plasma, and whole blood. Please note that use of biospecimens in genetic research is subject to a tiered consent. Available Data: The data available for request now include Long Term Outcome data.Objectives: To compare the effects of a restrictive fluid strategy (with early use of vasopressors) to a liberal fluid strategy in participants with sepsis-induced hypotension.Background: Intravenous fluid resuscitation is a common therapy used in the initial treatment of participants with septic shock and sepsis-induced hypotension. The goal of initial fluid therapy is to increase depleted or functionally reduced intravascular volume that occurs in sepsis due to a vasodilated vascular network. However, intravenous fluid resuscitation can create dilutional coagulopathy, fluid overload, and pathogenic edema in the lungs and other organs. Vasopressor agents are also commonly used to treat hypoperfusion by inducing constriction of arterioles and venules and increasing cardiac contractility. Vasopressor therapy also comes with risks that include vasoconstriction resulting in tissue ischemia, increased cardiac workload, and arrhythmias. Clinicians have used these strategies, typically in combination, to provide supportive care for participants with sepsis-induced hypoperfusion. However, at the time of the CLOVERS study, there was limited data to guide specific use of these therapies, including fluid volumes, in the early care of participants with sepsis-induced hypotension. The CLOVERS study hypothesized that a restrictive fluid strategy used during the first 24-hours of resuscitation for sepsis-induced hypotension would lead to lower mortality before discharge home by day 90 than a liberal fluid strategy.Participants: A total of 1,563 participants, from 60 medical centers, of the planned 2,230 participants were enrolled, with 782 assigned to the restrictive fluid group and 781 to the liberal fluid group. Enrollment in the trial was ended after the second interim analysis due to a lack of significant difference observed between the two 24-hour strategies.Design: This study was a multi-center, prospective, phase 3 randomized non-blinded interventional trial of fluid treatment strategies in the first 24 hours for participants with sepsis-induced hypotension. Participants were randomly assigned in a 1:1 ratio to either a restrictive fluid strategy (with early vasopressor use) or a liberal fluid strategy. In each group, the assigned protocol was followed for a period of 24 hours. The restrictive fluid protocol prioritized vasopressors as the primary treatment for sepsis-induced hypotension, with 'rescue fluids' being permitted for prespecified indications that suggested severe intravascular volume depletion. The liberal fluid protocol consisted of a recommended initial 2000-ml intravenous infusion of isotonic crystalloid, followed by fluid boluses administered on the basis of clinical triggers (e.g., tachycardia) with 'rescue vasopressors' permitted for prespecified indications. A protocol amendment implemented in October, 2019, allowed for limiting the initial infusion to 1,000 ml if the participant's blood pressure and heart rate had stabilized and the clinical assessment was that the participant was unlikely to benefit from additional intravenous fluid administration. The clinical team could override the protocol-specified care instructions at any time if it was judged to be in the best interest of the participant.The primary outcome was death from any cause before discharge home by day 90. Secondary outcomes included 28-day measures of the number of days free from ventilator use, days free from renal-replacement therapy, days free from vasopressor use, days out of the ICU, and days out of the hospital. Conclusions: Among participants with sepsis-induced hypotension, the restrictive fluid strategy that was used in this trial did not result in significantly lower (or higher) mortality, or other measures of recovery such as length of hospital stay, before discharge home by day 90 than the liberal fluid strategy.

  Study phs004080

• What is a DAC?

  What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions.  You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks.  Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, the EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

  Documentation access/data-access-committee/what-is-dac

• Upcycling and merging data to challenge the dogma and identify new therapeutic targets for Glioblastoma

  Glioblastoma is the most common brain tumour. Characterised by a poor prognosis and its recurrence after multimodal treatments, the search for preventable risk factors has been mainly inconclusive up to date. Recently, the data merge from datasetsdeposited at the EGA allowed Aaron Diaz’s team to discover that the glioblastoma cells shift toward a mesenchymal phenotype when the tumour is recurring. Challenges in glioblastoma research As for virtually all cancer types, many efforts have been made to unveil the molecular features responsible of the disease, and several cellular pathways have indeed been identified as being frequently mutated in glioblastoma. Nonetheless, targeted therapies based on identified genes have so far failed to improve outcome, thus survival mostly relies on a standard treatment unchanged since 2005. This is a frustrating situation for both the scientific and medical communities, and above all for the patients, still facing a dreadful path. Some researchers hypothesised that this may be due to the inability to efficiently target cancer stem cells, the originators of the other cell types, thus inducing cancer relapse. In 2019 Charles P. Couturier and colleagues sequenced RNA from single cells of freshly excised glioblastomas of 16 patients, and demonstrated that glioblastoma cells replicate normal brain cell development with a conserved neural cancer cell hierarchy centered around glial progenitor-like cells. In this way, they helped identify the possible target cells to improve efficacy and durability of treatment. Data upcycling at the EGA: the glioblastoma case study Single cell RNA sequencing is generated with a laborious and expensive protocol. The quality of the starting material is crucial (cells sample freshly extracted from the patients) and often several attempts are needed before producing reliable quality sequencing results. Collecting big numbers of patients is also challenging. The sequencing data produced by Kevin Petrecca’s group in Montreal, Canada and deposited at the EGA (EGAS00001004422) was recently upcycled by Lin Wang in San Francisco, California and pooled with their freshly produced ones, and then deposited at the EGA as Dataset EGAS00001004909 The data merge allowed Aaron Diaz’s team to discover that the glioblastoma cells shift toward a mesenchymal phenotype when the tumour is recurring. They profiled 86 primary-recurrent patient-matched paired glioblastoma samples with single-nucleus RNA, among other techniques. These very comprehensive results lead the team to challenge the findings from several other cancer fields where chemotherapy standard chemo-radiation therapy selection pressure at the level of genomic alterations; this is indeed not the case for glioblastoma, where the pressure results in phenotypic transition between cellular states. Several technical controls were made to ensure that the merge of the data was not introducing a bias in the results, and an Inter-table analysis demonstrated nearly equal contribution to overall variance from each of the studies included, indicating that the findings were not due to inter-laboratory technical effect. A novel principal-component analysis showed that the largest contribution to variation in primary glioblastoma neoplastic cells was an axis between MES (mesenchymal) and proneural expression programs. In summary, treating glioblastoma often makes a MES, as commented by Lucy Stead about this remarkable work. Check Aaron Diaz’s team Nature Cancer paper, with strong technical tools, state of the art analysis and data from different sources converging to the same outcomes that made possible a significant step toward a better handling of a frightful cancer. References Couturier, C.P., Ayyadhury, S., Le, P.U. et al. Single-cell RNA-seq reveals that glioblastoma recapitulates a normal neurodevelopmental hierarchy. Nat Commun 11, 3406 (2020). Stead, L.F. Treating glioblastoma often makes a MES. Nat Cancer 3, 1446–1448 (2022). Wang, L., Jung, J., Babikir, H. et al. A single-cell atlas of glioblastoma evolution under therapy reveals cell-intrinsic and cell-extrinsic therapeutic targets. Nat Cancer 3, 1534–1552 (2022). Related links: Kevin Petrecca’s group dataset deposited at the EGA: EGAS00001004422 Lin Wang dataset deposited at the EGA: EGAS00001004909

  Blog upcycling-and-merging-data-to-challenge-glioblastoma

• Drug development for pediatric cancers: the importance of patient' s genomic data re-use

  Cancer in children is uncommon and the overall prognosis for most pediatric cancers is good. However, while the combined survival rates have improved over the last decades, certain childhood malignancies, such as high-grade gliomas or metastatic sarcomas, still remain incurable in most patients. New strategies for targeting those devastating diseases are imperative, and patient genomic data can become a key asset in the process [1]. The Pediatric Cancer Genome Project’s datasets At EGA, we store over 500 datasets with sequencing data from pediatric cancer patients. A remarkable case is the datasets belonging to the Pediatric Cancer Genome Project (PCGP) from St. Jude Children’s Research Hospital–Washington University (Table 1 - EGAS list). PCGP is an ambitious effort to identify the mutations that drive childhood cancer and find new cures. Those datasets include 600 patients with complete tumor and normal genomes from 15 different tumor types. PCGP datasets have been an important resource for various studies that pooled genomic data from different public and in-house datasets to perform extensive genomic characterizations and publish comprehensive pan-cancer pediatric studies [2],[3]. Other interesting pediatric cancer datasets are from the Pediatric Brain Tumor Consortium, Sickkids or ICGC PedBrain project. How data reuse impacts drug development for pediatric cancers Recently, in October 2024, Nature Communications published a work led by the University of Michigan where authors used data from EGA (PCGP) check the table below as part of their strategy to pursue the identification of new tumor vulnerabilities susceptible to becoming novel therapeutic targets in diffuse midline glioma. Diffuse midline gliomas (DMG) are treatment-resistant and uniformly fatal pediatric brain tumors. The prognosis of this brainstem tumor is dismal with a median overall survival of 9–12 months from diagnosis. In this study, the authors first developed a lab model of the disease and reanalyzed data from the EGA to identify genes potentially linked to tumor severity. This approach revealed involvement of specific metabolic pathways, suggesting new possibilities for therapeutic intervention. In mice, the study shows that the use of statins can improve survival. For a brief overview of the underlying science, diffuse midline gliomas present intratumor heterogeneity with subpopulations of less-differentiated oligodendrocyte precursors and more differentiated astrocytes. Authors established in vitro models to recapitulate both phenotypes and identify metabolic programs in both subpopulations. To determine the clinical relevance, the authors re-used gene expression data from 76 DMG patients identifying a gene signature predicting decreased overall survival. After extensive metabolic characterization of subpopulations, authors defined strategies to target specific metabolic vulnerabilities. Pre-clinical experiments in mice using OXPHOS inhibitors and statins showed a reduction in tumor burden and increased overall survival [4]. In this scenario, the re-use of high-quality patient’s sequencing data appeared as an advantageous strategy to support the clinical relevance of in-vitro and pre-clinical findings. On the other hand, in rare conditions such as childhood cancer, the availability of public datasets and the possibility of pooling data from different sources can be the only way to obtain impactful results that lead to improvements for patients. References Davidoff, A. M. Pediatric Oncology. Seminars in pediatric surgery 19, 225–233 (2010). Gröbner, S. N. et al. The landscape of genomic alterations across childhood cancers. Nature 555, 321–327 (2018). Venu Thatikonda et al. Comprehensive analysis of mutational signatures reveals distinct patterns and molecular processes across 27 pediatric cancers. Nature Cancer 4, 276–289 (2023). Mbah, N. E. et al. Therapeutic targeting of differentiation-state dependent metabolic vulnerabilities in diffuse midline glioma. Nature Communications 15, (2024). Datasets and Studies ID Title Access Policy Year EGAD00001000134 Driver mutations in histone H3.3 and chromatin remodelling genes in paediatric glioblastoma McGill-DKFZ Pediatric Brain Tumour Consortium 2016 EGAS0000100192 Somatic Histone H3 Mutations in Diffuse Intrinsic Pontine Gliomas and Non-Brainstem Paediatric Glioblastomas St. Jude Children's Research Hospital - Washington University Pediatric Cancer Genome Project 2017 EGAS00001000575 Whole genome sequencing and whole exome sequencing of DIPG tumors and matched normal tissue The hospital for sick children ("SickKids") 2016 EGAD00001000792 Exome sequencing reads of paediatric glioblastoma McGill-DKFZ Pediatric Brain Tumour Consortium 2016 EGAD00001002006 Whole genome sequencing of paediatric glioblastoma in the ICGC PedBrain project ICGC PedBrain project 2016

  Blog drug-development-for-pediatric-cancers

• National Cancer Institute (NCI) Biospecimen Pre-analytical Variables (BPV) Analysis

  The Biospecimen Pre-analytical Variables (BPV) Program is a National Cancer Institute-sponsored study to systematically assess the effects of pre-analytical factors on the molecular profile of biospecimens. A robust biospecimen collection infrastructure was established to prospectively collect biospecimens using rigorous standard operating procedures to control for most variables while introducing experimental conditions to study specific biospecimen handling issues, including the cold ischemic time (delay to formalin fixation), time in formalin, freezing methods, and storage temperatures and durations. RNA and DNA from biospecimens collected under these conditions was analyzed on multiple molecular platforms. The potential effects of these pre-analytical conditions on protein integrity and detection of metabolites were also examined. Data from this study will be used to develop evidence-based biospecimen standard operating procedures and best practices for fit-for-purpose collection, processing, and storage of biospecimens. The BPV 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 sub-studies below or in the &#34;Substudies&#34; box located on the right hand side of this top-level study page phs001304 BPV Cohort. The substudy links will be active once they are released by dbGaP. Preanalytical Impacts on Global Metabolite Profiling - plasma (MassSpec by Metabolon) This study was to evaluate the impact of the storage temperature (s) (-80&#176;C and LN2 vapor) and the length of storage on human plasma quality using LC-MS/MS (liquid-chromatography-mass spectrometry/mass spectrometry) based global metabolite profiling. The study includes 240 plasma samples collected from 40 donors. Investigate the effect of the delay to fixation on the proteome and phosphoproteome -FFPE (MassSpec by Caprion). The study is to do proteome and phosphoproteome analysis on Delay to fixation was carried out using FFPE tumor samples from colon and ovarian cancer patients comparing 2, 3, and 12hr delay to fixation to the 1hr time point. The study includes 100 samples 20 donors. Investigate the effect of storage conditions of tumor specimens on the proteome and phosphoproteome profiling- Frozen tissue and plasma (MassSpec by Caprion). The study was to evaluate the effects of storage conditions on tumor specimens. Plasma samples from 40 cancer patients stored at two different temperatures (-80&#176;C and LN2) for a given period (0-2, 6-8, and 12-14 months) were evaluated. Frozen kidney tumor samples from 20 patients were compared for effects of different snap frozen (dry ice vs. LN2) and storage temperatures (-80&#176;C and LN2). The study includes 100 tissue and 240 plasma samples from 60 donors. Preanalytical Impacts on Genomic Sequencing by Next Generation Sequencing (NGS) technology (mRNA/miRNA and WES by Expression Analysis). The goal of the study is to determine the effects of cold ischemic delay-to-fixation (4 time points) and formalin preservation (FFPE) on the nature and quality of genomic profiles using the matched freshly frozen sample as the gold standard, which including WES, RNAseq. The study includes 395 samples from 37 donors. Preanalytical Impacts on Copy Number Variation (CNV) Detection by aCGH technology (aCGH by Georgetown University). This study was to use aCGH to evaluate the effect of variation in cold ischemia time and time in formalin fixation on CNV in DNA extracted from kidney cancer specimens. The study includes 235 samples from 40 donors. Evaluation of frozen conditions on mRNA profiling by TaqMan assay (mRNA expression by Georgetown University). This study was to utilize gene expression profiling, using custom TaqMan arrays, to compare the molecular profiles of RNA from frozen tumor samples collected using two freezing methods (dry ice or LN2), two storage temperatures (-80&#176;C or LN2 vapor), as well as Optimal Cutting Temperature (OCT) compound and non-OCT embedded. The study includes 100 samples from 20 donors. mRNA signature for stratification by cold ischemia time (mRNA expression by IBBL). The study was to determine the effects of cold ischemic time (delay-to-fixation) and formalin preservation (FFPE) on mRNA detection by Taqman assay using tumor tissue specimens from kidney, colon and ovarian cancer patients. There are160 samples from 40 donors. The Biospecimen PV cohort is utilized in the following dbGaP individual studies. To view molecular data, and derived variables collected in these individual studies, please click on the following individual studies below or in the "Sub-studies" box located on the right hand side of this top-level study page phs001304 Biospecimen PV cohort. phs001634 CIT mRNA phs001635 CNV aCGH phs001636 Fixation Delay phs001637 Global Metabolite Profiling phs001638 mRNA TaqMan phs001639 NGS phs001640 Tumor Storage

  Study phs001304

• Submitter Portal API

  Submitter Portal API 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. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have 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, 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 the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

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

• National Cancer Institute Cancer Genome Characterization Initiative (CGCI)

  The Office of Cancer Genomics at the National Cancer Institute sponsored a series of studies as part of the Cancer Genome Characterization Initiative (CGCI) to assess novel emerging sequencing technologies in cancer. The CGCI program included comprehensive characterization of the genetic aberrations found in different pediatric and/or adult tumors. CGCI characterized a number of B-cell non-Hodgkin lymphomas (including diffuse large B-cell lymphoma (DLBCL) from patients with and without HIV+ infection, follicular lymphoma (FL), as well as adult and pediatric Burkitt lymphomas), and additional HIV-associated tumors (including DLBCL, lung, and cervical cancers). All data from these projects is available at the NCI Genomic Data Commons. Individual project descriptions are available by disease on the substudy pages (links are included at the top of this page). Brief summaries are as follows: Non-Hodgkin Lymphoma (NHL) - CGCI investigators probed genomic alterations more deeply than had previously been possible by using state-of-the-art RNA sequencing (mRNA-seq) and whole genome shotgun sequencing (WGS) coupled with leading edge bioinformatics, data management and analysis approaches. The project sequenced tumor DNA and/or RNA from 117 NHL tumor samples and 10 cell lines. This included the genomes or exomes of 1 Follicular Lymphoma (FL) and 13 diffuse large B-cell lymphoma (DLBCL) cases, all with matched constitutional DNA sequenced to comparable depths, RNA-sequencing (mRNA-seq) of 92 DLBCL, 12 FL and 8 B-cell NHL cases with other histologies and 10 DLBCL-derived cell lines. The DLBCL cases and cell-lines are from the two major subtypes of DLBCL: germinal center B-cell (GCB) and activated B-cell (ABC). HIV+ Tumor Molecular Characterization Project (HTMCP) - This project was a joint effort of the Office of Cancer Genomics (OCG) and the Office of HIV and AIDS Malignancy (OHAM). Its goals were to characterize HIV-associated cancers (obtained from HIV-infected patients) and compare them to the same types of cancers from patients without HIV infection. Investigators performed 30X genome sequencing of 100 cases of paired tumor and germline DNA, along with transcriptome sequencing in each of 3 types of HIV+ tumors (DLBCL, lung and cervical cancers). These platforms allow discovery of mutations both in coding and non-coding genomic regions, gene expression and genomic alterations (including translocations, insertions and deletions). Comparing tumors of cancer patients both with and without HIV-infection provides insight into the potential function of this virus in certain cancers. Burkitt Lymphoma Genome Sequencing Project (BLGSP) - This project was a collaborative effort between the National Cancer Institute and the Foundation for Burkitt Lymphoma Research to develop a databank of the many alterations found in Burkitt lymphoma (BL), an uncommon type of Non-Hodgkin lymphoma that occurs most often in children and young adults. The goal of the BLGSP was to explore potential genetic changes in patients with BL that could lead to better prevention, detection and treatment of the cancer. The project characterized the alterations of the tumors' genomes (with matched normal as control) and transcriptomes by sequencing the DNA and RNA of each case. Using the data generated, the ultimate goals of the project was to discover the molecular changes that are present in BL patients and then determine how those changes correlate with treatment regimen and outcome. CGCI data is accessible at the NCI's Genomic Data Commons (GDC) via the GDC's Data Portal and from each of the CGCI Publication Pages at the GDC (Please see the "Supplemental Links" section of any CGCI publication's "Publication Information and Associated Data Files page" at the GDC.). Available datasets include raw sequencing data, datasets generated by the original CGCI research teams (fully annotated clinical information and higher-level/analyzed molecular characterization data), as well as higher level data generated by the GDC. Please see the CGCI Use and Publication Guidelines for updated details on the sharing of any CGCI substudy data, including how to cite CGCI.To learn more about the CGCI studies, please visit the CGCI Program website.

  Study phs000235

• NHGRI GREGoR Consortium: Genomics Research to Elucidate the Genetics of Rare Disease

  The NHGRI GREGoR (Genomics Research to Elucidate the Genetics of Rare Disease) Consortium was established in June 2021 with the goal of developing novel tools and approaches to advance the discovery of the genetic basis of rare conditions. Numerous types of molecular data are generated in GREGoR and available on the AnVIL cloud platform via dbGaP application, including short- and long-read genome and exome sequencing, transcriptomics, metabolomics, methylomics, and proteomics. De-identified clinical and demographic data is obtained, with a focus on standardized ontologies.Visit the GREGoR Consortium data webpage for summary information about the GREGoR Dataset, including numbers of participants and data types, methods documentation, and Release Notes. The Consortium comprises five Research Centers (RCs - see below), a Data Coordinating Center (DCC), and various partner members and external collaborators.Baylor College of Medicine Research Center (BCM-GREGoR) The Baylor College of Medicine GREGoR program, which is part of the GREGoR consortium, enrolls individuals, families, and cohorts with suspected rare disease across a range of syndromic and non-syndromic phenotypes. Subjects are enrolled from national and international collaborating physician referrals. Subjects provide written informed consent for future re-contact. Data generated and shared include family structure, detailed phenotypes, exome or short-read genome data, and in some cases long-read genome or RNA-sequencing, and these are shared upon completion of standard quality control checks and annotation. Broad Institute (Broad) The Broad Center for Mendelian Genomics, part of the GREGoR consortium uses next-generation sequencing (exome, genome, transcriptome, and long read sequencing), computational approaches, and functional studies to discover the variants and genes that underlie Mendelian conditions with a particularly focus on neuromuscular, neurodevelopmental, and syndromic phenotypes. Samples come from collaborators and direct enrollment through the Rare Genomes Project and we are committed to rapid data sharing without an embargo period. University of California, Irvine (UCI-GREGoR) To accelerate the pace of Mendelian disease gene discovery and clinical implementation, we propose a Mendelian Genomics Research Center, part of the GREGoR Consortium, leveraging the broad pediatric and adult clinical and research expertise at Children's National Hospital and University of California, Irvine. Our goal is to develop best practices to increase the diagnostic yield of rare diseases, engage the community to reduce health disparities for complex diagnoses, while creating a dataset accessible to all. Our Center will unite world class experts combining basic and translational research with innovative approaches to phenotyping, variant identification and functional investigation of both coding and non-coding sequence changes with the goals of discovering novel Mendelian gene variations and identifying variants not detected on current sequencing pipelines, disambiguating uncertain variants into disease-causing versus benign categorizations, and sharing information by working collaboratively with the GREGoR community.GREGoR Stanford Site (GSS) The goal of the GREGoR Stanford Site (GSS) is to provide a platform for functional genomics research and validation to improve diagnosis in Mendelian disease. Participants included individuals with undiagnosed suspected Mendelian disease who had non-diagnostic exome sequencing and their immediate family members. Participants and their family members provided written, informed consent and biological samples from which DNA, RNA, plasma, fibroblasts, PBMCs and other cell types were generated and stored. Samples from research participants and their immediate family members may have undergone short and long-read genome sequencing, transcriptome sequencing, metabolomics and/or lipidomics profiling, methyl-capture-sequencing and ATAC-sequencing. De-identified clinical data extracted from participant medical records are linked to the samples. University of Washington Center for Rare Disease Research (UW-CRDR) The goals of the University of Washington Center for Rare Disease Research are to: (1) maximize novel gene discovery for Mendelian conditions by recruitment, short- and long-read whole genome sequencing, transcriptome sequencing and analysis of families with rare conditions for which the gene is either unknown or the gene is known but no pathogenic variant can be identified via clinical testing; (2) develop new strategies for gene discovery for Mendelian conditions caused by variants that are difficult to detect using conventional testing strategies, variants of unknown function effect (e.g., regulatory, structural variants) or have unusual modes of inheritance; and (3) implement high-throughput screening and targeted follow-up functional studies to prioritize and validate candidate non-coding variants. De-identified data and phenotypic information are shared via MyGene2, ClinVar, and AnVIL.

  Study phs003047

• The Finland-United States Investigation of NIDDM Genetics (FUSION) Tissue Biopsy Study

  The Finland-United States Investigation of NIDDM Genetics (FUSION) study is a long-term effort to identify genetic variants that predispose to type 2 diabetes (T2D) or that impact the variability of T2D-related quantitative traits (QTs). Most of the variants associated with T2D and related traits (glucose and insulin, anthropometrics, lipids) through genome-wide association studies (GWAS) occur in non-coding regions, suggesting a strong regulatory component to disease susceptibility. Regulatory element activity is often tissue-specific, which further complicates discovery of the causal/functional variation. Therefore, there is a critical need to identify the appropriate cell type, regulatory elements, target genes, and causal variants(s) in T2D-relevant tissues. We hypothesize that a subset of T2D and related variants alter gene expression regulation in skeletal muscle and adipose tissue - two major insulin target tissues and play key roles in insulin resistance. To that end, our study contains a comprehensive survey of genomics, epigenomics and transcriptomics in skeletal muscle and adipose tissue from individuals with glucose tolerance categories ranging from normal to T2D.For this FUSION Tissue Biopsy Study, we obtained RNA-Seq, microRNA (miRNA)-Seq, and DNA methylation (methyl)-Seq data on biopsy samples from 331 individuals from across the range of glucose tolerance: 124 normal glucose tolerance (NGT), 77 impaired glucose tolerance (IGT), 44 impaired fasting glucose (IFG), and 86 newly-diagnosed T2Ds. Participants completed two study visits, two weeks apart. First visits comprised most of the clinical phenotyping, including four-point OGTT (fasting, and 30, 60, and 120 minute post-load); BMI, WHR; lipids; blood pressure; and many other variables. Participants also completed FUSION health history, medication, and lifestyle questionnaires. On the second visit, we obtained ~250mg vastus lateralis skeletal muscle, ~750mg abdominal subcutaneous adipose, and a ~5x15mm section of abdominal skin. Visits were completed in March 2013. RNA isolation is ongoing in the Collins laboratory at the NIH, RNA and miRNA sequencing at the NIH Intramural Sequencing Center (NISC), and genotyping at the Center for Inherited Disease Research (CIDR). Individual-level data is available here for the 306 individuals who consented to data deposit. To focus on evaluation of gene expression and its regulation in skeletal muscle, we analyzed mRNA extracted from vastus lateralis skeletal muscle obtained from 271 of the 331 individual subjects from Finland, along with genome-wide genotypes. Individual-level data is available here for the 250 subjects who consented to the use of their data.Release phs001048.v2.p1 adds muscle data for an additional 42 subjects and data from adipose tissue for 276 subjects. Total RNA was isolated using Trizol extraction in the Collins laboratory at the NIH. The mRNA was poly-A selected, 24-plex libraries were generated using the Illumina TruSeq directional mRNA-seq library protocol and RNA sequencing was performed on HiSeq2000 sequencers using 101bp paired-end reads at NISC. miRNA libraries were prepared from total RNA from 296 muscle and 270 adipose samples, pooled and sequenced 50bp single-end reads on Illumina HiSeq2500. Data for 272 muscle and 251 adipose samples are available here for individuals with consent for data deposit. DNA was extracted from blood in the Collins laboratory, and genotyping on the Illumina Omni2.5M array was performed at CIDR. Genotypes were imputed using the HRC 2016 reference panel. In order to assess regions of open chromatin in skeletal muscle, we obtained muscle tissue from a commercial provider to perform ATAC-seq; these samples were sequenced at the University of Michigan DNA Sequencing Core.Release phs001048.v3.p1 adds single-nucleus (sn) RNA-seq and ATAC-seq data in 287 skeletal muscle samples out of the original 331 individuals. Individual-level data is available here for the 265 subjects who consented to the use of their data. The frozen tissue biopsy samples were processed in ten batches, each consisting of 40-41 samples. These batches were organized using a randomized block design to protect against experimental contrasts of interest including cohort, age, sex, BMI among others. Samples in each batch were pulverized, pooled together followed by nuclei isolation. The nuclei were processed on the 10X Genomics Chromium platform separately for snATAC-seq and snRNA-seq (v. 3.1 chemistry for snRNA-seq).Release phs001048.v4.p1 adds additional phenotypes and provides some corrections to several previous phenotypes.

  Study phs001048

• eMERGE Network Imputed GWAS for 41 Phenotypes

  The electronic Medical Records and Genomics (eMERGE) Network is a consortium of ten participating sites (Cincinnati Children&#39;s Hospital Medical Center/Boston Children&#39;s Hospital, Children&#39;s Hospital of Philadelphia, Essentia Institute of Rural Health, Marshfield Clinic Research Foundation and Pennsylvania State University, Geisinger Clinic, Group Health Cooperative/University of Washington, Mayo Clinic, Icahn School of Medicine at Mount Sinai, Northwestern University, Vanderbilt University Medical Center) funded by the NHGRI to investigate the use of electronic medical record (EMR) systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 55,000 individuals using EMR-derived phenotypes and DNA from linked Biorepositories. Using electronic phenotyping methods, the consortium used DNA samples from all participating sites to explore the genetic determinants of over forty phenotypes, including Abdominal aortic aneurysm; Ace-Inhibitor/Cough; Attention Deficit Hyperactivity Disorder; Age-related macular disease; Appendicitis; Asthma; Atopic Dermatitis; Autism; Benign Prostatic Hyperplasia; Carotid artery disease as a Quantitative Measure; caMRSA; Cataract; Clostridium difficile colitis; Extreme Obesity; Chronic Kidney Disease; Chronic Kidney Disease and Type 2 Diabetes; Chronic Kidney Disease, Type 2 Diabetes and Hypertension; Colon Polyps; Cardiorespiratory Fitness; Dementia; Diverticulosis; Diabetic retinopathy; Gastroesophageal Reflux Disease; Glaucoma; Height; Heart failure; Hypothyroidism; Lipids; Ocular hypertension; Peripheral Arterial Disease; QRS duration; Red blood cell indices; Remission of Diabetes after ROUX-EN-Y gastric bypass surgery; Resistant hypertension; MACE while on Statins; Type 2 Diabetes; Venous Thromboembolism; White blood cell indices; and Zoster virus infection, as well as using the phenome-wide association study (PheWAS) paradigm to replicate and discover relationships between targeted genotypes with multiple phenotypes. Sites and participants include: Children&#39;s Hospital of Pennsylvania (CHOP): The Center for Applied Genomics (CAG) at the Children&#39;s Hospital of Philadelphia (CHOP) is a high-throughput, highly automated genotyping and sequencing facility equipped with state-of-the-art genotyping and sequencing platforms. Children who are treated at the Children&#39;s Hospital Healthcare Network and their parents may be eligible to take part in a major initiative to collect more than 100,000 blood samples, covering a wide range of pediatric diseases. A large majority of participants consenting to prospective genomic analyses also consent to analysis of their de-identified electronic medical records (EMRs). EMRs are longitudinal, with a mean duration of 6.5 years. Cincinnati Children&#39;s Hospital Medical Center/Boston&#39;s Children&#39;s Hospital (CCHMC/BCH): Cincinnati Children&#39;s Hospital Medical Center (CCHMC) and Boston Children&#39;s Hospital (BCH) are pediatric institutions dedicated to improving health and welfare of children and to the shared purpose of discovery and practical application of new genomic information to the ordinary care of children. The CCHMC/BCH site has been built on a five-year history of collaboration, particularly in patient electronic record (ERM)-related informatics, the basis of much of eMERGE II. CCHMC and BCH together bring an extraordinary faculty to eMERGE II who are committed to diseases that afflict children, specifically phenotypes that focus upon diseases of children in ways that will leverage the available eMERGE adult GWAS and EMRs to discover meaningful use results. CCHMC/BCH plans to demonstrate real-time execution of phenotypic selection across their two distinct pediatric institutions as a model for ensuring phenotypic standardization and for national scalability. They will also look carefully at parents&#39; responses to results and use of their children&#39;s research results and better understand the factors that influence their decisions about learning incidental findings. In addition to patient and parent perceptions CCHMC/BCH will also explore clinician perceptions of pharmacogenetic research results after EMR integration. Geisinger Health System: A research cohort of adult Geisinger Clinic patients was enrolled from community-based primary care clinics of the Geisinger Health System. Patients were eligible for enrollment if they were a primary care patient of a Geisinger Clinic physician and were scheduled for a non-emergent clinic visit. All participants provided written informed consent and HIPAA authorization. Consenting patients agreed to provide blood samples for broad biomedical research use, and permission to access data in their Geisinger electronic medical record for research. The enrollment rate was 90% of patients approached. The demographics of the cohort approximate those of the Geisinger Clinic outpatient population. Research blood samples were collected during an outpatient clinical phlebotomy encounter. Research blood samples are coded and stored in a central biorepository. Samples are linkable to clinical data in a de-identified manner for research via an IRB-approved data broker process. For genomic analysis, DNA is extracted from EDTA-anticoagulated whole blood. Group Health(GH)/University of Washington (UW): GH participants for the PGx project were enrolled in the eMERGE Network through the Northwest Institute of Genetic Medicine (NWIGM) biorepository, and provided the appropriate consent to receive clinically relevant genetic results (N~6300.) Participants were eligible if aged 50 - 65 years old at the time of their enrollment into the NWIGM repository, living, enrolled in GH&#39;s integrated group practice, and had completed an online Health Risk Appraisal. The selection algorithm was based on several data sources from the EHR at Group Health: 1. Demographics - participants with self-reported race as Asian or African ancestry were prioritized and selected to enrich for non-European ancestry; 2. Diagnosis and procedure codes - participants were selected if found to have a history of hypertension, atrial fibrillation (AF), or congestive heart failure (CHF). Participants with a history of arrhythmia were added if the entire selection algorithm did not generate 900 individuals. We also enriched for participants with EHR evidence of actionable indications related to PGRNSeq genes. Participants were selected if found to have an ICD9 code for malignant hyperthermia, hypertension, atrial fibrillation, congestive heart failure or long QT syndrome (LQTS); 3. Laboratory values - if participants had any laboratory event of creatine kinase (CK) &#62;1000, and were dispensed statins within 6 months of the event, then they were selected; and 4. Medications - participants were excluded if ever on carbamazepine or had a current regimen of warfarin. Essentia Institute of Rural Health, Marshfield Clinic, Pennsylvania State University (Marshfield): The Marshfield Clinic Personalized Medicine Research Project is a population-based biobank in central Wisconsin with more than 20,000 adult subjects who provided written, informed consent to access their medical records and provided a blood sample from which DNA was extracted and plasma and serum stored. In addition to an average of 30 years of medical history data, a questionnaire about environmental exposures, including a detailed food frequency questionnaire, is available to facilitate gene/environment studies. Mayo Clinic: The Mayo biobank is a disease-specific biobank for vascular diseases including peripheral arterial disease (PAD). PAD patients were identified from individuals referred to the non-invasive vascular laboratory for lower extremity arterial evaluation. Since 1997, laboratory findings have been recorded into an electronic database employing an in-house software package for data archiving and retrieval; this data becomes part of the Mayo EMR. Patients referred to the center with suspected PAD undergo a comprehensive non-invasive evaluation including the ankle-brachial index (ABI) - the ratio of blood pressure measured in the upper arms divided by blood pressure measured at the ankles. Controls subjects are identified from patients referred to the Cardiovascular Health Clinic for stress ECG. The prevalence of PAD in patients with normal exercise capacity who do not have inducible ischemia on the stress ECG , was &#60;1%. Data regarding risk factors for atherosclerosis such as diabetes, dyslipidemia, hypertension, and smoking are ascertained from the EMR. Icahn School of Medicine at Mount Sinai School (Mt. Sinai): The Institute for Personalized Medicine (IPM) Biobank Project is a consented, EMR-linked medical care setting biorepository of the Mount Sinai Medical Center (MSMC) drawing from a population of over 70,000 inpatients and 800,000 outpatient visits annually. MSMC serves diverse local communities of upper Manhattan, including Central Harlem (86% African American), East Harlem (88% Hispanic Latino), and Upper East Side (88% Caucasian/white) with broad health disparities. IPM Biobank populations include 28% African American (AA), 38% Hispanic Latino (HL) predominantly of Caribbean origin, 23% Caucasian/White (CW). IPM Biobank disease burden is reflective of health disparities with broad public health impact: average body mass index of 28.9 and frequencies of hypertension (55%), hypercholesterolemia (32%), diabetes (30%), coronary artery disease (25%), chronic kidney disease (23%), among others. Biobank operations are fully integrated in clinical care processes, including direct recruitment from clinical sites, waiting areas and phlebotomy stations by dedicated Biobank recruiters independent of clinical care providers, prior to or following a clinician standard of care visit. Recruitment currently occurs at a broad spectrum of over 30 clinical care sites. Northwestern University: The NUgene Project is a repository with longitudinal medical information from participating patients at affiliated hospitals and outpatient clinics from the Northwestern University Medical Center. Participants&#39; DNA samples are coupled with data from a self-reported questionnaire and continuously updated data from our Electronic Medical Record (EMR) representing actual clinical care events. Northwestern has a state-of-the art, comprehensive inpatient and outpatient EMR system of over 2 million patients. NUgene has broad access to participant data for all outpatient visits as well as inpatient data via a consolidated data warehouse. NUgene participants consent to distribution and use of their coded DNA samples and data for a broad range of genetic research by third-party investigators. Vanderbilt University: BioVU, Vanderbilt&#39;s DNA databank, is an enabling resource for exploration of the relationships among genetic variation, disease susceptibility, and variable drug responses, and represents a key first step in moving the emerging sciences of genomics and pharmacogenomics from research tools to clinical practice. BioVU acquires DNA from discarded blood samples collected from routine patient care. The biobank is linked to de-identified clinical data extracted from Vanderbilt&#39;s EMR, which forms the basis for phenotype definitions used in genotype-phenotype correlations.

  Study phs000888

• From research to data sharing: exploring EGA user's experiences

  The Cell Plasticity and Regeneration Group at the Bellvitge Biomedical Research Institute-IDIBELL focuses on the process of recruitment of macrophages that takes place in the small intestine during injury and healing. They recently published a paper titled “Mucosal Macrophages Govern Intestinal Regeneration in Response to Injury" in Gastroenterology Journal. As part of the research, some experiments were conducted using human intestinal organoid lines. These cells were processed for RNA sequencing, and the sequencing data were deposited at the EGA to be made available to the scientific community. When dealing with human genomic information, repositories must ensure the availability of the datasets while ensuring data protection. In this context, the European Genome-phenome Archive stands as a service for secure archiving and sharing of genetic, phenotypic and clinical data resulting from biomedical research. Following the recent publication of their paper, we took the opportunity to talk to Ilias Moraitis, first author, and Jordi Guiu, group leader, to find out about their experience with data sharing. Could you explain the focus of your research? In the lab, we study intestinal regeneration and how immune cells participate in this process. We use several techniques: engineered mouse models, image tracing, as well as mouse and human cells intestinal organoids. What challenges do you face regarding data management? We didn’t have a lot of problems. Always the informatic part, the data analysis, can give problems. But everything was smooth and working. We think it’s very important to deposit the data in repositories. For the mouse data it is very straightforward, but for us it was the first time depositing human data, which is sensitive because it comes from patients, and this is legally regulated. That’s why we thought about the EGA, and it was our first time. Why do you think it is important to submit data to repositories such as EGA? Because we think data is important for the science. Nowadays, we are sequencing a lot everywhere worldwide and having these resources shared with the scientific community it’s not only good for science, but it is also saving money and reducing costs. And there is so much data in there that can be used for other projects and for other questions. And it saves time! How was the process of submitting the data to the EGA? The communication worked very well but it was slower than we would like. But I think this is something we learn on the way. People usually wait until the last minute to do this before publication but if you know it in advance, you can start the process earlier. If you had to repeat the process, would you do anything differently? It’s like everything, isn’t it? For the first time you don’t know, you aren’t sure, but for the second time you know the steps, you know what to do and it’s faster. Of course, we would to do it earlier. Also, there were some things related to the control access that we didn’t know how to manage, but it was something more internal to us. Who is going to receive the communications and when, is our ethical committee going to evaluate this? All these technicalities that we didn’t know before starting this process, so we had to think about all these things. Next time it will be faster on our side. Do you have any suggestions for us to improve the submission process? Maybe we’ll need to ask our bioinformatician who did it! He was in charge of this part. Besides that, we think if the process were faster, it would be better for everyone. Also, in science a lot of times you have to do a lot of things at the very last minute, because of the nature of the experiments, or the need to accomplish for submitting a paper. Being faster in the process would be a plus. On your side, we went through the process and were able to find some information, but there were aspects we weren't aware of and weren't sure how to handle. I'm not sure if other institutes have different protocols for managing data requests or how they handle these internally. We believe the main issue lies in how the forms are filled out. Do you have any recommendations for other submitters? The main advice is to do this with enough time. Submit the data when you have the sequences, and don’t wait until the last minute. And then it can be under embargo, so you don’t need to make it public at that moment. As soon as you sequence, upload it and then it will be there for whenever you need to publish. How do you think we could encourage other researchers to submit their data? There are different layers here. One is that it is mandatory. You have to do this. The other is that we belong to a research community, to the same community and sharing this is making our research community stronger and more efficient. And then, also because this gives you visibility. The data is there, other people can analyse your data, and this also will bring citations to your papers. It has many advantages.

  Blog from-research-to-data-sharing

• Detection of Colorectal Cancer Susceptibility Loci Using Genome-Wide Sequencing

  The Genetics and Epidemiology of Colorectal Cancer Consortium (GECCO) is a collaborative effort comprised of a coordinating center and scientific researchers from well-characterized cohort and case-control studies. This international consortium aims to accelerate the discovery of common and rare genetic risk variants for colorectal cancer by conducting large-scale meta-analyses of existing and newly generated genome-wide association study (GWAS) data, whole genome sequencing, replicating and fine-mapping of genetic discoveries, and investigating how genetic risk variants are modified by environmental risk factors. To expand these efforts, we assembled case-control sets or nested case-control sets from 6 different North American or European studies. Summary descriptions and study participant inclusions/exclusion criteria for each of these studies are detailed below. Cancer Prevention Study II (CPS II): The CPS II Nutrition cohort is a prospective study of cancer incidence and mortality in the United States, established in 1992 and described in detail elsewhere (Calle et al., 2002 PMID:12015775; Campbell et al., 2014 PMID:25472679). At enrollment, participants completed a mailed self-administered questionnaire including information on demographic, medical, diet, and lifestyle factors. Follow-up questionnaires to update exposure information and to ascertain newly diagnosed cancers were sent biennially starting in 1997. Reported cancers were verified through medical records, state cancer registry linkage, or death certificates. The Emory University Institutional Review Board approves all aspects of the CPS II Nutrition Cohort. We restricted to samples that had blood DNA source. Controls were matched to cases in a case/control ratio of 2:1 on reference year and sex. Darmkrebs: Chancen der Verh&#252;tung durch Screening (DACHS): This German study was initiated as a large population-based case-control study in 2003 in the Rhine-Neckar-Odenwald region (southwest region of Germany) to assess the potential of endoscopic screening for reduction of colorectal cancer risk and to investigate etiologic determinants of disease, particularly lifestyle/environmental factors and genetic factors. Cases with a first diagnosis of invasive colorectal cancer (International Classification of Diseases 10 codes C18-C20) who were at least 30 years of age (no upper age limit), German speaking, a resident in the study region, and mentally and physically able to participate in a one-hour interview, were recruited by their treating physicians either in the hospital a few days after surgery, or by mail after discharge from the hospital. Cases were confirmed based on histologic reports and hospital discharge letters following diagnosis of colorectal cancer. All hospitals treating colorectal cancer patients in the study region participated. Based on estimates from population-based cancer registries, more than 50% of all potentially eligible patients with incident colorectal cancer in the study region were included. Community-based controls were randomly selected from population registries, employing frequency matching with respect to age (5-year groups), sex, and county of residence. Controls with a history of colorectal cancer were excluded. Controls were contacted by mail and follow-up calls. The participation rate was 51%. During an in-person interview, data were collected on demographics, medical history, family history of CRC, and various life-style factors, as were blood and mouthwash samples. Routine formalin-fixed, paraffin-embedded (FFPE) tumor samples from the patients enrolled were requested from the pathology institutes and used for tumor tissue analyses. This analysis includes participants with blood source DNA that were recruited up to 2010 in this ongoing study. Controls were matched to cases on reference age and sex in a case/control ratio of 2:1. Health Professionals Follow-up Study (HPFS): A parallel prospective study to the NHS (Nurses' Health Study). The HPFS cohort comprised 51,529 men aged 40-75 who, in 1986, responded to a mailed questionnaire (Rimm et al., 1990 PMID:2090285). Participants provided information on health related exposures, including current and past smoking history, age, weight, height, diet, physical activity, aspirin use, and family history of colorectal cancer. Colorectal cancer and other outcomes were reported by participants or next-of-kin and were followed up through review of the medical and pathology record by physicians. Overall, more than 97% of self-reported colorectal cancers were confirmed by medical record review. Information was abstracted on histology and primary location. Incident cases were defined as those occurring after the subject provided the blood sample. Prevalent cases were defined as those occurring after enrollment in the study but before the subject provided the blood sample. Follow-up evaluation has been excellent, with 94% of the men responding to date. Colorectal cancer cases were ascertained through January 1, 2008. In 1993-1995, 18,825 men in the HPFS mailed blood samples by overnight courier, which were aliquoted into buffy coat and stored in liquid nitrogen. In 2001-2004, 13,956 men in the HPFS who had not provided a blood sample previously mailed in a swish-and-spit sample of buccal cells. Incident cases were defined as those occurring after the subject provided a blood or buccal sample. Prevalent cases were defined as those occurring after enrollment in the study in 1986, but before the subject provided either a blood or buccal sample. Participants with histories of cancer (except nonmelanoma skin cancer), ulcerative colitis, or familial polyposis, case-control sets were excluded. Control participants were required to be free of invasive colorectal cancer and non-invasive (stage 0 in situ) colorectal cancer. For this study, only European ancestry participants with blood source DNA and incident colorectal cancer cases were eligible for selection. Since enrollment year and sex matched exactly, controls were randomly selected in a case/control ratio of 2:1. Nurses Health Study (NHS): The NHS cohort began in 1976 when 121,700 married female registered nurses age 30-55 years returned the initial questionnaire that ascertained a variety of important health-related exposures (Belanger et al., 1978 PMID:248266). Since 1976, follow-up questionnaires have been mailed every 2 years. Colorectal cancer and other outcomes were reported by participants or next-of-kin and followed up through review of the medical and pathology record by physicians. Overall, more than 97% of self-reported colorectal cancers were confirmed by medical-record review. Information was abstracted on histology and primary location. The rate of follow-up evaluation has been high: as a proportion of the total possible follow-up time, follow-up evaluation has been more than 92%. Colorectal cancer cases were ascertained through June 1, 2008. In 1989-1990, 32,826 women in NHS I mailed blood samples by overnight courier, which were aliquoted into buffy coat and stored in liquid nitrogen. In 2001-2004, 29,684 women in NHS I who did not previously provide a blood sample mailed a swish-and-spit sample of buccal cells. Incident cases were defined as those occurring after the subject provided a blood or buccal sample. Prevalent cases were defined as those occurring after enrollment in the study in 1976 but before the subject provided either a blood or buccal sample. Participants with histories of cancer (except nonmelanoma skin cancer), ulcerative colitis, or familial polyposis, case-control sets were excluded. For this study, only European ancestry participants with blood source DNA and incident colorectal cancer cases were eligible for selection. Since enrollment year and sex matched exactly, controls were randomly selected in a case/control ratio of 2:1. Prostate, Lung, Colorectal and Ovarian Cancer Screening Trail (PLCO): PLCO enrolled 154,934 participants (men and women, aged between 55 and 74 years) at ten centers into a large, randomized, two-arm trial to determine the effectiveness of screening to reduce cancer mortality. Sequential blood samples were collected from participants assigned to the screening arm. Participation was 93% at the baseline blood draw. White colorectal cancer cases with a family history of colorectal cancer (no history of ulcerative colitis, Crohn's Disease, diverticulitis, Gardner's syndrome, Familial Polyposis) and successful genotyping from previous Peters GWAS were selected for this project. Controls were matched to cases on reference age and sex in a case/control ratio of 2:1. Women's Health Initiative (WHI): WHI is a long-term national health study that has focused on strategies for preventing heart disease, breast and colorectal cancer, and osteoporotic fractures in postmenopausal women. The original WHI study included 161,808 postmenopausal women enrolled between 1993 and 1998. The Fred Hutchinson Cancer Research Center in Seattle, WA serves as the WHI Clinical Coordinating Center for data collection, management, and analysis of the WHI. The WHI has two major parts: a partial factorial randomized Clinical Trial (CT) and an Observational Study (OS); both were conducted at 40 Clinical Centers nationwide. The CT enrolled 68,132 postmenopausal women between the ages of 50-79 into trials testing three prevention strategies. If eligible, women could choose to enroll in one, two, or all three of the trial components. The components are: Hormone Therapy Trials (HT): This double-blind component examined the effects of combined hormones or estrogen alone on the prevention of coronary heart disease and osteoporotic fractures, and associated risk for breast cancer. Women participating in this component with an intact uterus were randomized to estrogen plus progestin (conjugated equine estrogens [CEE], 0.625 mg/d plus medroxyprogesterone acetate [MPA] 2.5 mg/d) or a matching placebo. Women with prior hysterectomy were randomized to CEE or placebo. Both trials were stopped early, in July 2002 and March 2004, respectively, based on adverse effects. All HT participants continued to be followed without intervention until close-out. Dietary Modification Trial (DM): The Dietary Modification component evaluated the effect of a low-fat and high fruit, vegetable and grain diet on the prevention of breast and colorectal cancers and coronary heart disease. Study participants were randomized to either their usual eating pattern or a low-fat dietary pattern. Calcium/Vitamin D Trial (CaD): This double-blind component began 1 to 2 years after a woman joined one or both of the other clinical trial components. It evaluated the effect of calcium and vitamin D supplementation on the prevention of osteoporotic fractures and colorectal cancer. Women in this component were randomized to calcium (1000 mg/d) and vitamin D (400 IU/d) supplements or a matching placebo. The Observational Study (OS) examines the relationship between lifestyle, environmental, medical and molecular risk factors and specific measures of health or disease outcomes. This component involves tracking the medical history and health habits of 93,676 women not participating in the CT. Recruitment for the observational study was completed in 1998 and participants were followed annually for 8 to 12 years. All centrally confirmed White cases of invasive colorectal cancer, or death from colorectal cancer were selected as potential cases from the March, 2011 database. Case priory lists are: 1) have positive family history of colorectal cancer; 2) randomly select cases until we get a total of n=800 cases. Control participants were required to be White, free of invasive colorectal cancer and non-invasive (stage 0 in situ) colorectal cancer. Centrally denied cases of colorectal cancer were not allowed into the control pool. Case and control participants were subject to the following exclusion criteria: (1) had prior history of colorectal cancer at baseline; (2) had no available DNA (DNA searching as Nov 15, 2012); (3) cannot be deposited to dbGaP; (4) lost to follow-up after enrollment; (5) selected for WHI study M26 Phase II. Controls were matched to cases in a case/control ratio of 2:1. In order to get 2 cases with 1 control, cases were grouped by enrollment year (a total of 5 groups). For each year group, around 50% cases were selected to match controls. In total, 401 cases were selected to match controls. Matching was done on enrollment year, which was matched exactly. For additional information, see dbGaP: phs000200 and ClinicalTrials: NCT00000611.

  Study phs001554

• Women's Health Initiative Clinical Trial and Observational Study

  The Women&#39;s Health Initiative (WHI) is a long-term national health study that has focused on strategies for preventing heart disease, breast and colorectal cancer, and osteoporotic fractures in postmenopausal women. The original WHI study included 161,808 postmenopausal women enrolled between 1993 and 1998. The Fred Hutchinson Cancer Research Center in Seattle, WA serves as the WHI Clinical Coordinating Center for data collection, management, and analysis of the WHI. The WHI has two major parts: a partial factorial randomized Clinical Trial (CT) and an Observational Study (OS); both were conducted at 40 Clinical Centers nationwide. The CT enrolled 68,132 postmenopausal women between the ages of 50-79 into trials testing three prevention strategies. If eligible, women could choose to enroll in one, two, or all three of the trial components. The components are: Hormone Therapy Trials (HT): This double-blind component examined the effects of combined hormones or estrogen alone on the prevention of coronary heart disease and osteoporotic fractures, and associated risk for breast cancer. Women participating in this component with an intact uterus were randomized to estrogen plus progestin (conjugated equine estrogens [CEE], 0.625 mg/d plus medroxyprogesterone acetate [MPA] 2.5 mg/d] or a matching placebo. Women with prior hysterectomy were randomized to CEE or placebo. Both trials were stopped early, in July 2002 and March 2004, respectively, based on adverse effects. All HT participants continued to be followed without intervention until close-out. Dietary Modification Trial (DM): The Dietary Modification component evaluated the effect of a low-fat and high fruit, vegetable and grain diet on the prevention of breast and colorectal cancers and coronary heart disease. Study participants were randomized to either their usual eating pattern or a low-fat dietary pattern. Calcium/Vitamin D Trial (CaD): This double-blind component began 1 to 2 years after a woman joined one or both of the other clinical trial components. It evaluated the effect of calcium and vitamin D supplementation on the prevention of osteoporotic fractures and colorectal cancer. Women in this component were randomized to calcium (1000 mg/d) and vitamin D (400 IU/d) supplements or a matching placebo. The Observational Study (OS) examines the relationship between lifestyle, environmental, medical and molecular risk factors and specific measures of health or disease outcomes. This component involves tracking the medical history and health habits of 93,676 women not participating in the CT. Recruitment for the observational study was completed in 1998 and participants were followed annually for 8 to 12 years. Extension Studies: The original protocol allowed for follow-up until March 2005, after which participants were invited to enroll in the first WHI Extension Study for follow-up through 2010. Participants were invited again to participate in the second WHI Extension Study with continued follow up from 2010 to at least 2015. As of March 31, 2011 there were 93,122 women enrolled in the second extension. In Extension Study 2, the overall WHI study population was divided into two new subsamples, the Medical Records Cohort (MRC) and the Self-Report Cohort (SRC). The MRC consists of all former hormone trial participants and all African American and Hispanic participants from all study components. The SRC consists of the remaining participants. The extent of outcome information collected differs between the two cohorts, with more extensive outcomes information collection on the MRC. As part of Extension Study 2, selected older WHI participants were invited to participate in an In Person Visit (a.k.a., Long Life Study) at their homes during which additional blood samples were collected and various measurements were taken (such as blood pressure, height, weight, waist circumference, grip strength, etc.). In October 2015, Extension Study 2 was renewed with continued follow-up planned through October 2020, pending annual contract review and renewal. Additional Information: The WHI website, https://www.whi.org/about/SitePages/About%20WHI.aspx has much more information about the study. For WHI data collection forms used over the years, please see https://www.whi.org/researchers/studydoc/SitePages/Forms.aspx. For additional dataset documentation, see https://www.whi.org/researchers/data/Pages/Available%20Data.aspx. For data preparation and use, please refer to &#39;WHI dbGaP Cohort Data Release Data Preparation Guide May 2018&#39; for additional details about the WHI data. The WHI 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" box located on the right hand side of this top-level study page phs000200 WHI Cohort. phs000386 WHI SHARe phs000281 GO-ESP WHISP phs000315 WHI GARNET phs000503 WHISE phs000227 PAGE WHI phs000675 WHIMS+ phs000746 WHI Harmonized and Imputed GWAS phs001334 WHI Metabolomics of CHD phs001335 WHI BA23 phs001614 WHI LLS Phase III GWAS

  Study phs000200

• National Eye Institute (NEI) Age-Related Eye Disease Study (AREDS)

  The Age-Related Eye Disease Study (AREDS) was initially designed as a long-term multi-center, prospective study of the clinical course of age-related macular degeneration (AMD) and age-related cataract. In addition to collecting natural history data, AREDS included a clinical trial of high-dose vitamin and mineral supplements for AMD and a clinical trial of high-dose vitamin supplements for cataract. AREDS participants were 55 to 80 years of age at enrollment and had to be free of any illness or condition that would make long-term follow-up or compliance with study medications unlikely or difficult. On the basis of fundus photographs graded by a central reading center, best-corrected visual acuity and ophthalmologic evaluations, 4,757 participants were enrolled in one of several AMD categories, including persons with no AMD. The clinical trials for AMD and cataract were conducted concurrently. AREDS participants were followed on the clinical trials for a median time of 6.5 years. Subsequent to the conclusion of the clinical trials, participants were followed for an additional 5 years and natural history data were collected. The AREDS research design is detailed in AREDS Report 1. AREDS Report 8 contains the mainline results from the AMD trial; AREDS Report 9 contains the results of the cataract trial. Blood samples were also collected from 3,700+ AREDS participants for genetic research. Genetic samples from 600 AREDS participants (200 controls, 200 Neovascular AMD cases, and 200 Geographic Atrophy cases) were selected using data available in March 2005 and then were evaluated with a genome-wide scan. These data, as well as selected phenotypic data, were made available in the dbGaP. DNA from AREDS participants, which is currently being stored in the AREDS Genetic Repository, is available for research purposes. However, not all of the 3,700+ AREDS participants who submitted a blood sample currently have DNA available. In addition to including the data from the genome-wide scan on the 600 original samples, this second version of the AREDS dbGaP database provides a comprehensive set of data tables with extensive clinical information collected for the 4,757 participants who participated in AREDS. The tables include information collected at enrollment/baseline, during study follow-up, fundus and lens pathology, nutritional estimates, quality of life measures and measures of morbidity and mortality. In November 2010, over 72,000 high quality fundus and lens photographs of 595 AREDS participants (of the original 600 selected for the genome-wide scan) were made available in the AREDS dbGaP. In addition to the genome-wide scan data, the fundus and lens grading data for these participants are also available through the AREDS dbGaP. Details about the ocular photographs that are available may be found in the document "Age-Related Eye Disease Study (AREDS) Ocular Photographs". In January 2012, a measure of daily sunlight exposure was added in a separate &#34;sunlight&#34; table. Furthermore, the &#34;followup&#34; table has been revised. The visual acuity for the right eye was inadvertently missing at odd-numbered visits (01, 03, 05, etc.). This data is now part of the table. In February 2014 over 134,500 high-quality fundus photographs (macular field F2) of 4613 AREDS participants were added to the existing AREDS dbGaP resource. The AREDS dbGaP image archive already contains over 72,000 high quality fundus and lens photographs of 595 AREDS participants for whom dbGaP-accessible genotype data exist. Information about the available ocular photographs found in the document "Age-Related Eye Disease Study (AREDS) Ocular Photographs" has been updated with an addendum. It is hoped that this resource will better help researchers understand two important diseases that affect an aging population. These data may be applied to examination and inference on genetic and genetic-environmental bases for age-related diseases of public health significance and may also help elucidate the clinical course of both conditions, generate hypotheses, and aid in the design of clinical trials of preventive interventions. Definitions of Final AMD Phenotype Categories Please see phd001138.1 for a detailed description of how AREDS participants&#39; final AMD phenotype was categorized. User&#39;s Guide for AREDS Phenotype Data A detailed User&#39;s Guide for the AREDS phenotype data is available. This User&#39;s Guide is meant to be a comprehensive document which explains the complexities of the AREDS data. It is recommended that all researchers using AREDS phenotype data make use of this User&#39;s Guide.

  Study phs000001

• 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.&#160;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.&#160;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&#8217;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 &#8220;cases&#8221;) 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 &#8220;controls&#8221;). 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.&#160;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.&#160;&#160;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.&#160;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.&#160;

  Study phs002170

• Providing safe access to sensitive human data across borders: Federated EGA becomes a reality

  Enabling discovery and access to sensitive data across national boundaries is vital for improving human health. It enables more powerful and efficient research by increasing the volume and diversity of data available for analysis. It allows us to better understand the causes of diseases – cancer, rare diseases, infectious diseases like COVID-19 – and develop new medicines and treatments. Sensitive human omics data are typically generated by research initiatives and shared using specialist repositories which provide services for data submission, discovery, and access. The EGA is one such repository. Established in 2008 at EMBL’s European Bioinformatics Institute (EMBL-EBI) in the UK, since 2012 the EGA (“Central EGA”) has been jointly managed by EMBL-EBI and the Centre for Genomic Regulation (CRG) in Spain. Many countries have emerging personalised medicine programmes which generate data from national initiatives. These programmes are driving a transition in human genomics from being research-driven to receiving funding through healthcare. Data generated in a clinical context are subject to stricter governance than research data and must follow national data protection legislation. To solve these challenges, the Federated EGA provides a network of connected resources to enable transnational discovery of and access to human omics data for research, while also respecting jurisdictional data protection regulations. In this way, the Federated EGA infrastructure supports the goals of European initiatives such as the 1+ Million Genomes initiative (1+MG), the European Health Data Space, and a number of EU-funded 1+MG implementation projects including Beyond 1 Million Genomes. The Federated EGA is made up of “Nodes” – typically nationally funded and operated – which store and manage data locally while allowing global discovery within the Federated EGA network. Since 2016, multiple parallel efforts, supported by ELIXIR and other transnational and national initiatives, have created technical and legal frameworks for establishing the Federated EGA. In 2022, the first five Nodes – Finland, Germany, Norway, Spain, and Sweden – officially joined the Federated EGA by signing Federated EGA Collaboration Agreements with Central EGA. The Finnish FEGA Node is operated by CSC - IT Center for Science and provides data management services according to national laws and the requirements of the EU General Data Protection Regulation (GDPR). These services provide tools and support for the whole life-cycle of sensitive research data from collating to analysis, publication, and authorised re-use. The development of the services has been a joint effort with the other Nordic nodes within NeIC's Tryggve and Heilsa projects, and funded by Finnish Ministry of Education and Culture and projects coordinated by ELIXIR Finland. Read more about Finnish FEGA signing. The German Human Genome-Phenome Archive (GHGA) strives to provide a national infrastructure as well as an ethical and legal framework that balances FAIR omics data usage and data protection needs for Germany. As a Germany-wide consortium funded by the German Research Foundation under the umbrella of the NFDI association, GHGA combines the expertise of 21 universities and research institutions to form a federated national infrastructure. Read more about GHGA signing. The German Human Genome-Phenome Archive (GHGA) strives to provide a national infrastructure as well as an ethical and legal framework that balances FAIR omics data usage and data protection needs for Germany. As a Germany-wide consortium funded by the German Research Foundation under the umbrella of the NFDI association, GHGA combines the expertise of 21 universities and research institutions to form a federated national infrastructure. Read more about GHGA signing. In Norway, a key component of the infrastructure is the services of The Sensitive Data Service (TSD) offered by USIT at University of Oslo. The Federated EGA Norway Node is developed by ELIXIR Norway and operated by the University of Oslo as the responsible legal entity. Core software modules are developed jointly with the other Nordic nodes in the NeIC Tryggve and Heilsa projects. Read more about FEGA Norway signing. The Spanish FEGA (es-FEGA) is a national service for storing sensitive biomedical data in Spain. Supported by the Spanish Institute of Bioinformatics (INB) in collaboration with Central EGA, sensitive research datasets are primarily hosted at the Barcelona Supercomputing Centre facilities. The Swedish Sensitive Data Archive is a secure data archive and sharing platform for sensitive datasets. It was developed by the National Bioinformatics Infrastructure Sweden (NBIS) in collaboration with other Nordic ELIXIR Nodes through the Tryggve and Heilsa projects funded by NeIC and coordinated with Central EGA through ELIXIR. Read more about the Swedish Node signing. The Swedish Sensitive Data Archive is a secure data archive and sharing platform for sensitive datasets. It was developed by the National Bioinformatics Infrastructure Sweden (NBIS) in collaboration with other Nordic ELIXIR Nodes through the Tryggve and Heilsa projects funded by NeIC and coordinated with Central EGA through ELIXIR. Read more about the Swedish Node signing. By providing a solution for secure and efficient management of human omics data, the Federated EGA aims to foster data reuse, enable reproducibility, accelerate biomedical research, and improve human health. Find out more Interested in setting up your own Federated EGA Node? Check out the FEGA Onboarding Knowledge Base for more information. The ELIXIR Federated Human Data Community is a great entry point for anyone interested in learning more about the Federated EGA. You can: Join the ELIXIR Federated Human Data Community mailing list (select “Human Data”) Attend the ELIXIR Federated Human Data Community calls

  Blog safe-access-to-sensitive-human-data-federated-ega

• How to use EGA Webin?

  EGA Webin EGA Webin serves as a platform for registering metadata for array based submissions, large scale sequence submission as well as for legacy EGA submission accounts (ega-box-XXXX). For large scale submitters of sequence data you have also the option to submit metadata via XMLS programmatic submission, while new submitters are advised to utilise the Submitter Portal for their submissions. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. WEBIN actions: Register metadata for a sequence submission Register study, samples, experiments, runs, DAC, policy and dataset/s after file upload. Register components for your array-based metadata submission Register study, samples, DAC or policy before uploading files. Edit existing submission metadata Change or update previously submitted metadata. Register metadata for a sequence submission Ensure that all sequence files have been encrypted before uploading them to your submission account using the EgaCryptor. Go to the EGA Webin and log in using your submission account name (ega-box-XXX) and password. Register components of your metadata submission Study Samples Data Access Committee (DAC) Data access policy Dataset For array-base submissions: Study, Samples, Data Access Committee (DAC) and Data access policy may all be registered BEFORE file upload and dataset registration through the array-base template. Register your Study Go to the “Studies (Projects)” box Click on “Register Study” and fill in the information related to your study. Click on “Submit”, this will save the information and generate an EGA study ID. To use the study accession number in a publication, the study has to be previously released on the EGA website, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX.Further information about EGA can be found on https://ega-archive.org and “The European Genome-phenome Archive in 202 "(10.1093/nar/gkab1059)" Register your Samples Go to the “Samples” box Click on “Register Samples” Select “Download spreadsheet to register samples” and customise your template, there is a default EGA template (EGA default checklist) but more attributes can be added if required. For the EGA default checklist, there are mandatory,recommended and optional attributes. As well custom fields which can be added if required. Mandatory attributes Field Name Description tax_id Taxonomy ID of the organism as in the NCBI Taxonomy database. Entries in the NCBI Taxonomy database have integer taxon IDs. See our tips for sample taxonomy here scientific_name Scientific name of the organism as in the NCBI Taxonomy database. Scientific names typically follow the binomial nomenclature. For example, the scientific name for humans is Homo sapiens. sample_alias Unique name of the sample. If not selected system will auto generate an unique alias sample_title Title of the sample sample_description Description of the sample phenotype *** Where possible, please use the Experimental Factor Ontology (EFO) to describe your phenotypes. Recommended attributes Field Name Description subject_id Identifier for the subject where the sample has been derived from gender * Sex Optional attributes Field Name Description sex sex of the organism from which the sample was obtained disease_site Affected organ sample type Affected organ donor_id ** Identifier of the donor where the sample has been derived from *Gender should be described as 'male', 'female' or 'unknown'. If 'unknown' due to a known sex chromosome aneuploidy, please create a user defined attribute called 'Sex chromosome karyotype' and add the appropriate value, for example, 'XXY'. **Donor id (Subject id) should be a de-identified subject handle. If unknown, please add 'unknown' to the field. ***Phenotypes should, where possible, be an Experimental Factor Ontology accession. If a term cannot be found to describe your phenotype please use free text. All sample phenotypes considered important for further analysis of the data should be provided (for example, tumour type), additional phenotype attributes can be created by defining your own attributes; use the notion 'phenotype2', 'phenotype3', etc. After you have customised the fields for the sample submission, download the template and fill in the information. Example of the sample template: Finally upload the sample template to get the EGA accession IDs for the samples. Register your Data Access Committee (DAC) Further information on the role of your DAC Go to the “Data Access” box Click on “Register Dacs” Input the information about the DAC and register at least one main DAC contact. Register your Data Access Policy Your Data Access Policy provides the terms and conditions of data use, this is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAC). Go to the “Data Access” box Click on “Register Policies” Select the DAC to which this policy will be linked to and fill in the policy information. Submitting your Runs and Analyses This section is only for sequence data submission, for array-based submission it can be skipped. Please refer to our Submitting array based metadata Runs Registration Go to the “Raw Reads (Experiments and Runs)” box Click on “Submit Reads” Select “Download spreadsheet template for Read submission” Select the template corresponding to your submission type For the templates you have the option to customise the optional fields. To check their description click on “Show Description “ Download the template and fill in the required information. Example of the runs template: We recommend that Fastq, BAM, and CRAM read files are submitted using Webin-CLI When using this interface instead of Webin-CLI, raw sequences must be uploaded in one of the supported data formats before they can be submitted. The files can be uploaded using FTP or Aspera. The study and the sequenced samples must be pre-registered before the raw reads are submitted. Please note that each individual study and sample should be registered only once. You will be asked to provide information about the sequencing libraries and instruments. Submitting your Dataset This section is only for sequence data submissions, for array based submissions it can be skipped. Please refer to our Submitting array based metadata The dataset describes the data files, defined by the run (EGARXXXXXXXXXXX) and analysis (EGAZXXXXXXXXXXX) accessions that make up the dataset and links the collection of data files to a specified Data Access Committee and Data Access Policy. As a result, you must have registered your Reads and experiments, Data Access Committee (DAC) and Data access policy before submitting your Dataset. 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. Please contact EGA Helpdesk for further assistance. Go to the “Data Access” box Click on “Register Dataset” Select the Data Access Committee (DAC) and Data access policy Register your dataset After submitting your dataset you should contact the EGA Helpdesk to provide a release date for your dataset. Datasets are automatically held (i.e. not released) unless they are affiliated to a study that has already been released. Edit/update existing submission metadata Go to the “Report” section of the object you would like to edit. Locate the object and click on the arrow under action. An option menu will be displayed. Objects can be edited through their XML or with the WEBIN menu. After an object has been edited, changes would be available on the website until the submission is released again. Please contact the EGA Helpdesk if you require further assistance.

  Documentation submission/metadata/submission/EGA_webin

• Unrelated Donor Reduced Intensity Bone Marrow Transplant for Children with Severe Sickle Cell Disease (BMT CTN-0601-BioLINCC)

  ObjectivesThe primary objective is to determine event-free survival (EFS) at 1 year after unrelated donor (URD) hematopoietic stem cell transplantation (HCT) using bone marrow (BM) in patients with sickle cell disease (SCD).BackgroundSickle cell disease (SCD), also known as sickle cell anemia, is an inherited blood disease that can cause organ damage, stroke, and intense pain episodes. Children with sickle cell disease experience organ damage, impaired quality of life, and premature mortality. A blood stem cell transplant is a treatment option for someone with a severe form of the disease. Prior to undergoing a transplant, people typically receive a conditioning regimen of high doses of chemotherapy and other medications to prepare the body to accept the transplant. This type of conditioning regimen is known as a myeloablative conditioning regimen, but it can result in toxicities and sterility. A conditioning regimen that uses lower doses of chemotherapy and medications may be safer for transplant recipients. This type of regimen is known as reduced intensity conditioning (RIC) regimen. RIC has a more favorable toxicity profile but is associated with higher rates of graft rejection (GR), especially with graft sources such as umbilical cord blood This study evaluated the safety and effectiveness of blood stem cell transplants, using bone marrow from unrelated donors, in children with severe SCD who receive a RIC regimen prior to the transplant.SubjectsPatients 3.0-19.75 years old with symptomatic SCD AND one or more of the following complications: (1)-(i) a clinically significant neurologic event (stroke) or any neurologic defect lasting > 24 hours and accompanied by an infarct on cerebral magnetic resonance imaging (MRI); OR, (ii) patients who have a Transcranial Doppler (TCD) velocity that exceeds 200 cm/sec by the non-imaging technique (or TCD measurement of >185 cm/sec by the imaging technique) measured at a minimum of 2 separate occasions one month or more apart; OR, (2) Minimum of two episodes of acute chest syndrome within the preceding 2-year period defined as new pulmonary alveolar consolidation involving at least one complete lung segment (associated with acute symptoms including fever, chest pain, tachypnea, wheezing, rales, or cough that is not attributed to asthma or bronchiolitis) despite adequate supportive care measures; OR, (3) History of 3 or more severe pain events (defined as new onset of pain that lasts for at least 2 hours for which there is no other explanation) per year in the 2 years prior to enrollment despite adequate supportive care measures (if patients are receiving hydroxyurea and compliant with therapy, being symptomatic is an indication for transplantation; however, if patients decline hydroxyurea or non-compliant with this therapy, they would still remain eligible for study if pain criteria as described above are met). Lansky/Karnofsky performance score must be &#8805; 40. Hemoglobin S must be &#8804; 45%. Patients must have an unrelated adult bone marrow donor who is HLA-matched at 8 of 8 HLA-A, -B, -C and -DRB1 at high resolution using DNA-based typing. Patients with bridging fibrosis or cirrhosis of the liver, with uncontrolled bacterial, viral, or fungal infection in the past month, or seropositivity for HIV are excluded. Patients with HLA-matched family donors, or who have received prior HCT, and females who are pregnant or breast feeding are excluded. Thirty patients were enrolled on this study and of these, 29 patients met the criteria and proceeded to the study transplant.DesignParticipants attended a study visit prior to the transplant to undergo a blood collection, neurocognitive testing to measure learning and brain function, magnetic resonance angiogram (MRA) and magnetic resonance imaging (MRI) scans. Questionnaires to assess quality of life were also completed. All patients received erythrocyte transfusions before transplant. Twenty-two days (-22) before the transplant, participants began receiving a reduced intensity conditioning regimen of chemotherapy and medications. On days -21, -20, and -19 participants weighing 10 kg or more received 10 mg, 15 mg, and then 20 mg of Alemtuzumab intravenously (IV) followed by 30 mg/m2/day IV on days -8 through -4 of Fludarabine. Eight days (-8) before the transplant, participants were admitted to the hospital to continue the conditioning regimen which included 140 mg/m2 IV of Melphalan on day -3. Participants received the bone marrow transplant on day 0. Prophylaxis for GVHD consisted of a calcineurin inhibitor (tacrolimus or cyclosporine) administered from day -3 through day 100 after graft infusion, with subsequent taper through day 180; methotrexate 7.5 mg/m2 on days 1, 3, and 6; and methylprednisolone 1 mg/kg per day from days 7 through 28, with subsequent taper by 20% per week. One week after the transplant continuing until the WBC is normal, participants received granulocyte-colony-stimulating factor (G-CSF). After leaving the hospital, participants attended study visits weekly during weeks 1 to 8, at day 60, weekly during weeks 9 to 14, at Day 100, at month 6, and at years 1 and 2. At all study visits, a blood collection, medical history review, and physical exam occurred. In addition, at day 100, month 6, and years 1 and 2, questionnaires to assess quality of life were completed. At select visits the following procedures were conducted: lung function testing, heart function testing, MRA and MRI scans, and neurocognitive testing.The primary outcome was 1-year EFS. Death, disease recurrence or graft rejection by 1 year were considered events for this endpoint.ConclusionsThe trial met its prespecified 1-year EFS, and significantly improved HRQL was reported posttransplant. However, although the Reduced-intensity conditioning (RIC) provided successful engraftment in most patients, the regimen cannot be considered safe for widespread adoption without modification due to the regimen-related toxicity (RRT) and high rate of chronic GVHD, which was the predominant cause of mortality.

  Study phs003470

• Privacy Notice for EGA Web user

  Privacy Notice for EGA Public Website This Privacy Notice explains what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. 1. Who controls your personal data and how to contact us? European Genome- Phenome Archive - EGA offers a service for permanent archiving and sharing of all types of personally identifiable genetic and phenotypic data resulting from biomedical research projects, jointly managed by European Molecular Biology Laboratory – European Bioinformatics Institute (EMBL-EBI) and Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG). EMBL-EBI and CRG represent joint Data Controllers’ of processing of your personal data. They and their Data protection officers may be contacted for data protection queries and for exercising your rights under Section 8. You may contact EMBL-EBI, represented by Mallory Freeberg, by: email at: mfreeberg@ebi.ac.uk , or post at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: telephone at +49 6221 387-8590, email at dpo@embl.org , or post at EMBL Heidelberg, Data protection officer, Meyerhofstraße 1, 69117 Heidelberg, Germany. You may contact CRG, whose EGA team is represented by dr. Jordi Rambla de Argila, by: email at jordi.rambla@crg.eu, or post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), Dr.Aiguader 88, PRBB Building, 08003 Barcelona, Spain. CRG Data protection officer may be contacted by: email at dpo@crg.eu post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), C/ Dr. Aiguader, 88, PRBB Building, 08003 Barcelona, Spain. 2. Which is the lawful basis for processing personal data? For providing you access to the website and for offering support whilst using the website, we need your consent under Article 5 (2) of the IP 68 (equivalent to Article 6 (1)(a) of the GDPR). For monitoring your activities on the website, we process your personal data on the grounds of important public interest. Such legal basis is found in Article 5(1)(a) of EMBL Internal Policy No 68 on General Data Protection (hereinafter IP 68), which is equivalent to Article 6 (1)(e) of the EU General Data Protection Regulation (hereinafter GDPR) and upon which personal data are processed for the achievement of the aims laid down in 1973 agreement establishing EMBL, such as the promotion of the cooperation in the fundamental research, in the development of advanced instrumentation and in advanced teaching in molecular biology and dissemination of information. 3. What personal data is collected from users of the service? How do we use this personal data? We collect the following personal data from you: IP addressesDate and time of a visit to the service website Operating systemAmount of data transmittedBrowserEmail address (only when support is requested by the user) The data controller will use your personal data for the following purposes: To provide the user access to the serviceTo better understand the needs of the users and guide future improvements of the serviceTo monitor website activities according to and in compliance with the Terms of UseTo better understand the needs of the website visitors and guide future improvements of the serviceTo conduct and monitor website security activitiesTo create anonymous usage statistics 4. Who will have access to your personal data? The personal data will be disclosed to: Authorised staff in the data controller’s institutions acting on data controller`s behalf and instructions. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? There are no personal data transfers to third countries or international organisations. 6. How long do we keep your personal data? Any personal data directly obtained from you will be retained as long as the service is live. Such duration serves the purpose of enabling scientific research and ensures legal compliance and facilitates internal and external audits if they arise. By contrast, the log files for the data categories related to anonymous usage statistics (raw web service logs) are processed only for 30 days and thereafter erased. 7. The joint Data Controllers provide these rights regarding your personal data You have the right to: Not be subject to decisions based solely on an automated processing of data (i.e. without human intervention) without you having your views taken into consideration.Request at reasonable intervals and without excessive delay or expense, information about the personal data processed about you. Under your request we will inform you in writing about, for example, the origin of the personal data or the preservation period.Request information to understand data processing activities when the results of these activities are applied to you.Object at any time to the processing of your personal data unless we can demonstrate that we have legitimate reasons to process your personal data.Request free of charge and without excessive delay rectification or erasure of your personal data if we have not been processing it respecting the data protection policies of the respective controllers. It must be clarified that rights under points 4 and 5 are only available whenever you need support whilst using our website. For other processing based on the grounds of important public interest you cannot exercise your rights to object, rectify or erase your personal data according to the Article 13(2)(a)(b) of IP 68 (equivalent to Article 17(3)(b)(d) and Article 21(6) of the GDPR). 8. Supervisory authority If you wish to complain against the processing of your personal data, you may do so by post at: EMBL Heidelberg, Data Protection Committee, Meyerhofstraße 1, 69117 Heidelberg, Germany, or Autoritat Catalana de Protecció de Dades (Catalan Data Protection Authority), C/Rosselló 214, Esc A, 1r 1a, Barcelona 08008, Spain. 9. CookiesWe use cookies and similar technologies that are strictly necessary for the correct functioning and security of the EGA website (for example, to enable core site features and to help protect the service). These cookies do not store information that directly identifies you.You can set your browser to block or delete cookies. Please note that if you disable strictly necessary cookies, parts of the website may not function properly.Published on February 6, 2019

  Documentation data-protection/privacy-notice/ega-website

• Women's Health Initiative Clinical Trial and Observational Study - Imaging

  Objectives: The clinical trial assessed the safety and efficacy of three interventions. Specifically, it evaluated (1) the major health benefits and risks of estrogen plus progestin and estrogen alone, (2) the effects of a low-fat eating pattern on risk of colorectal cancer, and (3) the efficacy of calcium with vitamin D supplementation for preventing hip and other fractures. The objective of the memory study was to determine whether estrogen plus progestin therapy protects global cognitive function, and evaluate the therapy's effect on the incidence of dementia and mild cognitive impairment.The observational study is examining the relationship between lifestyle, socioeconomic, health, and other risk factors with cardiovascular, breast cancer, colorectal cancer and osteoporotic fracture outcomes. Secondary objectives include providing more reliable estimates of the extent to which known risk factors predict disease, more precise estimates of new occurrences of disease, and to provide a future resource for the identification of new or novel risk factors especially factors found in blood. Background: The Women's Health Initiative (WHI) is a long-term national health study that has focused on strategies for preventing the major causes of death, disability, and frailty in postmenopausal women, specifically heart disease, cancer, and osteoporotic fractures. The WHI is primarily composed of an observational study (OS), as well a clinical trial (CT) with three components: Hormone Replacement Therapy (HT), Dietary Modification, (DM) and Calcium/Vitamin D supplementation (CaD).Prior to the WHI, observational studies suggested that postmenopausal hormone therapy was associated with a decreased risk of coronary heart disease (CHD). Potential cardioprotection was based on generally supportive data on lipid levels in intermediate outcome clinical trials, trials in nonhuman primates, and a large body of observational studies suggesting a 40% to 50% reduction in risk among users of either estrogen alone or, less frequently, combined estrogen and progestin. Observational studies primarily examining unopposed estrogen preparations have suggested a 30% to 50% reduction in coronary events, and an 8% to 30% increase in breast cancer with extended use. Other research findings indicated that hormone therapy was also associated with a decreased risk of osteoporosis and increased bone density. The WHI HT trials were designed to test the effects of postmenopausal hormone therapy on risk for coronary heart disease and assess overall risks and benefits in predominantly healthy women. The Women's Health Initiative Memory Program (WHIMS) consists of a suite of studies which include cohorts of women who participated in the WHI HT trials. Postmenopausal women have a greater risk than men of developing Alzheimer's disease, but studies of the effects of estrogen therapy on Alzheimer's disease have been inconsistent. Additionally, observational studies have suggested that postmenopausal hormone treatment may improve cognitive function, but data from randomized clinical trials have been sparse and inconclusive. International comparisons and migration studies have suggested that countries with 50% lower fat intake than the US population had approximately one third the risk of colorectal cancer. Additionally, fairly consistent evidence existed for an effect of dietary fat, vegetables and fruits, and grains on colorectal cancer risk from within-country observational studies, although the protective effect of lower fat intake was no longer clear after adjusting for energy intake. The WHI DM trial was the first randomized trial to directly address the health effects of a low-fat eating pattern in predominantly healthy postmenopausal women from diverse racial/ethnic, geographic, and socioeconomic backgrounds. Osteoporosis is a major cause of injury, loss of independence, and death, and contributes to hip fractures. Observational evidence and data from previous randomized clinical trials suggest that calcium and/or vitamin D supplements may slow bone loss and reduce the risk of falls in postmenopausal and elderly women. However, evidence from trials, observational studies, and meta-analyses of calcium and vitamin D supplementation with respect to hip and other fractures was limited at the time the WHI was initiated. In two prior randomized trials, calcium plus vitamin D supplements did not reduce the risk of nonvertebral fractures among older women. When the WHI CaD trial was designed, guidelines recommended daily intakes of 800 to 1200 mg of calcium with 400 IU of vitamin D for the prevention of osteoporosis, which was not met by many American women. Therefore, the WHI CaD trial was designed to test the primary hypothesis that postmenopausal women randomly assigned to calcium plus vitamin D supplementation would have a lower risk of hip fracture and, secondarily, of all fractures than women assigned to placebo. Subjects: Postmenopausal women ages 50 to 79 were eligible to participate. A woman was considered postmenopausal if she had experienced no vaginal bleeding for 6 months (12 months for women under 55 years of age), had had a hysterectomy, or had ever used postmenopausal hormones. Recruitment was carried out in 40 US clinical centers in 1993-1998. The clinical trial components had additional specific inclusion or exclusion criteria.A total of 68,132 women were randomized into at least one component of the clinical trial. 27,347 women were enrolled in the hormone therapy component with 16,608 in the estrogen plus progestin trial and 10,739 in the unopposed estrogen trial, 48,835 women were enrolled in the diet modification component, and 36,282 women were enrolled in the calcium/vitamin D component. 7,479 women 65 years of age and older at baseline and that participated in the HT trial component were enrolled in the ancillary memory study. Women who were either ineligible or unwilling to participate in the clinical trial component were enrolled in the observational study. For example, many potential participants to the clinical trial component of the study were already undertaking a low fat diet or were using hormone replacement therapy. The effect of the selection process was that women enrolled in the observational study tended to have healthier lifestyles compared to those enrolled in the clinical trial. In total, 93,676 subjects were enrolled in WHI OS, with over 16% being members of a racial/ethnic minority group. The first WHI Extension Study enrolled 115,407 consenting participants from all components of the original WHI study for an additional five years of follow-up, from 2005 to 2010. In 2010, 93,567 women consented to continued follow-up. Design: The clinical trial component of the WHI included three randomized comparisons: hormone therapy, dietary modification, and calcium/vitamin D supplementation. Women could have been randomized into one, two or all three trials.The hormone therapy trial enrolled women to one of two double-blinded trials: estrogen (0.625 mg of conjugated equine estrogens daily) plus progestin (2.5 mg of medroxyprogesterone acetate daily) or estrogen alone. Women with a prior hysterectomy were eligible for the trial of unopposed estrogen. Women with an intact uterus at screening were initially also eligible for unopposed estrogen, but were reassigned to the trial of combined postmenopausal hormones beginning in 1995. Both trials randomized participants 1:1 to either hormone therapy or placebo. A 3-month washout period was required before baseline evaluation of women using postmenopausal hormones at initial screening. Study participants were contacted by telephone 6 weeks after randomization to assess symptoms and reinforce adherence. Follow-up contacts by telephone or clinic visit occurred every 6 months, with clinic visits required annually. The estrogen plus progestin trial was halted in July 2002 after a mean 5.2 years of follow-up because health risks, including increased risk of breast cancer and cardiovascular disease, exceeded benefits. The estrogen alone trial was stopped early in March 2004, because an increased risk of stroke was found with no benefit for coronary heart disease. The primary outcome was coronary heart disease (CHD) (nonfatal myocardial infarction and CHD death), with invasive breast cancer as the primary adverse outcome. The dietary modification trial evaluated the effect of a low-fat, high fruit, vegetable, and grain diet on preventing cardiovascular disease and cancer. Participants were randomly assigned to an intervention or a comparison group in the ratio of 2:3 for cost-efficiency. The intervention was an intensive behavioral modification program, using 18 group sessions in the first year and quarterly sessions thereafter, led by specially trained and certified nutritionists. The program was designed to promote dietary change with the goals of reducing total fat to 20% of energy intake, increasing vegetables and fruits to at least 5 servings daily and grains to at least 6 servings daily. The intervention did not include total energy reduction or weight loss goals. Comparison group participants received a copy of the US Department of Health and Human Services' Dietary Guidelines for Americans and other health-related materials but were not asked to make dietary changes. Dietary intake was monitored using the WHI food frequency questionnaire at 1 year and in a rotating one-third subsample every year thereafter. Women completed a medical update questionnaire every 6 months, and medical records were sought for all women reporting colorectal cancer. The primary outcome was invasive colorectal cancer incidence. Participants in the calcium/vitamin D trial were randomized 1:1 to either supplements or placebo. Active tablets contained 500 mg of elemental calcium (as calcium carbonate) and 200 IU of vitamin D3, to be taken twice daily with meals. The presence and severity of symptoms, safety concerns, and outcomes were ascertained at annual clinic visits and telephone or clinic visits at intervening six-month intervals. Risk factors for fracture were assessed by questionnaire, interview, and clinical examination. The primary outcome was incidence of hip fracture. Participants in the observational study attended a baseline examination and were re-examined three years later. Participants completed annual updates of exposures and clinical outcomes by mail. Final data were collected by mail during the close-out period in April 2004 to March 2005. The major clinical outcomes of interest were coronary heart disease, stroke, breast cancer, colorectal cancer, endometrial cancer, ovarian cancer, osteoporotic fractures, diabetes, and total mortality. Most outcomes were initially ascertained by self-report on an annual questionnaire and documented by hospital and related records. Charts with potential cardiovascular, cancer, and fracture outcomes were sent to the local physician adjudicator for evaluation and classification. Staff at the Clinical Coordinating Center coded and adjudicated all cancers of major interest in the study using standardized SEER guidelines. In 2005, WHI participants were invited to join the Extension Study for an additional five years of follow-up in order to collect long-term outcomes. Participants completed annual data collection forms primarily by mail, similar to the OS follow-up. Women reporting study outcomes were contacted by WHI field center staff to obtain additional details and medical records, which were evaluated by physician adjudicators. In 2010, the woman remaining were invited to join the next Extension Study. In the second extension, women were divided into two groups, one of which would have outcomes documented with medical records (the Medical Records Cohort, MRC), and the other would just be followed by self-report (the Self-Report Cohort, SRC). The MRC consists of women who were in the hormone therapy trials, and all African-American and Hispanic women. In 2012-2013, a subset of the MRC was identified for a potential in-home visit to collect blood and several objective measures of physical functioning. Conclusions: Overall health risks exceeded benefits from use of combined estrogen plus progestin after an average 5.2 year follow-up among healthy postmenopausal US women (Rossouw et al., 2002, PMID:12117397). Among postmenopausal women aged 65 years or older, estrogen plus progestin did not improve cognitive function when compared with placebo (Rapp et al., 2003, PMID: 12771113), increased the risk for probable dementia, and did not prevent mild cognitive impairment (Shumaker, et al., 2003, PMID: 12771112). The use of conjugated equine estrogen increased the risk of stroke, decreased the risk of hip fracture, and did not affect CHD incidence in postmenopausal women with prior hysterectomy after an average of 6.8 years of follow-up (Anderson et al., 2004, PMID: 15082697). Over approximately 8 years of follow-up, a low-fat dietary pattern did not reduce the risk of colorectal cancer (Beresford, et al., PMID: 16467233). Calcium with vitamin D supplementation resulted in a small but significant improvement in hip bone density; however, no significant difference was observed in hip fractures (Jackson, et al., 2006, PMID: 16481635). A recent review summarizes the conclusions from the WHI clinical trials with a focus on clinical practice (Manson, et al., 2024, PMID: 38691368).Description of ECG Imaging Data: Electric cardiograms (ECGs) were given to all clinical trial participants at baseline and in years 3, 6, and 9 of the original WHI study.EKG data consist of 12 lead 10 seconds ECGS sampled at 500Hz via GE ECG machines and process via GE MUSE system. The ECG waveform were directly exported from GE MUSE using MUSE export function in XML format, which include EKG waveform data as well as other ECG characteristics. Waveform data is in base64 encoded format, when it is decoded, it is a binary data that can be used to draw waveform graph. Many programming languages and data tools have built in functions to decode base64 strings. All the other necessary information is included in the LeadData section, total byte size, total sample size etc. (usually 1 sample is 2 bytes). See example below: encoded-data (base64 encoded string) JwAoAC0AKAAiACIAJAAkACQAIwAiACIAHgAcABwAGwAZABgAGAAYABcAEwAQABAAEAAL^/AAsADAAM... decoded-binary-data (1 sample is 2 bytes) 270028002D002800220022002400240024002300220022001E001C001C001B00 1900180018001800170013001000100010000B000B000C000C000D000D000D00 0A000A000A0009000600040004000700070005000500020... These binary values are integers (Y axis data of the graph), hence it is a straightforward process to draw the waveform graph. Acquisition dates have been redacted from this ECG data to comply with WHI policy. All acquisition dates within files and in file names have been set to January 1, 1900 (19000101) to comply with this policy.

  Study phs003824

• 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