Difference between revisions of "Phenoscape web UI"
From phenoscape
(→Development Roadmap) |
|||
Line 10: | Line 10: | ||
*** Services should return in no more than 2 seconds | *** Services should return in no more than 2 seconds | ||
*** Evaluate feasibility 2 weeks before meeting | *** Evaluate feasibility 2 weeks before meeting | ||
− | + | * Mockup publication data interface within web application | |
+ | * Mockup "splashy" search entry page - we should have a more graphically capturing entry gateway for exploring the data content | ||
+ | ** One of the following: | ||
+ | ***Hierarchical term explorer | ||
+ | ***Visual explorer, using schematic drawings ("the prototypical fish") | ||
+ | ***Visual explorer using 3D scans of catfish (and eventually zebrafish when done). | ||
+ | **Should explore various prototypes of these ideas using HTML mockups and get feedback from project team | ||
+ | * Mockup taxonomy-based tree-mapped data perspective | ||
+ | ** View taxonomic phenotype annotation results organized by a phylogenetic tree | ||
+ | ** Group phenotypes as simplistic union of descendant nodes, rather than ancestral reconstruction | ||
+ | ** Use taxonomy as basis for phylogenetic tree | ||
+ | **Develop HTML mockups in web application | ||
===March 2009=== | ===March 2009=== | ||
* Incorporate 1/5/09 team feedback on existing interface components | * Incorporate 1/5/09 team feedback on existing interface components | ||
Line 21: | Line 32: | ||
** Design data service schema to be implemented by Cartik | ** Design data service schema to be implemented by Cartik | ||
** Implement interface using live data service once developed by Cartik | ** Implement interface using live data service once developed by Cartik | ||
− | |||
* Incorporate publication data into user interface | * Incorporate publication data into user interface | ||
** Incorporate publication links into annotation results displays | ** Incorporate publication links into annotation results displays | ||
Line 36: | Line 46: | ||
===April 2009=== | ===April 2009=== | ||
− | * " | + | * Implement "splashy" search entry page as defined by mockup work |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* Possible user testing session in conjunction with RCN meeting at NESCent | * Possible user testing session in conjunction with RCN meeting at NESCent | ||
===May 2009=== | ===May 2009=== | ||
− | * | + | * Implement taxonomy-based tree-mapped data perspective |
− | |||
− | |||
− | |||
− | |||
− | |||
*Implement appropriate scalable deployment of web application | *Implement appropriate scalable deployment of web application | ||
**Multiple application instances and load balancing | **Multiple application instances and load balancing |
Revision as of 19:56, 9 February 2009
Contents
Development Roadmap
February 2009
- Mockup changes to existing interfaces required to incorporate 1/5/09 team feedback on existing interface components
- Taxon search interface
- Mockup interface using dummy data within web application - request group feedback
- Front page search interface and results table - may include intermediate results summary page
- Mockup interface using dummy data within web application - request group feedback
- Interface demo and feedback session - DECAP meeting, Feb. 27, 2009
- Present screenshots and mockups
- Possible live demo depending on data service performance progress
- Services should return in no more than 2 seconds
- Evaluate feasibility 2 weeks before meeting
- Mockup publication data interface within web application
- Mockup "splashy" search entry page - we should have a more graphically capturing entry gateway for exploring the data content
- One of the following:
- Hierarchical term explorer
- Visual explorer, using schematic drawings ("the prototypical fish")
- Visual explorer using 3D scans of catfish (and eventually zebrafish when done).
- Should explore various prototypes of these ideas using HTML mockups and get feedback from project team
- One of the following:
- Mockup taxonomy-based tree-mapped data perspective
- View taxonomic phenotype annotation results organized by a phylogenetic tree
- Group phenotypes as simplistic union of descendant nodes, rather than ancestral reconstruction
- Use taxonomy as basis for phylogenetic tree
- Develop HTML mockups in web application
March 2009
- Incorporate 1/5/09 team feedback on existing interface components
- Anatomy term search results - reorganize according to sketch
- Gene search results - reorganize according to sketch
- Taxonomic phenotype results page - add Order column for taxonomic grouping
- Present various phenotypic results grouped by custom "character slim"
- Requires slim development by team members (Wasila, Paula) and service implementation by Cartik
- Taxon search interface
- Design data service schema to be implemented by Cartik
- Implement interface using live data service once developed by Cartik
- Incorporate publication data into user interface
- Incorporate publication links into annotation results displays
- Columns referencing numbers of taxonomic phenotype or mutant phenotype match results will be accompanied by a column including number of publications referencing the search item
- Link from publication count to a publication listing
- Publication listing includes brief citation each of which links to a publication detail page
- Publication detail page(s)
- Full citation information
- Display curator credits
- Display or link to original matrix including free-text data and specimen listing
- Display or link to all phenotype annotations resulting from publication
- Requires publication data implementation in OBD by Cartik
- Requires specimen data implementation in OBD by Cartik
- Incorporate publication links into annotation results displays
April 2009
- Implement "splashy" search entry page as defined by mockup work
- Possible user testing session in conjunction with RCN meeting at NESCent
May 2009
- Implement taxonomy-based tree-mapped data perspective
- Implement appropriate scalable deployment of web application
- Multiple application instances and load balancing
Release candidate - June 2009
- Project team testing
- Bug fixes
- Overall performance evaluation