...
Indicating note-taker
- Brian Lowe
Mike Conlon- Benjamin Gross
- Ralph O'Flinn
- Don ElsborgAndrew Woods Andrew Woods
Don Elsborg- Huda Khan
Agenda
- Update on Solr configuration investigations
- Solr create core API
- Copy contents of vivo-solr into ${MY_DATA}
No Format curl -i http://localhost:8983/solr/admin/cores?action=CREATE\&name=vivocore\&instanceDir=${MY_DATA}
- Tickets to review / merge:
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1782 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1785 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1777 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1836
- 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 <-- start here
- 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
- Architectural diagrams - discuss at a future date
Notes
Solr
- One potential implementation approach
- Include vivo-solr Maven dependency
- if SOLR_DATA_HOME defined, copy vivo-solr content into that directory
- Can we support third-tier overlay?
- Interest in moving vivo-solr into vivo-project GitHub org
- Andrew to create ticket for finding diffs in vivo-solr - Huda -
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1849
VIVO installation
- Recognition that a released vivo.war artifact will likely have limited use, since even basic customizations (logos, ftl, js) require rebuilding the application
- Recognition that the approach of vivo.war populating the VIVO_HOME directory must also consider the upgrade scenario: some files should be overwritten... but not all
Actions
- ...
Previous Actions
...