Date

Call-in Information

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

To join the online meeting:

Slack

Attendees

(star)  Indicating note-taker

  1. Brian Lowe
  2. Georgy Litvinov 
  3. Michel Héon 
  4. Nicolas Dickner 
  5. William Welling (star)

Agenda

  1. Slack questions
    1. Non-volatile triple stores and Docker?
      1. https://vivo-project.slack.com/archives/C8RL9L98A/p1617748487051600
      2. https://vivo-project.slack.com/archives/C8RL9L98A/p1617898157060900
    2. Things to update/clarify in Documentation
  2. Let's get RC1 shipped:
    1. Blocker issues
  3. Defining a "VIVO in a Box" project
    1. Latest description / draft diagram:
    2. Discussion / questions / refining the idea:
      1. Feedback to provide to Leadership group later in April?
      2. Keeping it simple for both users and developers
      3. Technical aspects:
        1. Integrating Scholars Discovery
        2. Simplifying editing forms?
        3. Scalability of triple store
        4. Multi-source ingest
      4. Overlap with other interests/initiatives
      5. Resources and time frame
  4. Other topics?

Future topics

  1. Forward-looking topics:
    1. frameworks: Spring / Spring Boot / alternatives
    2. Horizontal scalability
    3. Deployment
    4. Configuration : files / environment variables / GUI settings
    5. Editing / form handling
    6. Adding custom theming without customizing build
  2. Post-release priorities
    1. Ingest / Kafka
    2. Advanced Role Management
    3. Moving Scholars closer to core - next steps
  3. Vitro JMS messaging approaches - redux
    1. Which architectural pattern should we take?
    2. What should the body of the messages be
  4. Incremental development initiatives
    3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

  1. Status of In-Review tickets


Notes

    1. Docker and VIVO
      1. Requires vivo-home be in a persistent volume
      2. Likely need more documentation how to use Docker or docker-compose
        1. VIVO/docker-compose.yml at main · vivo-project/VIVO (github.com)
        2. vivo-project/VIVO: VIVO is an extensible semantic web application for research discovery and showcasing scholarly work (github.com)
      3. How to make it easier?
        1. Improve documentation
        2. Standardize on one docker approach to avoid confusion after release
    2. How to get release out the door?
      1. Blocker issues
        1. [VIVO-1976] Memory leak in RDFServiceGraph.createRDFServiceModel() - LYRASIS JIRA 
          1. in review - merged
        2. [VIVO-1973] Site admin users cannot edit pages - LYRASIS JIRA 
          1. in review - merged
    1. Documentation available when RC1 released
  1. VIVO in a Box
    1. Data Ingest - ReCiter harvester
      1. Require external data
        1. Pubmed
        2. Web of Science
        3. Scopus
        4. Proquest (CDI)
        5. EBSCO (EDS)
      2. Issues with ReCiter
        1. Primary and foundation bein Pubmed with additional overlay sources of Scopus
        2. No harvester for Web of Science, Proquest, EBSCO, ORCID, etc.
      3. Problem Space
        1. Real-time streaming ingest using Kafka
        2. Name disambiguation
        3. Affording various/agnostic data sources
        4. Institution Data - LDAP, Active Directory
    2. Profile Editor
      1. Faculty input
    3. TDB scalability
    4. Discovery
      1. Integrate scholars-discovery core into VIVO core
      2. Scholars-discovery next release
    5. Question
      1. Is it goal to move RDF to relational database?
        1. Yes/No
      2. How to produce a better architectural diagram?
      3. Is VIVO in a Box an appropriate name?
        1. It is more than just VIVO?
        2. Is it moving VIVO away from the semantic web?
    6. Issues
      1. Relational data to triplestore
      2. Visualizing/Viewing/Navigating graph
      3. Understanding/Customizing ontology
    7. Alternative uses of VIVO to increase adoption

Draft notes on Google Drive