Date

21 Feb 2023

Call-in Information

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

To join the online meeting:

• https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09

  Meeting ID: 843 7861 5572
  Passcode: 556561
  One tap mobile
  +16699006833,,84378615572#,,,,*556561# US (San Jose)
  +19292056099,,84378615572#,,,,*556561# US (New York)

  Dial by your location
          +1 669 900 6833 US (San Jose)
          +1 929 205 6099 US (New York)
          +1 253 215 8782 US (Tacoma)
          +1 301 715 8592 US (Washington DC)
          +1 312 626 6799 US (Chicago)
          +1 346 248 7799 US (Houston)
          877 853 5257 US Toll-free
          888 475 4499 US Toll-free
  Meeting ID: 843 7861 5572
  Passcode: 556561
  Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4

Slack

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

Attendees

 Indicating note-taker

1. Dragan Ivanovic 
2. Brian Lowe    
3. Michel Héon 
4. William Welling
5. Georgy Litvinov  
6. Kevin Day 
7. Mark Vanin 

Agenda

• Questions/Issues/Pull requests/Announcements
  • SPARQL Update API throws parsing errors when the triple contains & symbol, Is there anyway to escape it?  (Slack question)
    • Dragan's response
  • VIVO release candidate
    • Release Testing - 1.14.0
  • Solr vulnerability issue
    • https://groups.google.com/g/vivo-tech/c/0LTVApDBFvQ
• VIVO map of science
  
  • Brian's request
• The sprint
  • The first meeting - 2023-02-20 - opening sprint meeting

