12230 results for "u7buy fc points Visit Buyfc26coins.com for latest FC 26 coins news..4F5O"

in 21.87 milliseconds.

• Exploring the role of mtDNA variation in Multiple Sclerosis in a large cohort of discordant monozygotic twins

  Several lines of evidence indicate that mitochondrial DNA (mtDNA) variants might predispose to multiple sclerosis (MS). We examined this in 49 monozygotic (MZ) twin pairs clinically discordant for MS at study entry. Since the nuclear DNA of MZ twins is identical, our study provides a unique setting to functionally associate unique mtDNA variants and skewed heteroplasmy with MS development. In order to identify mtDNA variants in the twin cohort, we deeply sequenced the mitochondrial genome in blood of all 49 MZ twin pairs using next generation sequencing (Illumina, HiSeq or MiSeq) with an average coverage depth of ~25,000 sequences per base. Heteroplasmic variants were validated using targeted deep sequencing (TDS) (Illumina, MiSeq) in DNA isolated from blood and buccal swabs. In addition, whole blood was also available of 5 additional MS-affected or healthy siblings and 1 dizygotic twin pair discordant for MS, comprising in total 6 non-identical sib pairs. Moreover, all cases were screened for pathogenic mtDNA polymerase gamma (POLG) mutations. The data provides valuable insights in the possible involvement of mtDNA variants in the pathogenesis of MS, and gives information on the segregation of heteroplasmic variants within MZ twins and non-identical siblings and across different tissues.

  Study EGAS00001001240

• Single cell sequencing of breast cancer T cells reveals a tissue-resident memory subset associated with improved prognosis

  The quantity of tumor infiltrating lymphocytes (TILs) in breast cancer (BC) is a robust prognostic factor for improved patient survival particularly in triple negative and HER2-overexpressing BC subtypes. Whilst T cells are the predominant TIL population, the relationship between quantitative and qualitative differences in T cell subpopulations and patient prognosis remains unknown. We performed single-cell RNA sequencing (scRNA-seq) of 6311 T cells isolated from human BCs, and show for the first time that significant heterogeneity exists in the infiltrating T cell population. We demonstrated that high TIL BCs contained significant numbers of CD8+ T cells with features of tissue-resident memory T (TRM) cell differentiation and that these CD8+ TRM cells expressed high levels of immune checkpoint molecules and effector proteins. A CD8+ TRM gene signature developed from the scRNA-seq data was significantly associated with improved patient survival in early-stage triple negative breast cancer (TNBC) and provided better prognostication compared with CD8 expression alone. Our data suggests that CD8+ TRM contribute to BC immunosurveillance and are the key targets of modulation through immune checkpoint inhibition. Further understanding of the development, maintenance and regulation of TRM cells will be crucial for successful immunotherapeutic development in BC.

  Study EGAS00001002845

• The Prediction and Prevention of Preeclampsia

  The Prediction and Prevention of Preeclampsia (PREDO) is a prospective birth cohort study of Finnish women who were pregnant between 2005 and 2010 and their children. The PREDO study cohort was set up to identify novel risk factors and biomarkers in pregnant women associated with the development of preeclampsia and intrauterine growth restriction (IUGR). Two groups of pregnant women were enrolled during the first trimester of their pregnancy: first, pregnant women with a known clinical risk factor status for preeclampsia and IUGR (N=1079; 969 of these women had at least one and 110 had none of the known risk factors for preeclampsia and IUGR), and second, pregnant women who volunteered to participate regardless of their risk factor status for preeclampsia and IUGR (N=3698). Both samples were monitored during pregnancy with four clinical visits and bi-weekly self-reports. The post-delivery follow-up has taken place at approximately 2 weeks, 6 months, and 3.5 years after the delivery. The most recent follow-up started in 2016 and is ongoing. In the high-risk sample, cord blood samples were collected and genome-wide genotyping has been conducted with Illumina OmniExpressExome 1.2 and genome-wide methylation status has been analysed with Illumina 450k HM array.

  Study EGAS00001001898

