23249 results for "ega"

in 38.14 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

• 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

• 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

• 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

• 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

• 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

• 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

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

  Dac EGAC00001002168

• 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

• 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

• 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

• 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

• 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

• 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

• 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

• Uppsala University Data Access Committee

  This DAC constitutes the Uppsala University access point EGA.

  Dac EGAC50000000433

• 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

• 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

• 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

• 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

• 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

• 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

• DAC anti-MPO BCR sequences

  DAC for the requests of access to data of anti-MPO BCR sequences in the EGA repository,

  Dac EGAC50000000446

• 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

• Norwegian Institute of Public Health – Cancer Registry of Norway Data Access Policy for JanusRNA transcriptomics datasets archived in Federated EGA Norway

  JanusRNA transcriptomics datasets are generated from biobank samples from the Janus Serum bank of the Cancer Registry of Norway/National Institute of Public Health. This Data Access Committee has been appointed to govern controlled access to these datasets archived in Federated EGA Norway.

  Dac EGAC50000000192

• DAC for EGA study: Multi-omic analyses from a randomized phase II study of epigenetic priming followed by nivolumab in previously treated metastatic non-small cell lung cancer

  This is the Data Access Committee for the EGA study: Multi-omic analyses from a randomized phase II study of epigenetic priming followed by nivolumab in previously treated metastatic non-small cell lung cancer (temp ID 800).

  Dac EGAC50000000563

• How to encrypt files with Crypt4gh

  File preparation Due to the processes used at the EGA for file archival the use of non-alphanumeric characters in a filename will cause issues in archival. By convention whitespaces in filenames are to be avoided and should be replaced with the underscore character (_). Before encrypting your files please make sure that any files that will be uploaded to EGA do not use special characters such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | & Crypt4gh EGACryptor Files encrypted with Crypt4gh must be uploaded via INBOX Before uploading If you are not a registered EGA user, you will first need an EGA user account. Please note that it may take a few days for your account to be activated, as it needs to be vouched for by the EGA Helpdesk. Once your account is validated you will be able to request a submitter role. Meanwhile, you can create and add your public key to your EGA account profile. This option is not available for old submission accounts (e.g. ega-box-NNN). As soon as you have been granted a submitter role, you will be able to connect with your username and password to the EGA inbox using the SFTP protocol. If you have also registered a public key in your profile, you can also connect using this key. Encrypting your files Please note that you can also encrypt your files by uploading them directly to the "to-encrypt" folder in your upload area If your connection is unstable, please encrypt them using Crypt4gh The EGA encryption of this inbox is based on Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git Save now the following Crypt4GH public key, into a file, say ingestion.pubkey. __EGA_INGESTION_PUBKEY__ Encrypt a given file with the following command: crypt4gh encrypt --recipient_pk ingestion.pubkey < file_to_encrypt > encrypted_file.c4gh The command reads the file from stdin (with < ) and output the encrypted version to stdout (with > ). Replace file_to_encrypt and encrypted_file.c4gh with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write.

  Documentation submission/data/file-preparation/crypt4gh

• Tenk10k Phase 1: Whole Genome Sequencing

  TenK10K Phase 1 is a dataset of matched human whole-genome sequencing (WGS) from 1,925 individuals, and single-cell RNA sequencing (scRNA-seq) from over 5 million peripheral blood mononuclear cells across 28 immune cell types. Single-cell ATAC sequencing was additionally performed on a subset of 922 individuals. This EGA study consists of the WGS data from 1,925 individuals while a separate EGA study comprises the scRNA-seq and scATAC-seq data.

  Study EGAS50000001654

• Submitting array based metadata

  Submitting array based metadata For further information please check our Submission FAQs, submission quickguide as well as submission terms! The submission metadata required for Array-based submission must be submitted using EGA programmatic submission and by completing the Array-based format (AF) template. The guidelines for this workflow are described on this page. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA Array-based-Format (AF) template. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA-Array-based-Format (AF) template. Metadata Model Registering Metadata Use the EGA programmatic submission to register your Study, Samples, Data Access Committee (DAC) and Policy. This online interface enables you to create new and edit existing submissions. Do not use the Submitter Portal to register the metadata objects for array submissions. Please, go to the EGA programmatic submission. Registering Study Go to the EGA programmatic submission Submit an study XML Take a note of your study accession number (EGASXXXXXXXXXXX) To use the study accession number in a publication, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found on https://ega-archive.org "The European Genome-phenome Archive of human data consented for biomedical research"(https://doi.org/10.1093/nar/gkab1059 ). Registering Samples Go to the EGA programmatic submission Submit a sample XML Save the list of accession numbers. These will be needed for the AF template. Registering Data Access Committee Further information on the role of your DAC. Go to the EGA programmatic submission Submit a DAC XML Take a note of the DAC accession number (EGACXXXXXXXXXXX) Registering Policy Your Data Access Policy provides the terms and conditions of data use. This is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAA) Go to the EGA programmatic submission Submit a Policy XML Take a note of the Policy accession number (EGAPXXXXXXXXXXX) Complete the Array-based format (AF) spreadsheet Once you have completed the registration of your Study, DAC and Policy using the programmatix submission, you must then complete and return the AF spreadsheet The AF spreadsheet consists on four components: Do not use EGA IDs registered using the Submitter Portal. You can easily identify objects registered in the Submitter Portal by their EGA ID pattern: EGA[A-Z]5{10 more digits} (e.g. for a sample EGAN50000002506). For populating an AF spreadsheet, please exclusively use EGA IDs following this specific pattern: EGA[A-Z]0{10 more digits} (e.g. for a sample EGAN00001691542). Tab1) Webin accessions : Provide the accession numbers for your study, DAC and policy. Please, also add your ega-box number. Tab2) Sample & phenotypes: Please, leave this tab blank. Tab3) Dataset: Describe the dataset to be created Tab4) Data files: Define how your data is going to be organised into datasets and packets for distribution (linkage between samples and files). Should further assistance be required after going through the guide below; please do not hesitate to contact the EGA helpdesk Once the AF spreadsheet is populated, please send it to our EGA helpdesk for further validation. AF spreadsheet Should your submission require multiple DAC's or policies, use ' ; ' to separate the accession numbers. Accessions AF spreadsheet: Samples & phenotypes Samples and phenotypes AF spreadsheet: Datasets We suggest that each dataset consists of a common set of data. The example below consists of two datasets, grouped according to shared data type, technology and by case/control. We also like to capture the number of unique samples that make up the dataset and the Data Access Committee (DAC) responsible for providing the named dataset and their policy (EGAP). Datasets AF spreadsheet: Data files What follows is an example of how to map your samples to the array based files added to your upload account (4th tab). Data Files Please, find below some practical examples on how to register the linkage between samples-files Case 1) 1 sample or list of samples in different datasets: Data Files In case you have a list of samples that belong to different datasets, please, repeat the samples accession number/s in the first column and link the sample to the corresponding dataset each time (each row). Each row is one linkage between sample-file-dataset. Case 2) 1 sample links to several files: Data Files In order to add multiple files to one sample you MUST use “ ; “ between filenames. Example: file1.gpg;file2.gpg;file3.gpg In case that you want to add an extra file to the sample (phenotype or .Rdata), please use “Additional files” column. Important note: You MUST upload the encrypted and unencrypted md5sum values of all files uploaded to your submission account using the filename nomenclature (file.gpg, file.md5,file.md5.gpg). Your submission will not be processed without md5values supplied for all files in the CORRECT format. What happens after the submission of a dataset? All datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitted or DAC contact instructs our EGA helpdesk for the study to be released. Finally, your data is archived within our databases and prepared for encrypted distribution upon the request of permitted EGA account holders. We strongly advise you NOT to delete your data until we confirm that your data has been successfully archived.

  Documentation submission/metadata/submission/array

