Date

28 May 2019

Call-in Information

Time: 11:00 am, Eastern Daylight Time (New York, GMT-04: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: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. Don Elsborg
2. Brian Lowe
3. Benjamin Gross
4. Huda Khan
5. Ralph O'Flinn 
6. Andrew Woods

Agenda

1. Announcements
   1. Next week's call: UF demonstration of TPF
2. Design - External Search - removing the veil...
   1. Objective: merging 'sprint-search' (vivo, vitro) into 'develop' 
   2. "Upgrade to Solr7" (from Sept 2018, in 'sprint-search')
      1. Minor updates for compatibility with Solr7
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. "Remove Embedded Solr" (in 'sprint-search')
      1. Removing Solr from codebase - all deletes
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. "Create documented external Solr7 install package" (in 'sprint-search')
      1. Quick start guide for running VIVO with externalized Solr
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. "Add ElasticSearch smoke test" (in 'sprint-search')
      1. Adds two new start-up smoke tests: 
         1. ElasticSmokeTest - for externalized ElasticSearch
         2. SearchEngineSmokeTest - based on runtime.properties, defers to ElasticSearch or Solr smoke-tests
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   6. "Externalized Solr Error Handling" (needs to be merged into 'sprint-search')
      1. Extends wait time for SolrSmokeTest to connect with Solr to 5 minutes
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
3. Working towards the VIVO 1.11.0 release
   1. Landing Design - External Search
   2. Other tickets we want to include?
      1. Docker work:
         1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Don Elsborg to review?
         2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Don Elsborg to review?
         3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Ralph O'Flinn to review? - Now in https://github.com/vivo-community/vivo-docker2
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Release manager?
4. Decoupling VIVO components
   1. Search index - almost complete
   2. Read-only UI - VIVO Scholars Task Force / TAMU
   3. Triplestore?
5. TAMU Scholars / VIVO Scholars Entities
6. New feature: Messaging
   1. Based on the IndexingChangeListener pattern
   2. Potentially with RDF-Patch bodies

7. Tickets

   1. Needing additional review
      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.  - Benjamin Gross?
   2. Received Tickets...

      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.

Tickets

1. Status of In-Review tickets

   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.

2. Received

   Click here to expand...

   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.

   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      1. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design

   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Should be low-hanging

   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      1. Where does this stand? What is needed to add more person identifiers to VIVO?

   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Mike Conlon : thoughts on where this stands?

3. Bugs (1.11)

   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

External Search

1. Ralph making progress on testing
   • Will be testing updated ElasticSearch
2. Also testing BlazeGraph
   • Don: is using vivo-docker2, VIVO 1.10
   • BlazeGraph errors should be addressed in sprint-search branch
3. Don to test sprint-search branch

4. A few use cases Docker can help with: vanilla installation or instance with local customizations.  

   1. What would be good is for docker setup to pull war file, whether the file is a standard 1.10 or one with local customizations.  

   2. Getting away from need to build the software.

5. What remains to be done with the externalized search sprint branch to allow that branch to be integrated into develop.  

   1. Andrew has listed the issues and we need a few people to look at these issues/review/merge in order for the sprint search branch to be mergeable into develop.

   2. How to actually test/review this work?  

      1. Potentially include data in the search index and then test against that.

6. Would be interesting to test Alessandro’s CINECA facets etc (pr-vitro-123) against this branch... but not a requirement
7. ElasticSearch integration is included in 'sprint-search' branch
   • Messaging/Documentation should be clear: ElasticSearch integration is "Beta"

8. Any unforeseen consequences to bring in the external search work?  Performance?

   1. No, the interaction between VIVO and Solr is unchanged

9. Jim did some work with ElasticSearch: https://github.com/vivo-project/Vitro/commit/45ddb56294eddccb929dd88a30072aec310d11ee

10. Should we consider having just Solr in the sprint-search branch and taking out ElasticSearch (since some of this still needs further work) or should we merge all of this work and then include a beta flag around the documentation for ElasticSearch?  

    1. People on the call prefer later option.

1.11

1. Shooting for a release before VIVO Conference
2. Open question regarding any additional tickets to target for 1.11 beyond what is already there and externalized-search

Actions

Previous Actions

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Mike Conlon, can you give this one a review?