Date 22 Jan 2019
Call-in Information Time: 12:00 pm, Eastern Time (New York, GMT-05:00)
To join the online meeting:
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
2019 Architectural Fly-in Travel Plans Defining the outputs of the fly-inTop-level architectural diagrams Component diagrams Inputs/Outputs for each component Draft HTTP API Draft requirements Convergence of diagrams Next stepsMeeting schedule leading up to Jan 29thJan 24th @noon ET Provide "required reading" materials before Jan 24th meeting..such as: Architecture 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 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 datachallenge 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 featuresfocus 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 APIsconfigure 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)Can include more brainstorming/high level component diagrams/discussions from presentations and documents as well but not sure this is the bullet for it Scholars at Cornell 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