Skip to end of metadata
Go to start of metadata

Date

Call-in Information

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

To join the online meeting:

Slack

Attendees

(star)  Indicating note-taker

  1.  Don Elsborg
  2. Ralph O'Flinn 
  3. Andrew Woods
  4. Huda Khan 
  5. Alex Viggio (star)
  6. Benjamin Gross
  7. Brian Lowe
  8. Laura Doyle
  9. Christopher Haines
  10. Robert Nelson

Agenda

  1. Misc
    1. Next week's dev meeting: Welcome to those new to the VIVO tech stack!
    2. Interesting article / podcast on the NYTimes' use of React and GraphQL
  2. CU Boulder update/demo: https://experts.colorado.edu/publications
  3. Architecture of populating external indexes
    1. Push from core?
    2. Harvest from external tools?
  4. March (18-29) sprint planning

    1. Finish work on externalizing Solr and Elasticsearch
    2. Externalize triplestore
    3. Decoupling - Dockerize: Solr, Elasticsearch, MySQL, Fuseki, rest-of-VIVO
      1. Reference: Docker 101 and 102
  5. From the previous actions

    1. Brian Lowe  confirm LDF server issue with TDB content stores
      1. VIVO-1615 - Getting issue details... STATUS
      2. Is there a fix?
    2. Brian Lowe   - check with ontology group on handles
      1. Any feedback from the ontology group? (reference)
  6. Mailing list messages

    1. Some triples not getting deleted in VIVO?
    2. how to link PDF of particular publication
  7. Status of In-Review tickets

     Click here to expand...

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

    1. Soft balls

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

        1. Low-hanging - need one more reviewer - Brian Loweis reviewing

      2. VIVO-1659 - Getting issue details... STATUS
        1. Low-hanging, documentation - Mike Conlon, can you give this one a review?
    2. Regular balls
      1. VIVO-1675 - Getting issue details... STATUS

        1. New
      2. VIVO-1670 - Getting issue details... STATUS

        1. Kitio Fofack ? Orcid and i18n

      3. VIVO-1656 - Getting issue details... STATUS
        1. Is this feature of broader interest?
      4. VIVO-1643 - Getting issue details... STATUS
        1. Andrew Woods to look into
      5. VIVO-1642 - Getting issue details... STATUS
        1. Mostly trivial, with conversation around Tomcat version support
      6. VIVO-1641 - Getting issue details... STATUS
        1. Relatively straight-forward bug fix
      7. VIVO-1661 - Getting issue details... STATUS
        1. An important step for i18n... resolves many other open issues
      8. VIVO-1630 - Getting issue details... STATUS
        1. Kitio Fofack to review?
  8. 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?
  9. Bugs (1.11)

     Click here to expand...

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

Notes 

Draft notes in Google-Doc

  • Topic next week “open forum for fielding questions and discussion -- welcome to new community members” with Ralph facilitating and other committers available

  • NYT React/GraphQL podcast link -- worth a listen https://softwareengineeringdaily.com/2018/10/22/react-and-graphql-at-the-nytimes/

  • Don’s CU Experts faceted search demo

    • Facetview2 integration at Deep Carbon, CU Boulder and UNAVCO

    • Stefan at RPI found Facetview2 from Cottage Labs (UK boutique consultants)

    • Integrated into Deep Carbon site for people, pubs, etc

    • Benjamin also used their code for UNAVCO and helped Nate get it running at CU Boulder

    • Don modified RPI code to use the SPARQL Query API instead of Fuseki

    • VIVO as source of data pushed into Elasticsearch index. Originally coded to query Fuseki, and now works against VIVO SPARQL Query API

      • Python script that pulls from VIVO triples to create Elasticsearch documents

      • 87k docs from VIVO into ES: process takes 30 minutes

      • Motivations for Elasticsearch upgrade… RPI and Cottage Labs code was on an old 1.x version of ES which is now at 6.x

    • Uploaded ES 6.x updated facetedsearch and facetview code to VIVO Community

    • Chris Haines: what’s the system reqs/resources for the ingest? Don: our dev VM is a 4 vCPU with 10GB RAM and works fine

    • Chris and Laura from EPA looking at faceted browse/search

    • Integration into VIVO user experience on GitHub under facetedsearch/html/

      • Could be improved -- maybe use GitHub Issues to track room for improvement?

    • Benjamin: “UNAVCO's people browse page template: https://github.com/NCAR/2014-EarthCube-BuildingBlocks-EnablingCollaboration-14402930-vivo-source/blob/develop/unavco-installer/webapp/src/main/webapp/themes/unavco-bootstrapped-vivo/templates/people-elasticsearch.ftl
”

      • Another example that’s more modular -- includes the VIVO FTL for header, footer, etc

    • Don: we put our facet .FTL files in CU’s 3rd tier -- described in the repo README

    • Andrew: do you imagine migrating more functionality into this read-only view

      • We arrived there borrowing RPI functionality

    • Don: quick sidebar on integrating wikidata (concept map) and ES (+1 from Huda) -- also one querying UNAVCO’s ES for CU Boulder ORCIDs

    • Andrew: knows some Cottage Labs folks in another context -- might be interesting to follow up with them to see if they have other work of interest to VIVO community

    • Andrew: follow up in future on how this fits in with Product Evolution

    • Benjamin: completing ES integration in VIVO which would support incremental updates of ES instead of requiring a “side car” that extracts from triple store to push into ES -- Chris: that would be the ideal integration option

  • Sprint in March -- opportunity to finish up the ES/Solr work from previous sprint, externalizing triple store, and separating components out into Docker containers

  • Andrew: take a look at Agenda item #6 (6a and 6b)

Actions

Previous Actions

  •  


  • No labels