431 results for "fc points ps4 Besuche die Website Buyfc26coins.com. Alles easy, top..XkV1"

in 15.39 milliseconds.

• Circulating, Cell-Free DNA Methylation Patterns Indicate Cellular Sources of Allograft Injury after Liver Transplant

  Post-transplant complications reduce allograft and recipient survival. Current approaches for detecting allograft injury non-invasively are limited and do not differentiate between cellular mechanisms. Here, we monitor cellular damages after liver transplants from cell-free DNA (cfDNA) fragments released from dying cells into the circulation. We analyzed longitudinal blood samples collected from patients at different time points after transplant. Sequence-based methylation of cfDNA fragments were mapped to an atlas of cell-type-specific DNA methylation patterns derived from 476 methylomes of purified cells. For liver cell types, DNA methylation patterns and multi-omic data integration show distinct enrichment in open chromatin and regulatory regions functionally important for the respective cell types. We find that multi-tissue cellular damage post-transplant recovers in patients without allograft injury during the first post-operative week. However, sustained elevation of hepatocyte and biliary epithelial cfDNA within the first month indicates early-onset allograft injury. Further, cfDNA composition differentiates amongst causes of allograft injury indicating the potential for non-invasive monitoring and timely intervention.

  Study phs003610

• Multiple Myeloma follow-up sequencing study

  A total of 40 Multiple Myeloma (MM) patients at clinical relapse who progressed during Proteasome Inhibitors (PIs) or Immunomodulating Drugs (IMiDs)-based therapies and who are assigned to antiCD38-based salvage treatments, will be enrolled. We will collect bone marrow (BM) and peripheral blood (PB) samples from patients at specific timepoints: baseline (BM, PB and buccal swab) every 3 month (PB) achievement of response (≥ Very Good Partial Response (VGPR)) (BM and PB) relapse or refractory status to antiCD38-based treatments (BM and PB) Samples will be processed and stored in the "Hematological Laboratory" located in the University of Turin (Italy) for various proposed analyses: at specific time-points CD138+ (Plasma Cells-PCs) awill be immunomagnetically enriched from the BM mononuclear cells and frozen as viable cells in dimethyl sulfoxide (DMSO); PB mononuclear cells (PBMCs) will be isolated from whole blood by density-gradient centrifugation, and frozen as above; plasma fraction from PB and BM will be obtained by centrifugation and stored frozen; Neutrophils will be obtained at the time of enrollment as a source of control germline DNA and stored frozen.

  Study EGAS00001007092

• Kalirin-RAC controls nucleokinetic migration in ADRN-type neuroblastoma

  The migrational propensity of neuroblastoma is affected by cell identity, but the mechanisms behind the divergence remain unknown. Using RNAi and time-lapse imaging, we show that ADRN-type NB cells exhibit RAC1- and kalirin-dependent nucleokinetic (NUC) migration that relies on several integral components of neuronal migration. Inhibition of NUC migration by RAC1 and kalirin-GEF1 inhibitors occurs without hampering cell proliferation and ADRN identity. Using three clinically-relevant expression dichotomies, we reveal that most of up-regulated mRNAs in RAC1- and kalirin-GEF1-suppressed ADRN-type NB cells are associated with low-risk characteristics. The computational analysis shows that, in a context of overall gene set poverty, the upregulomes in RAC1- and kalirin-GEF1-suppressed ADRN-type cells are a batch of AU-rich elements (ARE)-containing mRNAs, which suggests a link between NUC migration and mRNA stability. GSEA-based search for vulnerabilities reveals prospective weak points in RAC1- and kalirin-GEF1-suppressed ADRN-type NB cells, including activities of H3K27- and DNA methyltransferases. Altogether, these data support the introduction of NUC inhibitors into cancer treatment research.

  Study EGAS00001005023

