Skip to content

Data submission


FEGA is still in the pilot phase, so no submissions can be made to the service. The expected launch of the service is in the beginning of year 2023. We will process submissions in the order we have received the support requests. In addition to the legal agreements listed on this page, there needs to be a service agreement between CSC and the data controller specific for FEGA service. Make sure before starting submitting any data that all these legal agreements are in place. This user guide is still preliminary, and changes to the technical instructions are expected before the launch of the service.

Submission process overview

FEGA submission process overview

Step 1: Application form

Submission to the Finnish FEGA service starts with authorization of a person(s) that will represent data owner organization during the submission process. The FEGA service will provide customer support only to the named person(s).

To begin the submission process, please fill in the application form with contact information, details about the data submission type and information about the data controller. Send the filled form via email to (subject: Federated EGA). You will receive further instructions.


  • This workflow is specific for submitting datasets to Finnish FEGA. Central EGA and other FEGA nodes have different data submission processes.

  • Data submission might take up to a month or more. Therefore, please get in touch with us well in advance (before submitting your manuscript to a scientific journal). In this way, we can offer proper support and guide you during the entire process.

  • Please use the same email thread throughout the whole submission process.

Each user must provide a series of legal agreements to confirm that they have the authority and permission to deposit data in FEGA. Download the necessary documentation below and share the agreements concerning the data controller with the legal service of your home organisation. Please note that your organisation may already have some required agreements in place with CSC. We will provide support if additional agreements are needed. Send the finalised documents via email to by replying to the previous email of the CSC helpdesk.


The required legal documents state the roles of a data processor and a data controller, which are defined in the General Data Protection Regulation (GDPR). CSC acts always as a data processor. In most research projects, the data controller is an academic organisation or other legal entity. The ownership of the data does not change by using this service.

Here’s a list of the required documents:

  • Data Processing Agreement (DPA). A data processing agreement (DPA) is a contract between the data controller and the data processor. It regulates the particularities of data processing – such as its scope and purpose – as well as the rights and duties between the controller and the processor.

  • CSC General terms of use.

  • Description of the data processing activities.

  • Data Protection Impact Assessment (DPIA). In case you need to draft a DPIA, you can find the technical and organisational security measures for the protection of sensitive data in CSC Sensitive Data Services available for download here.

  • Data Access Agreement (DAA). In addition to the legal documents listed above, you should provide a copy of the DAA. The DAA is a contract between the Data Access Committee (DAC) and an applicant. The DAA includes all the policies regulating data re-use (e.g. data use, publication, download, or access) and it will be linked to each submitted dataset. It might also include a data transfer agreement (needed when researcher from non-EU/non-EEA are accessing the data via SD Desktop). For more info and examples, please check DAC and policy documentation and Data Use Conditions on EGA webpage.

  • Names and contact information of the Data Access Committee.

Step 3: Credentials

Once the legal agreements between the data controller and CSC are finalised, you can request the central EGA credentials by sending an email to the central EGA helpdesk at You will receive the credentials via email.


Central EGA credentials, including a username (format: ega-box-NNN) and a password, are required for the encryption and data upload to Finnish FEGA and for the metadata submission to the submitter portal of central EGA.

Step 4: Data formats

Before uploading the data to FEGA, you must prepare the datasets and verify the data formats. Some examples of the accepted formats are listed below.


A dataset is usually defined as a set of files belonging to the same experiment and data type. One study can be linked to multiple datasets. Your study may include both sensitive (e.g. human genetic or phenotypic information) and non-sensitive data (e.g. viral sequences, metabolites). Only the sensitive data can be submitted to FEGA. The non-sensitive data can be published openly in appropriate repositories. In this case, the sample accessions generated at the repository should be referenced in the FEGA submission.

Sensitive Data:

  • sequence data: CRAM, BAM, FASTQ, VCF formats

  • array data: Data from all types of array-based technologies, such as genotypes, gene expression, methylations etc. is accepted. Central EGA also recommends submitting raw data (IDATs, CELs, final reports) and any analysis files.

  • metagenomics: EGA has adopted the suite of Minimum Information about any (x) Sequence (MIxS) standards to describe data of this type.

  • phenotypic information: No specific format. Where possible, we recommend using the Experimental Factor Ontologies. To search for the correct ontology terms and to describe your phenotypic data, check the Ontology Lookup Service (OLS) developed by EMBL-EBI.

  • linking files: If non-sensitive datasets belonging to the same study have been submitted to a specific repository, the samples can be linked to sensitive information submitted to FEGA for the same sample. The datasets should have different anonymised sample IDs in each archive. The IDs obtained in the appropriate archive can then be referenced in the FEGA submission. For example, the sample ID can be linked in an additional .txt file that can be added to one of the sensitive datasets above.

Non-sensitive data:

Non-sensitive data (or open data) needs to be submitted in appropriate archives. For example, sequences to the ENA European Nucleotide Archive, variants to EVA European Variation Archive, array-based to ArrayExpress – functional genomics data, phenotypes to BioSamples and GWAS summary statistics to the GWAS Catalog.


For more information about data types and formats, check Central EGA webpage or contact us at (subject: Federated EGA).

Step 5: Data encryption and upload

Next, you can upload the data to Finnish FEGA. Each file uploaded to Finnish FEGA needs to be encrypted.


The data is encrypted with a FEGA public encryption key using crypt4gh, a tool designed to encrypt and share human genetic data according to the Global Alliance for Genomics and Health (GA4GH) standard.

