Date

13 Nov 2018

Call-in Information

Time: 11:00 am, 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

Slack

• https://vivo-project.slack.com
  • Self-register at:   https://goo.gl/forms/JxQFkut4TYj4Ehww1 
    

Development Process

• See https://github.com/vivo-project/VIVO/wiki/Development-Processes

Attendees

 Indicating note-taker

1. Mike Conlon 

2. Huda Khan 
3. Jim Blake 
4. Benjamin Gross 
5. Steven McCauley 
6. Kitio Fofack
7. Ralph O'Flinn
8. Andrew Woods

Agenda

1. Review of agenda

   1. Any pressing issues?

2. Project directions
   

   1. From Nov 7th VIVO Updates

      The Statement of Product Direction for 2019 bit.ly/vivo-direction-2019 will orient our development, grant, and event efforts, as well as shape work for architecture and development sprints.

      
      

      1. Modernize the presentation layer of VIVO

      2. Decouple the architecture
         

      3. VIVO Combine
         

      4. VIVO Search

   2. 2019 Architectural Fly-in

3. December sprint - (Dec 3 - 7)

   1. One week
   2. Introductory
   3. ElasticSearch?

4. Housekeeping

   1. Moving the Advanced Role Management feature forward

      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Vagrant
      1. Updating to 1.10  (issue-41)
      2. Documenting startx (pr-38) - needs minor formatting clean-up
   3. Triple Pattern Fragments
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Themes
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. Misc
      
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - one remaining comment
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - minor, need one more review

5. In-Review

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

6. 1.10 

   1. bugs (1.10.1?)

      Click here to expand...

      type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
      Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      
      

7. VIVO-tech mailing list activity

   1. how to modify and deploy vitro

Notes 

Draft notes in Google-Doc

Actions

Previous Actions

• Don Elsborg - add jira tickets for abox/tbox use cases - one ticket for each use case
• Brian Lowe  - check with ontology group on handles
• Alex Viggio will bring news of Elasticsearch instead of Solr up with Product Evolution.  
• Benjamin Gross to create new Jira issue for additional errors thrown startup.
  
• Don Elsborg - create Jira ticket for data property linking by default
• Don Elsborg - discuss his data property linking pull request with the ontology group