Date

16 Jul 2019

Call-in Information

Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)

To join the online meeting:

• Go to: https://duraspace.zoom.us/j/823948749
• Or iPhone one-tap :
  • US: +14086380968,,823948749#  or +16468769923,,823948749#
• Or Telephone:
  • Dial(for higher quality, dial a number based on your current location):
  • US: +1 408 638 0968  or +1 646 876 9923  or +1 669 900 6833
  • Meeting ID: 823 948 749
• International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. Ralph O'Flinn 
2. Steven McCauley 
3. Andrew Woods
4. Brian Lowe
5. Don Elsborg
6. Maria Amalia Florez
7. Rafael Mancera
8. Jose Mongui

Agenda

1. 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
2. Integrating content and navigating between VIVO installations
3. Internationalization partners in VIVO Scholars Task Force?
4. Tickets in-review
   1. Needing one more review - any volunteers? 
      1. 
      2. 

   2. 
      

      
      

Tickets

1. Status of In-Review tickets

   
   

2. Received

   (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design Should be low-hanging Where does this stand? What is needed to add more person identifiers to VIVO? Mike Conlon : thoughts on where this stands?

   
   

3. Bugs (1.11)

   
   

   
   

Notes 

Draft notes in Google-Doc  

1. VIVO 1.11.0 release
• 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
2. Integrating VIVO installations
• 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

Actions

Previous Actions

•  - Mike Conlon, can you give this one a review?