...

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

...

1. Can folks spin up vivo-docker2?

2. Reflections on CINECA UI demonstration?
3. Finalizing / merging: 
   1. Design - External Search

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1692

       (DuraSpace CheckStyle)

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1687

   4. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1682

   5. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1680

   6. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1679

   7. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1670

   8. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1652

   9. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1612

   10. Jira
       server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1415

   11. Jira
       server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1287

4. VIVO Acceptance tests - reducing runtime
5. Messaging
   1. Based on the IndexingChangeListener pattern
   2. Potentially with RDF-Patch bodies
6. Next steps

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1691

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

...