• DAC-2020-03-26-Lemola (DAC-039))

  DAC-2020-03-26-Lemola (DAC-039)), raw data in EGA, metadata in Harvard Dataverse

  Dataset EGAD50000000897

• Beacon v2 and Federated EGA, part of the GDI project Starter Kit to enable access to genomic and phenotypic data across borders

  The European Genomic Data Infrastructure project has released a ‘Starter Kit’ based on the rare disease and cancer proof-of-concepts from the Beyond 1 Million Genomes (B1MG) project. The Starter Kit, freely available to any interested parties, contains a set of software applications and components co-developed by the 20 GDI nodes and based on open community standards from the Global Alliance for Genomics and Health (GA4GH). Products in the Starter Kit give all countries the technical capability to access synthetic genomic and phenotypic data across borders. The image above shows the full workflow of the GDI Starter Kit user journey. The dotted circles are not included in the Starter Kit yet The EGA’s work is represented in the Starter Kit with Beacon v2 and Federated EGA among the software applications and components. About Beacon v2 Beacon is a protocol for data discovery. This API allows the search of genomic variants and associated information without breaching the datasets privacy. The European Genome-phenome Archive (EGA) is a key contributor to the Beacon v2 Protocol, the Beacon v2 Reference Implementation (B2RI) and the EGA Beacon(s). About Federated EGA The Federated EGA network offers a tool for data storage and sharing. Officially launched in 2022, this network of connected resources enables transnational discovery of and access to human omics data for research, while also respecting jurisdictional data protection regulations. The Federated EGA Onboarding Website contains all the information related to the establishment of a Federated Node.

  Blog beacon-v2-and-federated-ega-part-of-the-gdi-project-starter-kit

• Federated EGA

  Federated EGA Federated EGA Index Overview Map of FEGA status across the world Current status of the FEGA Network Documentation Overview Federated EGA is a global network of repositories enabling secure discovery and access to sensitive human data. Our vision is to accelerate scientific discovery and healthcare breakthroughs by creating the go-to worldwide sensitive human data resource. Our values are: Privacy & Trust: Ensuring privacy of data subjects, security of services and acting with integrity to build community trust.FAIRness: Driving reuse of data through standardisation of metadata and clear access policies.Diversity: Expanding our network and representing global diversity in the data we host to bring benefits worldwide. Federated EGA - European by name, global by nature Federated EGA collaborates with European and global initiatives (GA4GH, ELIXIR, 1+ Million Genomes Framework, GDI), demonstrating that a network for transnational discovery of and access to human data is possible. By providing a solution to emerging challenges around secure and efficient management of human omics and associated data, the FEGA Network fosters data reuse, enables reproducibility, and accelerates biomedical research. For general enquiries or to request more information about Federated EGA, please send an email to fega-info [at] lists [dot] ega-archive [dot] org. Read more about the Federated EGA in our commentary in Nature Genetics! Learn more about setting up a Federated EGA Node in our onboarding documentation. Map of FEGA status across the world Current status of the FEGA Network Node Description Joined CEGA Central EGA is managed by the Centre for Genomic Regulation (CRG) and EMBL-EBI. The EGA has been a trusted repository for sensitive data since 2008. CEGA coordinates the FEGA network, hosts central services and the EGA catalogue. 2022 Finland FEGA Finland is hosted by CSC - IT Center for Science Ltd., which is the national ELIXIR Node in Finland. CSC is a state-owned company specialising in providing high-quality IT infrastructure and services for Finnish higher education and research. 2022 Germany The German Human Genome-Phenome archive (GHGA) is part of the German National Research Data Infrastructure (NFDI). It is coordinated by the German Cancer Research Center (DKFZ) and includes over 20 academic partners. 2022 Norway FEGA Norway is a service by ELIXIR Norway, the Norwegian node of the European organisation ELIXIR. University of Oslo as a partner institution in ELIXIR Norway is hosting the service relying on the TSD infrastructure for sensitive data. ELIXIR Norway is a consortium of 5 Norwegian universities and is coordinated by University of Bergen. 2022 Spain FEGA Spain is co-hosted by the Barcelona Supercomputer Center (BSC) and the Centre for Genomic Regulation (CRG), both part of ELIXIR Spain and the Spanish National Infrastructure for Personalised Medicine associated with Science and Technology (IMPaCT). 2022 Sweden FEGA Sweden is hosted by the National Bioinformatics Infrastructure Sweden (NBIS), which legally is part of Uppsala University. NBIS forms the bioinformatics platform at SciLifeLab and constitutes the Swedish node of the European organisation ELIXIR. 2022 Poland FEGA Poland is hosted by Biobank Lodz, which is part of University of Lodz. Biobank Lodz is an element of the infrastructure of the Regional Digital Medicine Centers established by the Medical Research Agency. 2022 Portugal FEGA Portugal is managed by BioData.pt, the distributed infrastructure for Life and Health data for Portugal. This entity is a non-profit association of 15 life sciences R&I organisations spread across the country, and the home of ELIXIR Node in Portugal. 2023 Canada Canadian Genome-phenome Archive is part of the Pan Canadian Genome Library, with the mandate to allow the secure and responsible sharing and analysis of Canadian genomic information. 2024 Switzerland Swiss FEGA is hosted by SIB Swiss Institute of Bioinformatics, which is the national ELIXIR Node in Switzerland, on behalf of the Swiss FEGA Partnership which includes 4 other key partners (ETH Zurich, Health 2030 Genome Center, Swiss Data Science Center and Switch). 2025 Documentation Title Version Description Mission, vision, values Federated EGA Mission, vision, values 1.0 The official Mission-Vision-Values statement for FEGA, produced and formally approved by the FEGA Strategic Committee in September 2025. Structure and Organisation Federated EGA Structure and Organisation 2.0 The structure of the FEGA network and service expectations, responsibilities and commitments. FEGA is organised into three tiers: Central EGA, FEGA Nodes and FEGA Affiliates. Strategic Committee Federated EGA Strategic Committee 1.1 Terms of reference for the FEGA Strategic Committee describe the purpose and objectives of the committee, which is to provide direction and strategic planning for the FEGA network. The committee receives input from, and provides feedback for the EGA Strategic Committee. Operations Committee Federated EGA Operations Committee 1.1 Terms of reference for the FEGA Operations Committee describe the purpose and objectives of the committee, which is to review operational performance and coordinate technical roadmaps of FEGA Nodes and Central EGA. The committee receives advice from, and provides operational reporting to the FEGA Strategic Committee. Guidelines Node Operations guidelines 2.1 An overview of the operational areas which require resources in order to create a FEGA Node. The document is based on more than 15 years' experience of EMBL-EBI and CRG operating the EGA and initial expericences of the inaugural FEGA Nodes. The operational areas of responsability are in line with the FEGA Maturity Model, which guides establishment and operation of FEGA Nodes. Collaboration Federated EGA Node Collaboration Agreement 1.3 Nodes are welcome to make a copy of this current version of the CA to start its review with their legal teams and understand the responsibilities of joining FEGA. Nevertheless, this version (the one with a watermark) shall not be signed: the official version needs to be obtained from FEGA prior signing through its official channels.

  Documentation about/projects-and-funders/federated-ega

