543 results for "Daguerre+Crater+floor+materials+origin+nearby+crater+Chinese+name"

in 9.18 milliseconds.

• WES_of_adult_intellectual_disabilities_with_co_morbid_psychiatric_disorders

  ost adults with intellectual disabilities (ID) do not undergo genetic diagnostic investigation as part of their clinical care and have 'missed the boat' with regard to the WES and WGS genetic testing that is now being provided for children with ID. There is a dramatically increased risk of psychistric disorders in adults with ID, e.g. the risk of psychoses is 10X higher than in the general population. It remains an open question as to how much of adult ID is genetic in origin and how similar the genetic forms of adult ID are to those being diagnosed in children, in part due to survivor bias. There is also the opportunity to identify adults with treatable forms of ID, of which over 80 have been described, thus improving their clinical management. Furthermore, analysis of medical records of adults with genetic forms of ID can help to characterise the 'natural history' of individual disorders, resulting in more accurate prognoses for diagnosed children and identifying opportunities for improved management and possibly therapeutic intervention (e.g. optimal anti-epileptic therapy). Here we propose to exome sequence (to ~50X coverage) 200 adults with ID and co-morbid psychiatric disorders. This cohort has previously been assayed with chromosomal microarrays (Wolfe et al 2017 EJHG, 25, 66–72) identifying a diagnostic yield of ~11% which is comparable to the CNV diagnostic yield in various child ID cohorts (10-15%). The authors observed no substantive biases in diagnostic yield between different psychiatric diagnostic classes. The WES data will be analysed using the diagnostic workflows developed in the DDD study to ensure comparability between child and adult ID datasets. This study is intended as a pilot study to demonstrate the value of WES in adults with ID. This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/

  Study EGAS00001002962

• Distinct evolutionary trajectories of primary high grade serous ovarian cancers revealed through spatial mutational profiling

  High-grade serous ovarian cancer (HGSC) is characterized by poor outcome, often attributed to emergence of treatment-resistant sub-clones. We sought to measure the degree of genomic diversity within primary, untreated HGSC to examine the natural state of tumor evolution prior to therapy. We performed exome sequencing, copy number analysis, targeted amplicon deep sequencing and gene expression profiling on thirty-one spatially and temporally separated HGSC tumor specimens (six patients) including ovarian masses, distant metastases, and fallopian tube lesions. We found widespread intra-tumoral variation in mutation, copy number, and gene expression profiles, with key driver alterations in genes present in only a subset of samples (e.g. PIK3CA, CTNNB1, NF1). On average, only 51.5% of mutations were present in every sample of a given case (range: 10.2% to 91.4%), with TP53 as the only somatic mutation consistently present in all samples. Complex segmental aneuploidies, such as whole genome doubling, were present in a subset of samples from the same individual, with divergent copy number changes segregating independently of point mutation acquisition. Reconstruction of evolutionary histories showed one patient with mixed HGSC and endometrioid histology with common etiologic origin in the fallopian tube and subsequent selection of different driver mutations in the histologically distinct samples. In this patient, we observed mixed cell populations in the early fallopian tube lesion, indicating diversity arises at early stages of tumorigenesis. Our results reveal that HGSC exhibit highly individual evolutionary trajectories and diverse genomic tapestries prior to therapy, exposing an essential biological characteristic to inform future design of personalized therapeutic solutions and investigation of drug resistance mechanisms.

  Dataset EGAD00001000974

