...

1. Logistics

   1. Location: https://lakenona.ufhealth.org/
      1. University of Florida Research and Academic Center
         6550 Sanger Rd.
         Orlando, FL 32827
   2. Dates: Jan 29th -30th
      1. Travel on 28th and 31st
   3. Lodging (https://goo.gl/maps/sy4xyiqQWu42)
      1. Residence Inn by Marriott Orlando Lake Nona
         
         1. 6955 Lake Nona Blvd, Orlando, FL 32827
      2. or, Courtyard by Marriott Orlando Lake Nona
         1. 6955 Lake Nona Blvd, Orlando, FL 32827
2. Statement of VIVO's Product Direction for 2019
   1. Modernize the presentation layer of VIVO
   2. Decouple the architecture
   3. VIVO Combine
   4. VIVO Search
3. Introductions
   1. What interests do you bring to the effort?
4. Defining the objective / end-state
   1. Feature requirements
   2. Architectural requirements
5. What is needed prior to Jan 29th
6. Meeting schedule leading up to Jan 29th

Notes 

Actions

•  ...

Audio recording

• 2018-11-21-vivo-fly-in-planning.mp3

Introductions

1. Brian
   • 2006
   • semantic
   • RSP
   • historical knowledge
   • modularity
   • has a frontend developer
2. Benjamin
   • 2014
   • frontend (freemarker)
   • less java
   • Clarivate
     • ingest friction (wos+, internal.db-)
3. Huda
   • 2009
   • evolve arch to allow for goals: frontend, backend
   • decoupling, configurable
   • ingest
4. Jim
   • 2009 - NIH grant
   • modularity: triplestores, search engines
   • decoupling: deployable units
   • how to deploy js interface
5. Justin
   • Stanford
   • Rialto (VIVO adjacent), using ontology
   • 2011-2015
   • AWS: neptune, lambda
6. Ralph
   • enterprise apps engineer
   • UAB
   • ingest
   • index management
   • frontend
7. Richard
   • Duke
   • VIVO-widgets (providing JSON data)
   • decoupling: reasoner (no longer use a reasoner)
   • custom backend for editing (rails)
   • externalized ingest
   • ingest (what sources?)
   • central-IT
     + req: what must the reasoner do? (stardog)
   • early expectation that data is loaded manually
   • Is a reasoners needed at all?
     + Q: what degree of interactive editing is needed
   • would be very helpful to remove that requirement

What is needed prior to Jan 29th?

1. Arch diagram
2. Feature req list (what features do we move forward)
3. Feature deprecation list (what features are left behind)
4. APIs between components

Diagrams

1. ACTION: Collect diagrams from:
   • Duke (Richard)
   • Rialto (Justin)
   • Opera (Brian)
   • Cornell (Huda)

ACTIONS

• ACTION: ALL to help enumerate list of current features "Feature audit" (Google-doc)
  • What to carry forward
  • What to leave out
• Potentially poll the community

Next meetings

• Weeks of: Dec 3, 17 | Jan 7, 21
• ACTION: Andrew to send out Doodle for a number of dates