Date

27 Jun 2023

Call-in Information

Time: 10:00 am, Eastern Time (New York), 4pm Central European Summer 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. Georgy Litvinov  
3. Kshitij Sinha
4. Michel Héon 
5. Brian Lowe 
6. Benjamin Kampe 
7. Ivan Mrsulja 
8. Miloš Popović 
9. Mark Vanin 
10. William Welling 

Agenda

• Questions/Issues/Pull requests/Announcements
  • VIVO REST API (Dynamic  API) for Persons
  • Long delay when logging in
    • PR merged
  • Publication claiming
    • Documentation updated
      • https://github.com/vivo-project/VIVO/issues/3883
      • Editing Your Profile#PositionsandPublications
  • Capability map vulnerability
    • https://vivo-project.slack.com/archives/C8RL9L98A/p1687378615914659
    • https://github.com/vivo-project/VIVO/pull/3896 
• VIVO 1.14.0 RC 5
  • Testing week
    • 19-23 June 2023 
    • Release Testing - 1.14.0

      • New Features Tests (response summary) : these tests exercise new functionality in version 1.14.0. 

      • Standard UI Tests (response summary) : these tests exercise standard functionality in the VIVO user interface.

      • Advanced Tests (response summary) : these tests are intended for software developers.

• VIVO 1.15.0
  • features
    • REST API (person, org unit, research)
    • Search filters (extended search)
    • Audit module (change tracking)
  • Improvements
    • Advanced role management system (ABAC) 
    • Jena 4
    • Improved build and deployment process
    • Code style improvements
  • End of year
• Summer period meetings 
  • 04.07., 18.07., 01.08., 15.08.

Notes

Dragan: We continue our work on VIVO REST API, it is one of the most active VIVO development part at the moment. There is some progress, some issues were found and already fixed.
Long delay after login has been resolved. My question: have you tried it at the University of Florida?

Michael: We haven’t tried to fix it. It is on our list of things to check.

Dragan: It is merged to the main branch. 

Michel: I am going to check it. When will the next 1.14 release be ready?

Dragan: Hopefully soon, it might be released after this Thursday or in upcoming weeks.

Dragan: Publication claiming has been added to VIVO documentation, it was documented in release notes before that.

Dragan: Last week a vulnerability was found and it is already fixed and merged into the main branch. It relates to javascript code that could be provided as url and then executed in browser.

Dragan: We created release candidate 5 and tested it. There is one result for RC1 that Ivan did and Milos prepared results for RC5. It looks like features work as expected. It is great that we have VIVO tested with Windows and Linux. Hopefully we will release a new VIVO soon.

Also some discussions started about the next minor release. Hopefully Dynamic API will be part of VIVO 1.15.  We also have some pull requests that might also be part of 1.15 release. There is also improvement with attribute based access control, audit module. Also we might update jena to version 4.X. Also William prepared PRs to fix VIVO deployment. Also code style has been defined and included in the process of application building. It is going to be turned off for existing classes by default and part by part exclusions list is going to be reduced.

Besides that I am not sure we have now some implemented features, like “Restore forgotten password”.

Hopefully we will start reviewing pull requests and merging them in September.
Once we discussed that we could adapt only one theme and fix it in accordance to accessibility guidelines. 

Dragan: Next week we will have a regular meeting and then switch to biweekly meetings during the summer.

Draft notes in Google Docs

Task List

Previous Tasks 

• Michel Héon to share presentation slides with VIVO community via slack channel
• Dragan Ivanovic to document publication claiming feature - Editing Your Profile#PositionsandPublications
• Kshitij Sinha will inform Michael Bentz and other UF members about progress in resolving issue related to the long delay in logging in 
• Dragan Ivanovic will communicate further will Ceci and Rodrigo about csv import into the VIVO graph
• Brian Lowe will complete https://github.com/vivo-project/Vitro/pull/397, Dragan Ivanovic and Georgy Litvinov will review
• Brian Lowe will review https://github.com/vivo-project/Vitro/pull/395
• Dragan Ivanovic will prepare RC once when all blocking issues are resolved
• Dragan Ivanovic to discuss with VIVO committers whether we can improve VIVO WCAG  compliance
• Brian Lowe will work on implementation of https://github.com/vivo-project/VIVO/issues/3770
• Dragan Ivanovic will increase priority of https://github.com/vivo-project/VIVO/issues/3858, and https://github.com/vivo-project/VIVO/issues/3859 
• Dragan Ivanovic will continue communication with Joseph about the issue with mass removing data via slack
• Dragan Ivanovic to share results of discussion about using Docker images with Rodrigo via https://groups.google.com/g/vivo-tech/c/yAOHcsJg8ro (the problem might be that VIVO docker container is not seeing vivo-solr container, meaning it is a network mode issue)
• Dragan Ivanovic to reorganize VIVO upgrade wiki pages - Upgrading VIVO
• Maxim Prokopenko to open a ticket (bug) for Solr index directory mount with docker compose (https://github.com/vivo-project/VIVO/issues/3857)
• All to think about priorities for further development of VIVO   
• 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)
• 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