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

in 17.45 milliseconds.

• Genomic determinants of therapy response in ETV6-RUNX1 leukemia

  Study EGAS00001007066

• Genetic Basis of Early Onset Bicuspid Aortic Valve Disease

  The study protocol was approved by the Committee for the Protection of Human Subjects at the University of Texas Health Science Center at Houston (HSC-MS-11-0185). Study recruitment began on July 1, 2017, and concluded on March 30, 2022. After written informed consent, we enrolled probands with early onset BAV disease (EBAV), which we defined as individuals with BAV who were under the age of 30 at the time of first clinical event. Clinical events were defined as aortic replacement, aortic valve surgery, aortic dissection, moderate or severe aortic stenosis or aortic regurgitation, large aneurysm (Z > 4.5), or intervention for BAV-related conditions. Those with hypoplastic left heart, known genetic mutations, genetic syndromes, or complex congenital heart disease were excluded. Samples were collected and genotyped as previously reported. For comparison, we analyzed a cohort of older individuals of European ancestry with sporadic BAV disease selected from the International BAV Consortium (BAVGWAS). Phenotypes were derived from record review with confirmation of image data whenever possible [25-26]. The computational pipeline for CNV analysis of Illumina single nucleotide polymorphism (SNP) array data included three independent CNV detection algorithms.GenomeStudio was used to exclude samples with indeterminate sex or more than 5% missing genotypes, and single nucleotide polymorphisms (SNPs) with GenTrain = 0. Principal component analysis was used to remove outliers that did not cluster with European ancestry. Prior to CNV analysis, each dataset was trimmed by selecting a common set of 650,000 SNPs that were genotyped on each of the microarrays used in this study.Three independent algorithms (PennCNV, cnvPartition, and QuantiSNP) were used to generate CNV calls and sample-level quality statistics from SNP intensity data. PennCNV and QuantiSNP were run on Unix clusters and cnvPartition data were exported from GenomeStudio. The analysis was run using default configurations. PennCNV was used to generate QC data and remove CNV calls that intersect with polymorphic genomic regions. Samples that met any of the following criteria were excluded, standard deviation of the LogR ratio (obtained from PennCNV) > 0.35 or number of CNVs > 2 standard deviations above the mean for each data set. CNV calls less than 20 Kilobases in length and/or spanned by fewer than 6 probes were excluded. The overlap function for rare CNVs in PLINK was used to construct CNV regions (CNVRs) after adjacent regions were merged using PennCNV. LogR ratio (LRR) and B allele frequency (BAF) data at CNVRs and calls of interest were visualized in GenomeStudio for validation. For segregation analysis, GenomeStudio was used to determine the presence of CNVs in relatives.A total of 22,014 unselected control Illumina Genotypes obtained from the Database of Genotypes and Phenotypes were analyzed using identical methods (S1 Table). The Wisconsin Longitudinal Study (WLS) includes data on a cohort of 10,300 individuals who graduated from Wisconsin high schools in 1957. The Health and Retirement Study (HRS) includes data on 37,000 individuals aged 50 above from 23,000 households across the United States. Principal component analysis was used to select European ancestry genotypes from these datasets for analysis. Datasets were paired for case-control analysis based on the concordance of log-transformed sample-level quality control statistics (number of CNV calls and standard deviation of logR ratios). Chi-squared or Fisher exact tests were used to compare CNV frequencies in cases and controls.Rare CNV functions in PLINK (v1.7) were used to perform permutation-based burden tests or gene set-based enrichment tests. Case control burden tests were restricted to CNVs that were longer than 110 Kb and less than 0.1% in frequency. CNV overlap functions in PLINK were used to identify rare CNVs that intersect between datasets or involve specific BAV or CHD genes . The list of candidate genes included 190 CHD genes that have strong cumulative evidence to cause BAV or related congenital malformations from human or animal model data. Genome Reference Consortium Human Build 37 was used for CNV annotation [34].

  Study phs003705