• Genomic and functional fidelity of small cell lung cancer patient-derived xenografts

  Small cell lung cancer (SCLC) patient-derived xenografts (PDXs) can be generated from biopsies or circulating tumor cells (CTCs), though scarcity of tissue and low efficiency of tumor growth have previously limited these approaches. Applying an established clinical-translational pipeline for tissue collection and an automated microfluidic platform for CTC-enrichment, we generated 17 biopsy-derived PDXs and 17 CTC-derived PDXs in a two-year timeframe, at efficiencies of 89% and 38%, respectively. Whole exome sequencing showed that somatic alterations are stably maintained between patient tumors and PDXs. Early-passage PDXs maintain the genomic and transcriptional profiles of the founder PDX. In vivo treatment with etoposide and cisplatin (EP) in 30 PDX models demonstrated greater sensitivity in PDXs from EP naïve patients, and resistance to EP corresponded to increased expression of a MYC gene signature. Finally, serial CTC-derived PDXs generated from an individual patient at multiple time points accurately recapitulated the evolving drug sensitivities of that patient’s disease. Collectively, this work highlights the translational potential of this strategy.

  Study EGAS00001002853

• Philippine Ayta possess the highest level of Denisovan ancestry in the world

  Multiple lines of evidence show that modern humans interbred with archaic Denisovans. Here, we report an account of shared demographic history between Australasians and Denisovans distinctively in Island Southeast Asia. Our analyses are based on ~2.3 million genotypes from 118 ethnic groups of the Philippines including 25 diverse self-identified Negrito populations, along with high-coverage genomes of AustraloPapuans and Ayta Magbukon Negritos. We show that Ayta Magbukon possess the highest level of Denisovan ancestry in the world – ~30-40% greater than that of Australians and Papuans – consistent with an independent admixture event into Negritos from Denisovans. Together with the recently described Homo luzonensis, we suggest that there were multiple archaic species that inhabited the Philippines prior to the arrival of modern humans, and that these archaic groups may have been genetically related. Altogether, our findings unveil a complex intertwined history of modern and archaic humans in the Asia-Pacific region, where distinct Islander Denisovan populations differentially admixed with incoming Australasians across multiple locations and at various points in time.

  Study EGAS00001005407

• Philippine Ayta possess the highest level of Denisovan ancestry in the world

  Multiple lines of evidence show that modern humans interbred with archaic Denisovans. Here, we report an account of shared demographic history between Australasians and Denisovans distinctively in Island Southeast Asia. Our analyses are based on ~2.3 million genotypes from 118 ethnic groups of the Philippines including 25 diverse self-identified Negrito populations, along with high-coverage genomes of AustraloPapuans and Ayta Magbukon Negritos. We show that Ayta Magbukon possess the highest level of Denisovan ancestry in the world – ~30-40% greater than that of Australians and Papuans – consistent with an independent admixture event into Negritos from Denisovans. Together with the recently described Homo luzonensis, we suggest that there were multiple archaic species that inhabited the Philippines prior to the arrival of modern humans, and that these archaic groups may have been genetically related. Altogether, our findings unveil a complex intertwined history of modern and archaic humans in the Asia-Pacific region, where distinct Islander Denisovan populations differentially admixed with incoming Australasians across multiple locations and at various points in time.

  Study EGAS00001005408

• The clinical utility of genomics in childhood cancer extends beyond targetable mutations - WGS data

  We deeply sequenced 864 cancer-associated genes and the complete genomes and transcriptomes for 300 pediatric and adolescent/young adult (AYA) patients with poor prognosis or rare tumors. Using integrative somatic-germline analyses, we assessed the clinical utility of cancer genomics in this population. Clinically actionable variants were identified in 56% of patients. Improved diagnostic accuracy led to modified management in a subset. Therapeutically targetable variants, found in 54% of patients, were of unanticipated timing and type, with over 20% of these derived from the germline. Enrichment in corroborating mutational signature 3 (‘BRCAness’) in patients with germline homologous recombination defects suggests they are drivers of pediatric cancers and potential targets for PARP inhibition. Comprehensive somatic-germline cancer genomic profiling is useful at multiple points in the care trajectory for pediatric/AYA patients, supporting its integration into early clinical management. Re-biopsy at the time of relapse should be considered, and specific attention to mutational burden is indicated. Defective DNA repair genes in the germline may represent important targetable drivers.

  Study EGAS00001006610

