...

1. Justin Littman
2. Ralph O'Flinn
3. Alex Viggio
4. Benjamin Gross
5. Brian Lowe
6. Huda Khan
7. Jim Blake
8. Richard Outten
9. Andrew Woods 

...

1. Architectural diagrams
   1. Top-level and Detailed, component-level
   2. APIs and services, specified
2. Features spreadsheet
   1. Questions to answer:
      
      1. What will the product will do/support?
      2. What additional business value-add can the re-architecture offer?
      3. What are core? and why?
      4. Which features are in/out/optional?
      5. What audiences are specific features for?
      6. What are the logical groupings for features into modules?
      7. Will we offer multiple product distributions, analogous to VIVO/Vitro?
         1. Perhaps an "enterprise VIVO" vs. a "small-shop VIVO" vs. Vitro

Notes 

Audio recording

• 2018-01-24-vivo-fly-in-planning.mp4mp3

The word of Mike

1. Statement of direction
   • Focus on 2019 actions
   • Common goal: Advancing scholarship
2. VIVO community should be (will be) much larger... 1000s
   • Everyone should have a profile
   • ..with data that backs up the profile

Applications of VIVO

1. Research Information management application
2. Showcase profiles application
3. Data production application
   • Producing value for institutions and the broader community

Actions for each team member

1. See section "Pre-Fly-in actions"

More requirements

1. Response time to render profiles
   • 20sec too much
2. Cloud-ready?
3. Need suggestion for graph-store
   • Need that suggestion/answer as a foundation
   • Actively maintained, production ready, multi-threaded, etc
4. Speed of removing triples
   • Timeout on dumping large named graphs

Actions

•  ...

Collection of existing architecture diagrams / resources

...