Date

17 Dec 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. Brian Lowe
2. Huda Khan
3. Jim Wood 
4. Don Elsborg
5. Steven McCauley
6. Benjamin Gross
7. Andrew Woods

Agenda

1. Announcements
   1. VIVO Scholars updates
      1. Email to vivo-community list: "More about VIVO Scholar and other VIVO applications"
   2. New VIVO instance from CINECA: https://expertise.unimi.it/
   3. Andrew holiday schedule - out until week of Jan 20th (week of Jan 6th, online but in Singapore)
2. Items to be tied up for 2019
   1. 2019-12-06 - Special Topic - TDB vs SDB
   2. Managing VIVO/Vitro languages (related: https://github.com/vivo-project/VIVO-languages/pull/26)
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Dependency updates 
      1. Bringing it home:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Related: https://github.com/vivo-project/VIVO/tree/vivo-1.11.0-lib-updates

   5. Migrating out of vivo-project and into vivo-community (today) - maintainers?:

      1. https://github.com/vivo-project/VIVO-Harvester

      2. https://github.com/vivo-project/ontology-explorer

3. Items to focus on as we move into 2020
   1. Moving the community to the most recent release of VIVO
   2. Supporting both use cases:
      1. VIVO as-is - related large tickets (vivo-1545, vivo-1436)
      2. VIVO as decoupled components
4.  In-review tickets 
   1. 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.

Notes 

Draft notes in Google doc

Actions

• Organize a session on Brown's work on editing