• The clinical utility of genomics in childhood cancer extends beyond targetable mutations - Cancer Panel data

  We deeply sequenced 864 cancer-associated genes and the complete genomes and transcriptomes for 300 pediatric and adolescent/young adult (AYA) patients with poor prognosis or rare tumors. Using integrative somatic-germline analyses, we assessed the clinical utility of cancer genomics in this population. Clinically actionable variants were identified in 56% of patients. Improved diagnostic accuracy led to modified management in a subset. Therapeutically targetable variants, found in 54% of patients, were of unanticipated timing and type, with over 20% of these derived from the germline. Enrichment in corroborating mutational signature 3 (‘BRCAness’) in patients with germline homologous recombination defects suggests they are drivers of pediatric cancers and potential targets for PARP inhibition. Comprehensive somatic-germline cancer genomic profiling is useful at multiple points in the care trajectory for pediatric/AYA patients, supporting its integration into early clinical management. Re-biopsy at the time of relapse should be considered, and specific attention to the mutational burden is indicated. Defective DNA repair genes in the germline may represent important targetable drivers.

  Study EGAS00001006642

• Sequential Antigen-loss and Branching Evolution in Lymphoma after Anti-CD19 and Anti-CD20 Targeted T Cell Engaging Immunotherapy

  CD19 CAR T cells and CD20 targeting T cell engaging bispecific antibodies have been approved in B-cell Non-Hodgkin lymphoma lately, heralding a new clinical setting where patients are treated with both approaches, sequentially. The aim of our study was to investigate the selective pressure of CD19 and CD20 directed therapy on the clonal architecture in lymphoma. Using a broad analytical pipeline, we identified truncating mutations in the gene encoding CD20 conferring antigen loss in 80% of patients relapsing from CD20 bispecs. Pronounced T cell exhaustion was identified in cases with progressive disease and retained CD20 expression. We also confirmed CD19 loss after CAR T cell therapy and report the case of sequential CD19 and CD20 loss. We observed branching evolution with re-emergence of CD20 positive subclones at later time points and spatial heterogeneity for CD20 expression in response to targeted therapy. Our results highlight immunotherapy as an evolutionary bottleneck selecting for antigen-loss variants but also complex evolutionary pathways underlying disease progression from these novel therapies.

  Study EGAS00001007561

• GOSH_Childhood_Leukemia_Behjati_WellcomeCore_RNA

  Paediatric single-cell archival project This project is taking sequential samples of children with B-cell acute lymphoblastic leukaemia (B-ALL) treated at Great Ormond Street Hospital (GOSH) between 2011 and the present day. Patients selected, are those that have done badly (e.g. had to escalate treatment, relapsed or died) despite having apparently ""good"" or ""intermediate"" risk cytogenetics, and often also had immunotherapy (e.g., the bi-specific T-cell engager blinatumomab) because of this. Using samples from key treatment-points, we hope to better characterise their disease and treatment response, to re-define understandings of risk for patients who did unexpectedly poorly. Additionally, we hope to define the disease/immunological factors that determine response to increasingly used immunotherapies within the field of paediatric B-ALL. Each of the samples will be viably frozen bone marrow-derived mononuclear cells. They will come in Eppendorf's, frozen and de-anonymised, from GOSH. We plan to primarily do single cell analysis (GEX, BCR +/-TCR), and then tumour-only WGS and bulk-RNA expression on left-over

  Study EGAS00001007616

