23014 results for "ega"

in 29.23 milliseconds.

• using-ega-account

  Using your EGA account The purpose of this page is to help you access and download the data you have been granted permission to view through your EGA account. To obtain an EGA account please register here. Once your account is created, you can find details on how to manage your EGA account here. EGA access policy (New account holders please read) Access to EGA services are only provided to EGA account holders. EGA accounts are created, updated and closed upon direct instruction from the relevant DAC contact, using the EGA account management tools or through EGA Helpdesk. As part of the EGA account creation process, the EGA account holder must reset their password when instructed. Password resets are checked and verified usually within 24 business hours, during which time the EGA account is inaccessible. EGA accounts are assigned on an individual basis for the exclusive use of the registered EGA account holder; log-in details must remain private and only be used by the EGA account holder. Controlled access data files are only provided, in accordance to the permissions set by the DAC, to EGA account holders. EGA controlled access data files are encrypted prior to download and must be decrypted on the EGA account holders side. EGA account holders are provided access to the EGA download streamer to download access approved datasets and files therein. The EGA download streamer represents the primary means for the EGA account holder to download access approved datasets and files therein. EGA account holders may be provided with an EGA download account for accessing approved datasets and files therein, using FTP or Aspera in response to clearly defined technical reasons, which may restrict the use of the EGA download streamer. It is the sole responsibility of the EGA account holder to ensure full compliance to all terms and conditions of the Data Access Agreement are met once data is downloaded from the EGA. Should you move institute you must contact all Data Access Committee's contacts to update your details and, if necessary, re-apply for data access. The Data Access Agreement (DAA) is a contract made between the DAC and the EGA account holder; the EGA is not responsible for enforcing the DAA. EGA reserves the right to place EGA accounts 'onhold', pending DAC approval to re-activate, should EGA account 'misuse' be suspected. Further information Introduction to the EGA Frequently Asked Questions Subscribe to the EGA mailing list

  Documentation using-ega-account

• Using your EGA account

  Using your EGA account The purpose of this page is to help you access and download the data you have been granted permission to view through your EGA account. To obtain an EGA account please register here. Once your account is created, you can find details on how to manage your EGA account here. EGA access policy (New account holders please read) Access to EGA services are only provided to EGA account holders. EGA accounts are created, updated and closed upon direct instruction from the relevant DAC contact, using the EGA account management tools or through EGA Helpdesk. As part of the EGA account creation process, the EGA account holder must reset their password when instructed. Password resets are checked and verified usually within 24 business hours, during which time the EGA account is inaccessible. EGA accounts are assigned on an individual basis for the exclusive use of the registered EGA account holder; log-in details must remain private and only be used by the EGA account holder. Controlled access data files are only provided, in accordance to the permissions set by the DAC, to EGA account holders. EGA controlled access data files are encrypted prior to download and must be decrypted on the EGA account holders side. EGA account holders are provided access to the EGA download streamer to download access approved datasets and files therein. The EGA download streamer represents the primary means for the EGA account holder to download access approved datasets and files therein. EGA account holders may be provided with an EGA download account for accessing approved datasets and files therein, using FTP or Aspera in response to clearly defined technical reasons, which may restrict the use of the EGA download streamer. It is the sole responsibility of the EGA account holder to ensure full compliance to all terms and conditions of the Data Access Agreement are met once data is downloaded from the EGA. Should you move institute you must contact all Data Access Committee's contacts to update your details and, if necessary, re-apply for data access. The Data Access Agreement (DAA) is a contract made between the DAC and the EGA account holder; the EGA is not responsible for enforcing the DAA. EGA reserves the right to place EGA accounts 'onhold', pending DAC approval to re-activate, should EGA account 'misuse' be suspected. Further information Introduction to the EGA Frequently Asked Questions Subscribe to the EGA mailing list

  Documentation download/using_ega_account

• EGA FUSE Client

  EGA FUSE Client What is EGA FUSE Client? The EGA FUSE Client is a Java Native Runtime (JNR) based Filesystem in Userspace (FUSE) client that allows users to access authorised EGA files by presenting them in a virtual directory. This means that users can use authorised EGA files like regular files without having to download them first. The EGA FUSE Client is a useful tool for researchers who need to access and work with large amounts of EGA data. Why use EGA FUSE Client? The EGA FUSE Client provides several benefits for researchers working with EGA data: Efficient use of storage space: With the EGA FUSE Client, users can access authorised EGA files without having to download them first. This means that users can save storage space on their local machines. Faster access to data: Since users can access authorised EGA files directly through the EGA FUSE Client, they can work with the data more quickly than if they had to download the files first. Simplified workflow: The EGA FUSE Client presents authorised EGA files in a virtual directory, allowing users to work with the files like regular files. This simplifies the workflow for researchers who need to access and work with large amounts of EGA data. Get started with EGA FUSE Client To get started with EGA FUSE Client visit the EGA FUSE Client GitHub repository for more information and installation instructions.

  Documentation access/download/visualisation/fuse-client

• EGA QuickView

  EGA QuickView Secure and Remote Access to EGA Files What is EGA QuickView? EGA QuickView is a FUSE file system that allows secure and remote access to EGA files. It is a hybrid of sshfs and crypt4ghfs, which means it uses ssh to connect to the EGA distribution servers, downloads data in Crypt4GH format, and transparently decrypts those files. It is compatible with Linux and macOS 12. Why use EGA QuickView? EGA QuickView is a highly useful and convenient tool for anyone who needs to access EGA files remotely and securely. The software offers a quick and convenient way to browse through EGA files without the need for complete downloads, thus saving bandwidth and time. Whether you are a medical professional requiring access to sensitive patient data or a research scientist working on a project that involves EGA files, EGA QuickView provides a highly useful solution. The software boasts advanced security features, ensuring that your data is safe and protected at all times. Get started with EGA QuickView To get started with EGA QuickView, visit the EGA QuickView GitHub repository for more information and installation instructions.

  Documentation access/download/visualisation/ega-quickview

