Date

12 May 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. Don Elsborg
   
2. Huda Khan 
3. Benjamin Gross 
4. Ralph O'Flinn 
5. Brian Lowe 
6. Michel Héon
7. Nicolas Dickner 
8. Alexander (Sacha) Jerabek

Agenda

1. The i18n effort continues
   1. Need merge from VIVO Committer (other than Andrew)
      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.
   2. Sprint next week
2. VIVO installation: the vision and requirements - Where does this conversation stand? Is there consensus?
   1. VIVO should be able to be deployed by dropping vivo.war into a servlet container (e.g. Tomcat)
   2. On startup, VIVO should create ${VIVO_HOME}, if it does not exist
   3. On startup, VIVO should download, start, and configure Solr, if it has not been configured
   4. System administrators should be able to enable i18n languages via runtime configuration files
   5. VIVO should only load i18n triples that are associated with enabled i18n languages
   6. Developers should be able to use a three-tier build to create a vivo.war for advanced customization
3. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be?
4. VIVO Scholars... next steps
5. Tickets to be reviewed

   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      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.

6. Who is working on what? - Are there active tickets in-progress?
   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.

7. 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