What are the key stages of the EVA submission process?

Prepare your data and metadata

Submissions to the EVA consist of VCF file(s) and metadata that describe sample(s), experiment(s), and analysis that produced the variant and/or genotype call(s). This metadata is described in an Excel template. You can find a mocked-up version of this template that has been completed for a fictional study on our website (metadata example file).

Submit

Submissions to the European Variation Archive (EVA) can be made either through the eva-sub-cli command-line tool or by contacting the EVA Helpdesk.

The eva-sub-cli tool is a command-line interface tool for data validation and upload. The tool enables users to perform validation and submission to the EVA directly, without requiring interaction with our helpdesk team. For instructions on how to install and use eva-sub-cli, please see our documentation. This method has faster turnaround times, but may be more suitable for more technical users. Before submitting data through eva-sub-cli, please make sure you have a Webin Account.

Alternatively, submitters can initiate a submission by contacting the EVA helpdesk, after which they will be provided with a private FTP location and guidance from the EVA team to upload their VCF files and metadata templates. Once the files are uploaded and successfully validated, the EVA processes the submission and assigns accession numbers, which are communicated to the submitter by email. 

Receive

The EVA aims to process submissions within two business days. Accession numbers will be sent via email to the submitter upon successful archival of the deposited data.

What are the requirements for submission to the European Variation Archive?

EVA accepts submission of genetic variation data based on three criteria:

1. The genome assembly used is International Nucleotide Sequence Database Collaboration (INSDC) registered, or will be at point of submission

2. The variation data is described in valid VCF file(s) – this can be tested prior to submission using the EVA VCF validation suite

3. Submitted variants have allele frequency values and/or genotypes