• Distinct evolutionary trajectories of primary high grade serous ovarian cancers revealed through spatial mutational profiling

  High-grade serous ovarian cancer (HGSC) is characterized by poor outcome, often attributed to the emergence of treatment-resistant subclones. We sought to measure the degree of genomic diversity within primary, untreated HGSCs to examine the natural state of tumour evolution prior to therapy. We performed exome sequencing, copy number analysis, targeted amplicon deep sequencing and gene expression profiling on 31 spatially and temporally separated HGSC tumour specimens (six patients), including ovarian masses, distant metastases and fallopian tube lesions. We found widespread intratumoural variation in mutation, copy number and gene expression profiles, with key driver alterations in genes present in only a subset of samples (eg PIK3CA, CTNNB1, NF1). On average, only 51.5% of mutations were present in every sample of a given case (range 10.2 to 91.4%), with TP53 as the only somatic mutation consistently present in all samples. Complex segmental aneuploidies, such as whole-genome doubling, were present in a subset of samples from the same individual, with divergent copy number changes segregating independently of point mutation acquisition. Reconstruction of evolutionary histories showed one patient with mixed HGSC and endometrioid histology, with common aetiologic origin in the fallopian tube and subsequent selection of different driver mutations in the histologically distinct samples. In this patient, we observed mixed cell populations in the early fallopian tube lesion, indicating that diversity arises at early stages of tumourigenesis. Our results revealed that HGSCs exhibit highly individual evolutionary trajectories and diverse genomic tapestries prior to therapy, exposing an essential biological characteristic to inform future design of personalized therapeutic solutions and investigation of drug-resistance mechanisms

  Dataset EGAD00001000669

• Single cell characterization of T-cell lymphoma: RNA (2025-07-31)

  Lymphomas are types of blood cancer derived from lymphocytes, and can be classified into two main categories, Hodgkin's lymphomas (HL) and non-Hodgkin lymphomas (NHL). T-cell lymphoma is a type of NHL that develops from T lymphocytes and accounts for 10-15% of total NHL cases. As a rare disease, T-cell lymphoma is functionally, pathologically, and clinically complex and heterogeneous. The 2016 revision of the WHO classification has listed 29 subtypes of mature T/NK-cell neoplasms, among which over 25 are T lymphocyte in origin. These subtypes of T-cell lymphomas have different biological behaviours and clinical prognosis. Clinically, T-cell lymphoma ranges from indolent (slow-growing) to aggressive (fast-growing and spreading) disease. According to the guideline booklet provided by the Lymphoma Research Foundation (https://lymphoma.org/aboutlymphoma/nhl/), indolent T-cell lymphoma subtypes include adult T-cell leukaemia/lymphoma (ATLL), cutaneous T-cell lymphoma (CTCL), and mycosis fungoides (MF), while the aggressive subtypes include anaplastic large cell lymphoma (ALCL), angioimmunoblastic T-cell lymphoma (AITL), peripheral T-cell lymphoma (PTCL), and T lymphoblastic lymphoma (TLBL). PTCL and ALCL represent the most common subtypes of aggressive T-cell lymphoma whereas TLBL is a rare and aggressive subtype mostly diagnosed in children. In this study, we will use single cell RNA sequencing and single cell multiomic methods three aggressive T-cell lymphoma subtypes (ALCL, PTCL and TLBL) and try to gain a deeper insight into the genotypic and phenotypic features of these T-cell lymphomas. . This dataset contains all the data available for this study on 2025-07-31.

  Dataset EGAD00001015669

