Date
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
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
- Don Elsborg
- Huda Khan
- Benjamin Gross
- Ralph O'Flinn
- Brian Lowe
- Michel Héon
- Nicolas Dickner
- Alexander (Sacha) Jerabek
Agenda
- The i18n effort continues
- Need merge from VIVO Committer (other than Andrew)
- Sprint next week
- Identifying participants
- Defining goals
- Need merge from VIVO Committer (other than Andrew)
- VIVO installation: the vision and requirements - Where does this conversation stand? Is there consensus?
- 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, andconfigure Solr, if it has not been configured - 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
- Vitro JMS messaging approaches - redux
- Which architectural pattern should we take?
- 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
- Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Tickets
Status of In-Review tickets
Notes
Actions