Date

03 Apr 2019

Call-in Information

• https://duraspace.zoom.us/my/vivo1

Attendees

 Indicating note-taker

1. Graham Triggs
2. Mike Conlon
3. Brian Lowe
4. Benjamin Gross
5. Jim Blake
6. Tim Worrall
7. John Fereira
8. Muhammad Javed
9. Huda Khan
10. Ralph O'Flinn
11. Andrew Woods

Agenda

1. Resolving:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Finalizing / merging: 
   1. https://github.com/vivo-project/VIVO/tree/sprint-search and
   2. https://github.com/vivo-project/Vitro/tree/sprint-search
3. Populating derivative stores

   1. Notes from last call:

      Maybe establish a new mechanism for populating derivative stores

      • Interface: listen to events from triplestore
      • Current Solr indexing would fit into this mechanism (i.e. implement interface)
      • Pushing external messages could be another implementation of the interface
      • Would require updates to applicationSetup.n3
        • Other configuration happens within the displayModel
        • DocumentModifier config should likely be pulled out of the displayModel, and put into applicationSetup.n3
        • Rationale for config to be in the displayModel was for UI/runtime updates

Notes 

• Considering presentations for VIVO conference.  Huda: Won't be there but any thought about presentations on architectural fly-in outcomes?  Andrew: Is planning/hoping to go and perhaps doing a state of VIVO update presentation which would include review of architectural directions.   Brian: may also be able to contribute and plans on being at conference.
•  VIVO 1685: Docker images have been created.  Sprint search branches probably need to be brought up to date - probably rebase on develop. 
  
  • Could collaboratively work through this issue live
  • Instructions/links for docker can be found here: https://github.com/vivo-community/vivo-docker2.   Issue has steps go through
  • Rebased sprint-search branches in VIVO and Vitro with develop.  The latter didn't require any changes but VIVO required a change (the solr/pom.xml file had been removed in the sprint search). 
  • After rebase, the docker compose step went through without the old JAVA error.
    • did a git rm for the file, didn't seem to like it. then did git add, didn't like it.  git status showed things ok, tried rebase again. then it was fine.
  • Although build process indicated the database was setup, starting the application resulted in error indicating connection to MariaDB/the database was not working

Actions

Previous Actions