Indicating note-taker

Agenda

VIVO 1.11.0 release... can we get a release candidate out before the VIVO conference?
1. External Search
  1. Merge 'sprint-search' (vivo, vitro) into 'develop'?
  2. Help with testing externalized search
Integrating content and navigating between VIVO installations
Internationalization partners in VIVO Scholars Task Force?
Tickets in-review
1. Needing one more review - any volunteers?
  1. Jira
    server DuraSpace JIRA
    columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
    key VIVO-1692
  2. Jira
    server DuraSpace JIRA
    serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
    key VIVO-1670
2. Expand
  Jira
  server DuraSpace JIRA
  jqlQuery filter=14416
  serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

...

Externalized Search: branch only waiting on review prior to merge, re: data logging. Review is close to completion
No change from users’ perspective: only change is to search engine deployment
Status of Elasticsearch integration is “extremely beta”
Blazegraph: how much work until we have an externalized triplestore? Externalizing triplestore has implications for loading data. Older processes depend on Jena API
How to share data for testing VIVO Scholars frontend
Adding T-Box data via the Update API: won’t be reasoned over, but will be added to triplestore
Ralph as release manager

Navigating between systems: trial runs by implementers using “same as” relationships
Describing a concrete use case from https://www.adaggio.com.co/
Start a new LOD slack channel for discussion and planning? Or just use the develop channel?
Basic question: federated search? Or ingest remote data into local installation?
Stay tuned to Slack: https://vivo-project.slack.com

...

Space shortcuts