Date

25 Apr 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. Brian Lowe 
3. Miloš Popović
4. Georgy Litvinov 
5. Doug Chestnut
   
6. Samantha Emerson
7. B. Henderson
8. Rishabh Tatiraju
9. Michael Bentz
10. Kshitij Sinha
11. William Welling 
12. Mark Vanin 
13. Yuji Shinozaki
14. Christopher P. Barnes 

Agenda

• Questions/Issues/Pull requests/Announcements
  • SWIB - VIVO meeting
    • https://swib.org/#call-for-satellite-events
  • SciDataCon
    • workshop about mappings
      • CERIF2VIVO mapping ???
  • WCAG  compliance
    • Deque performed analysis of VIVO compliance with WCAG in 2021
      • https://axeauditor.dequecloud.com/test-run/0fd39ab8-b17b-11eb-ae6c-c772582b8543
  • VIVO conferences/events
    • how well it is supported?
  • Customization of ontologies
    • appear in the list of ontologies, but no classes 
      • https://vivo-project.slack.com/archives/C8RL9L98A/p1682065844193869
  • New pull requests
    • Change PropertyKey class name and namespace (VIVO 1.14.0 - Brian)
      • https://github.com/vivo-project/VIVO/pull/3863
      • https://github.com/vivo-project/Vitro/pull/386
    • Prevents creation of button to add new object property if neither of 'select from existing' nor 'provide selection' options are set in object property configuration (VIVO 1.14.0 - Georgy)
      • https://github.com/vivo-project/Vitro/pull/385
    • Propagate selectFromExisting and offerCreateNew settings from base object property to new faux property (VIVO 1.14.0 - Brian)
      • https://github.com/vivo-project/Vitro/pull/384
    • Handle preferred language when creating new class and property groups (VIVO 1.14.0 - Brian)
      • https://github.com/vivo-project/Vitro/pull/383
    • slight modification of PR for fixing a bug with empty VIVO_HOME (VIVO 1.14.0 - Dragan)
      • https://github.com/vivo-project/VIVO/pull/3861
    • a commit for "Create vivo/home on application start-up" PR (VIVO 1.15.0 - William)
      • https://github.com/vivo-project/Vitro/pull/370
    • Extended search (VIVO 1.15.0 - Georgy)
      • https://github.com/vivo-project/VIVO/pull/3860
      • https://github.com/vivo-project/Vitro/pull/382
    • Parameter substitutions (Dynamic API - Georgy)
      • https://github.com/vivo-project/Vitro/pull/381
• Priorities 
  
  • What would you like to have in some future version of VIVO?
    • GDPR alignment
      • SPARQL API endpoint
      • GUI
    • Interoperability
      • OAI-PMH endpoint
      • data ingestion
      • Cross-site linking and searching
      • JSON-like REST endpoint
    • VIVO as a service
      • hosting 
      • decoupling data store
      • vivo_home
      • solr
      • multitenancy
        • https://en.wikipedia.org/wiki/Multitenancy
    • Consolidation of data
      • Deduplication
      • Splitting two person profiles
      • Enrichment of data
        • OpenAIRE broker - https://graph.openaire.eu/develop/broker.html
        • Altmetrics
    • Reporting
    • Project centered VIVO
  • Which improvements are needed?
    • Installation
    • Documentation
    • Customization

Notes

SciDataCon workshop about mapping, interesting event to consider. Not sure when the deadline is for submitting an abstract.

Talking about transition to new theme. WCAG Compliance review (that has been done couple years ago) - lot of issues are related to css (Color Contrast) that does not require changing a lot of frontend layout. Waiting too much to fix those compliance issues could cause loss of clients.

Some of those pull requests are linked with VIVO 1.14, some of them are investigation of releases for vivo 1.15, one of them is linked to dynamic api.

Extended search will be part of 1.15 update

Priorities for future:

Vivo as a service. We should discuss about hosting, decoupling data store, solr… 

Do we see need for this first of all?

Brain: It would be great to have this, this is usually a lot of pain because of unexpected performance issues. Standard service would be a nice thing. Having a standard hosting service to offer

William: We should be concerned should we use Solr or Elastic search.

There is an elastic search implementation for vivo that probably should work.

Lyrasis is going in that path, it is possible to get requirement in one or two year for VIVO as a service.

Vivo-Solr is using an old scheme.

Some solr vulnerability was in solr 8 which we are using in a lot of legacy components.

It would be good to update to solr 9

Next week we will speak about Consolidation of data.

Draft notes in Google Docs

Task List

• Dragan Ivanovic to discuss with VIVO committers whether we can improve VIVO WCAG  compliance

Previous Tasks 

• 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