Date

15 May 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. Tim Worrall
6. John Fereira
7. Muhammad Javed
8. Huda Khan
9. Ralph O'Flinn
10. Andrew Woods

Agenda

1. Can folks spin up vivo-docker2?

2. Reflections on CINECA UI demonstration?
3. Finalizing / merging: 
   1. Design - External Search
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  (DuraSpace CheckStyle)
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   9. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   10. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   11. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
4. VIVO Acceptance tests - reducing runtime
5. Messaging
   1. Based on the IndexingChangeListener pattern
   2. Potentially with RDF-Patch bodies
6. Next steps
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

Docker

1. Ralph using Docker in externalized Solr
2. Brian to use Mac for Docker
3. Huda making progress
4. Benjamin has yet to try

Cineca

1. Interest in seeing the code
2. Sounded like a good pattern
3. JSON configuration approach helpful when it fits
   • This may not always work with complex facets
   • One consistent way of defining search-indexing is important
   • Will need to pay attention to this in the code review
4. The features are appealing
   • Potential opportunity for UI clean-up
   • Would be interesting to evaluate against all approaches to UI features
5. Which implementation of a feature makes it into the core?
   • First pull-request?
   • Call to the community for a feature?
     • i.e. Duke has facets

Tickets

1. Asking for reviews
   • vivo-1692 - Benjamin
   • vivo-1415 - Andrew
   • vivo-1670 - Andrew

Acceptance tests

1. Need to establish a lightweight version
2. Suggestion: group tests together that do not require completely clean environment

VIVO-1691

1. Ideally, we could have ability to include modular UI components
2. Question around advantages of UI over original configuration capability

Actions

Previous Actions