• Exome sequencing reveals pathogenic variants in known and novel candidate genes for severe sperm motility disorders

  STUDY QUESTION: What are the causative genetic variants in patients with male infertility due to severe sperm motility disorders? SUMMARY ANSWER: We identified high confidence disease-causing variants in multiple genes previously associated with severe sperm motility disorders in 9 out of 21 patients (43%). We also identified variants in novel candidate genes in 8 additional patients (38%). WHAT IS KNOWN ALREADY: Severe sperm motility disorders are a form of male infertility characterised by vital, but immotile sperm often in combination with a spectrum of structural abnormalities of the sperm flagellum. Examples of this spectrum of disorders include dysplasia of the fibrous sheath / multiple morphological abnormalities of the sperm flagella (DFS-MMAF) and severe forms of asthenozoospermia associated to non-specific structural defects. These disorders frequently recur in families and may include chronic respiratory disease. As such, genetic causes are suspected and many genes have recently been reported. Currently, depending on the clinical sub-categorisation, up to 50% of causality in patients with severe sperm motility disorders can be explained by pathogenic variants in at least 21 known genes. STUDY DESIGN, SIZE, DURATION: We performed exome sequencing in patients with severe sperm motility disorders from two different clinics, aiming to identify the underlying genetic defects and establishing a diagnostic yield in both. PARTICIPANTS/MATERIALS, SETTING, METHOD: Two groups of infertile men, one from Argentina (n= 9) and one from Australia (n=12), with clinically defined sperm motility disorders were included. All patients in the Argentine cohort were diagnosed with DFS-MMAF, based on transmission electron microscopy. Exome sequencing was performed in all 21 patients and variants with an allele frequency of <1% in the gnomAD population were prioritised and interpreted. MAIN RESULTS AND ROLE OF CHANCE: In 9/21 patients (43%), we identified pathogenic variants in known sperm motility disorder genes: CFAP43 (3 patients); CFAP44 (2 patients), QRICH2 (2 patients), DNAH1 (1 patient) and DNAH6 (1 patient). The diagnostic rate did not differ markedly between the Argentinian and the Australian cohort (44% and 42%, respectively). Furthermore, we identified patients with variants in the novel candidate sperm motility genes CFAP58, DNAH12, DRC1, MDC1, PACRG, SSPL2C and TPTE2. One patient presented with two possibly damaging variants in four candidate genes and it remains unclear which variants were responsible for the severe sperm motility defect in this patient. LIMITATIONS, REASONS FOR CAUTION: In this study, we described patients with potential bi-allelic variants in known and novel candidate genes for severe sperm motility disorders. Due to unavailability of parental DNA, we have not assessed de novo or maternally inherited dominant variants and could not phase the mutations to establish in all cases that the mutations occur on both alleles. WIDER IMPLICATIONS OF THE FINDINGS: Our results confirm an important role for five known genes for sperm motility and we demonstrate that exome sequencing is an effective method to diagnose patients with severe sperm motility defects (9/21 diagnosed; 43%). Furthermore, our analysis revealed seven novel candidate genes for severe sperm motility disorders. Genome-wide sequencing of additional patient cohorts and re-analysis of exome data of currently unsolved cases may reveal additional variants in these novel candidate genes.

  Study EGAS00001005018

• How to use the EGA search box

  Tips on how to search Tip 1: Use simple and clear keywords No matter what you are searching: a study, a dataset or a committee; the search will look recursively in all the fields of all the entities in the database. Thus, there is no need to specify which type of data you are looking for. Try to use single and specific words and avoid long and complex expressions. Try it out: cancer rna-seq instead of cancer studies using RNA-seq. Tip 2: Narrow your results using search operators Search operators give you more control over the results. They manage the way keywords are used to restrict the search. By default, the search engine applies an OR operator when a space is inserted between two words. Include AND (capitalised) between the keywords in your search in order to show only pages containing both terms. Try it out: Search all the studies based on transcriptomic data, including those ones that use RNA sequencing to obtain this data. Tip 3: Do not worry about details The search engine automatically checks for the most common spelling mistakes of given words and suggests the use of the correct version. It also ignores capital letters and most punctuation so none of these mistakes will hamper the accuracy of your search. Besides, when using a combination of words, the search engine will suggest similar combinations with a higher number of results. Tip 4: Use words that are likely to appear within the text Unfortunately, our search engine is not able to interpret words yet. Therefore, words which do not appear in the body text will not return any result despite them denoting a group of present terms. For instance, if we are looking for studies focused on neurological diseases, using neurological as a keyword would not be the best option. Instead, you should use the name of each neurological disease such as bipolar disorder, schizophrenia or depression. In the same fashion, incomplete words do not return any result. Please include an asterisk (*) before and/or after the incomplete word in order to allow for partial matching. Try it out: canc* instead of canc(without wildcard). Also you can try out *oma, or even *geneti* Tip 5: Narrow down your search by filtering the results You can filter the results by the following options: general, study, and dataset. Under these categories, you will find more sub-filters to refine your search. Make sure that you click on Apply in order to filter the results. You can clear the filtering anytime. Advanced Searches Additional example queries: Search for DUO:0000005 and word lung example query Or write: DUO:0000005 AND lung Search for an exome sequencing study in dbGaP example query Or write: study_type: "exome sequencing" AND repository:dbGaP Search for an exome sequencing study in EGA example query Or write: study_type: "exome sequencing" AND repository:ega Search for a dataset that is at the EGA beacon and with type "Whole genome sequencing" and with number of samples between 100 and 2000 and with technology "Illumina HiSeq 2000" example query Or write: is_in_beacon:true AND dataset_types:"Whole genome sequencing" AND samples:[100 TO 2000] AND dataset_technologies:"Illumina HiSeq 2000" Search for PMIDS example query Or write: pmids:32025007

  Documentation discovery/metadata/search-box

