Date

30 Jun 2020

Call-in Information

Time: 11:00 am, Eastern 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. Benjamin Gross 
2. Brian Lowe 
3. Ralph O'Flinn 
4. Andrew Woods
5. Nicolas Dickner 
6. Jeff Tyzzer
7. Michel Héon
8. Huda Khan
9. Don Elsborg

Agenda

1. Input on Product Direction for 2020
   1. Goal:  agree on the set of near-term project priorities so that we can collaborate on moving the project in a mutually beneficial direction.
   2. 
   3. Comments on proposed priorities

      1. Simple data ingest methods is a great way to get up and running fast. Working in a test environment with your own data REALLY make the understanding of the system way easier. Now, I only tinkered with the system a few days so take this for what it is.

      2. Show new graphics and new analysis of the stored information could be interesting for develop.

      3. Decoupling allows easier development, but often means more complicated administration. It's worth to keep this in mind. We were not able to install VIVO 1.11 for example. It's already more complicated then it was.

      4. Data ingest

      5. Data ingest should include better options for concepts, journals, conferences, and other data via VIVO itself, like the publication claim or concept import.

      6. Continue decoupling; establish APIs. This positions for future work.

      7. For i18n - put all linguistic terms in ontological form

      8. Javed had an almost complete new interface for the ontology editor

Future topics

1. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be?
2. Incremental development initiatives
   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. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
      1. 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