Sept 17-28, 2018


  1. Graham Triggs
  2. Andrew Woods
  3. Mike Conlon (Second week: September 24-28, documentation, testing)
  4. Qazi Asim Ijaz Ahmad (Not sure about the dates yet. Would like to work on Elastic Search with Don)
  5. Kitio Fofack mainly on i18n (available for the sprint)
  6. Christian Hauschke (2nd week, i18n)
  7. Ralph O'Flinn
  8. Brian Lowe
  9. Don Elsborg
  10. Steven McCauley
  11. Manuel Schwarz


2018-09-17 Sprint - Kickoff Meeting


Scrum Board

Elasticsearch / Solr Upgrade


  1. Don Elsborg (CU Boulder)
  2. Qazi Asim Ijaz Ahmad
  3. Steven McCauley
  4. Ralph O'Flinn


  1. Security concerns with Solr dependencies

  2. Integrated elastic index in VIVO to support facetview UI used by Unavco, CU Boulder, DCO

  3. Brings index work from Product Evolution group closer to the VIVO core

  4. Deliver more structured and rich json and eventually json-ld documents from VIVO's indexes for web consumers


  1. Discuss/Analyze/Document the ElasticSearch work done by individual sites.

    1. Which sites?
  2. Create a design for externalized search
    1. Support ElasticSearch (v6.4.0)
    2. Support Solr (7.4.0 & 4.10?)
  3. Implement externalized search
    1. Initial Solr work from Huda (Ralph O'Flinn, Steven McCauley )
    2. Initial ElasticSearch work from Jim ( Don Elsborg)
    3. merge pull requests from items a and b above into a new combined sprint branch
    4. verify the search engine abstraction layer such that VIVO can work with both ES and SOLR based on above 2 items
  4. Create instructions on how to make YOUR VIVO installation work with ES or SOLR (on the assumption that Solr will still be the default).

Second priority deliverables

  1. Analyze how to build a nested json-doc that represents an object ( person, publication, grant, etc ) in the index ( both SOLR or Elastic )

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

  3. Request: keeping the delivered Elasticsearch integration backwards compatible with VIVO 1.9.3 and 1.8.x – could be valuable

Relevant docs


Multi-Language Support


  1. Christian Hauschke
  2. Kitio Fofack
  3. Ralph O'Flinn
  4. Manuel Schwarz


Implement interface i18n  on home page, the capability Map and the profile header form.
The interface should be able to completely switch to the selected language.


  1. Identify all places in code/freemarker/jsp that need extraction and create related JIRA Tickets
    • Split codebase across different people (per package?)
    • ACTION: Kitio to divide codebase
  2. Initialize language artifacts necessary to be complete for interface i18n
    1. Create the translations (English, German, French)
  3. Improve toggling mechanism (do not use flags)
  4. Improve technical documentation for adding new languages
    • Pulling in Maven artifacts

Future deliverables

  1. Rectifying differences in grammar
  2. Pluralization - need appropriate infrastructure
  3. i18n support for multi-language content

ABox / TBox RDF Loading


  1. Don Elsborg
  2. Brian Lowe
  3. Mike Conlon


  1. Identify and understand current documentation
    1. Accessing VIVO Data Models#InitializingtheModels
    2. Directories and Files
    3. Graph Reference
    4. Ontology Reference
  2. Understand and Document recommendations for updating and overriding `firsttime` and `everytime` RDF files
  3. Understand and Document how this RDF data is organized in the content and configuration triple stores


  1. Documentation of Content, Structure, Purpose, etc of 'firstime' / 'everytime' / 'filegraph'  abox,tbox RDF files and each of the directories that they're located in. See item 1.b 'Directories and Files' above
  2. Documentation of where 'firsttime' / 'everytime' / 'filegraph' abox/tbox RDF is loaded (which triplestores-config vs content stores), and why
  3. Verify the documentation of the relationships with vdata/rdf and the actual graphs – changes in the GUI don't get reflected in $vitro-home/rdf 
  4. Documentation of pitfalls – things not to delete. (ClassGroups?  And other things that are loaded by firsttime and are difficult to reset to their initial state without clearing the triple store)
  5. Documentation of use cases for updating 'firsttime' / 'everytime' RDF files
  6. Documentation of recommendations for above use cases

Future deliverables

  1. Resetting 'firsttime' - Brian Lowe to elaborate
  2. Persisting updates from the GUI (ClassGroup / PropertyGroup / etc) - Don Elsborgto elaborate
  • No labels