Versions Compared

Key

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

...

    1. Create a new release candidate

    2. We will be testing vivo-ontology-lab pull request. https://github.com/vivo-project/VIVO/pull/63

    3. Is it good to go in production?

    4. Preparing documentation for release (LEAD - Mike)
    5. Team: Mike Conlon (VIVO) Muhammad Javed (Cornell) Benjamin Gross (Clarivate) Ralph O'Flinn (UAB)Jim Blake (Cornell)

    6. DELIVERABLES:

      1. Pull request merge in dev (and merge to master??)

Elastic Search 

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1423

  1. Decompose the task into smaller sections and focus on what can be achieved in two weeks time.

  2. Team: Benjamin Gross (Clarivate)Jim Blake (Cornell)Don Elsborg ( CU Boulder )
  3. DELIVERABLES:
  4. 1) Discuss/analyze the Elastic search work done by individual sites.
    2) Based on 1, implement current vitro search functionality in Elastic
    3) Create instructions on how to make YOUR VIVO installation work with Elastic (on the assumption that Solr will still be the default).
    4) analyze how to build a nested json-doc that represents an object ( person, publication, grant, etc ) in the index ( both SOLR or Elastic )
    5) lay groundwork for analysis of incorporating semantics ( json-ld, other ) in the indexed document. Mapping the objects from VIVO-ISF to an indexed semantic document would need to involve the ontology group


...