Date

27 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. Kitio Fofack 
2. Ralph O'Flinn 
3. Andrew Woods
4. Mike Conlon  
5. Benjamin Gross
6. Brian Lowe 
7. Steven McCauley  

Agenda

1. Review of agenda

   1. Any pressing issues?

2. December sprint - (Dec 3 - 7)

   1. One week
   2. Focus
      1. Introduction to VIVO development (minor clean-up)
      2. ElasticSearch? and Solr7?
      3. i18n?
      4. Containerization?
         1. A Docker Tutorial for Beginners - https://docker-curriculum.com/
         2. Dockerize your Java Application - https://runnable.com/docker/java/dockerize-your-java-application

3. Mailing list questions

   1. fresh 1.10 release install crashing with [OWLRDFConsumer] error
   2. how to modify and deploy vitro?

4. Housekeeping updates from last week

   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. Follow-on PRs addressing code review comments: Jim Blake / another to review

         1. https://github.com/vivo-project/Vitro/pull/94

         2. https://github.com/vivo-project/VIVO/pull/95

   2. Vagrant
      1. Updating to 1.10  (issue-41) - Don Elsborg?
   3. Triple Pattern Fragments
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Resolve "open" questions
      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.  - Thanks,Kitio Fofack! We need one more reviewer
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - may be unnecessary?
   5. Misc
      
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Don Elsborg(investigate) & Benjamin Gross(approve?) & Graham Triggs(approve after one more update?)
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Mike Conlon to review
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Guidance on "${blankSentinel} value on line 117 of personHasAdvisorRelationship.ftl"
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Can anyone reproduce or further describe this bug? Graham Triggs ?
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Suitable for newcomer to VIVO development?
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Needs more discussion: Stefan Wolff / Mike Conlon / Graham Triggs / Benjamin Gross / Huda Khan

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.

Notes 

Draft notes in Google-Doc

• Ralph is adding some dockerization links

• Sprint next week (one week).  Large number of folks. Many new.  Ramp up on VIVO development. Cherry pick some small tickets.  Open some small tickets. Ontology likely to have a ticket or two.  Many new Internationalization tickets. Work on containerization. Upgrade the vagrant.  Test frameworks. Meeting Monday at 11. See https://wiki.duraspace.org/display/VIVO/2018-12+Sprint  Add some tags regarding the kind of techology background that might be helpful.  This idea might be useful on tickets generally.

• Mailing list

• “fresh 1.10 release install crashing with [OWLRDFConsumer] error” We can ask how the precisely software was installed -- an artifact, or from source.  Andrew will respond

• how to modify and deploy vitro?  Source and class might be out of synch with the IDE? Or perhaps moving the war file is not the way to install VIVO.  The deploy process needs to do everything that the local process is doing. [Perhaps this could be fixed] Kitio will respond.

• Advanced Role management

• Many comments, many addressed in commits

• A separate branch

• Need reviews (for sprint)

• Vagrant improvement (might also be done in sprint)

• TPF discussion

• Needs to respect the publication flags

• Needs to be configurable (on/off) in runtime.properties (on by default)

• Mike will create tickets

• 1615 needs verification (TPF does not work with TDB)

• Need a review of 1543

• Need a review 1649

Actions

• Andrew Woods to respond to mailing list: "fresh 1.10 release install crashing with..."
• Kitio Fofack to respond to mailing list: "how to modify and deploy vitro"
• Mike Conlon to create ticket: TPF should be toggle-able, on by default
• Mike Conlon to create ticket: TPF should respect accessibility filters
• Mike Conlon to address:   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Previous Actions

• Don Elsborg to update vagrant for 1.10
• Kitio Fofack to work  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  
• Don Elsborg to investigate rationale for retaining two nearly identical propStatement-dataDefault.ftl files in VIVO and Vitro ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
  
• Kitio Fofack to review  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  

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