• • When
    • 20.02.23 - 10.03.2023
  • The topic
    • semantic web - https://github.com/orgs/vivo-project/projects/5/views/1
      • Jena upgrade
        • get rid of SDB code (Jena 4 is not supporting SDB)
        • fix live backup of TDB
      • External triple store performance improvement
        • analysis, not implementation
          • find bottle neck and identify how it should be improved
      • Implement a new owl-reasoner (maybe https://github.com/stardog-union/pellet)
        • analysis, not implementation
      • Addition of a new expertise vocabulary
        
        • To apply for a grant, Canadian researchers must classify the area of their research according to the Canadian federal government's standard taxonomy called Canadian Research and Development Classification (CRDC) 2020 Version 1.0. For this sprint we would like to port the code already developed internally to the vivo core
        • work already done https://github.com/michel-heon/CCRD-CRDC
        • Deliverables for this proposal
          • The RDF/S representation of the CRDC vocabulary in English and French
          • The Java code allowing the use of the CRDC by VIVO
          • Review the documentation that appeared to be incomplete (Configuring External Vocabularies)
          • Explore the possibility of introducing a vivo:Expertise class instead of using a skos:Concept to describe an expertise
    • Deployment/installer - https://github.com/orgs/vivo-project/projects/6/views/1
      • VIVO-Installer review depending on the target user: developer, infra architect, corporate/institutional evaluator, etc.
      • decoupling building and deployment
      • deployment for testing by including sample data
      • deployment for production
        • specification of tdb backup parameters ???

Notes

1. New feature for release candidate from 1.13.0.
1. Release VIVO-1.13.0 · vivo-project/VIVO (github.com)
2. Release VIVO-1.13.0 · vivo-project/VIVO (github.com)
2. Changes for 1.14.0
1. Release Testing - 1.14.0
2. Pull requests · vivo-project/VIVO (github.com)
3. Pull requests · vivo-project/Vitro (github.com)
3. Solr issues prompt for questions?
1. CVE-2021-27905
2. Does Vitro/VIVO replicate index date?
3. vivo-project/vivo-solr: Configuration and Installation instructions for VIVO's external Solr (github.com)
4. Projects · vivo-project (github.com)
1. Installation and environment improvements (github.com)
1. Code style [3]
2. Configuration [2]
3. Dependency [2]
4. Docker [2]
5. GitHub Action [4]
6. Maven [2]
7. Testing/Performance [2]
8. No Track [1]
2. Semantic web features improvements (github.com)
1. Bugs [4] [-1]
2. External graph base [2]
3. Jena TDB [5]
4. Reasoning [2]
5. Sample data [2]
6. No Track (Epic) [2]
5. [VIVO #3680] - Duplicated faux properties every time#3680 on board but closed
6. [VIVO #3822] Align Docker containers with changes introduced by decoupling VIVO build from installation#3822 needs triage
7. What is the estimated level of difficulty per issue?
8. Michel Héon to Everyone - For my part, I am available for semantic web External Graph Base and Reasoning Maybe Jena TDB

Draft notes in Google Docs

Task List

• Dragan Ivanovic to add columns in the project board for Priority and Difficulty.
• Sprint participants to read description of issues and think about their preferences. 

Previous Tasks 

• Dragan Ivanovic will contact Lyrasis admins to get an account for https://vivo.lyrasis.org/
• Dragan Ivanovic will fix issues with layout and French sample data and publication graph - https://github.com/vivo-project/VIVO/pull/3810
• Georgy Litvinov will fix the issue with faux data properties with xml literal range - https://github.com/vivo-project/Vitro/pull/363
• William Welling will review previously described issues
• Dragan Ivanovic will work on specification of tasks for the next sprint - https://github.com/orgs/vivo-project/projects/5 and https://github.com/orgs/vivo-project/projects/6
• Dragan Ivanovic to send a test email through contact form - https://vivo.lyrasis.org/contact/
• William Welling to complete review/testing of  https://github.com/vivo-project/VIVO/pull/3805 and to summarize results in the PRs comments
•  Dragan Ivanovic to review William's comments and check what should be fixed/resolved before merging of the the branch
  • Georgy Litvinov to fix issues with Russian email templates
  • Georgy Litvinov to fix issues with faux data properties
• All to think about organization/improvements of sample data, Dragan Ivanovic to add an item in the next week agenda for discussion
• Dragan Ivanovic in communication with Georgy Litvinov to write/update documentation for faux (data) properties
• Dragan Ivanovic to review and merge 
  • https://github.com/vivo-project/Vitro/pull/360
  • https://github.com/vivo-project/Vitro/pull/361

• Brian Lowe to review https://github.com/vivo-project/VIVO/pull/3788 and https://github.com/vivo-project/Vitro/pull/341 preferably by end of the week (11/25/2022)
• Brian Lowe to review https://github.com/vivo-project/Vitro/pull/347
• Michel Héon to validate https://github.com/vivo-project/Vitro/pull/347 and test performance with remote Fuseki 
• Anyone to validate https://github.com/vivo-project/Vitro/pull/348 and https://github.com/vivo-project/VIVO/pull/3797 preferably by end of the week (11/25/2022)  - description how it should be validated provided in the PR description
• Benjamin Kampe to review https://github.com/vivo-project/Vitro/pull/349 and https://github.com/vivo-project/VIVO/pull/3795 preferably by end of the week (11/25/2022)
• Dragan Ivanovic to create PR in cooperation with Michel Héon for merging ttl files (labels' translations) into Vitro/VIVO repositories
• Dragan Ivanovic to ask Arif for more info on the reported issue - https://groups.google.com/g/vivo-tech/c/gmyQIMWbm_Y
• Dragan Ivanovic to open a ticket for https://groups.google.com/g/vivo-tech/c/wDblxLmeTjs. Done, ticket available at https://github.com/vivo-project/VIVO/issues/3772
• Dragan Ivanovic will redirect reporter of this issue https://github.com/vivo-community/vivo-docker2/issues/22 to https://github.com/vivo-project/VIVO#docker
• All to analyze the issue reported in the slack (https://vivo-project.slack.com/archives/C8RL9L98A/p1663253504895989) and check whether we should open a GitHub issue and add to the i18n redesign project board - https://github.com/orgs/vivo-project/projects/4 
• Brian Lowe will respond on the email https://groups.google.com/g/vivo-tech/c/5AY9h15h4vc/m/OjqekVxlBgAJ?utm_medium=email&utm_source=footer&pli=1
• All to consider participation in the sprint and register via https://forms.gle/qLi1PhRrrpvUrrYRA
• Dragan Ivanovic to work on specification of tasks for the sprint - GitHub project board
• Michel Héon to work on the translation messages ontology
• Dragan Ivanovic will bring up with leadership group that we would like to set up task force for dynamic API
• Dragan Ivanovic will create infrastructure for the next sprint (slack channel, GitHub project board, wiki page, GitHub branch, GitHub issues, etc.)
• Michel Héon to work on the ontology for UI labels (in multiple languages)
• All to think about dates for the next sprint
• Dragan Ivanovic to resolve conflicts for https://github.com/vivo-project/Vitro/pull/311 and https://github.com/vivo-project/Vitro/pull/297
• Dragan Ivanovic to write script for preparing a release candidate - started at https://github.com/chenejac/VIVO-release-publisher
• All to test the release candidate - Release Testing - 1.13.0
• Dragan Ivanovic to publish VIVO 1.13.0 release (if there is no reported issue till 1st of September)
• Dragan Ivanovic to prepare presentation for demo meeting - 2022-07-07 - Dynamic API demo meeting
• Dragan Ivanovic to send reminder for the demo meeting - 2022-07-07 - Dynamic API demo meeting
• Dragan Ivanovic to open an issue for a reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
  • https://github.com/vivo-project/VIVO/issues/3698
• Dragan Ivanovic to contact Andrew Wood for resolving the issue with registration for the Slack channel
• All to consider participation in the sprint and if decide  to participate to register for the sprint - link
• Dragan Ivanovic to send a require to add in the Leadership group agenda a topic for discussing Copyright owner in License
• All please help in filling this document - spreadsheet
•  Dragan Ivanovic to create a draft version of a Google Spreadsheet document with labeled columns representing requirements and to share with committers
• Committers to review the structure of the document and to fill it with data for JS and CSS frameworks