Date

04 Jun 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. Don Elsborg
2. Brian Lowe
3. Benjamin Gross
4. Ralph O'Flinn
5. Andrew Woods
6. Taeber Rapczak
7. Team Univ of Florida
8. Mike Conlon
9. Steven McCauley
10. Alex Viggio
11. William Welling

Agenda

1. Upcoming sprint (June 17th - 28th)

   1. External Search

   2. Enable connection of decoupled, read-only "profiles" user interface to VIVO

      1. Leverage "Product Evolution" efforts

   3. Define "shapes" of VIVO entities

   4. Dockerize appropriate components

2. UF demonstration of TPF
3. Potential topics for next week:
   1. Design - External Search
      1. Merged 'sprint-search' (vivo, vitro) into 'develop'?
   2. Working towards the VIVO 1.11.0 release
      1. Landing Design - External Search
      2. Other tickets we want to include?
         1. Docker work:
            1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Don Elsborg to review?
            2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Don Elsborg to review?
            3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Ralph O'Flinn to review? - Now in https://github.com/vivo-community/vivo-docker2
         2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         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.
      3. Release manager?
   3. Decoupling VIVO components
      1. Search index - almost complete
      2. Read-only UI - VIVO Scholars Task Force / TAMU
      3. Triplestore?
   4. TAMU Scholars / VIVO Scholars Entities
   5. New feature: Messaging
      1. Based on the IndexingChangeListener pattern
      2. Potentially with RDF-Patch bodies

   6. Tickets

      1. Needing additional review
         1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Benjamin Gross?
      2. Received Tickets...

         type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
         Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Tickets

1. Status of In-Review tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Received

   Click here to expand...

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

      1. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design

   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Should be low-hanging

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

      1. Where does this stand? What is needed to add more person identifiers to VIVO?

   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Mike Conlon : thoughts on where this stands?

3. Bugs (1.11)

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

Recording

• http://bit.ly/vivo-uf-2019-06

Draft notes in Google-Doc

1. Initiative being hosted from the Univ of Florida
   1. metabolomics science
   2. Cross-institutional VIVO - 15 univ
      1. national repo, metabolomics-workbench
   3. Site: metabolomics.info
   4. Building ontology at present
2. Using VIVO's triple-pattern-fragments (TPF) endpoint
   1. VIVO 1.10

   2. TPF is serving local content

   3. Friendly to non-developers, javascript

   4. GitHub: https://github.com/ctsit/m3c-web
      1. TPF client pulls triples, then renders
      2. TPF client follows complex relationships, filtering results
      3. Mike C is the initial author of the TPF client
         1. Enables rich traversal of graphs, even remote links
3. UNAVCO is exposing TPF, but not actively using it
4. Sept timeline for UF to go live
5. Discussion of overlap with VSTF?
   1. Read-only UI
6. performance? - would be interesting to test at larger scale
   1. Suspicion that performance will not be an issue
   2. Exploration of client vs server-side solutions

Actions

Previous Actions

• Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Mike Conlon, can you give this one a review?