Date
Call-in Information
Time: 2: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
- Location: https://lakenona.ufhealth.org/
- University of Florida Research and Academic Center
6550 Sanger Rd.
Orlando, FL 32827
- University of Florida Research and Academic Center
- Dates: Jan 29th -30th
- Travel on 28th and 31st
- Lodging (https://goo.gl/maps/sy4xyiqQWu42)
- Residence Inn by Marriott Orlando Lake Nona
- 6955 Lake Nona Blvd, Orlando, FL 32827
- or, Courtyard by Marriott Orlando Lake Nona
- 6955 Lake Nona Blvd, Orlando, FL 32827
- Residence Inn by Marriott Orlando Lake Nona
- Location: https://lakenona.ufhealth.org/
- Statement of VIVO's Product Direction for 2019
- Modernize the presentation layer of VIVO
- Decouple the architecture
- VIVO Combine
- VIVO Search
- Introductions
- What interests do you bring to the effort?
- Defining the objective / end-state
- Feature requirements
- Architectural requirements
- What is needed prior to Jan 29th
- Meeting schedule leading up to Jan 29th
Notes
Audio recording
Introductions
- Brian
- 2006
- semantic
- RSP
- historical knowledge
- modularity
- has a frontend developer
- Benjamin
- 2014
- frontend (freemarker)
- less java
- Clarivate
- ingest friction (wos+, internal.db-)
- Huda
- 2009
- evolve arch to allow for goals: frontend, backend
- decoupling, configurable
- ingest
- Jim
- 2009 - NIH grant
- modularity: triplestores, search engines
- decoupling: deployable units
- how to deploy js interface
- Justin
- Stanford
- Rialto (VIVO adjacent), using ontology
- 2011-2015
- AWS: neptune, lambda
- Ralph
- enterprise apps engineer
- UAB
- ingest
- index management
- frontend
- 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?
- Arch diagram
- Feature req list (what features do we move forward)
- Feature deprecation list (what features are left behind)
- APIs between components
Diagrams
- 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