Date

06 Aug 2019

Call-in Information

Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1

• One tap mobile:

  • US: +16699006833,,9358074182# or +19292056099,,9358074182#

• Or Telephone:

  • US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257

  • Meeting ID: 935 807 4182

• International numbers available: https://zoom.us/u/aeANHanzED

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. María Amalia Flórez Huertas 
7. Huda Khan
8. Benjamin Gross
9. Robert Nelson

Agenda

1. Community updates
2. VIVO 1.11.0 release candidate planning (and testing)
   1. If there is interest in getting this functionality into 1.11.0, please help review
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Pending response from alessandro galasso
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Should be ready to go once we get "member" credentials for final testing
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Need to re-verify integrity of commit merges
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Need one more VIVO committer to test/merge
   2. These Docker-related tickets should be closeable by the next person who can verify spinning up the MariaDB / Solr / VIVO environment
      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. For the above, username/password
   3. Code-freeze: Friday, Aug 9th
3. VIVO Cross-linking
4. RDF-Delta-TDB (the diff)
5.  In-review tickets
   1. 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