Diff for "groupAPI/UseCase_3A"

Differences between revisions 4 and 5

$/!\$ Edit conflict - other version:

Use Case Name : ...

For Feature : ...

Editors: ...

Summary

We would like to be able to represent detailed sub-gene data in a second window after selecting a node from the parent graph. These below use cases apply to datasets where many different pieces of data (e.g. probesets or interaction partners) are available, that themselves can be represented as distinct nodes. Examples include individual probes or replicate spots from a microarray dataset, data from distinct time-point comparisons in a dataset polymorphism data from whole genome SNP experiments*, exon and exon-junction specific data*, ChIP on chip experiment data* and interaction partners for a node in the parent network*. Examples with an asterisk are illustrated below.

Step-by-Step User Action

Associating Data for Sub-Gene Views

Requires a new interface for data input and selecting from specific options for compatible sub-gene views. Once required data is supplied for a specific sub-gene entity method (see above for built-in examples) or generic sub-gene objects (e.g. probesets) along with filters for node coloring supplied, values associated with specific
Choose "Form complex" from a context menu, main menu or toolbar
Automatically view collapsed view of complex with default label (editable)
Be able to expand complex as vertically stacked set of nodes by a very simple mechanism (e.g., click on a plus/minus icon)
1. perhaps other restricted views of the children will be allowed:
  1. horizontal stack
  2. block (e.g., 2x2, 3x4)
  3. overlapping "clump" of nodes packed into a some defined circular area
  4. new network
Be able to destroy complex
Be able to expand-all or collapse-all complexes in a given network

Loading a Network with a Complex

Same as 3-6 above

Visual Aides

attachment:sub-gene-vis.jpg

Requirements for Cytoscape

Importance

Other Examples

Comments

PageComment2

$/!\$ Edit conflict - your version:

Describe groupAPI/UseCase 3A here.

$/!\$ End of edit conflict

-  ← Revision 4 as of 2006-11-15 06:39:07 →
  Size: 2400
  Editor: adsl-71-146-133-52
  Comment:
+  ← Revision 5 as of 2006-11-15 06:54:05 →
  Size: 3860
  Editor: adsl-71-146-133-52
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+---- /!\ '''Edit conflict - other version:''' ----
-Line 21:
+Line 22:
-We would like to be able to represent detailed sub-gene data in a second window after selecting a node from the parent graph.  These below use cases apply to datasets where many different pieces of data (e.g. probesets or interaction partners) are available, that themselves can be represented as distinct nodes.  Examples include individual probes or replicate spots from a microarray dataset, data from distinct time-point comparisons in a dataset polymorphism data from whole genome SNP experiments*, exon and exon-junction specific data*, ChIP on chip experiment data* and interaction partners for a node in the parent network*. Examples with an astrick are illustrated below.
+We would like to be able to represent detailed sub-gene data in a second window after selecting a node from the parent graph.  These below use cases apply to datasets where many different pieces of data (e.g. probesets or interaction partners) are available, that themselves can be represented as distinct nodes.  Examples include individual probes or replicate spots from a microarray dataset, data from distinct time-point comparisons in a dataset polymorphism data from whole genome SNP experiments*, exon and exon-junction specific data*, ChIP on chip experiment data* and interaction partners for a node in the parent network*. Examples with an asterisk are illustrated below.



== Step-by-Step User Action ==

## Provide a step-by-step account of how the user would execute the use case.  For example: (1) right click on node, (2) choose "expand" from context menu, (3) new view is created, etc...



'''Associating Data for Sub-Gene Views'''

 1. Requires a new interface for data input and selecting from specific options for compatible sub-gene views. Once required data is supplied for a specific sub-gene entity method (see above for built-in examples) or generic sub-gene objects (e.g. probesets) along with filters for node coloring supplied, values associated with specific 

 1. Choose "Form complex" from a context menu, main menu or toolbar

 1. Automatically view collapsed view of complex with default label (editable)

 1. Be able to expand complex as vertically stacked set of nodes by a very simple mechanism (e.g., click on a plus/minus icon)

  a. perhaps other restricted views of the children will be allowed:

   i. horizontal stack

   i. block (e.g., 2x2, 3x4)

   i. overlapping "clump" of nodes packed into a some defined circular area

   i. new network

 1. Be able to destroy complex

 1. Be able to expand-all or collapse-all complexes in a given network



'''Loading a Network with a Complex'''

 1. Same as 3-6 above
-Line 40:
+Line 60:
+---- /!\ '''Edit conflict - your version:''' ----

Describe groupAPI/UseCase 3A here.



---- /!\ '''End of edit conflict''' ----