Dipper is a Python package to generate RDF triples from common scientific resources. Dipper includes subpackages and modules to create graphical models of this data, including:
Models package for generating common sets of triples, including common OWL axioms, complex genotypes, associations, evidence and provenance models.
Graph package for building graphs with RDFLib or streaming n-triples
Source package containing fetchers and parsers that interface with remote databases and web services
The dipper-etl.py script wraps all of the source parsers, enabling users to specify one or more sources to process. The general strategy is that there is one class per data source. We define the files to be fetched, any file scrubbing, and then the parsing methods. As the files are parsed, triples are loaded into an in-memory graph. This graph is then typically dumped into triples in turtle format. For testing purposes, a subset of the graph is also dumped to *_test.ttl.
Data generated from this pipeline can be used in a variety of ways downstream. We recommend loading the data into a triple store or graph database that is optimized for use with ontologies, such as BlazeGraph. We also maintain SciGraph, an application that loads RDF and OWL into Neo4J. Smaller files can be loaded into an ontology editor like Protege.
Dipper requires Python 3.6 or higher.
To run the dipper pipeline, or use it as a python module, install the latest stable version with pip:
pip3 install dipper
To install the development branch, clone the repository and run:
pip3 install -e /path/to/git/dipper
Or alternatively without cloning,
pip3 install git+git://github.com/monarch-initiative/dipper.git
you can run the code by supplying a list of one or more sources on the command line. some examples:
dipper-etl.py --sources impc,hpoa
furthermore, you can check things out by supplying a limit. this will only process the first N number of rows or data elements
dipper-etl.py --sources hpoa --limit 100
you can also run the stand-alone tests in
tests/test_* to generate subsets of the data and run unittests
other commandline parameters are explained if you request help:
To build locally, clone this repo and install the requirements using pip.
Required external python packages can be found in the requirements.txt
Optional source specific python packages can be found in ./requirements/
Note, Dipper imports source modules dynamically at runtime. As a result it is possible to build a core set of requirements and add source specific dependencies as needed. Presently this only implemented with pip requirements files. For example to build dependencies for MGI:
pip3 install -r requirements.txt pip3 install -r requirements/mgi.txt
To install dependencies for all sources:
pip3 install -r requirements.txt pip3 install -r requirements/all-sources.txt
If you encounter any errors installing these packages using Homebrew, it could be due to a curent known issue in upgrading to pip3. In this case, first force reinstall pip2 (
pip2 install --upgrade --force-reinstall pip) and then install the package using pip3 (eg.
pip3 install psycopg2.)
The full documentation, including API docs, can be found on read the docs.
The following sources have been mapped:
Each source has a corresponding script at https://github.com/monarch-initiative/dipper/tree/master/dipper/sources
Many sources have a corresponding concept map diagram that documents modeling patterns implemented in SciGraph, via Dipper-mediated transformation into Monarch's common target model. These are stored in the ingest-artifacts repo.
Don't see a parser you want? Feel free to request a new one, or you could contribute a Source parser to our suite! Please see our best-practices documentation for details on writing new Source parsers using Dipper code, and make a pull request.
Our identifier documentation as referenced in our recent paper on identifiers(doi:10.1371/journal.pbio.2001414)[https://doi.org/10.1371/journal.pbio.2001414]
For instance, Monarch has type-agnostic in-house redirection rules like
https://monarchinitiative.org/<curie> where the curie is in prefixed notation like
The kinds of external identifiers that we reference are listed here https://github.com/monarch-initiative/dipper/blob/master/dipper/curie_map.yaml
For more information on our identifiers, see here.
The Dipper data pipeline was born out of the need for a uniform representation of human and model organism genotype-to-phenotype data, and an Extract-Transform-Load (ETL) pipeline to process it all. It became too cumbersome to first get all of these data into a relational schema; so, we decided to go straight from each source into triples that are semantically captured, using standard modeling patterns. We are currently working on tooling around defining, documenting, and constraining our schema as biolink models.
A manuscript on the Dipper pipeline is in preparation. In the meantime, if you use any of our code or derived data, please cite this repository and doi: 10.1093/nar/gkw1128.