Date

19 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. Huda Khan 
2. Benjamin Gross 
3. Ralph O'Flinn 
4. Brian Lowe 
5. Michel Héon
6. Nicolas Dickner 
7. Alexander (Sacha) Jerabek  
8. Andrew Woods
9. Rachid Belkouch

Agenda

1. Announcements
   1. VIVO Conference proposals deadline extended to Friday, May 22nd
2. This week's i18n sprint
   1. Goals:
      1. Adding en_CA language
      2. Clarify the vision about the replacement of the labels '@en_US' by '@en' in ontologies from VIVO & Vitro Repo and evaluate the consequence of these changes.
      3. Further progress in the identification of bugs in fr_CA
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. Click here to expand...

      key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
      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.
   4. 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 

This meeting came directly after the current 2020-05-19 - i18n Editing sprint kick-off meeting

• The i18n topics were discussed then

VIVO Conference

• VIVO Conference proposals deadline extended to Friday, May 22nd
• Some discussion of proposals underway, i18n, etc.
• ND: will add proposed text for presentation on i18n

Solr config

• Brian + Benjamin: looking at solr config, make sure there is proper alignment with different releases of Vivo, esp with i18n efforts
• BG: some discussion of solr issues, how to simplify, vivo configuring solr, in which directory solr starts, do not really want to do configuration via API, inclination is to not support solr Cloud version
• Aw: best to scope this to solr standalone, so for autoconfiguration of solr there is no news
• MH: what is the utility of solr inside Vivo, since Vivo can work without solr?
• RoF, BL: it has been there since beginning to handle indexing, etc. Vivo Scholar is just continuing on with using it.
• BG: solr is fast, helps searching, suggestions, prompts, etc.
• MH: is there some architectural documentation about role of solr in Vivo?
• RB: for info on solr, see
  • VIVO and the Solr search engine (*) and
  • VIVO and the Solr search engine

Actions