Difference between revisions of "Roadmap for first iteration"

From phenoscape
(Jim)
(Jim)
Line 3: Line 3:
 
===Jim===
 
===Jim===
 
* Document interface design requirements on wiki
 
* Document interface design requirements on wiki
* Investigate additional data service needs required by interface
+
* Investigate and begin documenting additional data service needs required by interface
 
* Start Rails web interface project
 
* Start Rails web interface project
 
* Write EQ count script using Ruby
 
* Write EQ count script using Ruby
 +
 
===Cartik===
 
===Cartik===
 
* Set up Eclipse project for Restlet based web service application in OBD-WS
 
* Set up Eclipse project for Restlet based web service application in OBD-WS

Revision as of 21:15, 11 November 2008

This is a development roadmap for the first production iteration of the Phenoscape database and web interface, for introduction at the SICB 2009 meeting.

Nov. 10-14

Jim

  • Document interface design requirements on wiki
  • Investigate and begin documenting additional data service needs required by interface
  • Start Rails web interface project
  • Write EQ count script using Ruby

Cartik

Nov. 17-21

Jim

  • Document data retrieval web service specifications
    • Anatomy
    • Taxon
    • Genes
  • Implement Rails app skeleton and begin coding front page
  • Implement reusable JavaScript term info panel
  • Address file merging issues with Paula.

Cartik

  • Complete Term Info service
  • Deploy OBD-WS application; continue deploying in-progress builds.
    • Include real or dummy info and autocomplete services.
  • Enhance OBD data loader pipeline to perform pre-processing of ZFA ontology, replacing xrefs with is_a links to TAO
    • These xrefs seem to still be in TAO - may have to fix that or work around
  • Implement autocomplete service

Nov. 24-28

Jim

  • mostly on vacation

Cartik

  • Provide dummy Anatomy data service(s).
  • Implement data service(s) related to Anatomy (requirements documented Nov. 17-21).

Dec. 1-5

Jim

  • Implement anatomy UI.
  • Begin using autocomplete and term info services in all so-far developed user interfaces.

Cartik

  • Provide all defined services as dummy services if not yet implemented.
  • Complete implementing Anatomy data services.
  • Begin implementing Taxon data services.

Dec. 8-12

Jim

  • Complete anatomy user interface.
  • Begin implementing taxon user interface.

Cartik

Dec. 15-19

Jim

  • Complete taxon user interface.
  • Implement and complete gene user interface.

Cartik

Outcome

Query UI

  • Anatomy
  • Taxon
  • Gene

Data Content

  • Ontologies
  • Anatomy ontologies linkage
  • Phenoscape annotations (NeXML)
  • ZFIN annotations (tab-delimited)