You can carry out the encryption and upload steps using:

  • Fi-FEGA upload application. The Fi-FEGA upload application (graphical user interface) can be used to encrypt and upload files or folders automatically to Finnish FEGA.


  • Command-line interface. Data encryption with crypt4gh CLI and data upload with sftp CLI. If you prefer to use the command-line interface, you can find information on the encryption and upload step below.

Fi-FEGA upload application

  1. You can download the Fi-FEGA upload application specific to your operating system from the GitHub repository: Linux, Mac or Windows. After downloading and unzipping the file, you can find the application in your download folder. When you open the application, you might encounter an error message. In this case, click on More info and verify that the publisher is CSC-IT Center for Science (or in Finnish: CSC-Tieteen tietotekniikan keskus Oy) and click on Run anyway.

  2. Next, download the Finnish FEGA public encryption key.

  3. Open the upload application and click on Load recipient public key. This opens a file browser that you can use to select the Finnish FEGA public encryption key (example_ega.key). Next, click on Open.

  4. Click on Select file to upload or Select directory to upload to upload a single file or an entire folder.

  5. Next, you need to fill in the SFTP (or secure connection) credentials, which correspond to your Central EGA account username. In SFTP Username, write your EGA username (ega-box-NNN). In SFTP Server, write the following: Loading an SFPT key is not required for data uploads to FEGA.

  6. Click on Encrypt and upload files. The tool will ask the SFTP Passphrase, which corresponds to your Central EGA account password. After clicking on OK, the application will start the data encryption and upload.

  7. The application is not provided with a progress bar. Data encryption and upload can take minutes or up to several hours, depending on the size of the dataset. Data upload is successfully finished when the activity log in the application visualises the following message: Disconnecting SFPT. SFPT has been disconnected.

  8. Please inform the Finnish FEGA helpdesk via email ( when you have completed the data encryption and upload to Finnish FEGA. You will receive further instructions for the metadata submission.

Fi-FEGA upload application

Command line interface

Data encryption with crypt4gh CLI:

  1. Python 3.6+ is required to use the Crypt4GH encryption utility. If you need help with installing Python, please follow these instructions.

  2. Open a terminal and install Crypt4GH directly with pip tool:

    pip install crypt4gh

  3. To encrypt a file with the Finnish FEGA public encryption key use crypt4gh encrypt command:  

    $ crypt4gh encrypt  --recipient_pk < example_file.txt > example_file.txt.c4gh

Where the syntax --recipient_pk defines the public key used to encrypt the data. In this case, Finnish FEGA public key example_file.txt.c4gh defines the input file and output encrypted file.

Data upload with sfpt CLI (default in Linux and Mac OS):

Open a terminal and transfer the encrypted files or directory with the following syntax, where ega_user is the EGA credentials username ega-box-8903:

sftp -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -P 9002 <ega_user>

Please inform the Finnish FEGA helpdesk via email ( when you have completed the data encryption and upload to Finnish FEGA. You will receive further instructions for the metadata submission.

Step 6: Metadata submission

Next, you can describe all the information related to your study, i.e. metadata, using the central EGA submitter portal or programmatically. The public metadata will be published on the EGA website to facilitate data discovery and re-use.

Log in to the submitter portal using the EGA credentials (username: ega-box-NNN and password). Specific guidance on EGA submitter portal can be found on EGA website: user guide and video tutorials.

Using the submitter portal, you can register the following metadata objects:

  • Study. Information about the sequencing study.

  • Samples. Information about the sequencing samples.

  • Experiments. Information about the sequencing methods, protocols, and machines.

  • Runs. Samples, experiments, and files are linked through runs. Appropriate objects for FASTQ and BAM/CRAM submissions.

  • Analysis. References the analysis (BAM) files. Associated with samples and study. Analysis should be only be used for BAM/BAI pair, VCF and phenotype linkage to samples. The analysis is an EGA specific metadata object that links Samples, to Files.

  • DAC. Contains information about the Data Access Committee (DAC).

  • Policy. Contains the Data Access Agreement (DAA). Associated with DAC.

  • Dataset. Contains the collection of runs/analysis data files to be subject to controlled access. Associated with Policy.

After data release, each of these objects will be assigned with a permanent identifier or unique accession number.


  • Study, Samples, DAC, and Policy metadata can all be registered before uploading files, while run and analysis objects cannot be registered until at least 24 hours after the files have been uploaded to Finnish FEGA.

  • If you are performing array-based submission(s), the submitter portal should only be used to register the Study, Samples, Data Access Committee (DAC), and Policy metadata objects. In contrast, the other metadata objects need to be registered using an excel template.

After uploading the data to Finnish FEGA, you will receive a dataset application link for each dataset via email from the CSC helpdesk. The dataset application links must be added to each metadata submission in EGA submitter portal. In order to add the dataset application link to the submission, you must register a new Policy metadata object for each dataset. Create a policy and select the checkbox “The policy has an url.” under the Policy field. Write the dataset application link in the popping up “Policy URL” textbox.


If someone wants to apply access to your dataset stored in Finnish FEGA, they must click the dataset application link on the EGA website. The link will direct the user to the application form in SD Apply. SD Apply is a service for applying access rights to sensitive datasets stored at CSC.

Step 7: Data release

To finalise your submission, write to to confirm that the submission can be released and add the following information from the submitter portal:

  • Name of the submission (as on the submitter portal)

  • Study Accession number (EGAS)

  • Dataset Accession number (EGAD)

  • Appropriate Data Use Ontology codes (DUO). You can find more information in Data Use Conditions on EGA webpage.

CSC helpdesk and central EGA helpdesk will work together to complete the release process. You will receive confirmation of successful submission and accessions suitable for publication, grants, etc. from the CSC helpdesk.

Last update: December 9, 2022