• The Federated EGA network

  In the last 10 years, most human omics data has been generated in the context of research consortia while recently there has been an emergence of large cohorts of human data generated by healthcare initiatives. Many countries in Europe now have nascent personalised medicine programmes. Thus, human genomics is shifting from being predominantly research-driven to being funded through healthcare systems. Genetic data generated in a healthcare context is subject to more stringent information governance than research data and nonetheless all data must adhere to national data protections laws. In this context, EGA identified the need for the development of a federated network to enable secure sharing of data whilst enabling genetic data to remain within the jurisdiction in which it was generated. The Federated EGA is designed to support national data management requirements for genomic and clinical data collected from citizens as part of healthcare or biomedical research projects. It includes a secure authorised access mechanism to support research use of these data across Europe and worldwide. We have engaged with over 14 ELIXIR countries to develop the federation model. The EGA federated configuration is composed of Central EGA, Federated EGA nodes and Community EGA nodes: Central EGA offers international submissions and helpdesk support, currently EGA co-managed by EMBL-EBI and CRG, Federated EGA nodes offer EGA services to researchers within their national jurisdiction, Community EGA nodes are individual institutions or initiatives with human genetic data intended to be shared with the research community. Key services available in the Federated EGA structure are: Central EGA Federated EGA node Community EGA nodes Data submission Offers international submissions service Offers submission service in a particular jurisdiction Does not offer an external submissions service Helpdesk support Provides external international helpdesk Provides helpdesk support for submitters in its jurisdiction and for approved users of data managed at its facilities Provides helpdesk support only for approved users of data managed at its facilities Data distribution Manages worldwide distribution for data hosted at Central EGA Manages worldwide distribution for data hosted at Federated EGA node Distribution for data hosted at Community EGA node EMBL-EBI and CRG have prepared a series of documents describing the overall governance and coordination framework. These describe the Federated EGA structure, the rights and responsibilities of the different parties and governing committees, and node operation guidelines. The federation governance proposal is under review by the first countries invited to join as Federated nodes, with further interested countries likely to join in the coming years. The Central EGA team has been working closely with many ELIXIR partners, including ELIXIR Finland, Luxembourg, Germany, Norway, Spain and Sweden.

  Blog the-federated-ega-network

• Archive growth Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue In this section, we expose the overall volume of data available to download and the different archived file types. EGA Archive growth in size and number of files The below figure represents the EGA archive growth in size (TB) and number of files. EGA Archive Growth per year lineChart('ega-archive-growth', 'https://stats.ega-archive.org/growth/archive', ['Volume (TB)'], ['T']) Archive files The below figure represents on a initial level, the percentage of archived files by data technology. The second level, acessible by clicking in the required extension, displays the number of files by extension archived in the ega archive. Please click over the extension to learn more about the files. EGA Archived Files barChart('ega-archived-files', 'https://stats.ega-archive.org/extensions', false ,'', true)

  Documentation about/statistics/archive

• Data distribution Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue Here, we show the amount of data distributed by the EGA. Data Distributed / Live EGA Data Distribution / Live SFTP Aspera HTSGET lineChartLive("svg#ega-dist-live", document.querySelector("#ega-figure-dist-live figcaption")); Data Distributed The below figure represents the cumulative EGA data distribution via the download clients(v2 and v3.x api versions) using HTTPS, FTP, and download boxes using ASPERA. You can see cumulative values by clicking "Cumulative". EGA Data Distribution //lineChart('#ega-data-distribution svg.stats', 'https://stats.ega-archive.org/distribution', // ['Amount of Distributed Data', ['Aspera', 'Download Clients', 'Total']]) curveChart('#ega-data-distribution', [ { domId: 'stats-aspera', label: 'Aspera', url: 'https://stats.ega-archive.org/distribution/aspera' }, { domId: 'stats-sftp' , label: 'SFTP', url: 'https://stats.ega-archive.org/distribution/sftp' }, //{ domId: 'stats-htsget', label: 'HTSGET', url: 'https://stats.ega-archive.org/distribution/htsget' }, { domId: 'stats-streamer' , label: 'Download Client', url: 'https://stats.ega-archive.org/distribution/streamer' }, { domId: 'stats-total' , label: 'Total', url: 'https://stats.ega-archive.org/distribution/total' } ] );

  Documentation about/statistics/distribution

• Germline sequencing

  Detection of SNV/indels in the germline of pediatric cancer patients with a focus on CHEK2 germline variants. Included in this EGA upload are the parents of the children in EGA uplodad EGAD00001008763.

  Study EGAS00001006651