• OLINK metadata EGA v2

  Sample metadata for the olink dataset. This dataset includes subject-level data and longitudinal visit day information for the corresponding samples.

  Dataset EGAD00001011165

• Whole genome sequencing data of relapsed paediatric KMT2A-rearranged acute lymphoblastic leukemia

  Whole genome sequencing data of relapsed KMT2A-rearranged leukemia. Dataset includes bam-file of released case. Diagnostic (ALLT-375D) and remission (ALLT-375R) samples can be found with EGA ID: EGAD50000001568.

  Study EGAS50000001100

• TEST_STUDY for submitter testing

  This is a test study for the purpose of submitters wishing to test the EGA submission procedure. All objects, such as DAC and datasets, linked to this study can also be considered to be for testing purposes.

  Study EGAS00001000889

• Covacta RNAseq merged EGA metadata

  Sample metadata for the RNA-seq dataset. This dataset includes subject-level data and longitudinal visit day information for the corresponding samples.

  Dataset EGAD00001011162

• TUM Experimental Neuroimmunology

  This DAC will decide about all data requests to human data deposited at EGA that was primarily produced at the Institute for Experimental Neuroimmunology at the Technical University Munich, Germany.

  Dac EGAC50000000093

• Data of the Institute of Pathology, University Medical Center Freiburg, Germany

  DAC for proteomics data deposited in EGA by the proteomics laboratory of the Institute of Pathology, University Medical Center Freiburg, Germany

  Dac EGAC50000000048

• Download Metadata

  Metadata Distribution Welcome to the realm of Metadata Distribution within the EGA ecosystem! Our Metadata REST API empowers you to effortlessly retrieve metadata from the expansive landscape of EGA. By utilising this API, you gain access to publicly available insights across various EGA domains, including studies, samples, experiments, runs, analyses, policies, DACs, and datasets. Furthermore, this API facilitates cross-referencing of objects, enabling you to gather, for example, all the datasets associated with a specific DAC, seamlessly. In addition, we have added the ability to query private data using the metadata API. If you possess the necessary permissions, you can access behind-the-login private data for a specified list of datasets. Metadata Distribution Index Identifiers Dataset Mappings Website Download Metadata API - Private Identifiers At the core of EGA's organisational structure are unique accessions that serve as essential tags for our diverse objects. Here's a quick overview of the accessions and their corresponding object types: 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 For further information check our metadata schema documentation. Dataset Mappings For authorised datasets, comprehensive mappings reveal meaningful connections: Sample_file: This file presents information about the linkage between samples and files available in the dataset. Study_experiment_run_sample: This file presents information about the linkage between studies, experiments, runs, and samples within the dataset. Study_analysis_sample: This file presents information about the linkage between studies, analyses, and samples contained within the dataset. Run_sample: This file presents information about the linkage between runs and samples within the dataset. Analysis_sample: This file presents information about the linkage between analyses and samples within the dataset. An empty file indicates the absence of corresponding information. Website Download Our website serves as your gateway to downloading metadata. Simply navigate to the dataset page, and you'll find a blue Metadata button. Once authenticated, you can click this button for authorised datasets. If you lack permissions for a particular dataset, request access by clicking the 'Request Access' button. For authorised datasets, choose your preferred metadata format: CSV, TSV, or JSON. Metadata API - Private Leverage the power of programmatic metadata downloads! Start by authenticating yourself with your credentials to obtain an access token. With this token, programmatically query private information. Queries mirror the structure of the Public Metadata API. However, behind the login, you can delve into specific mapping information (as mentioned above in dataset mappings) alongside object-level exploration. Authentication An active session is required to work with the API. Each time you log in with your credentials a new session is started, which is identified by an access_token. Below an example on how to obtain one using curl: curl https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token \ -d 'client_id=metadata-api' \ -d 'username=...' \ --data-urlencode 'password=...' \ -d 'grant_type=password' All responses from the API are in JSON format. A successful response should include a new token to be used for the session: {"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCIgOiA...TNw", "expires_in":300, "refresh_expires_in":1800, "refresh_token":"eyJhbGciOiJIUzI1NiIsInR5cCIgOiA...pTX10", "token_type":"Bearer", ... } Save the access_token value and include it in the API call headers. Example query usage Below you can find some example of queries available behing authentication and authorisation. Querying study-experiment-run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_experiment_run_sample \ -H 'Authorization: Bearer access_token' Querying run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/run_sample \ -H 'Authorization: Bearer access_token' Querying study-analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_analysis_sample \ -H 'Authorization: Bearer access_token' Querying analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/analysis_sample \ -H 'Authorization: Bearer access_token' Querying sample-file mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/sample_file \ -H 'Authorization: Bearer access_token' You can get a different output format by adding one of these options to the curl command: -H 'Accept: text/tsv' -H 'Accept: application/json' -H 'Accept: text/csv' For more detailed information, refer to the Metadata API Specification.

  Documentation access/download/metadata

