Page History

...

Update on Solr configuration investigations
1. Solr create core API
2. Copy contents of vivo-solr into ${MY_DATA}
3. No Format
  curl -i http://localhost:8983/solr/admin/cores?action=CREATE\&name=vivocore\&instanceDir=${MY_DATA}
Tickets to review / merge:
1. Jira
  server DuraSpace JIRA
  serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
  key VIVO-1782
2. Jira
  server DuraSpace JIRA
  serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
  key VIVO-1785
3. Jira
  server DuraSpace JIRA
  serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
  key VIVO-1777
4. Jira
  server DuraSpace JIRA
  serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
  key VIVO-1836
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 <-- start here
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

...

Space shortcuts