Date
Call-in Information
Time: 12:00 pm, Eastern Time (New York, GMT-05:00)
To join the online meeting:
- Go to: https://duraspace.zoom.us/j/823948749
- Or iPhone one-tap :
- US: +14086380968,,823948749# or +16468769923,,823948749#
- Or Telephone:
- Dial(for higher quality, dial a number based on your current location):
- US: +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833
- Meeting ID: 823 948 749
- International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5
Attendees
Indicating note-taker
- Justin Littman
- Ralph O'Flinn
- Alex Viggio
- Benjamin Gross
- Brian Lowe
Huda KhanJim Blake- Richard Outten
- Andrew Woods
Agenda
- 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
Working documents
- 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
Cornell (Huda)
- VIVO (in general)
- From the wiki: diagram from architecture overview page
- component diagram from main architecture page
- Can include more brainstorming/high level component diagrams/discussions from presentations and documents as well but not sure this is the bullet for it
- From the wiki: diagram from architecture overview page
- Scholars at Cornell
- Presentation: https://figshare.com/articles/Scholars_Cornell_Visualizing_the_Scholarship_Data/5277958/1 (Slide 19 shows a high level overview of the components)Data Distribution API structure:
- image which shows API-related components (these would connect to VIVO)
- Presentation: https://figshare.com/articles/Scholars_Cornell_Visualizing_the_Scholarship_Data/5277958/1 (Slide 19 shows a high level overview of the components)Data Distribution API structure:
Discussion
Previous Actions
- All to complete priority row
- All to review produce diagrams
Collect diagrams Opera (Brian)
Collect diagrams Rialto (Justin)
ACTION: ALL to help enumerate list of current features "Feature audit" (Google-doc)
- What to carry forward
- What to leave out
- Andrew to Potentially poll the community