• VHIR Renal Physiopathology Group DAC

  This DAC describes the members of the Data Access Committee and the policy that will regulate access to the datasets uploaded at EGA from the Renal Phyisiopathology Group at VHIR

  Dac EGAC50000000510

• The EGA at the International Congress of Human Genetics

  Today is the start of the International Congress of Human Genetics (ICHG). This event, hosted by the African Society of Human Genetics (AfSHG) and the Southern African Society for Human Genetics (SASHG), will reunite international experts to highlight how genomic technologies are being managed to address challenges generated by the current status of Human Health and Genomics. The European Genome-phenome Archive (EGA) will be at the Congress participating in workshops, meetings and talks where topics such as data access and discovery as well as the Federated EGA will be present. Data access and discovery In the context of the “Federated data analysis workshop“ that will be held the 26ᵗʰ, managed in the context of the CINECA project, a hands-on-session on Beacon v2 Discovery will be led by Mauricio Moldes. Another session on authorisation and data access will be presented by Mallory Freeberg and Coline Thomas, with and introduction by Thomas Keane. During the workshop, an end-to-end federated data analysis use case will be presented. Data access and discovery In the context of the “ Federated data analysis workshop“ that will be held the 26ᵗʰ, managed in the context of the CINECA project, a hands-on-session on Beacon v2 Discovery will be led by Mauricio Moldes. Another session on authorisation and data access will be presented by Mallory Freeberg and Coline Thomas, with and introduction by Thomas Keane. During the workshop, an end-to-end federated data analysis use case will be presented. During the last four years, CINECA has been identifying gaps in data sharing between Africa, Canada and Europe in order to build a federated solution for data access. Thomas Keane will present the project within the sessions happening the 24ᵗʰ. The Federated EGA at the ICHG A Federated EGA poster will be shown during the Poster Session 1 that will take place the 23ʳᵈ. The objective is to bring awareness of the European Genome-phenome Archive as a resource for permanent archive and secure data sharing. In this context, the network generated by the Federated EGA is key for cases where research data cannot be shared outside local jurisdictions. The Federated EGA was officially launched on 2022 with research institutes from five countries becoming the first nodes of this network. Nowadays, with more than 20 nodes preparing to join, it aims to become the largest human omics data sharing initiative towards understanding human health and disease. The H3Africa Initiative and the African research represented in the EGA 1.1% of the EGA studies include samples from African populations. Countries such as South Africa, Kenya, Uganda or Egypt, among others, are present in the 72.577 samples from African individuals archived at the EGA. 23 EGA datasets are managed by the Human Heredity and Health in Africa Initiative (H3Africa). This Initiative will celebrate its Consortium Meeting the 27ᵗʰ and 28ᵗʰ, back-to-back with the ICHG. H3ABioNet, the Pan African Bioinformatics Network for the H3Africa consortium, will also take this context to celebrate its 10-Year Symposium during the Congress. Members of the EGA team will attend both of them, as the H3ABioNet works in conjunction with H3Africa projects, to submit data to the European Genome-Phenome Archive.

  Blog the-ega-at-the-international-congress-of-human-genetics

• Providing safe access to sensitive human data across borders: Federated EGA becomes a reality

  Enabling discovery and access to sensitive data across national boundaries is vital for improving human health. It enables more powerful and efficient research by increasing the volume and diversity of data available for analysis. It allows us to better understand the causes of diseases – cancer, rare diseases, infectious diseases like COVID-19 – and develop new medicines and treatments. Sensitive human omics data are typically generated by research initiatives and shared using specialist repositories which provide services for data submission, discovery, and access. The EGA is one such repository. Established in 2008 at EMBL’s European Bioinformatics Institute (EMBL-EBI) in the UK, since 2012 the EGA (“Central EGA”) has been jointly managed by EMBL-EBI and the Centre for Genomic Regulation (CRG) in Spain. Many countries have emerging personalised medicine programmes which generate data from national initiatives. These programmes are driving a transition in human genomics from being research-driven to receiving funding through healthcare. Data generated in a clinical context are subject to stricter governance than research data and must follow national data protection legislation. To solve these challenges, the Federated EGA provides a network of connected resources to enable transnational discovery of and access to human omics data for research, while also respecting jurisdictional data protection regulations. In this way, the Federated EGA infrastructure supports the goals of European initiatives such as the 1+ Million Genomes initiative (1+MG), the European Health Data Space, and a number of EU-funded 1+MG implementation projects including Beyond 1 Million Genomes. The Federated EGA is made up of “Nodes” – typically nationally funded and operated – which store and manage data locally while allowing global discovery within the Federated EGA network. Since 2016, multiple parallel efforts, supported by ELIXIR and other transnational and national initiatives, have created technical and legal frameworks for establishing the Federated EGA. In 2022, the first five Nodes – Finland, Germany, Norway, Spain, and Sweden – officially joined the Federated EGA by signing Federated EGA Collaboration Agreements with Central EGA. The Finnish FEGA Node is operated by CSC - IT Center for Science and provides data management services according to national laws and the requirements of the EU General Data Protection Regulation (GDPR). These services provide tools and support for the whole life-cycle of sensitive research data from collating to analysis, publication, and authorised re-use. The development of the services has been a joint effort with the other Nordic nodes within NeIC's Tryggve and Heilsa projects, and funded by Finnish Ministry of Education and Culture and projects coordinated by ELIXIR Finland. Read more about Finnish FEGA signing. The German Human Genome-Phenome Archive (GHGA) strives to provide a national infrastructure as well as an ethical and legal framework that balances FAIR omics data usage and data protection needs for Germany. As a Germany-wide consortium funded by the German Research Foundation under the umbrella of the NFDI association, GHGA combines the expertise of 21 universities and research institutions to form a federated national infrastructure. Read more about GHGA signing. The German Human Genome-Phenome Archive (GHGA) strives to provide a national infrastructure as well as an ethical and legal framework that balances FAIR omics data usage and data protection needs for Germany. As a Germany-wide consortium funded by the German Research Foundation under the umbrella of the NFDI association, GHGA combines the expertise of 21 universities and research institutions to form a federated national infrastructure. Read more about GHGA signing. In Norway, a key component of the infrastructure is the services of The Sensitive Data Service (TSD) offered by USIT at University of Oslo. The Federated EGA Norway Node is developed by ELIXIR Norway and operated by the University of Oslo as the responsible legal entity. Core software modules are developed jointly with the other Nordic nodes in the NeIC Tryggve and Heilsa projects. Read more about FEGA Norway signing. The Spanish FEGA (es-FEGA) is a national service for storing sensitive biomedical data in Spain. Supported by the Spanish Institute of Bioinformatics (INB) in collaboration with Central EGA, sensitive research datasets are primarily hosted at the Barcelona Supercomputing Centre facilities. The Swedish Sensitive Data Archive is a secure data archive and sharing platform for sensitive datasets. It was developed by the National Bioinformatics Infrastructure Sweden (NBIS) in collaboration with other Nordic ELIXIR Nodes through the Tryggve and Heilsa projects funded by NeIC and coordinated with Central EGA through ELIXIR. Read more about the Swedish Node signing. The Swedish Sensitive Data Archive is a secure data archive and sharing platform for sensitive datasets. It was developed by the National Bioinformatics Infrastructure Sweden (NBIS) in collaboration with other Nordic ELIXIR Nodes through the Tryggve and Heilsa projects funded by NeIC and coordinated with Central EGA through ELIXIR. Read more about the Swedish Node signing. By providing a solution for secure and efficient management of human omics data, the Federated EGA aims to foster data reuse, enable reproducibility, accelerate biomedical research, and improve human health. Find out more Interested in setting up your own Federated EGA Node? Check out the FEGA Onboarding Knowledge Base for more information. The ELIXIR Federated Human Data Community is a great entry point for anyone interested in learning more about the Federated EGA. You can: Join the ELIXIR Federated Human Data Community mailing list (select “Human Data”) Attend the ELIXIR Federated Human Data Community calls

  Blog safe-access-to-sensitive-human-data-federated-ega