• Copy-Number Analysis of Understudied Black Women Ovarian Cancers

  Two general types of genetic alterations drive cancer progression: mutations and copy number alterations (CNAs). With the exception of p53, single nucleotide variant mutations (here, simply "mutations") are not drivers of 80% of tumors within the most frequent and deadly histotype of ovarian cancer: serous ovarian cancer (SOC). Rather, CNAs are more prevalent in SOC than any other cancer type studied by phs000178 The Cancer Genome Atlas (TCGA). Fully two-thirds of genes are altered by CNAs in the average SOC. Bioinformatic methods have shown that these CNAs modulate specific molecular pathways, such as autophagy, and this finding enabled effective pathway-targeted therapies1. Unfortunately, TCGA ovarian cancer data lacks racial diversity. Only 6% of SOC tumors (n=32) studied are from African origin. Black women diagnosed with ovarian cancer are more likely to die from their disease than white women. Five-year survival after diagnosis is 31% among blacks versus 42% among whites, and this disparity is seen in every age group and tumor stage distribution. Dr. Kelemen examined data from 365 white and 95 black ovarian cancer patients from the Hollings Cancer Center (HCC) Cancer Registry between 2000 and 2015 and found that black women had an 81% higher risk of death after diagnosis compared to white women (HR 1.81, 95% CI 1.35-2.43), independent of diagnosis center (98% were treated at HCC but half were diagnosed elsewhere), tumor stage, histology, extent of residual tumor remaining following surgery, insurance status, smoking, type of treatment for ovarian cancer, and age-adjusted Charlson comorbidity index. This disparity remained even when restricted to women who received the standard of care, surgery-chemotherapy sequence (HR 1.79, 95% CI 1.10-2.89). Despite receiving the same treatment, black race was still associated with inferior survival. A similar disparity has been reported by others, indicating that the HCC experience is representative of national data. Here, an additional set of high-grade serous ovarian cancer primary tumors were acquired from biorepositories with a focus on expanding data originating from African American women. Data were analyzed for copy-number alterations using exome sequencing and control-FREEC software.

  Study phs002313

