Date

23 May 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. Miloš Popović
3. Georgy Litvinov  
4. Doug Chestnut
5. Kshitij Sinha
6. Yuji Shinozaki
7. Michel Héon 
8. Brian Lowe 
9. Mark Vanin 
10. Benjamin Kampe 
11. B Henderson

Agenda

• Questions/Issues/Pull requests/Announcements
  • A PR for VIVO REST API (Dynamic  API)
    • Plain parameter for SPARQL query
    • https://github.com/vivo-project/Vitro/pull/391
    • Do we have some scenario for plain parameters for N3 Template or SOLR query?
  • UF performance issue with login
    • Michael Bentz:

      • Hi everyone, I mentioned on the call last week that we are having login and logout performance issues for VIVO 1.13. It takes between 8-10 seconds to login with a VIVO account. I have tested installing VIVO both in a container and on the host. In both cases the VIVO application hangs when a login or logout request is made. The steps to reproduce are:

        • Install using https://wiki.lyrasis.org/display/VIVODOC113x/Installing+VIVO
        • Wait for VIVO application to finish initial startup
        • Load VIVO with data (11GB tdbContentModels, 2.4GB tdbModels).
        • Restart Tomcat
    • https://github.com/vivo-project/Vitro/commit/67c0421bea4ba6578037644d459be6a4318fd4ca 
      • not a solution
  • ORCID global participation fund
    • https://info.orcid.org/global-participation-program/global-participation-fund/
    • https://github.com/vivo-project/VIVO/issues?q=is%3Aissue+is%3Aopen+ORCID
• VIVO 1.14.0 RC 3
  • blocking issue
    • https://github.com/vivo-project/VIVO/issues/3870
    • https://github.com/vivo-project/VIVO/issues/3871 
• Projects
  • Dynamic API - https://github.com/orgs/vivo-project/projects/2/views/1
    • VIVO REST API - https://github.com/orgs/vivo-project/projects/2/views/8
      • June 2023
  • Semantic web features - https://github.com/orgs/vivo-project/projects/5
    • Jena 4
    • external graphs (triple store)
    • sample data 
  • Installation and environment improvements - https://github.com/orgs/vivo-project/projects/6
    • Building improvements
    • Code style
    • CI improvements
  • i18n - https://github.com/orgs/vivo-project/projects/4
    • Multilingual data

Notes

• Questions/Issues/Pull requests/Announcements
• A PR for VIVO REST API (Dynamic  API)

Plan for plain parameters for N3 Templates or SOLR query: No ideas brought

UF performance issue with login

Discution will continue in slack regarding logging, Dragan assumption is that maybe log level is higher than actual logs.

• ORCID global participation fund

The GPF is designed to develop ORCID Communities of Practice in low- and lower-middle-income economies

Applicatn should be from low incoming countries or product should have impact in low incomming country, since that VIVO is open source it could has impact

Dragan: I believe that there is more implementation in vivo than in open vivo

Side question from Uruguay Is it possible to integrate google scholar into vivo, Dragan responded that there is no api to google scholar so it would be possible

VIVO 1.14.0 RC3

Issue#3871

Brain explained that the release issue seems to be deeper. It's gonna take a little more of a deep dive into it.

Brain: I hope I’ll find someting soon it should stay much longer as this.

Dynamic API

Talked about statistic, and possible hige results and needs for pagination in responses 

Mentioned opened tickets about upgrading Jena 4, external graph ussages, improving sample data (rdf for testing vivo)

Some contributions about code style, improvements about integration

Just mentioned issues about Multilingual data

Dragan: If anyone is interested in some of topic, should contact back so we can synchronize work.

Draft notes in Google Docs

Task List

Previous Tasks 

• 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
• William Welling will improve docker images (https://github.com/vivo-project/VIVO/issues/3857)
• 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)
• William Welling to upgrade docker instructions in VIVO GitHub
• 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