...

 Indicating note-taker

1. Brian Lowe 
2. Mike Conlon 
3. Benjamin Gross  
4. Ralph O'Flinn 
5. Don ElsborgAndrew Woods Andrew Woods
6. Don Elsborg
7. Huda Khan

Agenda

1. 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}

      
      

2. 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

3. 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

...

1. Vitro JMS messaging approaches
2. Architectural diagrams - discuss at a future date
   1. VIVO Components
   2. VIVO Ecosystem

Notes

Solr

1. One potential implementation approach
   1. Include vivo-solr Maven dependency
   2. if SOLR_DATA_HOME defined, copy vivo-solr content into that directory
2. Can we support third-tier overlay?
3. Interest in moving vivo-solr into vivo-project GitHub org
4. 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

1. Recognition that a released vivo.war artifact will likely have limited use, since even basic customizations (logos, ftl, js) require rebuilding the application
2. 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

...