• Bibliography Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue Here we expose in a yearly and cumulative manner, the publications, citations, publishers journals and impact factor of EGA related studies. Publications citing data stored at the EGA The studies that use EGA datasets are requested to cite the EGA into their bibliography. This fact allows for a faster spreading of the role and purpose of the EGA, being the availability of their studies for testability and reusability purposes. In order to track the studies we use the unique study accession, provided by the EGA when submitting a new study, and comprised of the keyword EGAS followed by 11 digits such as EGAS00000000001. We use the Europe PMC RESTful Web Service in order to query, and index studies where the EGAS accession was used. Below, you can find a chart showing the journal publishers of the studies citing data stored in the EGA being cited: Publications Citing Data Stored in the EGA pieChart('publishers-citations', 'https://stats.ega-archive.org/publishers/citations', 'Publishers') Number of publications citing data stored in the EGA by year Here, you can find a chart showing the number of publications citing data stored in the EGA by year. These publications could have deposit, or re-used the data. The study acession can be found in the publication. The default values are non-cumulative. You can see cumulative values by clicking "Cumulative". Number of Publications Citing Data Stored in the EGA by Year barChart('publications-by-year', 'https://stats.ega-archive.org/publications/year', ['Number of Publications by Year', 'Publications by Year']) Journal Impact Factor of Publications Citing Data Stored in the EGA Here, you can find a chart showing the journal impact factor of publications citing data stored in the EGA. We have used Scimago Journal Rank for this purpose. Low impact treshold was defined between 0.0 and 5.0 excluding; Medium impact treshold was defined between 5.0 and 10.0 excluding; High impact range was established from values equal to or higher than 10.0; Journal Impact Factor of Publications Citing Data Stored in the EGA pieChart('citations-publication-impact-factor', 'https://stats.ega-archive.org/citations/publication/impact/factor', 'Publication Impact Factor') Publications citing a publication containing a EGA study accession The publications, stating a EGA study accession in the bibliography, can be cited for testibility or reusability purposes. Below, you can find a chart showing the publishers of the publications being cited: Publications Citing a Publication Containing a EGA Study Accession pieChart('publications-citations', 'https://stats.ega-archive.org/publications/citations', 'Publishers') Number of publications citing a publication containing a EGA study accession by year Here, you can find a chart showing the number of publications citing a publication containing a EGA study accession by year by year. The values are non-cumulative: Number of published citations by year barChart('citations-year', 'https://stats.ega-archive.org/citations/year', ['Number of Publications', 'Citations by Year'])

  Documentation about/statistics/bibliography

• EGA synthetic data

  Synthetic Data One of the limitations in genomics research is that human genomics data is not openly available; access must be controlled according to participant consent agreements and data protection regulations such as GDPR. Obtaining authorization to access such data can sometimes take a long time, resulting in delays to important research work. In this context, synthetic genomic and phenotype data can be useful resources for researchers to avoid these delays. Synthetic data are artificially generated datasets, often created with algorithms, which can be used without the need for authorization to test new products and tools, build technical demonstrators, validate data models, and train AI models. The EGA provides access to synthetic cohort datasets augmented with rich synthetic metadata that overcomes these real data usage restrictions. Whilst synthetic datasets are not included in the general EGA mandate and services, we can consider such submissions and evaluate their acceptance on the basis of their unique use cases not already covered by existing synthetic datasets. Access to synthetic data studies is managed by the EGA Helpdesk Data Access Committee. Study ID Title Located in EGAS00001002472 CINECA synthetic cohort EUROPE UK1 referencing fake samples Central EGA EGAS00001005591 Synthetic data - Genome in a Bottle Central EGA EGAS00001005042 Test Study for EGA using data from 1000 Genomes Project - Phase 3 Central EGA EGAS00001005702 Human genomic and phenotypic synthetic data for the study of rare diseases Central EGA EGAS50000000190 EOSC4Cancer Synthetic Colorectal Cancer Genomic data Central EGA EGAS50000000086 Synthetic - FEGA Sweden Heilsa synthetic dataset December 2023 Federated EGA Sweden EGAS50000000678 Synthetic - GDI synthetic data Federated EGA Spain

  Documentation synthetic-data

• 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

• EGA submission account terms

  Submission account terms Each EGA submission account has a dedicated submission box. To ensure continued service to all submitters EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. Those that are near to or exceeding this value will be monitored on a weekly basis by the helpdesk team and the submitter will be contacted and guidance provided accordingly on completing their metadata registration. You will be able to register your metadata associated with the files in your submission account via EGA Submitter Portal, Webin or the EGA REST API. EGA also requests that metadata is submitted within 60 days of upload data to a submission box. When we detect files that are over 60 days old in a submission box we will notify the submitter requesting that metadata be submitted or the files removed from the submission box. It is important to note that data is not archived at the EGA until the metadata describing the files has been associated and the archival process has completed. It is only when associated metadata has been submitted that the archival process into EGA is fully triggered. EGA removes files from the submission box once they have been successfully archived, so no action is required by a submitter to remove successfully archived files. Files over 90 days old will be deleted from the submission box unless EGA Helpdesk has been contacted and confirmed an exemption with the submitter.

  Documentation submission/terms