• Identifying transcriptional programs underlying anti-EGFR small molecule response and resistance with TraCe-seq

  Genetic and non-genetic heterogeneity within cancer cell populations represents a major challenge to anti-cancer therapies. We currently lack robust methods to determine how pre-existing and adaptive features affect cellular responses to therapies. Here, by conducting clonal fitness mapping and transcriptional characterization using expressed barcodes and single-cell RNA-sequencing, we have developed TraCe-seq, a method that captures at clonal resolution the origin, fate, and differential early adaptive transcriptional programs of cells in a complex population in response to distinct treatments. We used TraCe-seq to benchmark how next-generation dual EGFR inhibitors-degraders compare to standard EGFR kinase inhibitors in EGFR-mutant lung cancer cells. To QC the TraCe-seq strategy, single-cell RNA-seq libraries were generated from a variety of human cancer cell lines transduced with the TraCe-seq library to validate the TraCe-seq strategy. Specifically, 5 different cell lines (PC9, MCF-10A, MDA-MB-231, NCI-H358, and NCI-H1373) were each transduced with a unique TraCe-seq barcode. The transduced cells were selected with puromycin only, dissociated to single cell suspensions, and then mixed together. The complex mixture of the 5 cell lines was profiled by 10X scRNA-seq. Furthermore, transduced NCI-H1373 cells were sorted by FACS to enrich for the top 50% of eGFP positive cells, and sorted cells were cultured briefly and used to construct scRNA-seq libraries and profiled by 10x scRNA-seq. To carry out the full TraCe-seq experiment, ~600 PC9 cells carrying unique TraCe-seq barcodes were expanded over 12 doublings to establish the barcoded population. A subset of the barcoded PC9 population was used to generate scRNA-seq libraries and profiled by 10x scRNA-seq prior to treatment to establish a baseline transcription profile for each barcoded clone. The rest of the cells were then treated for four days with 1 µM erlotinib, 1 µM GNE-069, or 1 µM GNE-104 respectively. scRNA-seq libraries were then generated form the treated cells and profiled by 10x scRNA-seq.

  Study EGAS00001005405

• Multi-omic and functional analysis for classification and treatment of sarcomas with FUS-TFCP2 or EWSR1-TFCP2 fusions(H021/INF)

  Many rare cancers are not well understood, and pathogenesis-directed therapies are often lacking, resulting in poor patient outcomes. Leveraging two (inter)national precision oncology trials that enroll large numbers of rare cancers, we investigated the clinical, histopathologic, molecular, and functional characteristics of rhabdomyosarcoma (RMS) with fusions of FUS or EWSR1 to the TFCP2 transcription factor, a recently discovered ultra-rare entity whose classification, pathogenesis, and optimal treatment are unclear. Unusually for fusion-driven sarcomas, most cases had highly rearranged genomes, including chromothripsis, and signs of defective homologous recombination DNA repair. All tumors showed extreme expression of a truncated TERT variant and the ALK receptor tyrosine kinase, which was additionally affected by intragenic deletions and aberrant splicing, resulting in the expression of shortened variants in 58% of cases. Three ALK variants were oncogenic in immortalized cells, and patient-derived tumor cells expressing two variants responded to certain ALK inhibitors. Other recurrent alterations included CDKN2A/MTAP co-deletions and mutations in PAPPA2, encoding an IGFBP5-specific proteinase, in 67% and 25% of cases, respectively. DNA methylation analysis, along with 19 other soft-tissue sarcoma classes, revealed a close relationship with undifferentiated sarcoma but not other RMS subtypes, suggesting that TFCP2-rearranged RMS is a separate entity, possibly arising from a distinct cell of origin. Expression of TFCP2 fusions in immortalized human cells blocked late myogenic differentiation and significantly induced genes that were also highly expressed in patient tumors, including ALK, TERT, and two known regulators of skeletal muscle cells, IGFBP5 and PTH1R. Genome-wide chromatin profiling demonstrated direct binding of FUS-TFCP2 to the ALK and TERT loci outside their regular promoters, which correlated with the expression of alternative transcript variants. Finally, FUS-TFCP2 inhibited the repair of DNA double-strand breaks in immortalized cells, rendering them sensitive to treatment with cisplatin. This study provides insight into the pathogenesis and therapeutic vulnerabilities of a new RMS subtype and illustrates the value of linking comprehensive molecular diagnostics and functional annotation within multicenter consortia to improve the understanding and clinical management of rare cancers.

  Study EGAS00001006939

• 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