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. Design - External Search - removing the veil...
   1. "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.
   2. "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.
   3. "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.
   4. "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.
   5. "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.
2. Working towards the VIVO 1.11.0 release
   1. Landing Design - External Search
   2. Other tickets we want to include?
   3. Release manager?
3. Decoupling VIVO components
   1. Search index - almost complete
   2. Read-only UI - VIVO Scholars Task Force / TAMU
   3. Triplestore?
4. TAMU Scholars / VIVO Scholars Entities
5. New feature: Messaging
   1. Based on the IndexingChangeListener pattern
   2. Potentially with RDF-Patch bodies

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

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?

Previous Actions