• Whole Exome Sequencing PPGL

  Whole exome sequencing (WES) libraries were prepared with the SureSelectXT Human All Exon V6+COSMIC target enrichment system (Agilent, 5190-9307) by following kit manufacturer`s instructions. 200 ng of genomic DNA from FFPE tumoral samples and 1 µg from FF or germline samples were used as starting material. SureSelectXT HS (Agilent, G9704A) and SureSelectXT2 (Agilent, G9621A) reagent kits were alternatively used for FFPE derived and good quality samples, respectively. DNAs were fragmented on a Covaris S2 sharing instrument based on initial sample’s integrity. Fragmented DNA samples were processed through subsequent enzymatic treatments of end-repair, dA-tailing, and ligation to Illumina's adapters. Adapter-ligated libraries were PCR amplified with Illumina PE primers and subsequently hybridized to SureSelect Oligo Capture Library Mix. Biotinylated hybrids were captured and the enriched fraction eluted. Libraries were completed by limited-cycle PCR with Illumina TruSeq primers and KAPA HiFi HotStart DNA pol (Roche KK2501). Sample-specific libraries were combined into equimolarly balanced pools and applied to Illumina flow cells for cluster generation. Sequencing was performed on either the Illumina HiSeq2500 or NovaSeq6000 in a paired-end 100bp reads mode to a median target coverage of ~200x and ~100x for tumors and germline, respectively.

  Study EGAS00001006043

• Whole genome sequencing delineates regulatory, structural, and cryptic splice variants in early onset cardiomyopathy

  Cardiomyopathy (CMP) is a heritable disorder. Over 50% cases are gene-elusive on clinical gene panel testing. The contribution of variants in non-coding DNA elements that result in cryptic splicing and regulate gene expression has not been explored. We analyzed whole genome sequencing (WGS) data in a discovery cohort of 209 pediatric CMP patients and 1,953 independent replication genomes and exomes. We searched for protein-coding variants, and non-coding variants predicted to affect the function or expression of genes. Thirty-nine % cases harbored pathogenic coding variants in known CMP genes, and 5% harbored high-risk loss-of-function (LoF) variants in additional candidate CMP genes. Fifteen % harbored high-risk regulatory variants in promoters and enhancers of CMP genes (Odds ratio 2.25, p=6.70×10-7 versus controls). Genes involved in α-dystroglycan glycosylation (FKTN, DTNA) and desmosomal signaling (DSC2, DSG2) were most highly enriched for regulatory variants (Odds ratio 6.7-58.1). Functional effects were confirmed in patient myocardium and reporter assays in human cardiomyocytes, and in zebrafish CRISPR knockouts. We provide strong evidence for the genomic contribution of functionally active variants in new genes and in regulatory elements of known CMP genes to early-onset CMP.

  Study EGAS00001004929

• Significant and pervasive effects of RNA degradation on Nanopore direct RNA sequencing

  Abstract Oxford Nanopore direct RNA sequencing (DRS) is capable of sequencing complete RNA molecules and accurately measuring gene and isoform expression. However, as DRS is designed to profile intact RNA, expression quantification may be more heavily dependent upon RNA integrity than alternate RNA-seq methodologies. It is currently unclear how RNA degradation impacts DRS or if it can be corrected for. To assess the impact of RNA integrity on DRS we performed a degradation time-series using SH-SY5Y neuroblastoma cells. Our results demonstrate that degradation is a significant and pervasive factor that can bias DRS measurements, including a reduction in library complexity resulting in an overrepresentation of short genes and isoforms. Degradation also biases differential expression analyses; however, we find explicit correction can almost fully recover meaningful biological signal. In addition, DRS provided less biased profiling of partially degraded samples than nanopore cDNA-PCR sequencing. Overall, we find samples with RIN > 9.5 can be treated as undegraded and samples with RIN > 7 can be utilised for DRS with appropriate correction. These results establish the suitability of DRS for a wide range of samples, including partially degraded in-vivo clinical and post-mortem samples, whilst limiting the confounding effect of degradation on expression quantification.

  Study EGAS00001006542

• Natural genetic variation of the cardiac transcriptome in non-diseased donors and patients with dilated cardiomyopathy

  Background: Genetic variation is an important determinant of RNA transcription and splicing, which in turn contributes to variation in human traits including cardiovascular diseases.Results: Here we report the first in-depth survey of heart transcriptome variation using RNA-sequencing in 149 (97)* patients with dilated cardiomyopathy and 113 (108)* non-diseased controls. We reveal extensive differences of gene expression and splicing between dilated cardiomyopathy patients and controls, affecting known as well as novel dilated cardiomyopathy genes. Moreover, we show a widespread effect of genetic variation on the regulation of transcription, isoform usage and allele specific expression. Systematic annotation of genome wide association SNPs identifies 60 functional candidate genes for heart phenotypes, representing 20% of all published heart genome wide association loci. Focusing on the dilated cardiomyopathy phenotype we found that eQTL variants are also enriched for dilated cardiomyopathy genome wide association signals in two independent cohorts.Conclusions: RNA transcription, splicing and allele specific expression are each important determinants of the DCM phenotype and are controlled by genetic factors. Our results represent a powerful resource for the field of cardiovascular genetics. (*) numbers in parentheses represent samples that the publication is based on.

  Study EGAS00001002454

• Stratifying and Targeting Pediatric Medulloblastoma through Genomics

  In this project, genomic analyses of pediatric medulloblastoma samples, obtained through the international medulloblastoma consortium, will be performed. RNA and miRNA expression profiles of 1000 samples, representing all four subgroups (Wnt, Shh, Group C, and D), will be studied to identify novel subtypes within each subgroup. The resulting subtype-specific expression profiles will support the development of reliable and robust biomarkers to more accurately and reliably classify medulloblastomas for treatment in clinical trials. For that purpose, two assays will be developed: an antibody-based immunohistochemical assay and an orthogonal nucleic acid-based hybridization assay. Additional genomic DNA analysis of the 300 high risk subgroup cases will support the discovery of subgroup specific somatic mutations in order to inform current clinical trials of targeted therapies, and to identify genes and pathways already targeted in other diseases. Such therapies could be rapidly transitioned to Phase II trials in medulloblastoma. Furthermore, the discovery of somatic mutations could be used for developing as well as validating specific biomarkers. The project team will also try to identify risk factors that predispose children to this type of cancer.

  Study EGAS00001000273

• FASTQ files of total RNA-Seq data from the POPS PET (pre-eclamptic) samples

  All the samples were obtained from the Pregnancy Outcome Prediction–a prospective cohort study of nulliparous women attending the Rosie Hospital, Cambridge (UK) for their dating ultrasound scan between January 14, 2008, and July 31, 2012. Ethical approval for the study was given by the Cambridgeshire 2 Research Ethics Committee (reference number 07/H0308/163) and all participants provided written informed consent. Cases of preeclampsia (PET) were defined on the basis of the 2013 ACOG criteria and cases of small for gestational age (SGA)infants were confined to severe SGA, i.e. a customized birth weight <5th percentile. Chorionic villi from the corresponding placentas (free from decidua, visible infarction, calcification, hematoma, or damage) were collected and processed within 30 minutes of separation from the uterus. After repeated washes in chilled phosphate buffered saline, the samples were placed in RNA later (Applied Biosystems) and stored at -80°C. Total placental RNA was extracted using mirVana Isolation Kit (Ambion). For each placenta, approximately 5 mg of tissue were homogenized in the Lysis/Binding solution for 20 sec at 6 m/s using a bead beater (FastPrep24) and Lysing Matrix D Tubes (MP Biomedicals). The samples were then spun at 13,000 rpm for 5 min at 4°C and the supernatants recovered. Afterwards, the manufacturer's instructions were followed. Immediately after the RNA extraction, placental RNA samples were DNase-treated using DNA-free DNA Removal Kit (Ambion), aliquoted, and stored in -80°C. Quantity and quality of the RNA samples were assessed using the Agilent 2100 Bioanalyzer, the Agilent RNA 6000 Nano Kit (Agilent Technologies), and Qubit fluorometer. Libraries were prepared starting with 300-500 ng of good quality total RNA (RIN ≥7.5) using the TruSeq Stranded Total RNA Library Prep Kit with Ribo-Zero Human/Mouse/Rat (Illumina), according to the manufacturer's instructions. The kit contains 96 uniquely indexed adapter combinations in order to allow pooling of multiple samples prior to sequencing. After determining their size (with the Agilent 2100 Bioanalyzer and the Agilent High Sensitivity DNA Kit by Agilent Technologies) and concentration (by qPCR with the KAPA Illumina ABI Prism Library Quantification Kit, Kapa Biosystems), libraries have been pooled and sequenced (single-end, 125 bp) using a Single End V4 Cluster Kit and an Illumina HiSeq2500 or HiSeq4000 instrument.

  Dataset EGAD00001003508

• Single-cell level characterization of B cell depletion and repopulation following rituximab in systemic lupus erythematosus

  Rituximab, a CD20+ B cell depletion therapy, is frequently used in the treatment of systemic lupus erythematosus (SLE). However, variability in patient response highlights the need for a deeper understanding of the underlying immune cell dynamics of B cell depletion and repopulation. In this study, we conducted longitudinal single-cell profiling of nine SLE patients treated with rituximab from pretreatment to up to 15 months post-treatment. These were compared to eight healthy controls. We profiled PBMCs via 10X Genomics single-cell RNA, surface protein (CITE-seq), B cell receptor (BCR), and T cell receptor (TCR) sequencing and sequenced bulk BCR repertoires in parallel. For single cell sequencing, 10 pools were created with an equal number of cells from 4 samples each. Samples collected at different timepoints from the same patient were distributed across different pools to allow demultiplexing of individuals using genotypes captured from the scRNA-seq data. Libraries were pooled using a ratio of GEX:CITE:TCR:BCR=9:2:1:1 and were sequenced across two lanes of the NovaSeq 6000. For bulk BCR sequencing, individual samples were demultiplexed using primer barcodes and paired-end BCR amplicon reads were merged prior to submission; data are provided as unmapped single-end reads.

  Study EGAS00001006798

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! The EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• DAC - Comparison of sequencing assays for sensitive detection of circulating tumour DNA in stage IA-IV breast cancer

  Dac EGAC00001002549

• Data Access Committee for data from EGAS00001002864: Genome analysis of oesophageal cancer and Barretts oesophagus

  Dac EGAC00001000863

• This DAC is to control access to data contained within dataset EGAS00001001147, for Myeloma XI clinical trial patients.

  Dac EGAC00001000307

• Centre for Genomic Regulation - Beta Cell Genome Regulation Lab

  Dac EGAC00001000853

• DAC for Clonal somatic copy number altered driver events inform drug sensitivity in high-grade serous ovarian cancer

  Dac EGAC00001002644

• ITER-FIISC Data Access Committee (microbiome)

  DAC for Metagenomic characterization of tracheal aspirates from non-pulmonary sepsis patients

  Dac EGAC50000000230

• DAC Fondazione Michelangelo

  This is the DAC responsible for granting access to sequencing data generated by Fondazione Michelangelo

  Dac EGAC50000000179

• Uni_Wue_Chair of Microbiology

  Dual RNA seq datasets of M2 sequenced macrophages after chlamydia infection for 30 hours.

  Dac EGAC50000000577

• South African Blood Regulatory (SABR) Resource Committee

  Data access committee for the South African Blood Regulatory (SABR) Resource.

  Dac EGAC50000000501

• OICR-DAC, Ontario Institute for Cancer Research; Biliary Tract Cancer

  Next Gen Sequencing data from Biliary Tract Cancers

  Dac EGAC50000000528

• DAC for "Establishment and characterization of circulating tumor cells-derived organoids from metastatic breast cancer patients."

  Dac EGAC00001003514

• Breast Cancer Association Consortium Data Access Coordinating Committee

  Data access committee for the Breast Cancer Association Consortium (BCAC).

  Dac EGAC50000000824

• Synthetic modeling reveals HOXB genes are critical for the initiation and maintenance of human leukemia

  Study EGAS00001003627

• Evaluation of protocols for rRNA depletion-based RNA sequencing of nanogram inputs of mammalian total RNA

  Study EGAS00001003849