Date

18 May 2021

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?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
  • Passcode: 351860

• 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. Benjamin Kampe 
3. Georgy Litvinov 
4. Michel Héon 
5. William Welling 
6. Huda Khan 

Agenda

1. Announcements / updates
   
   1. RC1 is out!
2. Mailing list / Slack discussion
3.  Internal testing efforts: Release Testing - 1.12.0
4. Prioritizing and planning post-1.12 development
   1. https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing

4. Other topics?

Future topics

1. Forward-looking topics:
   
   1. frameworks: Spring / Spring Boot / alternatives
   2. Horizontal scalability
   3. Deployment
   4. Configuration : files / environment variables / GUI settings
   5. Editing / form handling
   6. Adding custom theming without customizing build
2. Post-release priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps
3. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be
4. 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

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

1. Bruce Herbert sends his congratulations to the team on achieving the RC1 milestone.
2.  
3. Release testing
   1. Michel notes that the RC test forms are long and there is no option to save and resume.
      1. Does not seem to be a Google feature, or maybe it would only be activated if multiple submissions are disabled
      2. There's no problem in submitting multiple submissions each with only part of the test filled out.  Doesn't need to be completed in one sitting.
   2. Should add link to 1.11 test results table for sample API submissions to use in 1.12 API tests
   3. Michel notes that the UI test procedure also serves as a nice demo of the capabilities of VIVO.  Would be nice to turn this into a kind of walthrough for new users after testing is done.
   4. Michel's testing of new i18n functionality largely successful, but uncovered a few bugs (especially 'no match to existing data property' errors when trying to edit certain existing values)
   5. The capability map text search does not fall back to other language values: have to enter text in the language in which the interface is currently set.  Should be made clear in the instructions.
4. UQAM's Vivo Studio discussion
   1. ontology is at center of workflow
   2. multiple types of users: librarian works on ontology/vocabulary and pushes to GitHub.  Developer can use same environment to develop data ingest pipeline.  Sysadmin can develop deployment environment.
   3. Uses Eclipse plugins / update site / Maven approach to everything
   4. Will be presented at the conference
   5. Uses TopBraid Composer free edition
      1. not (at least yet) open source, but could be interesting to explore potential for VIVO community to collaborate with TopBraid developers on maintenance of free ediition.