• Metadata Public API

  Metadata Rest Endpoints Common Aspects Functionality Identifiers Requests and Responses Request Response Querying Querying by Object Cross-Querying by Object Common Aspects Functionality The Metadata REST API allows EGA users to request metadata from the EGA. Using this api you will be able to obtain the publicly available information from EGA study, sample, experiment, run, analysis, policy, dac and dataset. The API also allows for objects to be cross-referenced in order to obtain for example all the datasets linked to a dac. Identifiers EGA objects can be identified by their unique accession. These are ID's displayed everywhere, shared among all EGA locations and specific for each data type (More information on the list below) EGA Accession ID EGA Object description EGAS EGA Study Accession ID EGAC EGA DAC Accession ID EGAP EGA Policy Accession ID EGAN EGA Sample Accession ID EGAR EGA Run Accession ID EGAX EGA Experiment ID EGAZ EGA Analysis Accession ID EGAD EGA Dataset Accession ID EGAB EGA Submission ID EGAF EGA File Unique Accession ID Server Request and Response Request All the endpoints implement these two HTTP methods, GET and HEAD. Moreover, there is an authentication layer that allows to disclose the private information about each object if the user runs the endpoint with their token and has permissions to the related dataset. HTTP Method Description GET Returns the objects and their public information (including private information if the user has permissions) HEAD Returns the count of objects to be returned Response API responses are diverse but they always return a status call. Below you have a summary on what these codes mean and some tips that can help you troubleshooting them: HTTP Status Code Description Resolution 200 OK No error handling necessary 206 Partial Content Expected status code when paginating the results. No error handling necessary 400 BAD REQUEST Request incorrectly formulated 401 UNAUTHORISED/FORBIDDEN You do not have permissions over the object you are trying to access. / The authorised user is not permitted to make the given request. 404 NOT FOUND The object/resource you are trying to access does not exist. 500 INTERNAL SERVER ERROR This is a server-side error, try later. If the issue persists, contact the Heldpesk. Querying Querying by Object In the below documentation, worked examples can be found on how to use the API, to query about each unique EGA object. https://metadata.ega-archive.org/analyses/{id} https://metadata.ega-archive.org/dacs/{id} https://metadata.ega-archive.org/datasets/{id} https://metadata.ega-archive.org/runs/{id} https://metadata.ega-archive.org/samples/{id} https://metadata.ega-archive.org/studies/{id} Worked example for the EGA data access committee(DAC) EGAC00001000514 https://metadata.ega-archive.org/dacs/EGAC00001000514 Points to notice Please, be advised that all EGA objects can be queried by using the same endpoint. For example: https://metadata.ega-archive.org/datasets Returns all the datasets registered at the EGA. https://metadata.ega-archive.org/datasets?limit=5&offset=15 Returns 5 results skipping the initial 15 results. Cross-Querying by Object The EGA REST API Metadata also allows for the crossquerying of public metadata. For example, should I want to query the datasets included in the ICGC DAC: https://metadata.ega-archive.org/dacs/EGAC00001000010/datasets Below, you can find worked examples on how to perform the call to the API. https://metadata.ega-archive.org/datasets/EGAD00001000645/analyses https://metadata.ega-archive.org/datasetsEGAD00001000645/files https://metadata.ega-archive.org/datasets/EGAD00001000620/runs https://metadata.ega-archive.org/datasets/EGAD00001000620/samples https://metadata.ega-archive.org/samples/EGAN00001092114/datasets https://metadata.ega-archive.org/files/EGAF00000056146/dacs https://metadata.ega-archive.org/files/EGAF00000056146/datasets https://metadata.ega-archive.org/files/EGAF00000056146/studies There are more endpoints included in this category. Please, find all the possibilities (green tick) in the table below. Table The table displays in a ordered fashion the objects that can be crossreferenced using the metadata API. BY Analysis Dac Dataset Experiment Policy Run Sample Study File Analysis ✔ ✔ Dac ✔ ✔ Dataset ✔ ✔ ✔ ✔ Experiment ✔ ✔ ✔ ✔ Policy ✔ Run ✔ ✔ ✔ Sample ✔ ✔* ✔ Study ✔ ✔ ✔ ✔ ✔ ✔* File ✔ *: These cross queries do not include data from Array-File submissions. Check out the SPEC

  Documentation discovery/metadata/public-metadata-api

• Woodcock et al TenMenDeep Study EGA Dataset B

  Woodcock et al TenMenDeep EGA Dataset B. These are Illumina based deep sequencing data based on bait capture sequencing. See Woodcock et al methods for more detail. Note: the Amplicon sequencing data type is selected because the EGA Website currently has no option to select Bait Capture Sequencing or similar.

  Dataset EGAD00001005382

• Woodcock et al TenMenDeep Study EGA Dataset A

  Woodcock et al TenMenDeep EGA Dataset A. These are Illumina based deep sequencing data based on bait capture sequencing. See Woodcock et al methods for more detail. Note: the Amplicon sequencing data type is selected because the EGA Website currently has no option to select Bait Capture Sequencing or similar.

  Dataset EGAD00001005381

• PGDx EGA Data Access Committee

  Dac EGAC00001002922

