...

1. Brian Lowe
2. Dragan Ivanovic  
3. Benjamin Kampe  
4. Georgy Litvinov 
5. Dominik Feldschnieders 
6. Ralph O'Flinn Benjamin Gross 
7. William Welling 
8. Michel Héon 
9. Veljko Maksimovic
10. Huda Khan 
11. Sandra Mierz 
12. Naveen SadhuBruce Herbert

Agenda

1. Announcements
   1. A new version of the VIVO-PROXY prototype has been published - https://github.com/vivo-community/VIVO-PROXY/tree/rel-2021-10-13
2. The new issues/questions
   1. https://vivo-project.slack.com/archives/C8SDQQYJ2/p1634320019009500
      1. https://vivo-project.slack.com/archives/C8SDQQYJ2/p1634326647014200 
3. Discussion about organizing sprints and publishing time-based minor releases
   1. https://docs.google.com/document/d/1hJSWAa3ENoFOYyp0GyvDqBdehra3AmFBAD9X2dX3cSo/edit?usp=sharing
4. Discussion about priorities for further development of VIVO - https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
   1. The topic will be i18n
      1. Move i18n properties from resource bundles to ontology / (editable) RDF
      2. Find solution for syntax differences between languages that does not require template customization per language 
   2. Data ingest

Notes

1. Announcements
   1. New version of VIVO-PROXY has been published.
   2. 1. Michel: Code is in VIVO-community in GitHub; if someone is interested in working together with me on this, that would be great. https://github.com/vivo-community/VIVO-PROXY/tree/rel-2021-10-13
      2. Now includes Bash script that loads sample data into VIVO using VIVO-PROXY.
      3. This release includes changes for populating data in multiple languages and use of a new SPARQL function for assigning IRIs to new individuals.
      4. Is there interest in the community?
      5. 1. 1. Ralph and William: Yes, there is interest.  Encourage continuing to publish to VIVO-community.  Important way for it to get seen and for people to have the opportunity to use it.
      6. William: What are your aspirations for VIVO-PROXY?
      7. 1. 1. Michel:  want non-Semantic Web specialists to be able to script data ingest into VIVO.  Many institutions need to do the same things all the time; this is a way to generalize this without using Semantic Web technology.
            1. Michel: In this release PROXY does more SPARQL updates instead of form submissions.  IRI-creation SPARQL extension helps make this possible.
         1. Now includes Bash script that loads sample data into VIVO using VIVO-PROXY.
         2. This release includes changes for populating data in multiple languages and use of a new SPARQL function for assigning IRIs to new individuals.
         3. Is there interest in the community?
         4. William: What are your aspirations for VIVO-PROXY?
         5. William: Do you see this being packaged with VIVO?  Has potential for VIVO-in-a-Box, but VIAB is proposed to have modular design with looser coupling.  PROXY has coupling to the UI
      .Michel: In this release PROXY does more SPARQL updates instead of form submissions.  IRI-creation SPARQL extension helps make this possible
      8. 1. .
         2. Sandra: if you use the sparql api, then vivo-proxy becomes the same as generate2vivo, in fact I made a branch vivo-proxy-demo where you can already see the same functionality based on the SPARQL API
      1. New version of VIVO-PROXY has been published.
      9. New issues/questions
      Problem of widget-login.ftl placed in theme folder not overriding the default.
      10. 1. Expected behavior is that any .ftl in the theme folder should override the default, wherever it may be.  Should double-check that it’s not a problem of caching (e.g. use Developer Tools panel to disable the cache and always load current version of each template).  Otherwise, might be an obscure bug in the template loader that would have to be investigated.
      1. Problem of widget-login.ftl placed in theme folder not overriding the default.
      11. Organizing sprints / minor releases
      https://docs.google.com/document/d/1hJSWAa3ENoFOYyp0GyvDqBdehra3AmFBAD9X2dX3cSo/edit?usp=sharing 
      12. 1. Please add comments to this document and we will continue discussing it next
      week.
      13. Ralph suggests releases in early April and early October 2022.
      Three four-
      14. 1. week
      sprints per year, topic based (plus minor bugfixes)
      15. 1. .
          1. Should plan topics in coming weeks.
          2. William: VIVO-in-a-Box is one of the most desired items.
          3. Discussion of federated / cross-site VIVO search scope.
             1. Michel: depends on client making request.
             2. William: seems not as feature-rich as Solr’s built-in support for relevance and boosting.  SPARQL might give comprehensive list, but ordering of that list might not be useful.
          1. Michel: needs to include semantic search using SPARQL endpoint (e.g. with Jena/Solr extension).  Federated Solr search is difficult.
          2. William: Easier now.  Solr Cloud on Solr 8+ can query across instances that have the same schema.
          3. William: semantic federated search is research-oriented, while free-text federated search is readily applied by general users.
          4. William: using SPARQL, does schema need to be the same?  How is relevance score computed across instances?
      16. Michel: depends on client making request.
      William: seems not as feature-rich as Solr’s built-in support for relevance and boosting.  SPARQL might give comprehensive list, but ordering of that list might not be useful.
      17. 1. Proposed sprints in February, May, August (lighter/documentation-oriented), November
          1. Ralph: Are sprints tied to releases?  If so, should be scheduled with sufficient testing periods in between.  
          2. William: releases should always happen on a schedule, regardless of whether specific sprint-related items are ready.
      1. https://docs.google.com/document/d/1hJSWAa3ENoFOYyp0GyvDqBdehra3AmFBAD9X2dX3cSo/edit?usp=sharing 
      2. Ralph suggests releases in early April and early October 2022.
      3. Three four-week sprints per year, topic based (plus minor bugfixes).
      18. Committers call should be organized this Thursday.

      Draft notes on Google Drive

      Task List

      •   Dragan Ivanovic to summarize discussion and update the google sheet describing priorities - https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
      •  All to review and provide comments on roadmap for publishing minor releases and organizing sprints https://docs.google.com/document/d/1hJSWAa3ENoFOYyp0GyvDqBdehra3AmFBAD9X2dX3cSo/edit?usp=sharing
      •  Dragan Ivanovic to summarize discussion and update the google doc describing roadmap for publishing minor releases and organizing sprints - https://docs.google.com/document/d/1hJSWAa3ENoFOYyp0GyvDqBdehra3AmFBAD9X2dX3cSo/edit?usp=sharing

      ...