Date

03 Mar 2020

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. Benjamin Gross 
2. Andrew Woods
3. Brian Lowe 
4. Ralph O'Flinn 
5. Michel Héon 
6. Alexander (Sacha) Jerabek  
7. Don Elsborg

Agenda

1. Announcements
   1. Dev meeting change in frequency?
   2. Initial Selenium test framework verified
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. Performance testing different VIVO / triple store configuration - take #2 (no inferencing)
   1. Performance Testing
      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. 2020 - VIVO Sprints
   1. VIVO-i18n - Canadian French Initiative
   2. Dates: Apr 6th - 17th
4. 1.11.1 maintenance release - security patch
5. Vitro JMS messaging approaches
6. VIVO Scholar - Docker setup
7. Vitro pull-requests
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - looks good
   2. 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

1. Announcements:
   1. Discussion about frequency of meetings, would help to move development of software, move to bi-weekly or monthly in exchange for work to move the project forward.
   2. Rf: meetings serve to keep everything and everyone on track
   3. Mh: do we have a meeting to prepare the sprint?
   4. Aw: there is usually a kickoff, but ideally more meetings in advance to organize things before starting the sprint.
2. Selenium testing: 
   1. AW has tried this out with a plugin for a browser session with Vivo, Selenium generates Java (or Ruby) code based on activity and then gets dumped into testing code base, which you can then use to adapt and test. Testing can take some time however if you have to bring Vivo down and wipe it each time you run the test.. AW will document the process and see if it is interesting to implement to integrate into current Travis/Jira workflow. Can create the test in Chrome and then run in Firefox. Would help with dev work on i18n to make sure we don’t break anything. With its own GitHub repository.
3. Performance testing different VIVO / triple store configurations - take #2 (no inferencing)
   1. AW has documented ingest tests, which methods are taking the most amount of time, and then to determine if and how to optimize the calls. [discussion about various aspects of setting up the tests...indexing and inferencing turned off, lower startup costs,].Will give a clear picture of performance now so that as we make changes we have a baseline against which to compare. DE will spin up dockers and run tests with different configurations.
   2. See: Procedures and results being documented on the wiki: https://wiki.lyrasis.org/display/VIVO/Performance+Testing

Actions