Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Draft notes in Google-Doc

External Search

  1. Ralph making progress on testing
    • Will be testing updated ElasticSearch
  2. Also testing BlazeGraph
    • Don: is using vivo-docker2, VIVO 1.10
    • BlazeGraph errors should be addressed in sprint-search branch
  3. Don to test sprint-search branch
  4. A few use cases Docker can help with: vanilla installation or instance with local customizations.  

    1. What would be good is for docker setup to pull war file, whether the file is a standard 1.10 or one with local customizations.  

    2. Getting away from need to build the software.

  5. What remains to be done with the externalized search sprint branch to allow that branch to be integrated into develop.  

    1. Andrew has listed the issues and we need a few people to look at these issues/review/merge in order for the sprint search branch to be mergeable into develop.

    2. How to actually test/review this work?  

      1. Potentially include data in the search index and then test against that.

  6. Would be interesting to test Alessandro’s CINECA facets etc (pr-vitro-123) against this branch... but not a requirement
  7. ElasticSearch integration is included in 'sprint-search' branch
    • Messaging/Documentation should be clear: ElasticSearch integration is "Beta"
  8. Any unforeseen consequences to bring in the external search work?  Performance?

    1. No, the interaction between VIVO and Solr is unchanged
  9. Jim did some work with ElasticSearch: https://github.com/vivo-project/Vitro/commit/45ddb56294eddccb929dd88a30072aec310d11ee

  10. Should we consider having just Solr in the sprint-search branch and taking out ElasticSearch (since some of this still needs further work) or should we merge all of this work and then include a beta flag around the documentation for ElasticSearch?  

    1. People on the call prefer later option.

1.11

  1. Shooting for a release before VIVO Conference
  2. Open question regarding any additional tickets to target for 1.11 beyond what is already there and externalized-search

Actions

  •  
    Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyVIVO-1659
     - Mike Conlon, can you give this one a review?

...