...
- Justin Littman
- Ralph O'Flinn
- Alex Viggio
- Benjamin Gross
- Brian Lowe
Huda KhanJim Blake- Richard Outten
- Andrew Woods
...
- Today's keynote speaker: Mike Conlon !
- Pre-Fly-in actions
- Integration with Combine - Justin Littman
- Integration with Product Evolution - Alex Viggio / Richard Outten
- Decoupling UI from core - Brian Lowe
- Separation of view and edit frontends - Benjamin Gross / Ralph O'Flinn
- Re-envisioning configuration - Andrew Woods
- Modularity/Distribution of CPU-heavy components/processes - Huda Khan
- Framework for modular APIs/endpoints - Jim Blake
- Defining the outputs of the fly-in
- Top-level architectural diagrams
- Component diagrams
- Inputs/Outputs for each component
- Draft HTTP API
- Draft requirements
- Performance considerations
- Data flow considerations
- Convergence of diagrams - using Jim Blake's diagram as a rally-point
- How to improve VIVO to more seamlessly consume Rialto-Combine-esque data?
- How to improve VIVO to more seamlessly produce Product-Evolution-esque data?
- How to modularize core VIVO to be more accessible and maintainable for developers?
- How to distribute CPU-intensive processes across multiple machines?
- "Required reading" materials before fly-in
- Architecture
- ?product evolution
- ?Rialto (VIVO/Vitro assessment)
- ?JavaScript frameworks
- Thoughts on the fly-in agenda
...
- Architectural diagrams
- Top-level and Detailed, component-level
- APIs and services, specified
- Features spreadsheet
- Questions to answer:
- What will the product will do/support?
- What additional business value-add can the re-architecture offer?
- What are core? and why?
- Which features are in/out/optional?
- What audiences are specific features for?
- What are the logical groupings for features into modules?
- Will we offer multiple product distributions, analogous to VIVO/Vitro?
- Perhaps an "enterprise VIVO" vs. a "small-shop VIVO" vs. Vitro
- Questions to answer:
Notes
Audio recording
The word of Mike
- Statement of direction
- Focus on 2019 actions
- Common goal: Advancing scholarship
- VIVO community should be (will be) much larger... 1000s
- Everyone should have a profile
- ..with data that backs up the profile
Applications of VIVO
- Research Information management application
- Showcase profiles application
- Data production application
- Producing value for institutions and the broader community
Actions for each team member
- See section "Pre-Fly-in actions"
More requirements
- Response time to render profiles
- 20sec too much
- Cloud-ready?
- Need suggestion for graph-store
- Need that suggestion/answer as a foundation
- Actively maintained, production ready, multi-threaded, etc
- Speed of removing triples
- Timeout on dumping large named graphs
Actions
- ...
Collection of existing architecture diagrams / resources
...