• Implementation of the GDPR

  Data Protection 1 About the EGA The European Genome-phenome Archive (EGA) was formally launched in 2008 at the European Bioinformatics Institute (EMBL-EBI), an outstation of the European Molecular Biology Laboratory (EMBL), to address an identified need for archiving and sharing the results of genome-wide association studies from the Wellcome Trust Case Control Consortium. In late 2012, with the signing of a memorandum of understanding (and subsequent formal agreement in 2016) between EMBL-EBI and the Centre for Genomic Regulation (CRG), the EGA formally became a joint project of the two institutes. The two institutes work together to support the EGA services, including supporting submissions, web site, strategic leadership, and data infrastructure developments. 2 EMBL-EBI & GDPR The EGA is co-managed by EMBL-EBI and CRG. EMBL-EBI is an international organisation established by treaty and has certain privileges and immunities (e.g. exemptions from the application of national law) and also may self-regulate its activities (e.g. establish its own institutional legal framework) within the framework of its founding act of 1973. The General Data Protection Regulation (GDPR) is a European Union (EU) regulation that legislates how organisations can share and process personal data of EU citizens. EMBL places great value in maintaining collaboration with researchers who are subject to GDPR. For that reason, it is of utmost importance for EMBL to handle data received from those collaborators in a secure and responsible manner. Mindful of its public mandate and the sensitivity of the data it handles, EMBL has always ensured a high level of data protection in its activities. Since the introduction of GDPR in May 2018, EMBL has established its internal policy on General Data Protection (IP68), exercising its right to self-regulate its operations,., IP 68 establishes a robust personal data protection framework that provides for data protection principles, enforceable data subject rights and oversight and redress mechanisms offering a level of protection comparable with GDPR. 3 CRG & GDPR The Centre for Genomic Regulation (CRG) is an international biomedical research institute of excellence, created in July 2000 and mainly participated by the Catalan Government. It is a non-profit foundation and its mission is to discover and advance knowledge for the benefit of society, public health and economic prosperity. The CRG is a CERCA center. CERCA is the collective organisation for all research centres of excellence in Catalonia. CERCA ensures these centres develop successfully by promoting synergies and strategic cooperation improving their visibility and the impact of their research and promoting the dialogue amongst both public and private stakeholders. As a legal entity based in Spain and operating within the EU, the CRG ensures the compliance with the GDPR and the legal regulations on personal data protection applicable at the national level, as well as any other legislation that may replace, modify or supplement the above-mentioned in terms of personal data protection. 4 EGA & GDPR EGA GDPR Schema 4.1 Genetic and phenotypic data Within GDPR, there are two main actors: data controllers and data processors. Data controllers are persons or entities which determine the purposes and means that the personal data may be processed, e.g. companies, researchers, or universities. For EGA, the data controller is ultimately the data producer and the submitter(s) who submit the data to EGA. The data controller also creates a Data Access Committee (DAC) who will decide on data access permissions at EGA. Data processors are the persons or entities which process the data on behalf of a data controller. With regard to GDPR, EGA is a data processor as it processes data as instructed by the data controller. GDPR applies to any organisation which accesses personal data from an individual within the EU. Under GDPR, personal data is defined as any data that is identifiable, including names and email addresses as well as health-related and genetic data. EGA does not accept personally identifiable data except genetic and phenotypic data, so all other data submitted to EGA, such as names and addresses, must be pseudonymised. GDPR requires that data controllers implement data protection principles, such as data minimisation, to minimise the risk of data leakage, and protect the rights of the data subjects. As a data processor, EGA has a set of security policies that are followed to minimise the risk of unauthorised data access or data loss. In its role as a data processor, EGA requires all submitters to sign a Data Processing Agreement (DPA) when the submission account is first created. This agreement is only required to be signed once per submitter, and will remain valid for future submissions to EGA. 4.2 Other personal data The EGA also collects personal data as part of our interactions with submitters, data access committees, and researchers accessing data distributed by EGA. The below privacy notices explain 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. Privacy Notices for EGA Title Version Last Updated EGA Data Access Committee Account Privacy Notice for EGA Data Access Committee Account 1.0 February 6, 2019 EGA User Account Privacy Notice for EGA User Account 1.0 February 6, 2019 EGA Helpdesk Service Privacy Notice for EGA Helpdesk Service 1.0 February 6, 2019 EGA Website Service Privacy Notice for EGA Website Service 1.0 February 6, 2019 Documentation Title Version Description EGA Security Overview Security Document 1.1 The EGA Security Document provides an overview of EGA’s practices in ensuring the security of data stored at EGA. EGA Data Processing Agreement Data Processing Agreement 1.5 The Data Processing Agreement must be completed and returned as part of the submission process. Please note that this document is non-negotiable. Authorised Submitters Authorised Submitters Formulary 1.0 The Authorised Submitters Form must be completed and returned as part of the submission process. Please list all those that should have access to the submission account in order to submit to the EGA should be detailed here. Dispute Resolution Any controversy or claim arising out of, or relating to, the DPA (including the enforceability or breach thereof, any question regarding its existence, validity or termination) or relating to the EGA Service shall be resolved using the internal dispute resolution mechanisms of EGA including those related to Data Protection. The EGA’s internal dispute resolution mechanism has the following procedure: EGA OPERATIONAL PHASE: Meetings between EGA staff and the Data Controller.LEGAL MANAGEMENT PHASE: Meetings between legal teams of EMBL, CRG and the Data Controller. DIRECTION MANAGEMENT PHASE: Negotiation between the legal representatives of EMBL, the CRG and the Data Controller. If the internal dispute resolution mechanism doesn’t resolve the controversy or claim the next phase is:ARBITRATION PHASE: Resolution by arbitration under the WIPO Expedited Arbitration Rules (“Rules”).

  Documentation about/privacy-notice

• Tools

  EGA Tools This page provides details of the applications available at the EGA. Submission Tool Description EgaCryptor Encrypt and create md5sum values. Crypt4gh Encrypt, decrypt or re-encrypt files. INBOX Upload your files once encrypted. FTP Upload your files once encrypted. Submitter Portal Submit and manage your submission metadata online (SEQUENCING AND PHENOTYPE ONLY) Submitter Portal API Submit and manage your submission metadata programmatically. Webin Submit and manage your submission metadata online (array data) Webin API Submit metadata using XML files. Aimed to array-based submissions. Star2xml Format conversion tool to transform tabular formats (e.g. spreadsheets) into EGA's XMLs. Used for large programmatic submissions. Data Access Tool Description DAC Portal Manage and control data access request. Download Tool Description PyEGA3 Download and decrypt datasets requested through your EGA web account. Live Outbox Download and decrypt datasets requested through your EGA web account. Fuse Client A quick and convenient way to browse through EGA files without the need for complete downloads. EGA QuickView A quick and convenient way to browse through EGA files without the need for complete downloads.

  Documentation tools

