Roadmap for first iteration

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; commit to SVN.
• Write EQ count script, as per Paula's request, using Ruby; provide results to Phenoscape mailing list.

Cartik

• Set up Eclipse project for Restlet based web service application on personal machine, commit to OBD-WS SVN.
• Begin implementing Term Info service
• Write code to parse ZFIN phenotype data and load into OBD
  • See http://zfin.org/zf_info/downloads.html#phenotype
  • Data: http://zfin.org/data_transfer/Downloads/pheno_obo.txt
  • should use "exhibits" relation

Nov. 17-21

Jim

• Document data retrieval web service specifications
  • Anatomy
  • Taxon
  • Genes
• Implement Rails app skeleton and code front page
• Implement reusable JavaScript term info panel and embed in front page search interface.
• Address NEXUS/Phenote file merging issues with Paula. Provide problematic files as NeXML to Paula and Wasila.

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.

Dec. 15-19

Jim

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

Outcome

Query UI

• Anatomy
• Taxon
• Gene

Data Content

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