Genomic Epidemiology Entity Mart
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

The Genomic Epidemiology Entity Mart

The Genomic Epidemiology Entity Mart (GEEM) is a portal for examining and downloading ontology-driven specifications for standardized data components. The portal aims to provide term reviewers and software developers with ways to utilize application ontology contents (a collection of terms and relations from other ontologies that combine to model the operation of some domain) without the need to be trained in ontology curation or querying. Ontology-driven standards benefit from features of open-source published OWL 2.0 ontologies such as globally unique identifiers for terms, multilingual label and definition functionality, and logical validation and reasoning over controlled vocabularies. Such a specification can be designed to satisfy the requirements of an environmental pH measurement, or a person's age, or a more structured entity like a contact address, or a genomic sequence repository submission for example.

  • View details of our overal project aim, description, and implementation on the Wiki site.
  • A working prototype of the portal is available at This version doesn't currently incorporate the Django framework yet.

Ontology Term Fetch

We also now have a scripts/ script which will process a given OBOFoundry RDF/XML-formatted ontology (by local file reference or by URI address) into json and tabular data output. Assuming that the ontology's terms are positioned under owl:Thing, this script fetches term id, parent_id, label, definition, deprecated status, term replaced_by id (if any), and a number of other fields, for use in software applications and databases. It is a good place to start to see what an ontology provides in a basic flat format, outside of the context of an ontology editor or RDF/XML text file. A discussion piece on basic ontology-driven vocabulary-software is available at:

Creating a Development Server

Using Docker

  1. Build the GEEM docker image:
$ docker build .
  1. Set up the database:
$ docker-compose run web python /code/ makemigrations --noinput
$ docker-compose run web python /code/ migrate --noinput
  1. Create your admin user:
$ docker-compose run web python /code/ createsuperuser
  1. Load initial data:
$ docker-compose run web python /code/ loaddata shared_packages
  1. Run the development server:
$ docker-compose up

Without Docker

  1. Create a postgresql database and edit config/ with connection details.

  2. Create a conda environment:

$ conda create -n geem python=3.6
$ source activate geem
  1. Install dependencies:
$ pip install -r requirements.txt
  1. Prepare development database:
$ python migrate
  1. Create your admin user. (Enter details when prompted)
$ python createsuperuser
  1. Load initial data:
$ python loaddata shared_packages
  1. Run the development server:
$ python runserver

Setting up Social Authentication

  1. Create a file config/ to contain our application secrets. This file is included in the project .gitignore file and should not be checked into version control.
  1. A Django SECRET_KEY can be generated with the following command:
python shell -c 'from import utils; print(utils.get_random_secret_key())'
  1. Register an Oauth2 application on Github: Enter http://localhost:8000/complete/github/ as the Authorization callback URL. Once the application is created, enter the Client ID and Client Secret into the file as SOCIAL_AUTH_GITHUB_KEY and SOCIAL_AUTH_GITHUB_SECRET, respectively.

  2. Create a new project on the Google Developers Console: . In the Library tab, find and activate the Google+ API ( Create OAuth client ID Credentials. Select 'Web Application' as the appliction type. Enter http://localhost:8000/complete/google-oauth2/ as the 'Authorized redirect URI'. Once the application is created, enter the Client ID and Client Secret into the file as SOCIAL_AUTH_GOOGLE_OAUTH2_KEY and SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET, respectively.

Viewing the Application