• Catalogue Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue What is in the EGA? The European Genome-phenome Archive (EGA) overview The EGA archives and distributes the results of several types of studies. Such studies include genome-wide association studies (GWAS), different purpose sequencing and molecular diagnosis assays among others. Moreover, these studies target many different kind of diseases from cancer to neurodegenerative alterations. We summarised all this data in the charts below. The statistics are computed daily based on an updated list of studies. Each pie chart depicts a different aspect of the studies: which disease type was studied, which type of sampling method was used and what was the scope of the genomic analysis. Number of studies per disease type Studies in the EGA by disease barHorizontalChart('disease-graph', 'https://stats.ega-archive.org/catalog/by_disease') Number of studies per technology type Studies in the EGA by technology barHorizontalChart('technology-graph', '/stats/studies/technology', 'Include dbGaP') Number of studies per sample type Studies in the EGA by samples barChart('samples-graph', '/stats/studies/sample-types', 'Include dbGaP')

  Documentation about/statistics/catalogue

• DAC-for-UniExome-EGA-upload-2021

  Dac EGAC00001002168

• Access to public datasets in the EGA

  Dac EGAC00001000514

• Helse Bergen HF Data Access Committee for the MetBreCS trial dataset submitted to Federated EGA Norway

  This Data Access Committee is appointed by Helse Bergen HF to administer access requests for the MetBreCS trial dataset submitted to Federated EGA Norway.

  Dac EGAC50000000523

• Data Access Committee for EGA study accession EGAS00001006831

  Dac EGAC00001002988

• S3-EGA-swe5-sample

  S3 genotype data wave 5 (phenotypes)

  Dataset EGAD00010002627

• S3-EGA-swe6-sample

  S3 genotype data wave 6 (phenotypes)

  Dataset EGAD00010002618

• S3-EGA-swe1-sample

  S3 genotype data wave 1 (phenotypes)

  Dataset EGAD00010002623

• S3-EGA-s234-sample

  S3 genotype data wave 2-4 (phenotypes)

  Dataset EGAD00010002621

