...

1. Dragan Ivanovic 
2. Brian Lowe 
3. Miloš Popović
4. Georgy Litvinov 
5. Doug ChestnutMaxim Prokopenko
   
6. Samantha Emerson
7. B. Henderson
8. Rishabh Tatiraju
9. Michael Bentz
10. Stanley Welling
11. Michel Héon
12. Kshitij Sinha
13. William Welling 
14. Mark Vanin 
15. Yuji Shinozaki
16. 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

Previous Tasks 

•  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 

...