BBOP OBD visit

Setup

Checkout code from NCBO GForge

• OBDAPI
• OBDUI

Developers recommended to use Eclipse

Everything can be run from command line; eventually everything can be run from a RESTy web admin interface.

• TODO: web admin interface (PUNT)

• TODO: add instructions for setting up PATH

Initialization

Core database plus ontologies

Run

obd-create-db.pl -h <HOST> -d obdevo -c obdevo.conf

Then run

obd-reasoner.pl -d obdevo@HOST

This populates the deductive closure

• TODO: create and test obdevo.conf (1 day)

This is just a newline separate list of ontology IDs (teleost_anatomy quality etc) or URLs

(Optional: sources can be loaded later)

Load Phylogenies

OPEN. Is this entirely covered by loading TTO? Do we want to load alternative phyogenetic hypotheses? Metadata on how the tree was arrived at? Branch lengths? How will these be used in queries?

Loading of PhyloXML or NHX files would be easiest for us

Load annotations

Run

obd-exec --format org.obd.parser.NESCENTPhenoteConfigParser <TAB-FILES>

• TODO: write org.obd.parser.NESCENTPhenoteConfigParser (1 day)

(use NCBO one as a template)

Note that we could write a phenote mapping to org.obo.annotation instead. This is probably the way to go in the long run, but it will slow us in the short term. See Phenote section below

Once the annotations are loaded we run the reasoner again:

obd-reasoner.pl -d obdevo@HOST

This computes the subsumption relations between EQs

• TODO: add NESCENT specific rules (3+ days) (PUNT)

TBD: discuss the relation between a higher taxon and phenotypes instantiated by sub-taxa. How to deal with loss?

See also phylogenies above

Set up UI / REST interface

ROB: fill in generic OBD TomCat instructions here

The web interface is bare bones, but it will allow you to navigate taxon-taxon, taxon-phenotype, phenotype-phenotype, phenotype-taxon

(here phenotype encompasses EQ class expressions as well as individual ontology classes)

Also uses reasoner results in querying

PLAN: set up initial install, demo, discuss further requirements, what is required from API to implement them

Annotation and Ontology Lifecycle

For now the easiest way to deal with lifecycle is to recreate the database from scratch. If all primary data is in cvs/svn/ftp we lose nothing, but there is admin overhead etc

Longer term OBD will support incremental loading

• TODO: incremental annotation loading support (PUNT)

Medium term the entire load cycle can be automated, so long as everything is configured:

• TODO: add NESCENT .tab file location to annotations metadata file

This is the file here: http://obo.cvs.sourceforge.net/obo/obo/website/cgi-bin/annotations.txt?view=log

It is easiest for OBD if all sources are registered.

• TODO: load + reason entire OBD database automatically from config

Phenote integration

• TODO: write org.phenote.datamodel.NESCENTTaxonPhenotypeMappingDriver (3 days) (PUNT)

As noted above, this can be sidestepped in the short term for OBD loading

• TODO: write adapter GUI in Phenote

Additional capabilites

TBD. Some ideas:

• evo-devo lenses (Jim/Rob)
• integration with wider phenotype database

e.g. to do integrate ZFIN genotype-phenotype annotations with evo-debo ones This can be done dynamically with a MultiShard

Notes

OBD model

• Began mapping of Phenex data model to OBD model. This is currently implemented in org.phenoscape.bridge.OBDModelBridge.java, in the Phenex source.
  • "Administrative" entities such as the character matrix, characters, and states, are modeled as instances of types from CDAO. This is currently done in a placeholder manner, e.g. "cdao:CharacterStateDataMatrix".
  • The mapper gives some of these entities generated IDs, which makes them easier to work with in ODB (avoiding blank nodes). These IDs are being generated because it doesn't seem prudent to rely on the given ID in the NeXML file/Phenex, as that is more of a local, in-file identifier. However, this presents complications for adding or modifying data for a data set already in OBD.
  • Need to interact with EvoInfo group to confirm correct usage of types and relations from CDAO.
  • Mapping of specimens is still to be implemented.
• Phenotypes
  • Quantities such as measurement are not yet handled. This will require further discussion between Cartik, Chris, and Jim. Beyond basic quantities, we want to also handle min and max, as defined in PhenoXML.
  • We may want to remove the count field from Phenex and input counts as measurements instead. The "count" unit is available in the units ontology. This is up for discussion at the moment.
• Status of phylogeny data is still undecided and unimplemented. Could leave as an opaque piece of data and deal with only in application. Other extreme is to completely represent phylogeny via OBD links. Middle path could leave opaque but at least create relations to TTO taxa referenced within.

OBD SQL

• Instantiating the OBD database is easiest via running of scripts in the scripts directory in the OBDAPI project.
• These scripts are currently not written to accept arbitrary DB usernames and passwords, but work well for a DB on localhost with no password.
• The scripts are critical for easy importing of all needed ontologies.
• Workaround - created a local OBD instance on laptop, then dumped and imported into darwin.nescent.org.
• Importing dump into darwin.nescent.org is complicated by its attempt to create a plpgsql language, which can only be done by a DB superuser.
• Workaround - have superuser create language for a blank DB. Copy it as a template for future use ("emptydbplpgsql"). Comment out language creation in dump SQL. Import dump into darwin DB.
• We need to work with Chris and Rob on script workflow and handling of stricter DB security situations.

OBD API

• We used the OBD Java API to implement the mapping in Phenex (above), including data loader from Phenex into OBD.
• We successfully connected to and manipulated a local OBD database as well as an OBD instance at darwin.nescent.org via the OBD API.
• Queries to the API can be performed directly from the Restlet application. However, it would make sense to develop convenience APIs above OBDAPI for our application data model (reduce tedious traversals performed by view code).

OBD Web UI

• OBDUI project is quite easy to build and package into a WAR from Eclipse. Automated server builds via Ant are not yet implemented.
• It is also quite simple to run the OBDUI application directly from Eclipse via a local copy of Tomcat.
• Additional databases can be made available in the application by adding to the configuration in WebContent/obdRestServletConfig.xml.

Phenex OBD interaction, OBD data loading

• Loading of data from Phenex into OBD is implemented in org.phenoscape.bridge.OBDModelBridgeTest.java, as a JUnit test.
• Ideally the reasoner needs to be run after ontology and data loading, to precompute relations.
• For this reason a "data warehousing" approach may be the best plan for using the current code.
  • Annotated data could be deposited into a public directory (possibly SVN), and a script could periodically clear and repopulate the database, by importing those files, then run the reasoner.
  • This approach also avoids issues still under consideration regarding unique IDs for particular datasets and how to import modifications to datasets already in ODB.
  • This would also keep ontology content up-to-date. The reasoner cannot currently remove previously precomputed links that an updated ontology version no longer implies.