• Selective targeting of TBXT with DARPins identifies regulatory networks and therapeutic vulnerabilities in chordoma

  The embryonic transcription factor TBXT (brachyury) drives chordoma, a spinal neoplasm without effective drug therapies. TBXT’s regulatory network is poorly understood, and strategies to disrupt its activity for therapeutic purposes are lacking. We developed designed ankyrin repeat proteins that block TBXT-DNA binding (T-DARPins). In chordoma cells, T-DARPins reduced cell cycle progression, spheroid formation, and tumor growth in mice and induced signs of senescence and differentiation. Transcriptomic and proteomic analyses identified gene networks involved in cell cycle regulation, embryonic cell identity, and interferon response and revealed features of regulome components, such as druggability for future translational studies and the fine-tuning of TBXT downstream effectors through IGFBP3. Finally, we found high interferon signaling in chordoma cell lines and patient tumors, which was promoted by TBXT and associated with sensitivity to JAK2 inhibitors. These findings demonstrate the potential of DARPins for probing nuclear proteins to understand the regulatory networks of transcription factor-driven cancers, including entry points for therapies that warrant testing in patients.

  Study EGAS00001008140

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• MicroRNAs, Hypertension and End Organ Damage in Humans

  Study 1) Profiling of microRNAs in plasma of patients with hypertension complicated or not by metabolic syndrome or chronic kidney disease Hypertension (HTN) or high blood pressure is associated with subclinical target organ damage such as cardiac, vascular and kidney injury, which may lead to complications and death. In this study, we investigated circulating microRNAs as biomarkers of target organ damage in HTN patients. We profiled circulating microRNAs by RNA sequencing in platelet-poor plasma of normotensive subjects and patients with HTN complicated or not by metabolic syndrome (MetS) or chronic kidney disease (CKD) (n=15 each group). Differentially expressed microRNAs were identified with a threshold of false discovery rate <0.1. Differentially expressed microRNAs were identified uniquely to associate with HTN (8), MetS (1) or CKD (13), and 8 were similarly differentially expressed in different groups. This study identified the association of differentially expressed circulating microRNAs with target organ damage in HTN patients, which could have some pathophysiological and therapeutic implications. Study 2) Profiling of microRNAs in gluteal subcutaneous small arteries of patients with hypertension complicated or not by chronic kidney disease Hypertension (HTN) is associated with vascular damage characterized by endothelial dysfunction and vascular remodeling and stiffening, which contributes to kidney injury leading to chronic kidney disease (CKD). MicroRNAs are short non-coding RNAs which repress/degrade target mRNAs. The microRNA role in vascular injury in HTN remains unclear. In this study, we aimed to identify differentially expressed microRNAs in small arteries of patients with HTN associated or not with CKD, in order to shed light on the pathophysiological molecular mechanisms. Normotensive subjects and HTN patients associated or not with CKD grades 3-4 were studied (n=15-16). Small arteries were isolated from subcutaneous gluteal biopsies, RNAs were extracted, and small and total RNA sequencing was performed by Illumina HiSeq-2500. Differentially expressed genes were identified with a P<0.05 and fold change (FC) >1.3. Differentially expressed microRNAs and mRNAs were identified uniquely to associate with HTN (microRNAs: 10, mRNAs: 68), CKD (microRNAs: 68, mRNAs: 395), and both groups (microRNAs: 2, mRNAs: 32). This study identified differentially expressed microRNAs and mRNAs in small arteries with target organ damage in HTN, which could have some pathophysiological and therapeutic implications.

  Study phs002389

