Date

22 Jan 2019

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

1. Justin Littman
2. Ralph O'Flinn
3. Alex Viggio
4. Benjamin Gross
5. Brian Lowe
6. Huda Khan
7. Jim Blake
8. Richard Outten
9. Andrew Woods 

Agenda

1. Logistics

   1. 2019 Architectural Fly-in Travel Plans
2. Defining the outputs of the fly-in
   1. Top-level architectural diagrams
   2. Component diagrams
   3. Inputs/Outputs for each component
   4. Draft HTTP API
3. Draft requirements
4. Convergence of diagrams
5. Next steps
   
   1. Meeting schedule leading up to Jan 29th
      
      1. Jan 24th @noon ET
   2. Provide "required reading" materials before Jan 24th meeting
      1. ..such as: Architecture

Working documents

1. Architectural diagrams
   1. Top-level and Detailed, component-level
   2. APIs and services, specified
2. Features spreadsheet
   1. Questions to answer:
      
      1. What will the product will do/support?
      2. What additional business value-add can the re-architecture offer?
      3. What are core? and why?
      4. Which features are in/out/optional?
      5. What audiences are specific features for?
      6. What are the logical groupings for features into modules?
      7. Will we offer multiple product distributions, analogous to VIVO/Vitro?
         1. Perhaps an "enterprise VIVO" vs. a "small-shop VIVO" vs. Vitro

Notes 

Audio recording

• 2018-01-22-vivo-fly-in-planning.mp4

Architectural Goals

1. Merge sensibilities of Combine-esque and Product Evolution environmental perspectives with deep-dive into core VIVO refactoring

Diagrams

Brian

1. Breaking out the frontend
2. Need filtered views of data
   • challenge this assumption?
   • potentially push filtering deeper into the core
3. Do we generally need self-edit of user pages?
4. Can we split edit from view applications?
5. Design web-API focused on high-priority features
   • focus on refactoring public-facing pages
   • admin pages will likely get less attention

Jim

1. Push reasoning behind RDFService interface?
2. Support authN/Z pluggable interface for things like LDAP
3. UI APIs
   • configure blocks of data (JSON structures) to be served from API
4. How much of the current configuration can be eliminated?
5. Require compile-time separation of concerns

Actions

• ...

Collection of existing architecture diagrams / resources

• Architectural diagrams

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
• 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)

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