VizDev Team Meeting Notes

July 25, 2014

1. TBD

July 11, 2014  Kickoff Meeting

1. Intros

2. Overview of purpose:  

   1. widgets built from ground up with cross-project reusability in mind

   2. Flexible, use-case driven, results-oriented 

      1. Fast prototypes of concepts ... iteratively improved ... scientists strongly in loop

      2. Not 6 month waterfall amongst SWEs before Line 1 of code is written

   3. potential to change how SWE is approached at Broad:  crack (if not break) silos

   4. Ben's comments
      

      
      
      

3. Deliverables

   1. QQ plot

   2. Table widget
      ---------------------- Initial Work ---------------

   3. Linked Hierarchies visualization

   4. CoMut plot

   5. Heatmap?

4. How / when to reach out to others:

   1. Jim Robinson / IGV

   2. Mesirov portals group

   3. Bang & Noam Viz Skunkworks

   4. Broad-Wide Service Registry

5. General Approach

   1. Architectural model

      1. Very clear separation of data and rendering functionality

   2. Not clear yet which approach is right ... but Once a sufficient bolus of code is in hand ... think Shared Repo or Registry:  

      1. Broad-Wide Component_registry

      2. nascent widgets ok to live in project-specific repo
         Example:  https://github.com/broadinstitute/igv-js/tree/master/igv/igvexp

      3. but when mature/stable enough to share, list in common registry (or repo?)
         Example:  https://github.com/broadinstitute/vizdev/expression

   3. Build, share, increment

   4. Data services (or object definitions) are not in scope for Ben

      1. He can mock input source JSON 

      2. While RESTful api data source is being implemented or provisionied

   5. Process stuff?  Specs, requirements gather, etc?

6. Brief Review of State of Art & Toolchains

   1. Bootstrap

   2. D3

   3. DataViva :  additional description here

   4. Other?