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 Khan
- Jim Blake
Richard Outten- Andrew Woods
Agenda
Logistics
- Defining the outputs of the fly-in
- Top-level architectural diagrams
- Component diagrams
- Inputs/Outputs for each component
- Draft HTTP API
- Draft requirements
- Convergence of diagrams
- Next steps
- Meeting schedule leading up to Jan 29th
- Jan 24th @noon ET
- Provide "required reading" materials before Jan 24th meeting
- ..such as: Architecture
- Meeting schedule leading up to Jan 29th
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
Architectural Goals
- Merge sensibilities of Combine-esque and Product Evolution environmental perspectives with deep-dive into core VIVO refactoring
Diagrams
Brian
- Breaking out the frontend
- Need filtered views of data
- challenge this assumption?
- potentially push filtering deeper into the core
- Do we generally need self-edit of user pages?
- Can we split edit from view applications?
- Design web-API focused on high-priority features
- focus on refactoring public-facing pages
- admin pages will likely get less attention
Jim
- Push reasoning behind RDFService interface?
- Support authN/Z pluggable interface for things like LDAP
- UI APIs
- configure blocks of data (JSON structures) to be served from API
- How much of the current configuration can be eliminated?
- Require compile-time separation of concerns
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