Date

28 Mar 2023

Call-in Information

Time: 10:00 am, Eastern Time (New York), 4pm Central Summer European Time

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. William Welling  
4. Ivan Mrsulja 
5. Miloš Popović
6. Maxim Prokopenko
   
7. Samantha Emerson
8. B. Henderson
9. Mei M
10. Rishabh Tatiraju
11. Christopher P. Barnes 
12. Mark Vanin 

Agenda

• Questions/Issues/Pull requests/Announcements
  • https://github.com/vivo-project/VIVO/issues/3850
    • https://github.com/vivo-project/VIVO/pull/3851
  • DSpace-VIVO wiki page
    • DSpace-VIVO
  • Installation of VIVO, issue with Tomcat read/write permissions
    • Installing VIVO
• iText-core vulnerability
  • https://github.com/vivo-project/VIVO/security/dependabot/3
  • https://github.com/vivo-project/VIVO/pull/3852
  • The last upgrade of iText-core in VIVO
    • https://github.com/vivo-project/VIVO/commit/980c48f84b00313bc3cf954702d842a52e765d81
  • The usage of itext
    • https://github.com/vivo-project/VIVO/search?q=PDFDocument
• VIVO release candidate number 3
  • https://github.com/vivo-project/VIVO/issues/3847
  • https://github.com/vivo-project/VIVO/issues/3848
  • https://github.com/vivo-project/VIVO/issues/3849
  • Readme file
• Dynamic API UI
  • https://docs.google.com/document/d/1jIIr90vTpI4l5KZeM30f_gOc-TpmlgKol-2oOEaU2Is/edit?usp=sharing
• Improvement of building process
  • Survey
  • Results - Summary
  • Sample data
    • https://github.com/vivo-project/sample-data/pull/9
• Upgrade to Jena 4
  • https://github.com/vivo-project/VIVO/pull/3836 https://github.com/vivo-project/Vitro/pull/368
  • https://github.com/vivo-project/VIVO/pull/3845 https://github.com/vivo-project/Vitro/pull/374
  • https://github.com/vivo-project/Vitro/pull/379
  • https://github.com/vivo-project/Vitro/pull/380
• The sprint 
  
  • Plan for the next sprint
    • continuation of the previous sprint or
    • some other topic
      • 2022/2023 VIVO Releases Planning
    • date
      • May 22nd - June 9th, 2023

Notes

Issue from a week ago about tomcat read/write permissions…

Itext core vulnerability, for current version, but that library is used only in one class that is not used anywhere look like it was experimental class that was forgotten

William: I think its experimental, I’m not sure we even generate pdf-s in VIVO

Dragan: maybe in some visualizations, I will check

Brian Lowe: First time I’m seeing this

—--------------

Dynamic api

Introduction

Got feedback from 3 institution

Maxim:

System specs where vivo was tested
Mac m2
Intel base 16gb Ram i7 or i9 2016
Tested on 32GB ram and it was still pagging for to long

Dragan:

If I copy all at once I am getting a memory exception. Every single file can be loaded 1 by 1 but loading all at once make problem

Chris Brain: You can open bug for it it doesn’t sound right

Dragan: I will try to open issue for this to have documented

Jena 4

No progress yet

Sprint

Dragan: I would like to know 3 weeks in advance, we don’t have to decide right now. For some other participants it’s quite important to know in advance

Draft notes in Google Docs

Task List

• Dragan Ivanovic to check whether PDFDocument class is needed at all (and itext dependency)
• Dragan Ivanovic to open a ticket (github issue) for ingesting sample data memory problem
• all
  • to provide feedback on https://docs.google.com/document/d/1jIIr90vTpI4l5KZeM30f_gOc-TpmlgKol-2oOEaU2Is/edit?usp=sharing,
  • consider participating in https://forms.gle/16QbRU62CmJCaeJp8
  • check personal calendars for the next sprint (May 22nd - June 9th, 2023)

Previous Tasks 

• Dragan Ivanovic to announce publishing VIVO 1.14.0 RC2
• someone to test RC2
  • Ivan Mrsulja tested RC2
• Dragan Ivanovic to create survey for collecting standard practice in VIVO deployment process 

• 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. 

• 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