• Longitudinal snRNAseq and DNAseq of IDHmutant glioma

  We collected longitudinal glioma samples from 35 patients with an IDH-mutant oligodendroglioma (n = 13) or IDH-mutant astrocytoma (n = 22) diagnosis based on 2021 WHO glioma classification at two or three time points (n = 75 samples). For each patient, we designated the two earliest samples as the initial and recurrence for longitudinal analyses. In 17 of 35 longitudinal pairs, the initial sample was obtained at primary diagnosis, whereas the remaining 18 cases the initial samples were collected at a subsequent surgery. Between the initial and recurrence samples, 26 of 35 patients received radiotherapy and/or alkylating chemotherapy, whereas no adjuvant treatment was reported for the remaining patients. To comprehensively investigate IDH-mutant glioma evolution, we used snRNAseq and bulk DNA/RNA sequencing from the same resected glioma samples. A subset of these samples was profiled with simultaneous snRNA-ATAC sequencing (48 out of 75), including 21 matched longitudinal pairs,

  Dac EGAC50000000973

• SCANDARE HNSCC 3' Tag RNA-seq

  SCANDARE (NCT03017573) is a multicentric biobanking study, enrolling adult patients with newly diagnosed head and neck squamous cell carcinoma (HNSCC), triple negative breast cancer (TNBC), ovarian and cervical cancer. Tumor tissue and blood samples are collected at several time points during patient's journey, including at diagnosis, post-neoadjuvant chemotherapy in case of neoadjuvant treatment, at surgery, at recurrence and at disease progression following treatment initiated at recurrence. Since its launch in 2017 at Institut Curie, SCANDARE has enabled the longitudinal collection and preservation of samples for in-depth analyses. Here, we describe molecular alterations in 264 FFPE samples at baseline from 90 HNSCC patients using 3'-tag RNA-seq technology, with FASTQ files deposited in the dataset.

  Dataset EGAD50000001655

• SCANDARE TNBC WES data

  SCANDARE (NCT03017573) is a multicentric biobanking study, enrolling adult patients with newly diagnosed head and neck squamous cell carcinoma (HNSCC), triple negative breast cancer (TNBC), ovarian and cervical cancer. Tumor tissue and blood samples are collected at several time points during patient's journey, including at diagnosis, post-neoadjuvant chemotherapy in case of neoadjuvant treatment, at surgery, at recurrence and at disease progression following treatment initiated at recurrence. Since its launch in 2017 at Institut Curie, SCANDARE has enabled the longitudinal collection and preservation of samples for in-depth analyses. Here, we describe molecular alterations in 247 frozen samples at baseline and 138 germline DNA from 139 TNBC patients using WES technology, with FASTQ files deposited in the dataset.

  Dataset EGAD50000001661

• SCANDARE TNBC WGS data

  SCANDARE (NCT03017573) is a multicentric biobanking study, enrolling adult patients with newly diagnosed head and neck squamous cell carcinoma (HNSCC), triple negative breast cancer (TNBC), ovarian and cervical cancer. Tumor tissue and blood samples are collected at several time points during patient's journey, including at diagnosis, post-neoadjuvant chemotherapy in case of neoadjuvant treatment, at surgery, at recurrence and at disease progression following treatment initiated at recurrence. Since its launch in 2017 at Institut Curie, SCANDARE has enabled the longitudinal collection and preservation of samples for in-depth analyses. Here, we describe molecular alterations in 108 FFPE samples at baseline and 108 germline DNA from 108 TNBC patients using WGS technology, with FASTQ files deposited in the dataset.

  Dataset EGAD50000001662

• Variant calling analysis of cfDNA whole exome sequencing in neuroblastoma

  This dataset contains VCF files from a variant calling analysis of 19 neuroblastoma patients. WES or WGS data of the primary tumor were compared to WES cfDNA analysis at the time of diagnosis and at a 2nd timepoint (complete remission, partial remission, disease progression or relapse). For 4 patients, WGS of germline, tumor at diagnosis and tumor at relapse DNA was performed on Illumina HiSeq2500, with 100-bp paired-end reads. For the other patients, WES was performed using either an AgilentSureSelect Human All Exon v5 or a Roche Nimblegen SeqCap EZ Exome V3 kit on Illumina HiSeq2000, with 100-bp paired-end reads. SNVs observed in any of the primary tumors or cfDNA samples studied by WES were targeted using a capture sequencing panel at all intermediate time points.

  Dataset EGAD00001003803

