Needs Analysis Workshop/Summary

From phenoscape
Revision as of 02:08, 18 January 2008 by Jpb15 (talk | contribs) (Driving questions/use cases)

Driving questions/use cases

  • Use the database to identify discrete evolutionary modules BG1
    • Depends on identifying patterns of evolutionary covariation among phenotypes
  • For a branch hypothesized to be under positive selection (from e.g. a molecular analysis), identify candidate phenotypes that could have been selected for BG1
    • Requires mapping phenotypic changes on phylogeny, visualizing synapomorphies
    • Topology can be modified and the results of modification visualized
  • Use the database to help with negative information - what knowledge is missing that is required to answer a particular question? BG1
  • Integrate data regarding ecologic conditions, life history, adaptation, and evolutionary time with phenotypic and genetic data to elucidate mechanisms of phenotypic change BG2
    • must integrate with existing databases, literature, across biological levels
    • use other factors (environment, ecology) as constraints on data presentation
  • User adds own annotations using modified curator interface, compares own data with database BG2, PB
    • user may also want to store media such as images and movies
  • Enrichment analysis: given a list of genes, find which phenotype terms are overrepresented among them RO1
  • User is notified of additions or changes to the database relevant to him/her RO1
    • save user-defined queries as RSS feeds
  • Capture and represent within-species variation in phenotypes and genotypes RO1
    • describe polyphenism dependent on environmental factors or variable gene expression
    • view population frequencies of polymorphic phenotypes
    • describe phenotypic change through developmental time series
  • View traits related to particular parts of anatomy - just tail, or just vertebra CB
  • User view ancestral character states on tree using default reconstruction methods CB
  • User downloads data in a form useful for applying their own methods of character reconstruction CB
  • find cloud of similar annotations using summary matrices CB
    • traits vs traits, traits vs genes, genes vs genes
    • cells would be number of branches on which the two traits change in common (traits vs traits), or number of mutants they have in common (traits vs traits, and traits vs genes), or number of traits in common (genes vs genes)
  • User uses interactive tree view to select taxa for summary matrix CB
  • User selects one or more regions on body plan view to view traits(genes) affecting all CB
    • then map corresponding traits on tree
  • User creates and edits a tree using MacClade-like interface, then visualizes character changes on tree PB
  • User may want to work with data regarding mutations actually underlying evolutionary change SB
    • different genetic states in different species