• Haukeland University Hospital Data Access Committee for STRAT-PARK datasets archived in Federated EGA Norway

  This is the Data Access Committee mandated by Haukeland University Hospital for the STRAT-PARK cohort: an initiative to stratify Parkinson's disease.

  Dac EGAC50000000428

• Dataset-linking-WGS-samples-in-ega-box-81-via-README-for-study-EGAS00001002923

  This dataset contains 318 Tumor and Control WGS files submitted in another EGA box for samples for Gerhauser et al.,Cancer Cell, 2018, 34:996-1011. WGS and sequencing protocol was earlier described in Weischenfeldt et al, Cancer Cell, 2013.

  Dataset EGAD00001007861

• Legal Notice EGA is a joint effort by the EBI and CRG. Please, check their terms of use and legal notice in order to follow them in the usage of the EGA website. EBI terms of use CRG terms of use

  Documentation legal-notice

• European Genome-phenome Archive 15th Anniversary Celebration

  2023 marks the 15th Anniversary of the EGA, jointly managed by the European Bioinformatics Institute (EMBL-EBI) and the Centre for Genomic Regulation (CRG). To mark the occasion, a simultaneous celebration was held in both institutions on the 13th of December 2023. The teams gathered online to play a quiz game and celebrate all the achievements and milestones with two wonderful anniversary cakes. In 2008, the European Genome-phenome Archive was created at the EBI-EMBL in Cambridge to guarantee that human genome and phenome data were available to the international scientific community while data privacy was preserved. The six-person staff at the beginning of the project is now far behind us, with a team that reaches the number of 35 members. Since 2013, the European Bioinformatics Institute and the Centre for Genomic Regulation share responsibility for The European Genome-phenome Archive (EGA). At that time, the EGA had data for about 0,5 petabytes. Currently, the Archive contains more than 12 petabytes. 2023 comes to an end with several good news. The EGA has been renewed as an ELIXIR Core Data Resource. This was announced during the GA4GH 11th Plenary held in San Francisco last September when ELIXIR-Beacon was also confirmed to be a GA4GH Driver Project. Thus, the Beacon API has maintained this title since 2018. What’s more, the first Federated EGA dataset is now live on our website. This year we also launched new services for EGA users in September. By the numbers, in 2023 the EGA counts 2.5 PB archived, 371 studies published, 208 new submitters and 19 active projects in which the team is participating, among others. We look forward to continuing to support your research in 2024!

  Blog 15-anniversary

• Beacon v2

  Beacon v2: a tool for data discovery Motivation In the era of data-driven health research and personalised medicine, human genomic data has become extremely valuable. These are also identifiable data, as they carry information pointing to a specific individual as well as their own family; and as such, they must be protected. This makes data discovery particularly challenging: this is where "Beacon" comes in. A "Beacon" is an API aiming to enable the search of genomic variants and associated information without jeopardising the privacy of the dataset. Here, we refer to its current version, namely version 2 (v2). Definition Beacon v2 is a term that can refer to different aspects. The EGA is playing a central role in the following aspects: The Beacon v2 protocol is a Global Alliance for Health and Genomics standard. The Beacon v2 Reference Implementation (B2RI) is an "out-of-the-box" Beacon instance developed with ELIXIR, which facilitates Beacon deployment. The EGA Beacon(s) are Beacons following the v2 standard and using the B2RI, deployed on top of data hosted at the EGA and allowing for their discovery. Resources Depending on whether you are visiting us a stakeholder (you need more general information about Beacon), a deployer /implementer (you want to have your own Beacon instance), or an EGA user (you want to query Beacon and start browsing data), you will be interested in the following resources: Your role Beacon aspect Documentation type Stakeholder Beacon v2 protocol Beacon website Beacon page on the GA4GH website Deployer/Implementer Beacon v2 protocol Read the docs: Beacon v2 standard technical description GitHub repository Beacon v2 standard Beacon v2 Reference Implementation Read the docs: B2RI technical description GitHub repository B2RI Guide to deploy Beacon using B2RI EGA user EGA Beacon EGA AF Browser

  Documentation about/projects-and-funders/beacon

• Whole genome sequencing data of relapsed paediatric KMT2A-rearranged acute lymphoblastic leukemia

  Bam-file of the one replased KMT2A-r case. Diagnostic (ALLT-375D) and remission (ALLT-375R) samples can be found from EGA submission EGAD50000001568.

  Dataset EGAD50000001593

• IL2 data set including 59 samples

  The dataset is referenced by EGA Study ID EGAS00001003605, which includes the short-reads data for 59 samples. All short-reads data files are in fastq format.

  Dataset EGAD00001004967

