Date

12 Feb 2019

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 
    

Attendees

 Indicating note-taker

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

Agenda

1. March (18-29?) sprint planning

   1. Ingest
   2. UI
   3. Decoupling
2. Docker experience? Interest from UF in helping with VIVO 1.10 Docker image
3. Product Evolution updates? (is there a wiki landing page?)

4. Mailing list messages

   1. Re: help related to facetview in vivo - (Jan 30th) Facet view expertise, anyone?
   2. jquery.scrollTo error - (Dec 13) Do we need to upgrade `jquery_plugins`? – Has anyone else been able to reproduce?
   3. No Subject - (Dec 12) "How can I add more associated profiles for that particular  editor."
   4. Freemarker Template Error (Dec 10)
      
   5. [vivo-tech] help regarding the custamization (Dec 6)
      
   6. [vivo-tech] Inferencing engine not adding triples needed (Dec 4)

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

   1. Soft balls

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

         1. Don Elsborg ?

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

         1. Only touches one file

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

         1. Low-hanging - need one more reviewer - Brian Loweis reviewing

      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Low-hanging, documentation - Mike Conlon, can you give this one a review?
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Low-hanging... need one more review - Huda Khanto review
   2. Regular balls
      

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

         1. New

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

         1. Kitio Fofack ? Orcid and i18n

      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Is this feature of broader interest?
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Andrew Woods to look into
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Mostly trivial, with conversation around Tomcat version support
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Relatively straight-forward bug fix
      7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. An important step for i18n... resolves many other open issues
      8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Kitio Fofack to review?

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

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

• 2019 sprint series

• Planning first sprint for March: focus on architectural fly-in topics

• Outstanding items from last sprint? Need to merge development branch

• decoupling search: need to resolve smoke tests

• Solr working; Elastic still needs to be implemented

• Integrating search engines and “shapes” as defined by Product Evolution group

• Shapes and JSON schema

• Not yet fleshed out; needs a second pass: integrating with ontology, etc.

• Product Data definition:

• https://docs.google.com/spreadsheets/d/14EJH8qNIoHpw7g3r7MzHiIBekhXaF385sCZZd8OvXac/edit#gid=471799009

• Start to json-schema (needs more work)

• https://github.com/vivo-community/product-evolution-sandbox/tree/master/experiments/duke/elastic_import/schemas

• Can search engine indexing and core VIVO shapes be bridged? Probably not ready yet, but Jim Blake can have a draft ready prior to sprint

• Using the DocumentModifier class

• Might be better to focus on modularization of VIVO components for now

• Necessary steps: what are the queries that need to be run? How to maintain multiple indices?

• Don Elsborg may be able to reuse CU’s python VIVO export to Elastic document scripts for Elasticsearch

• Triple-pattern fragments: lingering issues

• All data in triple store is publicly exposed

• TPF server is currently configurable: maybe needs more documentation

• Should data store be closed down by default? That would align with all best practices re: security, db administration

• March sprint goals: Solr and Elastic; modularization; Docker

• Upcoming releases: first, a maintenance release (maybe end of March); then, modularization

• Dockerization: tested locally, needs more work

• Product Evolution meeting

• JSON specification, GraphQL

• Adding shapes (resources): how to customize

• Mailing list messages: cleaning the slate

• Can Google Groups messages be forwarded to Slack?

• Need to update jQuery plugins: Ralph will examine

• Failed inferencing: mysteriously disappeared, problem solved

• Don will handle facetview

• Messages to be removed

• Closing out softball items under 5a

• 1674: update of image processing libraries

• Breaks on 1.9: may require too much work to get backported

• merged with Graham’s updates?

• Original library is no longer supported; doesn’t work with Open-JDK

• Ralph: should be done by next week

• 1672: error catching; Benjamin on it

• 1667: back to Graham

• 1659: documentation update; over to Mike

• 1525: Huda will take a look

Actions

•   Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Brian Loweis reviewing
• 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?
• Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Huda Khanto review

Previous Actions

• Brian Lowe  confirm LDF server issue with TDB content stores
• 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.