• Test dataset with ligh-weight files

  This is a test dataset derived from public data of the 1000 Genomes Project. Its purpose is not to allow for any inference about cohort data or results, but to aid bioinformaticians in the technical development and testing of tools, as well as data consumers in learning how to access information. This dataset consists of 3 pairs of light-weight (sliced) files: BAM + BAI, CRAM + CRAI and VCF + TBI. These files can be downloaded directly through the EGA-download-client PyEGA3 (https://github.com/EGA-archive/ega-download-client). For any further questions, please contact the DAC (Helpdesk - email: helpdesk [at] ega-archive [dot] org).

  Dataset EGAD00001009826

• Roifman_DAC

  This Data Access Committee (DAC) will be set up to review applications, and render decisions for requests submitted to EGA to access data deposited into ega-box-1592 by Dr. Chaim Roifman at the Hospital for Sick Children in Toronto, Canada. Contact: Dr. Chaim Roifman. email:chaim.roifman@sickkids.ca

  Dac EGAC50000000243

• S3-EGA-swe5-qc1

  S3 genotype data wave 5 (QC+ SNPs)

  Dataset EGAD00010002617

• S3-EGA-swe6-raw

  S3 genotype data wave 6 (all SNPs)

  Dataset EGAD00010002619

• S3-EGA-swe6-qc1

  S3 genotype data wave 6 (QC+ SNPs)

  Dataset EGAD00010002620

• S3-EGA-swe5-raw

  S3 genotype data wave 5 (all SNPs)

  Dataset EGAD00010002622

• S3-EGA-swe1-raw

  S3 genotype data wave 1 (all SNPs)

  Dataset EGAD00010002626

• New set of services for all users unveiled at the EGA

  The European Genome-phenome Archive (EGA) releases today a brand-new website as well as a set of improved services for users, comprising a revamped Submitter Portal with an improved API and data brokering functionality for submitters, as well as a new DAC Portal for Data Access Committee members to easily manage data access requests. The EGA team has been working hard over the past months on these improvements that will provide a better experience for the users. Discover them below! Visit our new EGA website and check the new functionalities and updated guides Our new website is live, with a fresh look and updated features to discover all the novelties. The homepage now includes three pathways to guide our users, depending on whether they want to deposit, download or manage data within the Archive. One of the most outstanding developments is the introduction of a streamlined process for requesting access to data: EGA Users can now directly request access to their preferred datasets through the website using their EGA accounts. Additionally, users can customise their profile, oversee active sessions, and manage the public keys, essential for our latest array of services, alongside a range of other features. Another major change is our new Help Desk contact method: a built-in website form tailored for user inquiries. This system, called "Need Help?", can be easily located on the top right-hand side of the website. It will encompass both EGA and Federated EGA node users' requests. We will detail its use soon, so stay tuned. Register your metadata to the EGA easily with our new Submitter Portal The new Submitter Portal makes the submission process quicker and more intuitive. The process is currently divided into sections that the user will know beforehand by taking the tour that the EGA team has created to guide users through the Portal before starting the first submission. Do not complete your data submissions alone! Our Submitter Portal now includes a collaboration mode so that every submission can be completed by authorised collaborators with an EGA Profile. There are a lot more features that we will be detailing from now on in incoming posts. A new platform for Data Access Committee Members The new DAC Portal brings novelties for individuals engaged in governance, legal, technical, operational roles, or those acting as data stewards. DAC members will be able to easily manage DACs, policies, and data access requests with the new Portal. Take the tour now to check them out! Help us improve the services completing the EGA Survey As part of our ongoing journey to improve your experience, we have created an EGA User Survey. This questionnaire covers a wide range of aspects such as user experience, support and data accessibility, among others. Participate now and take the opportunity to suggest your own improvements. Help us enhance your experience in this new era for the EGA. Subscribe to the EGA Mailing List and stay tuned In the next weeks we will share more information about the possibilities of the new services. You can easily join the EGA Mailing List to receive all the updates.

  Blog new-set-of-services-at-EGA

• S3-EGA-s234-raw

  S3 genotype data wave 2-4 (all SNPs)

  Dataset EGAD00010002624

• S3-EGA-s234-qc1

  S3 genotype data wave 2-4 (QC+ SNPs)

  Dataset EGAD00010002628

• Introducing Federated EGA Affiliates: a newly defined tier in the Federated EGA Network

  We're happy to announce that we are now accepting Affiliates in the Federated EGA Network! Federated EGA is a global network of repositories enabling secure discovery and access to sensitive human data. Currently, Federated EGA consists of Central EGA (CEGA), which serves the global community, and nine national Nodes that serve respective jurisdictions. Did you know that the Federated EGA (FEGA) has always envisioned a third tier within the network? This brings us to FEGA Affiliates, recently defined in the newly approved "Federated EGA Structure and Organisation" document. This new tier broadens the range of institutions or organisations that can become part of FEGA. Thus begins a new era for the network. What is a FEGA Affiliate? A FEGA Affiliate archives and serves controlled-access data within its own governance scope, while still participating in federated discovery through the EGA catalogue. Affiliates can be individual organisations or institutions, healthcare genomics initiatives, consortia of institutions, as well as project-specific consortia (national or international). In practical terms, a FEGA Affiliate: Hosts and safeguards the data it archives. Submits non-personal metadata to CEGA so studies are discoverable and can receive EGA accessions. Manages permissions and data access workflows for its datasets. Provides data access and/or distribution, along with support, to authorised users. Key takeaways about FEGA Affiliates FEGA is now organised into three tiers: CEGA, FEGA Nodes, and FEGA Affiliates. Affiliates archive data from their own organisation and/or selected partner institutions (for example, an international consortium). Affiliates make studies discoverable through the EGA catalogue by submitting non-personal metadata for accessioning. Access decisions and conditions are managed locally by the Affiliate (e.g. distribution or access in a trusted research environment). Are you considering whether your institution or project might be a good fit as a FEGA Affiliate? Would you like to learn more about this tier? We have published a blog post that addresses potential common questions, providing answers on this topic. You can read it here.

  Blog fega-affiliates

• Uppsala University Data Access Committee

  This DAC constitutes the Uppsala University access point EGA.

  Dac EGAC50000000433

• EGA account management

  How to manage your EGA account Welcome to the documentation page for creating an EGA user. The European Genome-Phenome Archive (EGA) is a platform for archiving, managing, and sharing human genomic and phenotypic data. To submit, access, and manage requests for the data hosted on the EGA platform, users are required to register for an account. This documentation page provides step-by-step instructions for creating an EGA user account, as well as information on the different types of EGA user accounts and their associated privileges. You can check the EGA data flow for a better understanding. Manage EGA account step-by-step guide Contact Information Public Keys Password Authenticator Federated Identity Sessions Request an EGA account step-by-step guide Fill in this form.You cannot use a generic email account (e.g., Gmail). Make sure you use your institutional email account.Your email is by default your username.The criteria for a strong password is: It should contain between 8 and 32 charactersIt should contain at least one uppercase letterIt should contain at least one numberIt should contain at least one special characterYou will need to wait for the Helpdesk team to check your identity. Please allow two business days for this step.After the Helpdesk validation step, you will receive an email with a link to validate your institutional email.Click the link to verify your email. It will redirect you to the EGA website.As soon as your account has been validated, you will be able to start adding more information to your EGA profile. For that, you first need to log in using your credentials from step 1. Manage EGA account step-by-step guide As a logged-in user, go to your profile by clicking on Welcome > My Profile. To modify it, click the Edit button.You will see the following options: Contact Information In this section, you can modify the personal information of your EGA account. Public Keys Adding a public key is necessary for downloading data via Live Outbox distribution. If you don’t know how to generate your key, you can follow the instructions available on How do I create a key? Password In the Password tab, you can change your password anytime to ensure the security of your account. However, if you receive an email notifying you that your password was modified and you did not initiate the change, it could be a sign that your account has been compromised. In this case, you should immediately contact our Helpdesk team to report the issue and receive assistance in restoring your account security. Authenticator You can set your two-factor authentication (2FA) system for your EGA account as an identity and access management security method that requires two forms of identification to access resources and data. To obtain your code, please follow the instructions below, also available in the Authenticator tab in your profile. Sessions The Sessions tab displays a list of all devices where you are currently logged in as an EGA user. This includes any open sessions you have on your computer, phone, or other devices. By reviewing the list of active sessions, you can monitor the devices that have access to your account and ensure that there are no unauthorised logins. If you notice any suspicious activity, you can close the sessions from this page to immediately terminate access to your account from the unauthorised device.

  Documentation how-to-manage-your-account

• WNT-signaling and Dupuytren's Disease

  The EGA hosts the summary genotype results of the GWAS in 856 patients with Dupuytren's disease and 2,836 population based controls from 'LifeLines' cohort study

  Study EGAS00000000043

• About

  About What's the EGA? The European Genome-phenome Archive (EGA) is a global network for permanent archiving and sharing of personally identifiable genetic, phenotypic, and clinical data generated for the purposes of biomedical research projects or in the context of research-focused healthcare systems. Jointly managed by the European Bioinformatics Institute (EMBL-EBI) in Cambridge (UK) and the Centre for Genomic Regulation (CRG) in Barcelona, we aim to advance biomedical research and promote personalised medicine worldwide by enabling discovery of and access to human genomic and health research data. The EGA contains data collected from individuals whose consent agreements authorise data release for specific research use to bona fide researchers. We ensure strict security measures to control access to the data and maintain patient confidentiality. With expertise in data management and technical infrastructure, we promote FAIR data reuse and enable researchers to share their data securely. By leveraging public funding and our strategic partnerships, the EGA provides a free service for permanent data storage, data discovery, and secure data access. In addition, we foster a federated network to provide transnational access to human research data in compliance with legal frameworks. For additional information about the EGA, please contact: Helen Parkinson and Mallory Freeberg EMBL European Bioinformatics Institute Arcadi Navarro, Roderic Guigó, and Jordi Rambla Center for Genomic Regulation History The European Genome-phenome Archive was launched in 2008 at the European Bioinformatics Institute (EMBL-EBI), an outstation of the European Molecular Biology Laboratory (EMBL), to address an identified need for archiving and sharing the results of genome-wide association studies from the Wellcome Trust Case Control Consortium. With the signing of a memorandum of understanding in 2013 and a formal agreement in 2016, the EGA became a joint project of EMBL-EBI and the Centre for Genomic Regulation (CRG). The two institutes work together to support the EGA services, including supporting submissions, website, strategic leadership, and data infrastructure developments. In 2022, the Federated EGA was officially launched with the signature of the first five countries: Finland, Germany, Norway, Spain, and Sweden. With more than 20 additional nodes worldwide preparing to join, the Federated EGA aims to become the largest human omics data sharing initiative towards understanding human health and disease. EGA overview If you're a researcher you may need to deposit, manage, or access genomic data in a secure and regulated way. The European Genome-phenome Archive (EGA) is a platform that facilitates these processes, ensuring that sensitive data is stored and shared in accordance with legal and ethical regulations. Submission process To start a submission, you need to become an EGA submitter. For that, you’ll need to sign a Data Processing Agreement (DPA) with us, that defines the terms and conditions under which your data will be processed and shared within the EGA system. The access to each study is controlled by its Data Access Committee (DAC). The DAC is responsible for managing data access requests and ensuring that the release of data is in accordance with the General Data Protection Regulation (GDPR). Please, note that once your data is released, all public metadata related to your study and dataset(s) will be searchable on the EGA website. However, the files are only accessible under controlled access, which means that a DAC has to agree to a previous data access request. Request process It is possible to submit an access request to data stored at the EGA. The DAC assigned to the study will assess the request and, if approved, grant access to the data. Requesters must provide sufficient justification for your request and comply with the intended data usage in order to get access to it. Each dataset is covered by a Data Access Agreement (DAA) that defines the terms and conditions of use for the specified dataset/s. The DAA is created and provided by the DAC, and must be signed by the individual requesting access to the given dataset/s. Download process Once the request for access is approved, the data and metadata can be downloaded. The EGA offers various download options to fit the needs: it is possible to preview files without downloading them, download specific files of interest, or even download terabytes of data. Overall, the EGA provides a secure and regulated environment for depositing, managing, and accessing human data. Regardless of the role - submitter, DAC member, or requester - the EGA provides assistance for each while ensuring that sensitive data is managed in an ethical and responsible manner. More information on how EGA handles data is available in the EGA dataflow.

  Documentation about/ega

• How are we funded?

  How are we funded? The EGA is provided infrastructure, administrative support, advisory input, and other relevant and necessary aspects by: CRG The EGA at the CRG is funded and supported by “La Caixa Foundation”, The Generalitat de Catalunya (Catalan Government), the Spanish Ministerio de Asuntos Económicos y Transformación Digital (Spanish Government) and the Instituto de Salud Carlos III. The Generalitat de Catalunya contributes with funding to the CRG and to the Barcelona Supercomputing Centre (BSC). The Barcelona Supercomputing Center is decisively contributing to EGA by providing the required compute, storage and networking resources, as well as key personnel for shared operations of EGA infrastructure. EMBL-EBI As part of the European Molecular Biology Laboratory (EMBL), the EGA at EMBL’s European Bioinformatics Institute receives funding from the governments of EMBL’s member states. The UK government, via UK Research and Innovation, also continues to support EMBL-EBI technical infrastructure, with EMBL supporting operational costs. A major source of funding for the EGA both at CRG and EMBL-EBI are competitive projects.The EGA resource continues to be funded through strategic engagement in collaborative partnerships and projects. Please see our projects page for more information. Other funders include the European Commission, the US National Institutes of Health, the Wellcome Trust, UK Research Councils, and our Industry Programme partners. Last updated on October, 2024.

  Documentation about/projects-and-funders/funders

• scRaCH-seq fastq files

  We base called the raw data of nanopore sequencing using the Guppy software (v3.1.5) with “dna_r9.4.1_450bps_sup_prom.cfg” configuration. The passed reads (Qscore > 9) are deposited in this EGA study.

  Study EGAS50000000165

• Growth Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue In this section the growth of registered objects such as studies, datasets and DACs in the EGA. Available Study, Dataset and DAC by year. The below figure represent the distribution of available Studies, Datasets and DACs per year. Available EGA Studies, Datasets and DACs. barChart('growth-objects-released', 'https://stats.ega-archive.org/growth/objects/released', ['Number of Objects', ['DAC', 'Dataset', 'Study']]) Created Study, Dataset and DAC by year. The below figure represent the distribution of created Studies, Datasets and DACs per year. Created EGA Studies, Datasets and DAC barChart('growth-objects', 'https://stats.ega-archive.org/growth/objects', ['Number of Objects', ['DAC', 'Dataset', 'Study']])

  Documentation about/statistics/growth