17848 results for "the best way to get coins in fc 26 Navštivte Buyfc26coins.com Společnost známá transparentními transakcemi..CQ2q"

in 26.58 milliseconds.

• Single cell RNA sequencing of colorectal cancer patients (KUL5)

  All libraries were sequenced on Illumina NextSeq or NovaSeq6000 until sufficient saturation was reached.

  Dataset EGAD00001008585

• Sequencing data for oesophageal and related samples - OACs release 2 (RNA)

  Dataset EGAD00001003839

• 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

• RNA-seq samples

  Raw FASTQ files obtained by RNA sequencing of tumor samples from patients (age 12-29) with newly diagnosed, recurrent intermediate or high-grade sarcoma.

  Dataset EGAD00001008393

• 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

• Paired-end Whole Exome-seq analysis of the 3D evolution of glioma cell populations. Part 2.

  Dataset contains paired-end Whole Exome sequencing data from 257 glioma samples from 28 patients. 26 normal blood samples are also included.

  Dataset EGAD00001009496

• California Pacific Medical Center Research Breast Health Cohort

  Description of Cohort: The California Pacific Medical Center (CPMC) Breast Health Cohort is a cohort study based at CPMC and is linked to the San Francisco Mammography Registry, one of the sites of the NCI-funded Breast Cancer Screening Consortium (U01CA063740). CPMC is a community hospital in San Francisco, which has one of the highest volumes for mammography in San Francisco. Between September 2004 and June 2007, >90,000 mammograms were performed at CPMC. The CPMC breast health cohort collects demographic and risk factor data on women receiving mammography through participation in the San Francisco Mammography Registry, as part of the Breast Cancer Screening Consortium (U01CA063740). The SFMR database collects information from all sources, including a questionnaire on demographic and risk factor information, the clinical results of the breast examination, the measures of breast density by Dr. John Shepherd and the women who agreed to donate a blood sample. By merging these various sources of information we have very efficiently developed a large sample of women who have donated blood and have had a measure of mamographic density. Blood Collection: Dr. Steve Cummings is leading an effort to collect and archive blood samples from women who are receiving mammography screening. All women who are sent for a screening mammogram at CPMC are considered eligible. Since the cohort began collecting blood samples in July 2004 until June 2007, samples have been collected from over 11,000 women. Measurement of Breast Density: Dr. John Shepherd is currently measuring breast density in a large fraction of the cohort using an automated approach with single X-ray absorptiometry. Dr. Shepherd has established a link with the CPMC mammography center that allows him to collect routine digital mammography information. Using the data from the mammogram, Dr. Shepherd and his group have developed the single X-ray absorptiometry (SXA) technique for measuring density which is described in more detail below. The table demonstrates the distribution of demographic variables and some breast cancer risk factors of women who donated blood and had a breast density measurement in the CPMC breast health cohort. Nearly 80% of the participants are Caucasian and most of the women are post-menopausal with a median age of ~52. Since it will be difficult to accrue a large enough sample from each ethnic group, our study will focus only on Caucasian women. Table: Demographic variables, reproductive history and family history of breast cancer among 2962 women participating in the CPMC cohort study who contributed blood samples between 1994-1997. Variable Median/Percentage Age (Median/IQR) 52 (46-59) Ethnicity Caucasian/White 0.76 Asian/Pacific Islander 0.141 Hispanic 0.029 Mixed Race/Ethnicity 0.039 African American/Black 0.022 American Indian 0.001 Other 0.009 First degree relative with breast cancer 0.17 Age at first birth Nulliparous 0.39 Age<20 0.043 Age>40 0.032 Age<30, ≥20 0.251 Age>30, ≤40 0.282 Measurement of Breast Density in Cohort: Measurement of breast density is accomplished using an automated technique for all mammograms obtained by Dr. Shepherd using Single X-Ray absorptiometry (SXA). SXA measurement of breast density is done on approximately 30% of all screening mammograms. Below we describe the method for measurement of breast density by SXA by Dr. Shepherd's group and its validation and association with breast cancer. As we demonstrate below, breast density, as measured by SXA, is an automated, highly reproducible measure of the density of breast tissue and is associated with breast cancer risk. SXA for Quantifying Breast Density: Single x-ray absorptiometry (SXA) was initially developed for measuring bone density. SXA can determine the fraction of each of two densities simultaneously using the fact the sample is a constant thickness, the thickness in known, and the total attenuation is known. In applying this technique to breast density, we assume a two compartment model: fat and non-fatty (fibroglandular tissue). We use a reference material composed of various concentrations of two materials: one which is the same density as fat and another which is the same density as fibroglandular tissue. The reference material (phantom) is placed in the X-ray field with each mammogram. We have been able to implement this in a way that is unintrusive to the patient and technologist at CPMC. Assuming this two-compartment model and a constant known breast thickness, we can then calculate the percent density at any region of the breast based on the assumption that % pixel grey-scale is proportion to the mass fractions of breast fat and lean tissue. If reference materials (a phantom) of fat and fibroglandular tissue are imaged with the patient's breast and the reference materials have the same thickness as the patient's breast, then the breast's grey-scale values can be converted to fat/fibroglandular mass fractions by interpolating between those two references. The total percent density is found by averaging the volume fraction over all breast pixels. The phantom being used for breast density assessment at CPMC began to be used in September 2004. The phantom does not have to be manipulated by the technologist and stays attached on the mammography device during standard craniocaudal (CC) views. Thus it creates minimal to no interference with the clinical mammogram. Reproducibility of breast density measures: Traditional measures of mammographic density require some human interpretation. A human reader outlines the area perceived to be dense and a computer then calculates the percent area outlined as a percent of the entire image. Thus, while traditional mammographic density is associated with breast cancer risk, it has some limitations. In a study by Drs. Shepherd, Kerlikowske, et al., the correlation coefficient (Pearson's R) between different readers was 0.8-0.9. In contrast to the traditional mammographic density measurement, the SXA measurement is fully automated and, therefore, the reproducibility of the measurement is higher. Dr. Shepherd and colleagues have performed a replication study of SXA as a measurement of breast density. They have estimated the correlation coefficient of the SXA measurement of breast density to be >0.98. Thus, as expected for an automated measure, SXA is a highly reproducible measure of mammographic breast density. Drs. Shepherd and Kerlikowske have recently analyzed the association between breast cancer risk and breast density as measured by SXA (Shepherd et al., Cancer Epi Biomarkers and Prev, 2011, PMID: 21610220). They found that women in the highest quintile of % volumetric density had an odds ratio of 4.1 (95% CI: 2.3 - 7.2) for breast cancer risk compared to women in the lowest quintile of volumetric density. Thus volumetric density appears to be a highly reproducible, automated measure of breast cancer.

  Study phs000395

• 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

• Submitter Portal

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

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

• Paired-WGS Sequencing of Primary lymphomas of the central nervous system (PCNSL)

  26 Tumor/Control pairs of WGS data of PCNSL tumors, sequenced on either Illumina HiSeq2000/2500 instruments or HiSeq X Ten. The controls are blood or buffy coat samples in most cases.

  Dataset EGAD00001007806