• Security Overview

  Security Overview The European Genome-phenome Archive (EGA) houses consented human data under controlled access. Access decisions are handled by the relevant Data Access Committee (DAC), which autonomously manages requests through the DAC Portal. This document provides an overview of EGA’s practices in ensuring the security of data stored at EGA. As security is a prime concern of the EGA, the EGA is a member of the Global Alliance for Genomics and Health (GA4GH) Data Security work stream. The EGA contributes and helps develop the recommendations outlined the GA4GH Security Technology Infrastructure document, which defines guidelines, best practices, and standards for building and operating an infrastructure that promotes responsible data sharing in accordance with the GA4GH Privacy and Security Policy. Explore the EGA dataflow to gain deeper insights! Accessing data in the EGA involves several steps. First, users need to create an EGA account. Once logged in, they can request access to data controlled by a DAC through the EGA website (see documentation). The DAC oversees these requests through the DAC Portal, and if approved, grants the necessary permissions to the user's EGA account, allowing them to access and download all relevant data and metadata for the requested dataset(s). The key points of EGA security strategy are: 1 Regular Risk Assessment The EGA regularly identifies and assesses risk related to the following: Breach of confidentiality,Breach of privacy or autonomy,Malicious or accidental corruption or destruction of data archived at EGA,Disruption of services provided by the EGA. 2 Risk mitigation The EGA implements and maintains safeguards to minimise the risks identified above in accordance with the 6 control objectives listed in Appendix 1 and outlined in the GA4GH Security and Infrastructure document.If a breach is discovered, the EGA applies a defined protocol to minimise damage. 3 Identity and authorisation management The EGA authenticates the identity of individuals or software accessing controlled access data held at the EGA.The EGA ensures an appropriate level of assurance (LoA) is applied to the identity consistent with the risk associated with that individual, such as multi-factor authentication for DACs.The EGA provides the minimum access rights and privileges consistent with the user’s identity, allowing access consistent with the GA4GH Privacy and Security Policy, as determined by the appropriate DAC. 4 Audit Logs The EGA maintains a set of logs recording: Changes to user access rights,Data access requests,Resource usage. 5 Cryptography, communication security, and data integrity The EGA ensures data transmission integrity using a hash function.All data transmitted to or from the EGA is end-to-end encrypted.All data at EGA is stored using strong encryption.Encryption keys are not stored in the same system as the encrypted data.All data archived at EGA must be accompanied by a signed submission statement ensuring appropriate consent or ethical approval has been obtained, and is in accordance with all applicable laws and regulations. The EGA has a defined protocol defining the response in the event of a security breach, and is continuing to work with the GA4GH Data Security Work Stream to help define best practice and associated standards for breach responses. Appendix 1 GA4GH Control Objectives Control Objective 1: Implement technology safeguards to minimise the risk of unauthorised access, use, or disclosure of confidential and private data.Control Objective 2: Implement technology safeguards to minimise the risk of discovery, access, and use of individuals’ clinical and genomic data, and individual identities, other than as authorised by applicable jurisdictional law, institutional policy, and individual consents.Control Objective 3: Implement technology safeguards to minimise the risk of accidental or malicious corruption or destruction of data.Control Objective 4: Implement technology safeguards to minimise the risk of disruption, degradation, and interruption of services enabling access to data.Control Objective 5: Implement technology safeguards to minimise the risk of potential security attacks and misuse of authorised accesses and privileges.Control Objective 6: Implement technology safeguards to promptly detect the failure to attain the above control objectives and to respond with proper countermeasures.Appendix 2Refer to the document below to learn more about EGA long-term data preservation policy and procedures at EMBL-EBI.Long-term data preservation

  Documentation about/security