• NHLBI TOPMed - NHGRI CCDG: The BioMe Biobank at Mount Sinai

  The IPM BioMe Biobank, founded in September 2007, is an ongoing, broadly-consented electronic health record (EHR)-linked clinical care biobank that enrolls participants non-selectively from the Mount Sinai Medical Center patient population. BioMe currently comprises >42,000 participants from diverse ancestries, characterized by a broad spectrum of longitudinal biomedical traits. Participants are enrolled through an opt-in process and consent to be followed throughout their clinical care (past, present, and future) in real-time, allowing us to integrate their genomic information with their EHRs for discovery research and clinical care implementation. BioMe participants consent for recall, based on their genotype and/or phenotype, permitting in-depth follow-up and functional studies for selected participants at any time. Phenotypic and genomic data are stored in a secure database and made available to investigators, contingent on approval by the BioMe Governing Board. BioMe uses a "data-broker" system to protect confidentiality. Ancestral diversity - BioMe participants represent a broad racial, ethnic and socioeconomic diversity with a distinct and population-specific disease burden. Specifically, BioMe participants are of African (AA), Hispanic/Latino (HL), European (EA) and other/mixed ancestry. BioMe participants are predominantly of African (AA, 24%), Hispanic/Latino (HL, 35%), European (EA, 32%), and other ancestry (OA, 10%). Participants who self-identify as Hispanic/Latino further report to be of Puerto Rican (39%), Dominican (23%), Central/South American (17%), Mexican (5%) or other Hispanic (16%) ancestry. More than 40% of European ancestry participants are genetically determined to be of Ashkenazi Jewish ancestry. With this broad ancestral diversity, BioMe is uniquely positioned to examine the impact of demographic and evolutionary forces that have shaped common disease risk. Phenotypes available in BioMe - BioMe has a high-quality and validated set of fully implemented clinical phenotype data that has been culled by a multi-disciplinary team of experienced investigators, clinicians, information technologists, data-managers, and programmers who apply advanced medical informatics and data mining tools to extract and harmonize EHRs. BioMe, as a cohort, offers a great versatility for designing nested case-control sample-sets, particularly for studying longitudinal traits and co-morbidity in disease burden. Biomedical and clinical outcomes: The BioMe Biobank is linked to Mount Sinai's system-wide Epic EHR, which captures a full spectrum of biomedical phenotypes, including clinical outcomes, covariate and exposure data from past, present and future health care encounters. As such, the BioMe Biobank has a longitudinal design as participants consent to make all of their EHR data from past (dating back as far as 2003), present and future inpatient or outpatient encounters available for research, without restriction. The median number of outpatient encounters is 21 per participant, reflecting predominant enrollment of participants with common chronic conditions from primary care facilities. Environmental data: The clinical and EHR information is complemented by detailed demographic and lifestyle information, including ancestry, residence history, country of origin, personal and familial medical history, education, socio-economic status, physical activity, smoking, dietary habits, alcohol intake, and body weight history, which is collected in a systematic manner by interview-based questionnaire at time of enrollment. The IPM BioMe Biobank contributed ~10,600 DNA samples for whole genome sequencing to the TOPMed program. Samples were selected for the Coronary Artery Disease (CAD) and the Chronic Obstructive Pulmonary Disease (COPD) working groups. Using a Case-Definition-Algorithm (CDA), we identified ~4,100 individuals with CAD (~50% women) and ~3,000 individuals as controls (65% women). In addition, we identified ~800 individuals with COPD (62% women) and 1800 individuals as controls (72% women). Another 600 BioMe participants with Atrial Fibrillation, all of African ancestry, were included.

  Study phs001644

