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

in 130.19 milliseconds.

• Transposome Bisulfite Sequencing

  DNA belonging to 16 tumour/normal samples were treated with bisulfite, then up to 5 different bisulfite PCRs were performed in each one of the samples. Amplicons form the same sample were pooled and submitted to sequencing on a MiSeq platform.

  Dataset EGAD00001001028

• ICGC PCAWG Dataset: ORCA-IN_PCAWG_WGS_BWA

  ICGC PCAWG Dataset for WGS BAM aligned using BWA MEM. Project: ORCA-IN.

  Dataset EGAD00001002120

• CFTR Gene Variant Detection in Moroccan Individuals via Nanopore Long-Read Sequencing

  This study consists of sequencing the whole CFTR gene (coding and non-coding regions) using Oxford Nanopore on Moroccan CF patients

  Study EGAS50000001423

• CINECA_synthetic_cohort_EUROPE_UK1 referencing fake samples

  Please note: This synthetic data set (with cohort “participants” / ”subjects” marked with FAKE) has no identifiable data and cannot be used to make any inference about cohort data or results. The purpose of this dataset is to aid development of technical implementations for cohort data discovery, harmonization, access, and federated analysis. In support of FAIRness in data sharing, this dataset is made freely available under the Creative Commons Licence (CC-BY). Please ensure this preamble is included with this dataset and that the CINECA project (funding: EC H2020 grant 825775) is acknowledged. For any questions please contact isuru@ebi.ac.uk or cthomas@ebi.ac.uk This dataset (CINECA_synthetic_cohort_EUROPE_UK1) consists of 2521 samples which have genetic data based on 1000 Genomes data (https://www.nature.com/articles/nature15393), and synthetic subject attributes and phenotypic data derived from UKBiobank (https://journals.plos.org/plosmedicine/article?id=10.1371/journal.pmed.1001779). These data were initially derived using the TOFU tool (https://github.com/spiros/tofu), which generates randomly generated values based on the UKBiobank data dictionary. Categorical values were randomly generated based on the data dictionary, continuous variables generated based on the distribution of values reported by the UK Biobank showcase, and date / time values were random. Additionally we split the phenotypes and attributes into 4 main classes - general, cancer, diabetes mellitus, and cardiac. We assigned the general attributes to all the samples, and the cardiac / diabetes mellitus / cancer attributes to a proportion of the total samples. Once the initial set of phenotypes and attributes were generated, the data data was checked for consistency and where possible dependent attributes were calculated from the independent variables generated by TOFU. For example, BMI was calculated from height and weight data, and age at death generated by date of death and date of birth. These data were then loaded to the development instance of Biosamples (https://www.ebi.ac.uk/biosamples/) which accessioned each of the samples. The genetic data are derived from the 1000 Genomes Phase 3 release (https://www.internationalgenome.org/category/phase-3/). The genotype data consists of a single joint call vcf files with call genotypes for all 2504 samples, plus bed, bim, fam, and nosex files generated via plink for these samples and genotypes. The genotype data has had a variety of errors introduced to mimic real data and as a test for quality control pipelines. These include gender mismatches, ethnic background mislabelling and low call rates for a randomly chosen subset of sample data as well as deviations from Hardy Weinberg equilibrium and low call rates for a random selection of variants. Additionally 40 samples have raw genetic data available in the form of both bam and cram files, including unmapped data. The gender of the samples in the 1000 genomes data has been matched to the synthetic phenotypic data generated for these samples. The genetic data was then linked to the synthetic data in BioSamples, and submitted to EGA.

  Dataset EGAD00001006673

• Study of Clinical Efficacy of Antimicrobial Therapy Strategy Using Pragmatic Design in Idiopathic Pulmonary Fibrosis (CleanUP IPF-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. Objectives To investigate whether the addition of antimicrobial treatments improves outcomes compared to usual care alone among patients with idiopathic pulmonary fibrosis. Background Idiopathic pulmonary fibrosis (IPF) is a chronic progressive lung disease. Lung dysbiosis, characterized by increased bacterial load and/or loss of diversity, has been reported in patients with IPF and may contribute to hospitalization and death. Clinical trials investigating other chronic disorders suggest that antimicrobial therapy favorably alters the lung microbial community. The CleanUP IPF study was initiated to determine if an antimicrobial treatment reduces respiratory hospitalization or death among patients with IPF. Participants A total of 513 participants were enrolled. 254 participants were randomized to receive antimicrobials, of those 128 were randomized to receive co-trimoxazole and 126 were randomized to receive doxycycline. 259 participants were randomized to receive usual care alone. Design CleanUP IPF was a randomized, unblinded, multicenter study. Patients were randomized to receive antimicrobials in addition to usual care or usual care alone. Antimicrobials included co-trimoxazole (trimethoprim 160 mg/sulfamethoxazole 800 mg twice daily plus folic acid 5 mg daily) or doxycycline (100 mg once daily if body weight Data collected included diffusion capacity of lungs for carbon monoxide (DLCO), forced vital capacity (FVC), and occurrence of severe adverse events. Several questionnaires were administered to assess quality of life, including the impacts of shortness of breath, fatigue, and chronic cough on participants. The primary end point was time to first nonelective respiratory hospitalization or all-cause mortality. The study was terminated early due to futility. Conclusions Among adults with idiopathic pulmonary fibrosis, the addition of co-trimoxazole or doxycycline to usual care, compared with usual care alone, did not significantly improve time to nonelective respiratory hospitalization or death. Martinez FJ, Yow E, Flaherty KR, et al. Effect of Antimicrobial Therapy on Respiratory Hospitalization or Death in Adults With Idiopathic Pulmonary Fibrosis: The CleanUP-IPF Randomized Clinical Trial. JAMA. 2021;325(18):1841-1851. doi:10.1001/jama.2021.4956

  Study phs004314

• All you need to know about the new Submitter Portal

  In September we launched new services for all EGA users, including a new version of the former Submitter Portal. Our main objective with this Portal is to transform the metadata submission in a simplified and user-friendly method. Although it is possible to find documentation about the Submitter Portal on our website, we wanted to highlight the new features in this article. Enjoy! Credentials: who needs to create a new user to access the Submitter Portal and who doesn't? Users with an old submission account (ega-box) can already access the new Submitter Portal. If it is the first time that you want to access, it is time to request a submitter role linked to the EGA User. In the form, it is mandatory to explain which type of data you want to deposit, the size of your submission, add any comment you’d like us to read, and manage the EGA Data Processing Agreement (DPA) document. This document should be checked by the legal department of your institution and signed by a person with authority to sign contracts on behalf of the institution. Note that we provide a DPA template for new Users; it can be found and downloaded in the Submitter Request section. With the DPA signed and the Submitter Request sent, it is time to wait for our Helpdesk team to validate the request. Metadata submission now can be collaborative It is possible to add collaborator(s) to your submissions. Only registered EGA Users will appear on the search bar. When adding a collaborator, it is mandatory to define the permission granted: Read only: collaborators with this permission can check if the information of the submission is correct but cannot modify anything. Read & write: collaborators with this label can register new objects and modify the registered ones. We wanted to save time for submitters that usually rely on the same collaborators. For that, we have implemented the possibility of adding the same collaborators from previous submissions; all you need to do is to search the submission, and the exact set of EGA users will have access to your submission. You can check the collaborators and their permissions at any point of the submission by going to the collaborators section. Even adding more people to complete the submission is allowed by following the same steps: looking for the EGA User and defining the permission granted (please, note that during the submission it is not possible to add collaborators from previous submissions). Use external links to complement the study information When filling the information about the study we recommend users to enrich the submission with complementary fields such as PubMeds IDs, custom tags and external links. External links are used to connect a study to an external repository. We have implemented an external link to Euro-Bioimaging for a European Project (EuCanImage). Now, we are looking forward to keeping increasing the list of external repositories! Choose the expected release date for your metadata to be searchable on our website Once all the metadata objects are registered it is time to finalise the submission so that the Helpdesk team can approve it. In the new version of the Submitter Portal users can choose the expected release date for the metadata to be searchable on the EGA website. Please, note that the selected date will have a minimum of one week margin from the day of finalisation. This time is necessary for your files to be archived and for the submission to be validated by the Helpdesk Team. Are you looking for the Array submission within the Submitter Portal? Our Submitter Portal does not support array submissions. The submission of Array-based metadata must be done using the EGA programmatic submission. You will find our Array-based format template and all the necessary information on our website, and you can find all the steps in our submission quickguide! More information about the submission process at the EGA Our Team has developed an extended documentation related to metadata submission. A good first step is to take a closer look at the Submission FAQ. To have a general overview of all the metadata submission process we recommend taking a glimpse of our take-the-tour or watching the tutorial available on our YouTube Channel. Don't miss our section on EGA Schemas, to learn more about how the EGA is built. It can be useful to fully ensure that your submissions comply with the EGA's standards and contribute to a valuable and accessible genomic resource.

  Blog new-submitter-portal

• PyEGA3 download client

  PyEGA3 Checks prior to download - Is the dataset available for download? Most datasets are available using the PyEGA3 Download client, except for specific legacy datasets. For these ones, refer to Live Outbox distribution, an alternative way to download these datasets.If the dataset you've been granted access to begins with the ID EGAD5XXXXXXX, please refer to the Live Outbox distribution. If the dataset you have been granted access to contains encrypted data (filename ending in .gpg), contact EGA Helpdesk for detailed information on how to download these files.General Information The PyEGA3 download client is available at its GitHub repository. In its README you will find a step by step guide on how to use it to download files you have been granted access to. PyEGA3 implements the GA4GH-compliant HTSGET protocol supporting requests over genomic ranges. This enables the download of specific regions of interest rather than the entire file. HTSGET is not possible for all the files held by EGA: if the dataset does not contain index files (e.g. filename ending in *.crai), then genomic range requests cannot be performed. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Check out our video tutorial! Frequently Asked Questions General questions How do I download the datasets to which I have been granted access? After setting up your EGA download account, you can proceed to download using the EGA download client – PyEGA3. The pyEGA3 download client is a python-based tool for viewing and downloading files from authorised EGA datasets. This download client is continuously being developed for more user-friendly download experiences. Can I download the dataset’s metadata via the download client? No, the download client cannot be used to download metadata. Registered EGA users can download metadata of an authorised dataset by logging into the EGA webpage and navigating to the dataset of choice. Approximately two thirds down the page you will find the option to download the metadata as a zip file. How do I download large datasets as quickly as possible? The main EGA download client is pyEGA3 download client, a python-based tool for viewing and downloading files from authorised EGA datasets.We could exceptionally consider the option of an Aspera download for users experiencing very slow download rates or facing particular issues.Contact the EGA Helpdesk for further information. Pre-requirement and Installation What are the major requirements for the PyEGA3 download client installation and usage? The PyEGA3 client is compatible with any OS with Python 3.6+ installed. The client requires a connection to the internet, sufficient space on the destination drive, and the EGA download account credentials. Where can I find the PyEGA3 download client installation and download instructions? We strongly recommend checking our video tutorial demonstrating the usage of PyEGA3 from installation to file download. More detailed information is available at PyEGA3 GitHub. What ports are required for the PyEGA3 download client to function? PyEGA3 makes HTTPS calls to the EGA Data API (https://ega.ebi.ac.uk:8443). This port 8443 must be reachable from the location where PyEGA3 is executed to avoid timeouts. PyEGA3 download client How to update the PyEGA3 download client to be on the latest version? Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 --upgrade I do not have an active EGA account. Can I test the download with the PyEGA3 download client? An EGA download test account (ega-test-data@ebi.ac.uk) has been created for troubleshooting and training purposes. The test account does not require an EGA username and password because it contains publicly accessible files from the 1000 Genomes Project. More information about the use of this account and log in details are available at pyEGA3. I lost my connection while the download was in progress. Does this mean that I have to download the file again from the start? The PyEGA3 download client supports automatic resumption of downloads. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the resume feature, downloads will automatically resume if you encounter any errors or if the connection is interrupted. How can I improve the overall download speed of the PyEGA3 download client? Download speeds can be optimised using the --connections parameter which will parallelise download at the file level. If the --connections parameter is provided, all files >100Mb will be downloaded using the specified number of parallel connections. It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Why is my file taking a long time to be saved? Please note that when a file is being saved, it goes through two processes. First, the downloaded file "chunks" are pieced back together to reconstruct the original file. Secondly, PyEGA3 calculates the checksum of the file to confirm that the file was downloaded successfully. Larger files will take more time to reconstruct and validate the checksum. Why is the HTSGET protocol not working with my dataset of interest? PyEGA3 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file, saving both time and storage space. Please note that in order for the genomic range requests to work for a BAM, CRAM or VCF file there must be an associated BAI, CRAI or TBI file, respectively. If the dataset does not contain these index files then genomic range requests cannot be performed. After download Do I need to decrypt data files downloaded through the pyEGA3 download client? Files are transferred over secure HTTPS connections and received unencrypted, thus there is no need for decryption after data download. What is the purpose of an MD5 file? After the download completes, file integrity is verified using checksums. The PyEGA3 download client automatically verifies each file’s unencrypted md5 after download to ensure that the file was downloaded correctly from the EGA. Errors Why do I get a “400 Client Error” while trying to access the download client? Ensure that your credentials are formatted correctly. Please contact the EGA Helpdesk if you are unsure about your account’s username (i.e. your email address). Why do I get a “500 Server Error”? It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Otherwise, 500 server errors are internal server errors from EGA’s end. Retry after some time and, if the 500 error persists: check our homepage or Twitter for any outage information or report it to EGA Helpdesk. Why do I get a “slice error”? This type of error occurs when one slice download was prematurely interrupted. Please re-start the same download. The download client will pick up any partial download and download any missing slices. Why do I get the error “Dataset' EGADXXXXXXXXXXX' is not in the list of your authorised datasets”? Please note that the data access was given to the email (username) provided to the Data Access Committee (DAC) in your official request. Therefore, you shall check that the account that you are using is the same one that you sent to the DAC. Why do I get “ERROR:root:Failed to obtain IP address”? This might mean that the connection ports are blocked. Check that the port 8443 is reachable.In case the port is reachable and the error persists, please try to modify the file pyega3.py on line 44 in the python module installation: Replace endpoint = 'https://ipinfo.io/json' with endpoint = 'https://api.myip.com' Why do I get the error “Invalid username, password or secret key - please check and retry”? Make sure that you are using the correct credentials (username and password) and there is no typo. Contact EGA Helpdesk if the problem persists.

  Documentation access/download/files/pyega3

• Cellular Diversity of the Developing Human Cerebral Cortex

  We sought to characterize cellular heterogeneity in the human cerebral cortex at a molecular level during cortical neurogenesis. We captured single cells and generated sequencing libraries using the C1TM Single-Cell Auto Prep System (Fluidigm), the SMARTer Ultra Low RNA Kit (Clontech), and the Nextera XT DNA Sample Preparation Kit (Illumina). We performed unbiased clustering of the single cells and further examined transcriptional variation among cell groups interpreted as radial glia. Within this population, the major sources of variation related to cell cycle progression and the stem cell niche from which radial glia were captured. We found that outer subventricular zone radial glia (oRG cells) preferentially express genes related to extracellular matrix formation, migration, and stemness, including TNC, PTPRZ1, FAM107A, HOPX, and LIFR and related this transcriptional state to the position, morphology, and cell behaviors previously used to classify the cell type. Our results suggest that oRG cells maintain the subventricular niche through local production of growth factors, potentiation of growth factor signals by extracellular matrix proteins, and activation of self-renewal pathways, thereby contributing to the developmental and evolutionary expansion of the human neocortex. For study version 2, we have updated this data set to include additional primary cells that we infer to represent microglia, endothelial cells, and immature astrocytes, as well as additional cells from the developing neural retina, and from iPS-cell derived cerebral organoids. The genes distinguishing these cell populations may reveal biological processes supporting the diverse functions of these cell types as well as vulnerabilities of specific cell types in human genetic diseases and in viral infections. For study version 3, we have updated the data set to include additional primary cells, including those published in Nowakowski et al., 2017 (PMID:29217575). For study version 4, we have additionally performed parallel analyses of transcriptomes and physiological responses of 476 single cells isolated from developing human cortex. As a result, we were able to identify physiological response profiles of specific progenitor and neuronal cell types during human cortical development.For study version 5, we have additionally performed bulk RNA sequencing of organotypic primary cultures from the developing human cortex with or without exposure to SARS-CoV-2 to understand the infectability and transcriptomic effects of SARS-CoV-2 on the developing human cortex.For study version 6, we investigated the impact of LIFR signaling on neural proliferation and differentiation of human oRG cells. Specifically, we isolated oRG cells from the primary developing neocortex and cultured them for four weeks with and without LIF treatment. We then performed single-cell RNA sequencing using the Chromium Single Cell 3’ Reagent Kits (v3.1, Dual index) from 10x Genomics to understand the molecular and cellular changes of oRG differentiation upon LIF treatment.

  Study phs000989

• Sickle Cell Disease Natural History Data Resource (SCD NHDR)

  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. BackgroundThe NHLBI initiated the Sickle Cell Disease Natural History Data Resource (SCD NHDR) to leverage existing SCD studies to build a data resource to provide phenotypic data on contemporaneous control cohorts for gene therapy trials and other studies. The potential uses of the NHDR are broad, including providing matched controls for clinical trials, observing a cohort of untreated patients as part of a natural history study, or conducting comparative effectiveness research on a subpopulation with selected co-morbidities or drug treatment profiles. The SCD NHDR includes two multi-center SCD longitudinal cohort studies with extensive annual clinical data and patient surveys, the Sickle Cell Disease Implementation Consortium (SCDIC-I and SCDIC-II) and the Globin Research Network for Data and Discovery (GRNDaD). The SCDIC-I, initiated in 2017 and concluded in June 2022, enrolled over 2400 patients with SCD from 8 US treatment centers. The SCDIC-II reconsented 1220 of the SCDIC-I patients as well as enrolling an additional 450 new patients from the same 8 centers between September 2022 and October 2023, for a total of 1670 in SCDIC-II. Only two of the many GRNDaD centers are submitting data to the SCD NHDR for deposit into BDC (approximately 122 patients). Data submissions from the SCD NHDR to BDC will be annually starting in early 2024. Description of the Study Data All data obtained for the SCD NHDR are considered common data elements (CDEs) important for studies of SCD. These CDEs were identified from several workgroups of SCD experts convened under the NHLBI's Cure-SC Initiative (https://curesickle.org/cde-catalog). The following types of data elements were abstracted from the medical record – variables that describe the SCD diagnosis, SCD co-morbidities and other clinical complications, elements from the physical examination, medications and transfusions, insurance type, laboratory measurements, healthcare utilization, history of SCD-related procedures, and measurements from cardiac procedures. The following types of data were self-reported on the patient survey – demographics, diagnosis information, pain experience, social and mental health information, other patient reported outcome domains (e.g., sleep, fatigue), and alcohol and smoking history. Standard PRO measures were used from ASCQ-Me, PROMIS and Neuro-QoL. Patient surveys were completed approximately annually. Under SCDIC-I, two medical record abstractions and labs were reported at enrollment and approximately 3 years later. Under SCDIC-II and GRNDaD, all data are collected annually. Patients may refuse to complete the survey.

  Study phs003529

• PanCuRx Translational Research Initiative

  The goal of the PanCuRx TRI is to seek solutions to the high fatality rate of pancreatic adenocarcinoma (PDAC), the most common type of pancreatic cancer, by generating new knowledge about the genetics and biology of the disease, mechanisms of how tumours grow and tailored treatment options. PDAC is the fourth leading cause of cancer death in Canada and is expected to become the second-leading cause of cancer death within the next decade. The current five-year survival rate of eight per cent is the lowest of all epithelial cancers. There are major clinical challenges to treating the disease, including the fact that PDAC spreads to other parts of the body early so surgical removal of the tumour benefits few patients, that PDAC has proven relatively resistant to systemic therapies such as chemotherapy and that there has been limited benefit from the use of newer molecular targeted agents. The PanCuRx team has created the world’s first resource of tumour-purified PDAC whole genomes; more than 500 PDAC samples, with combined clinical annotation, have been successfully sequenced and analyzed at the Ontario Institute for Cancer research in Toronto. The resulting clinical genomic resource created from this data has led to multiple new findings that have established a framework to better understand PDAC biology and lays the foundation for new genomic approaches to better understanding the disease. The team also launched a clinical trial called COMPASS (Comprehensive Molecular Characterization of Advanced Ductal Pancreas Adenocarcinoma for Better Treatment Selection: A Prospective Study), which is recruiting patients with advanced PDAC (both locally advanced and metastatic) at The Princess Margaret Cancer Centre (PM) in Toronto. The study uses the molecular results from individual patient tumours to guide selection of better second line treatment on a case-by-case basis. The primary objective of the initial study was to assess the feasibility of collecting tumour materials from patients with advanced PDAC and delivering results within 56 days of biopsy. Having achieved this objective, the trial has expanded to other cancer centres across Canada. Pancreatic cancer is one of the most deadly forms of cancer and outcomes have not improved in four decades. The PanCuRx initiative is providing a better understanding of the disease and actively applying new knowledge to cancer patients through clinical trials. This knowledge will help to improve quality of life and prolong survival for pancreatic cancer patients worldwide.

  Study EGAS00001002543