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

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

      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Low-hanging, documentation
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Low-hanging... need one more 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

Actions

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.