• Privacy Notice for the Account User

  Privacy Notice for EGA User Account 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 you: Name Email address Title/Position Organisation Organisational affiliation Username and password (to authenticate access to the system) IP Address (for anonymous usage statistics) We process your personal data: to provide you with the authenticated access to the EGA service (opening and managing submission and distribution account), to publicly publish some aggregate data to facilitate scientific research (e.g. number of accounts, geographic distribution), to better understand the needs of the users and to guide future improvements of the service, to create anonymous usage statistics. If you do not provide us with your personal data we will not be able to open the user account and offer you our services or we will only provide you a subset of functionalities available within the service. 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 (for all user account data), Requested dataset Data access committee – DAC will have access to the name, email, organization, affiliation, title/position of the distribution user account, using it for their own purpose of granting access to their datasets. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? Distribution user account data are in the process of granting access disclosed to dataset(s) DAC, which might be a recipient in countries outside of the European Economic Area. Insofar as the second joint controller may be subject to GDPR, data transfer to and from the first joint controller (EMBL-EBI) is necessary for important reasons of public interest embedded in the aims of the EMBL and justified in the Article 9(4) of IP 68 (equivalent to Article 49(1)(d) of GDPR) read in conjunction with EMBL`s 1973 establishing agreement and Article 179(2) of the Treaty on the Functioning of the European Union. 6. How long do we keep your personal data? All data are stored for as long as you have the account open. Thereafter the storage is prolonged for as long as our service is live, even if you stop using our services. This prolongation is necessary for further scientific research, to ensure legal compliance and security and to facilitate internal and external audits it 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-user-account

• National Institute of Neurological Disorders and Stroke (NINDS) Parkinson's Disease

  This study utilized the well characterized collection of North American Caucasians with Parkinson's disease, and neurologically normal controls from the sample population which are banked in the National Institute of Neurological Disorders and Stroke (NINDS Repository) collection. Two sub-studies are included, in sub-study NINDS-Genome-Wide Genotyping in Parkinson's Disease, genome-wide, single nucleotide polymorphism (SNP) genotyping of these publicly available samples was originally done in 267 Parkinson's disease patients and 270 controls, and this has been extended to include genome wide genotyping in 939 Parkinson's disease cases and 802 controls; in sub-study NINDS-Exome Sequencing in Parkinson's Disease, genome wide exome DNA sequencing was done in 618 Parkinson's disease samples deposited in Coriell NINDS repository. The DNA comes from a mixture of blood, and from cell lines (lymphoblast cell lines) derived from blood. The GWAS data and exome sequencing data was generated and provided by the laboratory of Neurogenetics lead by Dr. Andrew Singleton, NIA, and Dr. John Hardy, a former chief at NIA, NIH. The NINDS Parkinson's Disease Cohort study is utilized in the following dbGaP individual studies. To view genotypes, whole exome sequencing, and derived variables collected in these individual studies, please click on the following individual studies below or in the "Sub-studies" box located on the right hand side of this top-level study page phs001172 NINDS Parkinson's Disease Cohort study. phs000089 PD GWAS phs001103 PD Exome

  Study phs001172

• Follow-up of Ovarian Cancer Genetic Association and Interaction Studies (FOCI)

  (Excerpted/paraphrased from original grant application): FOCI seeks to expand our understanding of epithelial ovarian cancer through a coordinated and comprehensive approach. Project 1 will focus on discovery, expansion, and replication. By pooling GWAS, we expect to identify new associations and achieve independent replication, explore whether there are risk variants specific for histologic subtypes, and evaluate structural polymorphisms - copy number variants - as risk factors. Finally, Project 1 will leverage the GWAS data to correlate DNA variants with a new endpoint - survival. Project 2 will focus on biological studies designed to help inform interpretation of findings from Project 1. This will include efforts to identify the functional consequences of variants and improve understanding of biological mechanisms. Project 3 will include epidemiologic studies of gene by gene interaction, gene by environment interaction, and development of risk prediction models. The collective effort builds upon the strengths and history of collaboration inherent in the Ovarian Cancer Association Consortium (OCAC), a multidisciplinary group comprised of epidemiologists, genetic epidemiologists, statistical geneticists, molecular and cell biologists and clinicians that was formed in 2005. The FOCI Cohort is utilized in the following dbGaP sub-studies. To view genotypes, other molecular data, and derived variables collected in these sub-studies, please click on the following sub-studies below or in the "Sub-studies" box located on the right hand side of this top-level study page phs001133 FOCI Cohort. phs001131 Affymetrix Exome Chip phs001132 GWAS Meta Analysis phs001142 Mayo Omni Express phs001150 Mayo 2 5M

  Study phs001133

• Targeted and shallow whole genome sequencing identifies therapeutic opportunities in p53abn endometrial cancers

  Purpose: Shallow whole genome sequencing (sWGS) can detect copy number (CN) aberrations. In high-grade serous ovarian (HGSOC) sWGS identified CN signatures such as homologous recombination deficiency (HRD) to direct therapy. We applied sWGS with targeted sequencing to p53abn endometrial cancers (ECs) to identify additional prognostic stratification and therapeutic opportunities. Experimental Design: sWGS and targeted panel sequencing was performed on formalin-fixed paraffin-embedded p53abn ECs. CN alterations, mutational data and CN signatures were derived, and associations to clinicopathologic and outcomes data were assessed. Results: In 187 p53abn ECs, 5 distinct CN signatures were identified. Signature 5 was associated with BRCA1/2 CN loss with features similar to HGSOC HRD signature. 22% potential HRD cases were identified, 35 patients with signature 5, and 8 patients with BRCA1/2 somatic mutations. Signatures 3 and 4 were associated with whole genome duplication, and CCNE1, ERBB2 and MYC amplifications, with mutations in PIK3CA enriched in signature 3. We observed improved overall survival (OS) for patients with signature 2 and worse OS for signatures 1 and 3. 28% of patients had CCNE1 amplification and this subset was enriched with carcinosarcoma histotype. 34% of patients, across all histotypes, had ERBB2 amplification and/or HER2 overexpression on immunohistochemistry, which was associated with worse outcomes. Mutations in PPP2R1A (29%) and FBXW7 (16%) were among the top 5 most common mutations. Conclusions: sWGS and targeted sequencing identified therapeutic opportunities in 75% of p53abn EC patients. Further research is needed to determine the efficacy of treatments targeting these identified pathways within p53abn ECs.

  Study EGAS00001007661

• Coding and regulatory somatic profiling of triple-negative breast cancer in Sub-Saharan African patients

  The burden of triple-negative breast cancer (TNBC) may be shaped by genetic factors, particularly inherited and somatic mutation profiles. However, data on this topic remain limited, especially for the African continent, where a higher TNBC incidence is observed. In the age of precision medicine, cataloguing TNBC diversity in African patients becomes imperative. We performed whole exome sequencing, including untranslated regions, on 30 samples from Angola and Cape Verde, which allowed to ascertain on potential regulatory mutations in TNBC for the first time. A high somatic burden was observed for the African cohort, with 86% of variants being so far unreported. Recurring to predictive functional algorithms, 17% of the somatic single nucleotide variants were predicted to be deleterious at the protein level, and 20% overlapped with candidate cis-regulatory elements controlling gene expression. Several of these somatic functionally-impactful mutations and copy number variation (mainly in 1q, 8q, 6 and 10p) occur in known BC- and all cancer-driver genes, enriched for several cancer mechanisms, including response to radiation and related DNA repair mechanisms. TP53 is the top of these known BC-driver genes, but our results identified possible novel TNBC driver genes that may play a main role in the African context, as TTN, CEACAM7, DEFB132, COPZ2 and GAS1. These findings emphasize the need to expand cancer omics screenings across the African continent, the region of the globe with highest genomic diversity, accelerating the discovery of new somatic mutations and cancer-related pathways.

  Study EGAS50000001013

• 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