Difference between revisions of "Anatomy Tree Display"

From phenoscape
(Version 4)
Line 1: Line 1:
 
==Version 4==
 
==Version 4==
 
This revision puts the ontology tree on the left as the primary browsing tool.  Data for the selected term appears in the tabbed panels to the right.
 
This revision puts the ontology tree on the left as the primary browsing tool.  Data for the selected term appears in the tabbed panels to the right.
====page 1====
+
===page 1===
 
[[Image:singlewindow1.png|700px]]
 
[[Image:singlewindow1.png|700px]]
 +
====Comments====
  
====page 2====
+
===page 2===
 
[[Image:singlewindow2.png|700px]]
 
[[Image:singlewindow2.png|700px]]
 +
====Comments====
  
====page 3====
+
===page 3===
 
[[Image:singlewindow3.png|700px]]
 
[[Image:singlewindow3.png|700px]]
 +
====Comments====
  
====page 4====
+
===page 4===
 
[[Image:singlewindow4.png|700px]]
 
[[Image:singlewindow4.png|700px]]
 
+
====Comments====
  
 
== Version 3 ==
 
== Version 3 ==

Revision as of 16:19, 1 February 2010

Version 4

This revision puts the ontology tree on the left as the primary browsing tool. Data for the selected term appears in the tabbed panels to the right.

page 1

Singlewindow1.png

Comments

page 2

Singlewindow2.png

Comments

page 3

Singlewindow3.png

Comments

page 4

Singlewindow4.png

Comments

Version 3

For conference call on 1/26/10. Notes and features on screenshots based on 1/22/10 conference call.

Two panel display of summary results

page 1

Anatomy-tree-2panels-p1-rev1.png

page 2

Anatomy-tree-2panels-p2-rev1.png

Version 2

For conference call on 1/22/10

Access anatomy tree summary results from front search page:

Anatomy-search.png


Summary results, page 1

Anatomy-tree1-rev1.png

Summary results, page 2

Anatomy-tree2-rev1.png

Two panel display of summary results

Anatomy-tree-2panels.png

Version 1

From conference call on 1/21/2010"

Access anatomy tree summary results from front search page:

Anatomy-search.png


Summary results, page 1

Anatomy-tree1.png

Comments:

  • Alternatively, this could be a two-panel display with tree in the left panel and results table in right panel, similar to BioPortal's layout.
    • make mockup for next conf call
  • How to clearly indicate relationships on branches? For example, "type of" and "part of" with arrow pointing to parent?
    • Don't need to display relationships on branches if tree has "subtype results" and "subpart results" labeled.
  • tree is confusing. Would be clearer to indent child terms, similar to OBO-edit's ontology tree viewer.

Summary results, page 2

Anatomy-tree2.png

Version 0

Search summary results

Copied from this page: Knowledgebase_mockups

This would be an enhancement to the Phenotypes results currently displayed on a page like http://kb.phenoscape.org/search/anatomy/TAO:0000376

The leftmost column is intended to represent a disclosable tree display. The nearest common ancestor of the represented annotated anatomy terms is used as the root of the tree display. Each anatomy term has a flat list of the qualities annotated for it. Don't pay too much attention to the dummy numbers given in these results.

Root anatomy term "infraorbital" collapsed:

Infraorbital closed ontology tree.png

Root anatomy term "infraorbital" expanded:

Infraorbital open ontology tree.png

Possible further enhancement to page capabilities - redisplay data on a quality tree. The included results would be somewhat different.

Nearest quality ancestor collapsed:

Quality closed ontology tree.png

Quality ancestor expanded:

Quality open ontology tree.png

Comments

  • From Paula: Rename 'Entity' 'Anatomy' as per other mockups for consistency http://kb.phenoscape.org/search/anatomy/TAO:0000376
  • From Paula: swap column headings Entity-Quality on Quality tree table (below ' Nearest quality ancestor collapsed" text)
  • From Todd (cosmetic): I'm not sure the alternating colors will be clear when there are multiple rows - those are most useful as an aid to follow horizontally across many columns within a row
  • From Todd: would it be possible to collapse the quality column too (ie to "4 qualities" for a given entity? or "4 anatomical terms" for a given quality)?
  • From Todd: Personally I think having the anatomical entity in the 1st column is a lot more useful than having the quality tree there.