• How to request data

  Request Data Access If you're looking to access data from the EGA for your research, you are in the right documentation page! In this page you will find a step by step guide on how to request data archived at the EGA, as well as some frequently asked questions you might find useful. When requesting data, you'll need to provide information about your research project and intended use of the data. Keep in mind that your data access request may require additional approvals or agreements depending on the datasets and data providers involved. Step by step guide Register yourself as an EGA user. Validate your account. A validation link will be sent to your email to activate your EGA user account. Log into the EGA page. Search the dataset of interest from the dataset catalogue or search bar. Click on “Request access” Add a comment requesting these files and send your request Your request is successfully registered, and the DAC will receive a notification about your request In addition to submitting your request, you should also contact the DAC directly via e-mail. You can access the DAC's contact information from the relevant dataset page. Frequently Asked Questions (FAQ) Which is the role of the EGA in the data access process? The European Genome-phenome Archive (EGA) facilitates the secure distribution under controlled access of personally identifiable genetic and phenotypic data. Data Access Committee (DAC) is a body of one or more individuals who are responsible for data release to external requestors, based on participant consent and/or National Research Ethics terms. How do I request access to multiple datasets? To request access for multiple datasets managed by the same Data Access Committee (DAC), please start by visiting the DAC catalogue to locate the DAC of your choice. Once you've found the relevant DAC, proceed to its dedicated page where you'll find a "Request access" button. After logging in to the EGA website, you'll be presented with a comprehensive list of datasets under the chosen DAC. Select the datasets you're interested in, and then compose a message indicating your access request. Click the "Send" button to submit your request, which will include the chosen datasets. Please be sure to review the data usage policies for the requested datasets, as policies can vary among datasets managed by the same DAC. I am a co-applicant. Will I be given a joint access account? Each applicant needs to create an EGA account themselves, with unique login details. User log-in details are for individual use only and should never be shared, under any circumstances. EGA services are only provided to EGA account holders. Therefore, the co-applicant will send a formal request to the DAC. What happens if a co-applicant leaves or a new member needs to be added to an existing DAC application? The appropriate Data Access Committee (DAC) should be contacted and informed about the required changes so that the application can be updated. I have changed my place of work since my EGA account was created. Can I still have access to data? You must contact the relevant Data Access Committee (DAC). The DAC did not reply to my data access request. How should I proceed? There is no estimated time for DAC response. Please allow up to four weeks for a response. In the meantime, please send them a weekly reminder of the status of your request by emailing them directly.If the DAC becomes unresponsive, meaning that they fail to communicate with a requestor within the specified time frame, please contact the EGA Helpdesk team. I have an account with the EGA and would like access to further datasets. How should I proceed? You need to reapply to the relevant Data Access Committee (DAC). Once the DAC has approved your application your account will be updated and an email will be sent to notify you of a change made to your account. How do I download files of the datasets I have been granted access to? The preferred method for data download and decryption is the EGA Secure Download Client. Please carefully review the provided documentation. How do I download metadata? Metadata is retrieved from the EGA webpage; you will not need to use any download client. Be informed that you will only be able to download metadata of your approved datasets. For such download, you should first log in the EGA webpage with your credentials. Then browse the metadata's dataset you have gained access and you will find a metadata download button. You may also want to have a look our metadata schema. I have forgotten or misplaced my user account password; how do I get a new one? Click on “Log in”, located in the top right corner of the EGA homepage. Then click “Forgot password”, type in your registered institutional email address, and instructions for resetting your password will be sent to you. Please check both regular and junk/spam folders. I was sent a link to set a password for my download account, but it seems like the link has expired. What should I do? The procedure is the same as the one for a forgotten password, explained in the previous question.

  Documentation access/request-data/how-to-request-data

