Skip to end of metadata
Go to start of metadata

Date

Call-in Information

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

To join the online meeting:

Slack

Attendees

(star)  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 Stanley 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. VIVO-1679 - Getting issue details... STATUS  - Don Elsborg to review?
          2. VIVO-1680 - Getting issue details... STATUS  - Don Elsborg to review?
          3. VIVO-1682 - Getting issue details... STATUS  - Ralph O'Flinn to review? - Now in https://github.com/vivo-community/vivo-docker2
        2. VIVO-1670 - Getting issue details... STATUS
        3. VIVO-1415 - Getting issue details... STATUS
        4. VIVO-1692 - Getting issue details... STATUS
      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. VIVO-1692 - Getting issue details... STATUS
        2. VIVO-1687 - Getting issue details... STATUS
        3. VIVO-1675 - Getting issue details... STATUS  - Benjamin Gross?
      2.  Received Tickets...

        T Key Summary Assignee Reporter P Status Resolution Created Updated Due
        Loading...
        Refresh

Tickets

  1. Status of In-Review tickets

     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

  2. Received

     Click here to expand...
     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

    1. VIVO-1666 - Getting issue details... STATUS

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

    2. VIVO-1665 - Getting issue details... STATUS
      1. Should be low-hanging
    3. VIVO-1663 - Getting issue details... STATUS

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

    4. VIVO-1644 - Getting issue details... STATUS
      1. Mike Conlon : thoughts on where this stands?
  3. Bugs (1.11)

     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due
    Loading...
    Refresh

Notes 

Recording


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


  • No labels