The EGA provides submitters with a completely free, secure and permanent archiving solution for sharing data worldwide.
Submitters retain complete ownership over data and may submit data in stages and control access permissions to the data once submitted.
We support controlled access for named consortium members prior to publication; typically 6-12 months pre-publication.
Each organization that has deposited data in the EGA is given a publically viewable website on our system, which contains a user submitted description of the organization, the experiments and data used in the study together with a links back to the organization website.
In addition, each study is assigned a stable and unique accession number that may be referred to in future publications.
Throughout the data submission process the EGA will continue to consult with submitters to ensure that the data is accurately represented, that the formal data access application is in place and the granularity of data access has been set correctly.
We also provide a EGA helpdesk, which provides support to users and submitters.
Submissions made to the EGA will also be cross-linked in the study catalog at the NCBI resource, The Database of Genotypes and Phenotypes (dbGAP), with a link to the study in EGA. However, data files will only be able to be obtained from the EGA.
The EGA accepts de-identified data with an approved Data Access Consortium (DAC) plan; which is responsible for all data access decisions.
Data that does not need to be subject to controlled access can be submitted to other EBI archive resources.
You will receive your accession number upon the submission of your study.xml or registering your study using the online metadata submission tool (Webin). Full instructions of the submission process will be provided in your submission pack.
We suggest adapting and inserting the following paragraph in your publication:
“Genome data has been deposited at the European Genome-phenome Archive (EGA) which is hosted at the EBI and the CRG , under accession number EGAS#."
Further informatiion about the EGA can be found at https://ega-archive.org and is also availabale in the publication "The European Genome-Phenome Archive of human data consented for biomedical research"
A Data Access Committee (DAC) is responsible for making the data access decisions for the data submitted. A DAC may consist of a single individual or group of individuals.
EGA accounts are created and managed by an authorised DAC contact using the EGA DAC admin tools. Information regarding the use of these tools is sent to each DAC contact.
The named DAC contact may also send data applicant details to the firstname.lastname@example.org. Details must include the datasets to which access has been approved, registered email address and full institutional address of the data applicant.
The EGA will not create accounts without the required information and if the request is made by a DAC contact not specifically authorised to approve access, as should be stated in the DAC Access policy document.
Our accepted data types include all manufacturer raw data formats from the array-based and next generation sequencing platforms. Processed or analysed data, such as genotypes and structural variants as well as additional information (e.g. quality scores and intensity values) may all be uploaded to our databases.
We also accept and distribute phenotype data that may be associated with the samples.
Email our EGA-Helpdesk for more information
The EGA set-up consists of a secure computing facility for data processing and a shared EBI set-up for data submissions and distribution of data via data requests made through the EGA website.
All distributed data is encrypted and can only be accessed using an encryption key, which is distributed to uses by post or courier.
Our security protocols for log-in and downloading data have been successfully applied to other EBI-hosted EU projects containing restricted data.
Data files are uploaded into private submission drop boxes using FTP or Aspera protocols, which are provided as part of the submission procedure.
All submitters must use EgaCryptor, which encrypts, generates md5sum's.
Data files may are then uploaded using FTP or Aspera.
Submission, archiving and data processing for distribution can take several weeks, depending on the size of the data files you intend to submit.
Please contact us in advance, to ensure that your data is ready to release when required.
Please note: The EGA operates a queing system for submission processing. As a result, one submission CANNOT be prioritised over another.
All data submitted and distributed to the EGA must be encrypted with GnuPG, which ensures that the data is kept secure and accessed exclusively by permitted EGA personnel and users. All submitters must use the EgaCryptor to create EGA compliant files prior to upload.
Why are md5sum values generated for my submitted files?
We require pre and post encryption md5sum values to be provided for all submitted files, so that we can ensure that file integrity has been maintained during the transfer process. Md5sums are generated automatically using the EgaCryptor tool provided.
**YOUR SUBMISSION WILL NOT BE ACCEPTED AND MAY BE SIGNIFICANTLY DELAYED IF YOU DO NOT PROVIDE MD5SUM VALUES FOR ALL DATA FILES iN THE FORMAT REQUIRED**
The turnaround time for submissions upto 10TB of data is 90 days. We strongly advise all submitters to explore the use of Aspera for large and/or long distance transfers and if necessary to contact IT departments for further advice. The EGA helpdesk is happy to field technical queries regarding the use of Aspera.
**PLEASE CONTACT THE EGA HELPDESK PRIOR TO SENDING YOUR HARDISK**
Encrypted data files can be transferred to a user supplied hard drive, which should be sent to:
Mr Jeff Almeida-King
The European Genotype Archive,
European Bioinformatics Institute
Wellcome Trust Genome Campus
Cambridge CB10 1SD
To ensure that no custom charges are applied, please describe the goods as 'Intellectual Property Rights - no commercial value'.We reserve the right to refuse delivery or seek re-imbursement of costs if this instruction is not followed.
We have methods in place for the secure removal of deposited controlled access data. Contact EGA-helpdesk for further details.
After submission the EGA team will process the data into databases and archive the original files. Members of the EGA will then consult with the submitter to ensure that the data is represented accurately on the website and the formal arrangement for data access application has been set correctly.
If you have any further questions please do not hesitate to contact the EGA Helpdesk: email@example.com