Skip to content

Research Data File Submission Guide

To submit Research Data Files to GHGA, the GHGA Connector is used to deposit files in an upload box. A Data Steward creates an upload box for each submission with an appropriate storage volume and can grant access to verified users in the GHGA Data Portal. Files are encrypted and checksums are calculated on the fly. There is no need to prepare or encrypt files yourself before starting an upload.

Flowchart with icons showing the four steps to submit Research Data Files: Get Portal Access, Generate Crypt4GH Keys, Create Access Token, and Upload Data & Submit Box – as described in the text below on this page.

Data Processing Contract

A Data Processing Contract has to be signed by all parties before a Data Steward is allowed to generate an upload box and enable the submission of Research Data Files.

Get Portal Access

  1. Register in the GHGA Data Portal using your LS ID.
  2. Verify your account with a valid Independent Verification Address (IVA).
  3. Communicate your account (name/email) in a ticket to the GHGA Helpdesk.

Generate Crypt4GH Keys

The GHGA Connector uses a Crypt4GH keypair to encrypt your files as they are uploaded, just as it does to decrypt files on download. If you don't already have a keypair, generate one as described under Crypt4GH Keys in the GHGA Connector documentation. Keep your private key safe — only the public key needs to be shared with GHGA.

Create Access Token

Once a Data Steward has granted you access to an upload box, generate an access token for it in your User Account by clicking Create Token in the "Research Data Upload" tab and entering your public Crypt4GH key.

Upload & Submit Box

Start the file deposition as outlined in the GHGA Connector documentation, which supports two ways to deposit files: a TSV-driven batch-upload for depositing many files at once, or an interactive ubox shell for uploading single files and managing the upload box. Once the submission is complete, click Submit in the User Account to close the box.

Matching file aliases to metadata

Each uploaded file's alias must exactly match the file alias in your metadata submission, so the two can be linked by the GHGA services. Depending on the upload method, this alias is either set explicitly (the second column of the batch-upload TSV) or, unless overridden with --alias, defaults to the file name itself (ubox upload). Mismatched aliases are a common cause of validation errors — please double-check them before closing the upload box.