Date

21 Apr 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. Andrew Woods
3. Huda Khan 
4. Benjamin Gross 
5. Ralph O'Flinn
6. Brian Lowe
7. Michel Héon 
8. Alexander (Sacha) Jerabek
9. William Welling
10. Mike Conlon
11. Steven McCauley
12. Nicolas Dickner

Agenda

1. Sprint updates - i18n
2. VIVO installation: the vision and requirements
   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 does not exist
   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. Moving tickets forward
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - back on your plate, Mike Conlon
5. 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.

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

i18n updates

• Sacha reports UQAM is having their own sprint to complete some of the items that were not completed during the VIVO sprint. Capability map and resources page. Michel will be looking at Selenium. 
• What kind of testing? Sacha is working through the UI manually and logging all the issues in Jira. Testing has been thorough, impressive. Not complete but doing their best.
• Also planning on exploring language installation and configuration improvements.
• Next ‘official’ VIVO sprint is the third week of May
• Nicolas - many of the logged tickets appear to be specific to French, but they are more general syntactical issues. The concatenation of strings is built with English in mind.
• First draft of adding additional functionality to i18n included many .ftl files that were a copy of the core .ftl files with the suffix fr_ca. Most are exact copies. It has been culled so only .ftl files with modifications remain. Many of the issues are related to the use of single quotes in the original files.
• Can’t we just encode the single quotes? (discussion in french) Non. 
• Brian - shouldn’t we be finding a better way to escape quotes in Freemarker. Don’t want an issue where by switching to single quotes in a string we break the option to use double quotes. Michel - issue is when we are working between javascript, language properties, and .ftl
• Michel interested in exploring migration of .properties to ontology file (triples). 
• Discussion about implications of this (would the labels need to be assigned a class?)
• Debate between the complexity of using triples and purity and ‘coolness’ of doing it linked data app
• Andrew - has an issue been created to track the question about how languages are selected in VIVO? Benjamin - yes (https://jira.lyrasis.org/browse/VIVO-1839)

VIVO installation discussion

• 6 requirements listed. 
• VIVO should be able to be deployed by dropping vivo.war into a servlet container (e.g. Tomcat)
• On startup, VIVO should create ${VIVO_HOME}, if it does not exist
• On startup, VIVO should download, start, and configure Solr, if it does not exist
• System administrators should be able to enable i18n languages via runtime configuration files
• VIVO should only load i18n triples that are associated with enabled i18n languages
• Developers should be able to use a three-tier build to create a vivo.war for advanced customization
• Don-  we create a .war now and it appears to work
• For creating VIVO_HOME, there’s also the RDF files to consider. Currently copied over by Maven. Andrew is working on a pull request to address this. Brian - how is VIVO_HOME set? Andrew - currently appears to be 3 approaches. Server.xml, a system property, and…
• Don - would like to be able to dynamically set VIVO_HOME.
• Andrew - perhaps as a system property we can set
• Michel - why not using an install builder? E.g. bit rock  It will be simpler for the end user. 
• Brian - Andrew is describing feedback from sys admins. Perhaps it’s a different use case. 
• Andrew - does not need to be either/or. It’s a simplification effort and alignment with normal sys admin practices.
• Michel - Users - 1. normal end user who just wants to play with it, not developer 2. Developer ‘like us’ and Maven is fine 3. Sys admin and couldn’t they use Maven, too? 

Actions