• Sporadic ALS Australia Systems Genomics Consortium (SALSA-SGC)

  In 2016 we established the Sporadic ALS Australia Systems Genomics Consortium (SALSA-SGC) funded by the Ice Bucket Challenge Grant administered by the Motor Neurone Disease Research Institute of Australia. The goals of the SALSA-SGC are to collect biological samples from clinics across Australia with matched in depth clinical and self-report phenotypes and to generate multiple levels of genetic and genomic data. In this first data generation exercise of the SALSA-SGC the majority of the samples were collected prior to the formal establishment of SALSA-SGC from clinics across Australia.Briefly, the cohort includes the University of Sydney’s Australian Motor Neuron Disease DNA Bank (MND Bank) cohort recruited April 2000 to June 2011), with study protocol approved by the Sydney South West Area Health Service Human Research Ethics Committee (HREC). Cases were recruited from around Australia via state-based MND associations with diagnosis verified by a neurologist. The remainder of the cases were recruited from clinics across Australia between 2015 and 2017 under HREC approvals from Royal Brisbane and Women’s Hospital, Macquarie University Multidisciplinary Motor Neurone Disease Clinic,  Calvary Health Care Bethlehem in Melbourne , Fiona Stanley Hospital in Perth, and from 2016 under HREC approvals at each site for the sporadic ALS Australia Systems Genomics Consortium (SALSA-SGC). The ALS cases were diagnosed with definite or probable ALS according to the revised El Escorial criteria. Some controls were recruited as either partners or friends of patients, healthy individuals free of neuromuscular diseases. We are providing GWAS and MWAS data in this dataset. Individual level GWAS data were generated using Illumina Infinium CoreExome-24 version 1.1 chips for N= 846 cases and N=665 controls. Individual MWAS data was generated using the Illumina Human methylation 450K array for N=782 cases and N=613 controls. There 1315 individuals where GWAS and MWAS data has been generated and is available. Further information on these data sets can be found: Paper 1: Restuadi, R, Garton, FC, Benyamin, B, Lin, T, et al. Amyotrophic Lateral Sclerosis Genetic Correlation with Cognitive Performance, educational attainment and schizophrenia: evidence from polygenic risk score analysis. (submitted) Paper 2: Nabais, MF, Lin, T, Benyamin, B et al. Significant out-of-sample classification from methylation profile scoring for amyotrophic lateral sclerosis. 2020. NPJ genomic medicine. 5(10). Files provided in this submission include: GWAS: This folder contains QCed genotype for the Australian ALS case-control cohort. Contains PLINK files for genotyping data (not imputed yet). The individuals selected here have: good consistency on phenotype data ethics approval registered as part of sporadic ALS studies unrelated by GRM cut-off 0.05 No ancestry QC yet MWAS: This folder contains the IDAT and post-QC normalized DNAm (beta) for the Australian ALS case-control cohort. 2019_AUS_ALS_PCTG_DNAm.tar.gz - IDATS for 1315 individuals analyzed in the MWAS study normalized_beta_values - Binary files (created with the OSCA software) containing information on the individuals, probes and the DNAm (beta) values obtained after QC phenotype_file - contains all the covariates analysed in the MWAS including: case-control status, coded 0 = Control and 1 = ALS, predicted age, predicted cell-type proportions, predicted smoking scores, slide and chip position and sex Important Notes: The DNAm data were normalized together with samples that were not part of this ALS case/control study and thus, the normalization procedure may not be 100% reproducible using only the IDAT files uploaded here. Summary data has been made publicly available and can be accessed directly: Data collection and sample processing were performed at several clinics across Australia. Genotyping and DNA methylation arrays were performed by the Human Studies Unit, at the Institute for Molecular Bioscience (University of Queensland). Quality control of the genotypic, phenotypic and DNA methylation data was done by the Program of Complex Traits Genomics, at the Institute for Molecular Bioscience (University of Queensland).

  Study phs002068

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• What is a DAC?

  What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions.  You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks.  Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, 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! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

  Documentation access/data-access-committee/what-is-dac

• A body map of somatic mutagenesis in morphologically normal human tissues (WES)

  Study EGAS00001005459

• DAC for the study of response to EGFR Blockade in Colorectal Cancer

  Dac EGAC00001000360

• DAC Genomic and transcriptomic profiling of signalling networks in follicular lymphoma

  Dac EGAC00001000577

• DAC for study: Frequent mutation of the FOXA1 untranslated region in prostate cancer

  Dac EGAC00001000962