...
Agenda
- Sprint updates - i18n
- VIVO installation: the vision and requirements
- 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
- 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?
- Moving tickets forward
- back on your plate, Mike ConlonJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1658
- Who is working on what? - Are there active tickets in-progress?
Expand Jira server DuraSpace JIRA jqlQuery filter=15500 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
- Incremental development initiatives
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1688 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1751 - Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752
...