Date

23 Jul 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. Ralph O'Flinn 
2. Steven McCauley 
3. Andrew Woods
4. Brian Lowe 
5. Don Elsborg
6. Maria Amalia Florez
7. Rafael Mancera
8. Jose Mongui

Agenda

1. VIVO 1.11.0 release... 

   1. External Search

      1. Merge 'sprint-search' (vivo, vitro) into 'develop'?
      2. Related branches
         1. https://github.com/vivo-project/VIVO/tree/sprint-search
         2. https://github.com/vivo-project/VIVO/tree/dev-search
         3. https://github.com/vivo-project/Vitro/tree/sprint-search
         4. https://github.com/vivo-project/Vitro/tree/dev-search
      3. Related tickets
         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.
         4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. Integrating content and navigating between VIVO installations
3. Tickets in-review
   1. Needing one more review - any volunteers? 
      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.
   2. 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.

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

Previous Actions