• DAC-2023-07-05-Ritz (DAC-007)

  Full description of the dataset and all necessary information on metadata may be found under (https://zenodo.org/records/11237107): DAC-2023-07-05-Ritz (DAC-007), raw data in EGA, metadata in Zenodo (https://zenodo.org/records/11237107)

  Dataset EGAD50000001147

• Submission FAQ

  Submission FAQ Before Submission Is the EGA the right archive for my data? The most suitable archive for your data is dependent on the type of data you are wishing to submit and whether the data require public or controlled access. Public access is defined as complete and open access to all submitted data. On the contrary, controlled access, exerted by the EGA, requires formal applications to be made to access the submitted data files and metadata. EGA only accepts human-derived data subject to controlled access. If your submission contains other types of data, please choose the appropriate repository for it (see image below): ENA, EVA, ArrayExpress, BioSD and GWAS catalog.  Should your submission be subjected to controlled access? Data access conditions are normally defined in the original informed consent agreements signed by the participants involved in your study. All data submitted to the EGA is subject to controlled access. These consents prevent the derived data files, potentially identifiable, from being dispersed by open and public access. Controlled access data often refers to human data derived from medical research and consortium projects. If in doubt, consult the informed consent agreements that apply to your study The EGA enables you to hold a submission before publication. What data types can be submitted to the EGA? Data types accepted by the EGA can be split into three categories: Sequences: both in generic and platform-specific formats. Array-based: from raw signal files to processed matrices. Phenotypes: all possible phenotype formats are accepted. All manufacturer-specific raw data formats derived from major next generation sequencing platforms are accepted. Also generic sequence formats: flat reads in a FASTQ file, aligned sequences (BAM or CRAM files) as well as sequence variation files in VCF format. All array-based technologies are accepted, including raw data, intensity and analysis files, without any restriction on data formats accepted. We also accept and distribute phenotype data (associated to the samples) in almost any format: from an image to a README file. How long does a submission take? Submissions to EGA come in a variety of formats and sizes, thus it is difficult for us to exactly predict how long a submission will take. We, therefore, advise all of our submitters to allow as much time as possible to make a submission. Based on previous records, we anticipate that the submission process may take at least one month. The submitter’s familiarity with the procedures, possible technical issues that may arise during submission and the amount of data that is being submitted are the main factors that will affect the length of the submission process. However, each step of a regular submission should be considered when estimating the time it would take: Encryption of the files Upload of the files Metadata submission Archival of the files Release of the study and datasets to EGA webpage For example, the upload of the files depends on the submission size, while metadata submission mainly relies on each submitter’s expertise. Further, some steps (e.g. answering to inquiries) depend on the EGA Helpdesk team, which may take some days to be processed during busy times Is data deposited in the EGA secure? The EGA set-up consists of a secure computing facility for data processing, a shared EBI set-up for data submissions and distribution of data via data requests made through the EGA website. Data is also copied in the Barcelona Supercomputing Center (BSC) infrastructure, where all stored and distributed data is encrypted Data is encrypted along the submission process and stored securely, granting its access to authorised users exclusively. During the download process, through our Python Client or Aspera, all requested data is downloaded over secure https connections. All data at the EGA is encrypted, and only accessible (for log-in and download) through secure protocols. For further information please, visit our security overview. What documentation do I need to provide? All submissions require policy’s documentation: 'Data Access Agreement (DAA)', 'Data Processing Agreement (DPA)' and 'Authorized Submitters Formulary'. The data processors (EGA) and the data owners will also sign the DPA. Will all metadata be public? Among the submitted metadata we need to make the distinction between identifiable and unidentifiable metadata: (1) the former may allow the identification of the human the sample derived from (e.g. detailed geographical providence, personal name, family ancestry…); (2) while the latter can be used to interpret the data without compromising the anonymity of the patients. The majority of the metadata submitted to the EGA corresponds to the unidentifiable category (e.g. sequencer's model). This type of metadata is publicly available on the EGA website and other EBI resources/partners’ websites. On the other hand, some parts samples’ metadata are subject to being identifiable, and thus only accessible by authorized data requesters, with the exception of: 5 submitter-defined attributes of the sample: alias, title, subject_id, gender and phenotype. It is the submitter’s responsibility not to submit sensitive metadata in these public fields. 3 anonymised fields that pinpoint the sample record in archivals: sample’s EGA stable ID (EGAN…), BioSample ID (SAMEA…) and submitter’s center name. During Submission Are there any sample specific requirements for EGA? All samples submitted to the EGA must include the attributes of biological sex, subject ID (anonymised individual identifier) and phenotype information. These are critical for data findability and its analysis, and we highly recommend using controlled ontology terms where applicable. For example: defining tumour and non-tumour samples and/or defining disease state. The EGA recommends using the Experimental Factor Ontology Database to find ontologized terms that describe your sample phenotypes. How do I get an accession number to use in my publication? You will receive your study accession number (EGAS…) upon complete your submission, either: Programmatically. As soon as the metadata is submitted and validated your study will be assigned an accession number that will be given in the submission’s response. Manually registering your study and relevant metadata using the online metadata submission tool: the EGA submitter Portal. How are files uploaded to the EGA? Data files are uploaded into private submission drop boxes (i.e. environments to which you are granted access and where you can transfer your files) using INBOX or FTP. These spaces are provided as part of the submission procedure. Before uploading any file, you must encrypt your files, . Only encrypted files shall be uploaded to the drop boxes. Why does data need to to encrypted for my submitted files? It is one of the security steps the EGA has implemented. In case of a security breach, people without the proper encryption key will not be able to read or use the information that could have been leaked. This measure is essential when working with sensitive data, such as controlled access human data. All submitters must use crypt4gh to create EGA compliant files prior to uploading them. This encryption is GPG-based, using EGA’s public key. Why are my files not available if I see them in the INBOX? There exists a time window between the data upload and the availability of such files via the Submitter Portal. For this reason, some metadata (run and analysis objects) cannot be registered until at least 24 hours after the files have been uploaded to your box. Why are MD5 sum values generated for my submitted files? We require pre- and post- encryption MD5 (message-digest) checksum values to be provided for all submitted files. These 128-bit values are computed using the content of each file, creating unique sequences that allow us to ensure that file integrity has been maintained during the transfer process. In other words, if the MD5 checksums we generate and those you generated match, we infer that the content of the transferred files is correct (i.e. files are not corrupted or truncated). MD5 checksums are computed automatically using the crypt4gh tool provided. Your submission will not be accepted and may be significantly delayed if you do not provide MD5 checksum values for all data files in the required format. How can I check if my files are correctly uploaded to the inbox? It is important to check the status pf your file so you know whether your files are in the inbox, being processed, or if there is any issue with one of them. In order to check this, you should: Look for the file locally. Drag and drop it to the file table. Then bars will appear on the table, which means that we are processing it. Green: The files checksum are correct and your file will move to “ingested files”. No further actions are needed from your end.. Red: The files checksum does not match and your file needs to be re-uploaded. Please re-upload relevant files to your inbox using the same path. After Submission How do I use my accession number in my publication? We suggest the use of the below template, using your study accession ID (EGAS…) : Data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found at https://ega-archive.org and "The European Genome-phenome Archive of human data consented for biomedical research" Your study ID will be the one that groups your whole submission, and thus its usage is recommended as such. Nevertheless, all metadata submitted to EGA hold a unique and persistent identifier (starting with EGA…) that can be used to identify specific records. For example, you could reference a specific dataset (EGAD…) or sample (EGAN…) in your publications (see full list of identifiers). How do I make my data searchable? Once you have finalized your submission, you can schedule the data release. Please take into account that the release process needs time for the files to be archived in our system, and for the Helpdesk team to validate your submission. Can I withdraw (meta)data from the EGA? We have methods in place for the secure removal of deposited (meta)data. Contact EGA-helpdesk for further details. EGA complies with FAIRness of (meta)data, and thus, even when the data is removed we keep an entry for their identifiers in our system. In other words, we execute a soft delete on canceled objects (e.g. a study): metadata is still stored in our systems, but it loses all links, cannot be queried and data files cannot be retrieved anymore. The reason behind this behaviour is so that queries using withdrawn data properly respond back (see example of a canceled study). What happens to the data once it has been submitted to the EGA? When the data is submitted, the submitter can choose either keep their data private or schedule the release of their data.

  Documentation submission/metadata/submission/FAQ

• DAC for EGA study: "ctDNA residual disease analyses during perioperative nivolumab or nivolumab plus ipilimumab in resectable diffuse pleural mesothelioma"

  This DAC regulates access to the whole-exome sequence data for the study "ctDNA residual disease analyses during perioperative nivolumab or nivolumab plus ipilimumab in resectable diffuse pleural mesothelioma".

  Dac EGAC50000000706

• Hi-C for Junvenile Pilocytic Astrocytomas

  5 Hi-C datasets (4 JPA and 1 LGG). Hi-C data for the remaining 5 JPAs used in our paper as well as all controls have been uploaded to EGA under EGAS00001005476.

  Dataset EGAD00001009044

• NTNU Data Access Committee for “ProstOmics: spatial and bulk multi-omics of prostate cancer” datasets archived in Federated EGA Norway

  The ProstOmics project of NTNU contains spatial and bulk multi-omics datasets of prostate cancer, and access request to these datasets are handled by this Data Access Committee on behalf of NTNU.

  Dac EGAC50000000277

• Paired Biopsy Project: West Coast Dream Team

  This project contains the 16 WGS tumor samples and the corresponding 15 WGS normal tissue samples (germline control) not yet deposited in the public domain (e.g., EGA, dbGaP) at the time of submission of the manuscript (Zhu et al.)

  Dataset EGAD50000000473

• Boyes Lab - DAC policy

  Access to this data is controlled. Upon request from a third party for access to the data, a separate Data Sharing Agreement would be put in place between the University of Leeds and the third party prior to EGA granting access to the data to the third party.

  Dac EGAC50000000283

• The EGA joins EUCAIM, the European project powering AI and imaging in cancer research

  EUCAIM (EUropean Federation for CAncer IMages) is the cornerstone of the European Cancer Imaging Initiative, one of the flagships of the Europe’s Beating Cancer Plan (EBCP). The European Genome-Phenome Archive (EGA), as member of the EUCAIM consortium, attended the kick-off meeting organized this week in Brussels for the launch of the Initiative. The EGA will contribute to the project with the experience gained in the deployment of our federated network, the Federated EGA (FEGA), and the experience gained as partners of EuCanImage (AI4HI initiative) contributing to the definition of common data models, ontologies and data standards. The ultimate goal of the project is to unlock the power of imaging and Artificial Intelligence for the benefit of cancer patients, clinicians and researchers. The consortium will deploy a pan-European digital federated infrastructure hosting cancer-related images, and associated pathology, molecular and laboratory data from Real-World. This endeavour will provide a comprehensive dashboard for imaging data discovery, federated search, metadata harvesting, annotation and distributed data processing. EUCAIM joins 76 partners, gathering the experience and previous effort made by the different repositories of the AI4HI initiative, European Research Infrastructures and national/regional repositories. Find out more information about the EUCAIM launch here

  Blog the-ega-joins-eucaim

• Genome-wide SNP and CNV analysis identifies common and low-frequency variants associated with severe early-onset obesity

  We performed SNP and copy number variation (CNV) association analyses in 1,509 children with obesity at the extreme tail (&gt;3 s.d. from the mean) of the BMI distribution and 5,380 controls. The control samples were made available from the EGA with accession numbers EGAD00000000021 and EGAD00000000023.

  Study EGAS00001000878

• Submitter Portal API

  Submitter Portal API The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have an ega-box (submission account), you can skip this step.  Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal-api

• 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

• Placeholder

  Dac EGAC00001003297

• dummy

  Dac EGAC00001000681

• NSCLC_DAC

  Dac EGAC00001001009

• DAC_SMC

  Dac EGAC00001001083

• -

  -

  Study EGAS00001005142

• AHA_Uganda_Study_DAC

  Dac EGAC00001003615

• Dataflow

   

  Documentation about/ega/dataflow

• Cancer Discovery Hub (CDH), National Cancer Center Singapore

  This is a DAC for data deposited into EGA generated by Cancer Discover Hub, NCCS. The use of datasets in this portal is solely for research and academic use only, uses other than the have to be approved by the relevant DAC members.

  Dac EGAC50000000039

• Data set for pan.met study

  The dataset referenced by EGA Study ID EGAS00001004208 includes 20 human exome sequencing data and 11 human RNA sequencing data from tumor or normal tissues. Each sequencing data includes two pair-end short read files in fastq format.

  Dataset EGAD00001005957

• EGA metadata schema

  EGA Schemas In this page, you will find information on how the European Genome-phenome Archive (EGA) manages its metadata standards using both XML Schema Definition (XSD) and JavaScript Object Notation (JSON) formats. If you are not sure what this means, you may want to explore our brief metadata introduction. This information may be of your interest if you are planning to learn more about how the EGA is built and how to wrap around it for other processes. Nevertheless, if you are a common user (e.g. submitter or requester), you would not have to worry about these schemas nor their format, since they are implemented in user-friendly ways for you. Metadata standards are rules that define how to format and structure data of metadata objects (i.e. entities), like EGA's samples or experiments in a consistent manner. These objects are the nodes of the metadata model of the EGA (Figure 1). Figure 1. Diagram of EGA's metadata model. The model's building blocks are objects (e.g. sample), which can reference each other (e.g. an experiment referencing the used samples). Once your files are uploaded, they can also be referenced by Runs and Analyses. The submission object is an object itself that compiles many others. At EGA, we inherit our metadata schemas from the European Nucleotide Archive (ENA), and we have expanded them to include bespoke objects such as "Policy", "Dataset", and "DAC" (Data Access Committee) for our specific use-case: handling sensitive human data. See below a list of all our metadata objects and some context for each. Metadata Object EGA accession Description Examples of metadata fields Study EGAS… Information about the study Study type, study title, study abstract… Sample EGAN… Information about the used samples in the experiment or analysis Taxon ID, scientific name, biological sex, phenotype… Experiment EGAX… Information about the performed experiment Used libraries, sequencing platform, reference to the used samples… Analysis EGAZ… Contains information about the analysis Type of analysis, used assembly, reference sequence… Run EGAR… The run holds information about the files containing the raw reads generated in a run of sequencing Platform, spot descriptor, raw file references… DAC EGAC… Contains information about the Data Access Committee (DAC) DAC contacts, contact emails… Policy EGAP… Contains the Data Access Agreement (DAA) and policy which its usage complies with Policy text, data use ontologies (DUO) codes… Dataset EGAD… Contains the collection of runs/analysis to be subject to controlled access Dataset type, compilation of Run's and Analysis' IDs There are two different sets of schemas, based on their formats, in which the EGA accepts metadata: XSDs (for XML files) and JSON Schemas (for JSON files). EGA's XML Schema Definition . When programmatic submissions are pushed through the European Bioinformatics Institute (EBI) system, XML format is used. The schemas that are applied for this format are defined in XML Schema Definition (XSD) files, which can be found at ENA's GitHub repository. You can find more information on how to validate and submit your data programmatically in our programmatic submission documentation. Furthermore, see at our GitHub repository some XML examples with either made-up values (similar to what you would submit) or descriptive values for each field (just for documentation). EGA's JSON Metadata Schemas . When programmatic submissions are pushed through the Centre for Genomic Regulation (CRG) system, JSON format specifications are used instead. See the full JSON specifications for further details. In conclusion, the EGA metadata schemas are crucial for maintaining the quality and consistency of submitted data. By understanding and following the rules outlined in these schemas, you can ensure that your submissions comply with the EGA's standards and contribute to a valuable and accessible genomic resource. Sample checklists Besides the standards in our schemas, we have another layer called Sample checklists. These are another system that the EGA inherits from ENA, and specifies what attributes are required or allowed for a sample object. The EGA uses these checklists to enforce that, for example, a sample object has the three mandatory attributes: subject ID, sex and phenotype of the individual the sample was taken from. When you submit to EGA, our checklist is automatically selected by default.

  Documentation submission/metadata/ega-schema

• DAC_for_study___T2D_RV_pilot_NTR

  Dac EGAC00001000029

• DAC_for_study___PD_Progressive_Hearing_Loss

  Dac EGAC00001000059

• DAC_for_study___SEQCAP_Otosclerosis_gene_discovery

  Dac EGAC00001000060

• DAC

  Dac EGAC00001002649

• EGAC00001000680_IBIOM

  Dac EGAC00001000680

• Data_access_NWA_SNP_data

  Dac EGAC00001002962

• DAC AAV

  Dac EGAC00001003000