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

in 18.59 milliseconds.

• Single cell TotalSeqC protein data of 20 PMBC pools of HCC patients

  Single cell TotalSeqC protein data serial peripheral blood mononuclear cell (PBMC) samples taken from advanced HCC patients. TotalSeqC is available for 41 out of 72 PBMC samples included in the study, and were combined into 20 pools.

  Dataset EGAD00001011346

• Sequencing Data of Leukemic Samples

  Sequencing data of leukemic samples included in study. Including WES, WGS and targeted sequencing files from patients at diagnosis, remission and at relapse. The dataset includes samples from 52 pediatric patients, totaling 311 samples.

  Dataset EGAD00001015662

• 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

• Privacy Notice for Helpdesk service

  Privacy Notice for EGA Helpdesk service 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. Note that this service collects personal data directly provided by the user, and also collects personal data from users that is provided by other organisations. 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 dr. Thomas Keane, by: email at: tk2@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? We process your personal data on the grounds of important public interest. 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 users of the service: Name Email address Job title Date and time when the support request was sent We will use your personal data for the following purposes: To provide uninterrupted user access to the service To better understand the needs of the users and guide future improvements of the service To 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 organizations. 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. 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. Published at: February 6, 2019

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

• Whole Transcriptome Sequencing of Human Tumor Cells and Hematopoietic Stem and Progenitor Cells During Aging and Bone Marrow Disorders

  Whole transcriptome sequencing analyses were performed on human hematopoietic stem and progenitor cells during aging and bone marrow disorders. For this purpose, normal and diseased bone marrow or peripheral blood-derived mononuclear cells were FACS-purified into hematopoietic stem (CD34+CD38-Lin-) or hematopoietic progenitor (CD34+CD38+Lin-) populations. Primary human samples from healthy individuals were used along with comparative analyses in some pre-malignant and malignant conditions, including myelodysplastic syndrome (MDS), acute myeloid leukemia (AML) and plasma cell dyscrasias (e.g., multiple myeloma). Studies were also performed on total mononuclear cell fractions from patients with newly-diagnosed or relapsed multiple myeloma, or plasma cell leukemia. Briefly, RNA was extracted from all samples and quality was assessed using a Bioanalyzer instrument. Only samples with RNA integrity (RIN) values >7 were subjected to library preparation for RNA-sequencing. The SMARTer v4 cDNA amplification kit was used along with library construction by the NEB Ultra DNA kit for Illumina. Paired-end sequencing was performed on Illumina NextSeq instruments (Scripps Next Generation Sequencing Core), with all samples run over two separate flow-cells (to generate additional sequencing reads); >95M reads were generated in total for each sample. The RNA-sequencing data are available as FASTQ files.

  Study phs002291

• Predicting the Prevalence of Complex Genetic Diseases from Individual Genotype Profiles Using Capsule Networks

  Diseases with a complex genetic architecture, such as amyotrophic lateral sclerosis (ALS) as a most prominent example, are hard to disentangle. "Human mind-friendly" methods, such as linear approaches used in genome wide association studies (GWAS), remain blind to many genetic variants that matter. On the other hand, methods that are sufficiently sophisticated to entirely capture the characteristic interplay of genetic variants remain black boxes for the human mind. Here, we give this a decided, and as we argue, a very promising try. We present DiseaseCapsule, a capsule network-based approach that enables us to predict prevalence/occurrence of a genetically complex disease from individual genotype profiles. Importantly, capsule networks are considerably easier to decompose into their components than ordinary deep neural networks, which promotes the interpretability of their results. The data we used are from Project MinE, a large-scale study that aims to reveal the genetic and epigenetic mechanisms that underlie ALS in the framework of a globally concerted collaboration. Specifically, we used data from the Dutch cohort of the project, which contains 7213 healthy ('control') individuals and 3192 individuals affected with ALS. The cohort includes 5208 females and 5197 males. All participants of the study were genotyped using an Illumina 2.5M SNP array.

  Study phs003146

• Pathways Study

  The Pathways Study (NCI R01 CA105274, PI: Kushi), is a prospective cohort study of a diverse population of recently diagnosed breast cancer survivors in KPNC. The aims are to examine the effect on recurrence and survival of 1) lifestyle factors such as diet, physical activity, and use of complementary and alternative therapies and 2) molecular factors such as biomarkers of inflammation and tumor DNA methylation profiles. Recruitment into the cohort was from January 2006 to May 2013. Baseline data collection was by in-person interview (on average two months post-diagnosis), with follow-up via mailed or phone questionnaires at 6, 24, and 72 months and outcomes and comorbidities at 12, 24, 48, 72, and 96 months post-enrollment. The Pathways Study is now funded through May 2021 as a cancer cohort infrastructure grant (U01 CA195565, MPI: Kushi/Ambrosone). The Pathways baseline interview consists of interviewer- and self-administered questionnaires. Interviewer-administered questionnaires collected information including demographics, family health history, pregnancy health history, menstrual history, history of breast care screening procedures, smoking history, hormone use, medication history, and vitamin and mineral use. Self-administered questionnaires collected information on diet, physical activity, CAM use, lymphedema, and psychosocial and quality of life measures.

  Study phs001534