Date

02 Apr 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: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1.  Don Elsborg  
2. Ralph O'Flinn 
3. Andrew Woods 
4. Mike Conlon
5. Benjamin Gross  
6. Jim Blake 
7. Steven McCauley
8. Alex Viggio

Agenda

1. Sprint update
2. Given Fly-in design overview
   1. Where are the open questions?
   2. How can we move the effort forward (2019 sprints, Product Evolution, other)

3. Search index: approaches for configuration and processes 

4. Acceptance tests moved to vivo-community, thanks Jim Blake
   1. https://github.com/vivo-community/vivo-acceptance-tests
   2. How to run it

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. Low-hanging, documentation - Mike Conlon, can you give this one a 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. 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

• 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