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

Indicating note-taker

The i18n effort continues
1. Need merge from VIVO Committer (other than Andrew)
2. Sprint next week
  1. Identifying participants
  2. Defining goals
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
Vitro JMS messaging approaches - redux
1. Which architectural pattern should we take?
2. What should the body of the messages be?
VIVO Scholars... next steps
Tickets to be reviewed
Who is working on what? - Are there active tickets in-progress?
Incremental development initiatives
3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Ralph and Don unsure about whether there was a consensus about war files
Andrew working on a PR : if there is an empty VIVO home dir, the war file will populate it ; if it is there, but not empty, the war file will not change it. A recent pull-request is configured to make sure only the rdf files specified get loaded in the db -- but less a matter of technical detail, but vision. All the languages are included in the war file, but only the ones specified in the runtime.properties are loade
Andrew : need a consensus on that option.

Ralph : agrees
Don : what about the non i18n RDF files (abox, tbox) ? Otherwise, sounds good ; would be great for deployment on AWS
Benjamin : “all for this”
Brian: agrees too.
Michel : agrees : that solution is ok for people who just want to install VIVO; not optimal from a dev standpoint ; but as far as UQAM is concerned, we’ll be using our own installer.
Huda : “The streamlined approach seems like a good idea. I do wonder about debugging but that probably means I need to get better versed with debugging content in a .war file. That said, assuming this doesn't prevent download of the source as we normally have done it, but just adds an option for download and deployment, so in that case, anyone who wants to debug and develop the code should be set.”
Don and Ralph : discussions about CLI config maneuvers that would no longer be possible in that scenario??