LogoLogo
OT PlatformOT GeneticsCommunityBlog
  • Open Targets Platform
  • Getting started
  • Target
    • Tractability
    • Safety
    • Chemical probes & TEPs
    • Baseline expression
    • Molecular interactions
    • Core Gene Essentiality
    • Pharmacogenetics
  • Disease or Phenotype
    • Clinical signs and symptoms
  • 🆕Variant
  • 🆕Study
  • Drug
    • Clinical Precedence
    • Pharmacovigilance
    • Pharmacogenetics
  • 🆕Credible Set
  • Target–disease evidence
  • Target–disease associations
  • 🆕GWAS & functional genomics
    • Data sources
    • Fine-mapping
    • Colocalisation
    • Locus-to-Gene (L2G)
    • Gentropy
  • Bibliography
  • Web interface
    • Associations on the Fly
    • Target Prioritisation
    • Evidence pages
    • Entity profile pages
  • Data and code access
    • Download datasets
    • Google BigQuery
    • GraphQL API
    • 🆕Platform infrastructure
    • 🆕Data pipeline
  • 🆕FAQs
  • Release notes
  • Citation
  • Licence
    • Terms of use
  • Partner Preview Platform
Powered by GitBook
On this page
  • Introduction
  • GitHub repositories
  • Data and evidence
  • Gentropy
  • Orchestration
  • Unified pipeline

Was this helpful?

Export as PDF
  1. Data and code access

Data pipeline

The Open Targets data pipeline is a complex process orchestrated in Apache Airflow, and it is divideded into data acquisition, transformation and data output.

Introduction

The data pipeline is composed of multiple elements:

  1. Data and evidence generation processes

  2. Input stage

  3. Transformation stage and ETL processes

  4. Output stage

  5. Gentropy-specific processes

  6. Orchestration

GitHub repositories

Data and evidence

  • curation — Open Targets curation repository

  • evidence_datasource_parsers — internal pipelines used to generate evidence

  • json_schema — evidence object schema used for evidence and association scoring

  • OnToma — Python module to map disease or phenotype terms to EFO

Gentropy

  • gentropy — Open Targets' genomics toolkit

See here for more info on the Gentropy pipelines.

Orchestration

  • orchestration — Open Targets data pipelines orchestrator

See detailed orchestration documentation here.

The Platform ETL (“extract, transform, and load”) and the Genetics ETL were separate processes before, but they are now merged into one single pipeline. This means that the data produced for both Genetics ETL and the Platform are released at the same time. Herein, we refer to this joint pipeline as the "unified pipeline".

The orchestration occurs on Google Airflow using Google Cloud as the cloud resource provider. The logic of the orchestration is based on the steps. The combination of steps forms directed acyclic graphs (DAGs).

The unified pipeline uses many static assets (link), like Open Targets related data and data needed to run Genetics ETL.

Unified pipeline

  • otter — Open Targets' Task ExecutoR i.e. scripts that process and prepare data for our ETL pipelines

  • platform-etl-backend: ETL pipelines to generate associations, evidence, and entity indices

  • platform-etl-openfda-faers: ETL pipeline to process Open FDA adverse events data

  • platform-etl-literature: ETL pipeline to generate similar entities and publications

  • platform-output-support: scripts for infrastructure tasks and generating a Platform release

If you have further questions, please get in touch with us on the Open Targets Community.

PreviousPlatform infrastructureNextFAQs

Last updated 3 months ago

Was this helpful?

🆕
Schematic overview of Open Targets pipelines