Date 06 Dec 2018
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
Flights? Hotels (hold off) Defining the outputs of the fly-inReview of VIVO components and interfaces Features to carry forward and leave behind DiagramsDuke (Richard) Rialto (Justin) Opera (Brian) Cornell (Huda) - see below Homework for Dec 20th meeting:Rough, brainstorm architecture diagram of decoupled VIVO Meeting schedule leading up to Jan 29thDec 20th @noon ET Jan 10th @noon ET Jan 24th @noon ET Notes Audio recording From last week's actions: DiagramsCornell (Huda)VIVO (in general)From the wiki: diagram from architecture overview 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 Scholars at Cornell Discussion We must review / augment / categorize / annotate the feature list Answering the questions: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? Anticipated products that will come out of the fly-inArchitectural diagramsTop-level and Detailed, component-level APIs and services, specified Also noted, we should have an Architectural Framework independent of the feature listHow will we support modularity?i.e. Will each module be able to be compiled separately? What is the framework for swapping in replacement modules? We should consider defining goals, but the focus is on design and architecture Questions: To what degree do we keep the legacy code vs. replacement?It is the data that bridges the past and present Are we talking about VIVO only, or VIVO/VitroWhat are the community implications of collapsing VIVO/Vitro? Principles:Components must be configurable and extensibleAlthough we will not be able to develop every feature, the architecture should allow others to For example, the web layer must support adding widgets To what degree do we need to bring security (filtering) reqs forwardIs this in line with VIVO principles? Next meeting Action : Alex to create initial Google Sheet to classify features (matrix)Move features in from Google Doc and add categorization columns Action : Each member of the team to create rough draft architectural diagram(s)Previous Actions Collect diagrams Cornell (Huda)
Collect diagrams Opera (Brian)
Collect diagrams Rialto (Justin)
Collect diagrams Duke (Richard)
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