Date

24 Jan 2023

Call-in Information

Time: 10:00 am, Eastern Time (New York, GMT-04:00)

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. Michel Héon 
4. William Welling 

Regrets

1. Georgy Litvinov  
2. Benjamin Kampe 

Agenda

• Questions/Issues/Pull requests/Announcements
  • The issue with calendars
    • No response yet
  • The support link
    • No response yet
  • PIDSKG workshop
    • the last year event - https://cost-dkg.eu/pidskg
    • this year it should be in Italy on February 13th-15th 
    • The draft abstract - https://docs.google.com/document/d/1iGl-06AGRiWMADmY6QzX9Qv3XsrQwuc3Yta8BfU9_s8/edit?usp=sharing
    • Privacy issues in graphs
      • hide from display
      • dynamic api and privileges for fetching 
      • editor (at institutional level)
  • Annual report
    • Sites: percentage increase: 30% more active sites (55 in 2019,  76 now)
• PRs
  
  • https://github.com/vivo-project/VIVO/pull/3808
  • https://github.com/vivo-project/Vitro/pull/360
  • https://github.com/vivo-project/Vitro/pull/361
  • Others
• The VIVO 1.14.0 release
  • review and merging of PRs 
    • previously listed + https://github.com/vivo-project/VIVO/pull/3805
  • Release notes
    • Release Notes
  • Documentation
    • Internationalization
      • updated, please review
    • Other documentation update is needed
      • VIVO 1.14.x Documentation
  • Release testing
    • update wiki page - Release Testing - 1.14.0
    • copy and adopt google forms
• The next sprint

• • When
    • 20.02.23 - 10.03.2023
  • The topic
    • Jena upgrade
      • clean up or get rid of SDB code
      • fix live backup of TDB
    • External triple store performance improvement
    • integration of vivo-solr into main codebase
      • is that vitro-solr or vivo-solr?
    • VIVO-Installer review depending on the target user: developer, infra architect, corporate/institutionnal evaluator, etc.
    • Implement a new owl-reasoner (maybe https://github.com/stardog-union/pellet)
    • Reformat codeSource replace tabs by spaces.

Notes

Questions/announcements

1. Calendar issue: vivosurvey@gmail.com automatically sent calendar invites at beginning of year that are no longer accurate.  No response on this yet.
2. Vivoweb.org support link should be fixed later today.
3. Dragan will present at PIDSKG about privacy
1. Brian: VIVO currently has display/edit/linked data publishing role-level annotation properties that can be set on each property in the domain ontology.  This is not dependent on the current UI technology and can (should) be respected on any API access to the data.
2. SPARQL queries have access to all the data regardless of role level.  William wonders if there are triple stores that might offer privacy controls built in.  Brian mentions that we could at least parse SPARQL queries and reject those that include prohibited predicates.
3. GDPR questions.  William: Can a user request that they not be listed as a coauthor on someone else’s profile?
4. Brian: ORCID presumably has to deal with the same issue and has a knowledge base article about GDPR. https://support.orcid.org/hc/en-us/articles/360006895834 Might be instructive.
4. Michele updated VIVO registry; 76 current active VIVO databases in the registry.

Next release

1. Dragan: Current sample data is not so useful for testing i18n.  The Map of Science can’t be tested because the journal names are not real journal names.  
1. For i18n, Michel can put up sample datasets for people to use.
2. William: Cucumber(?) testing framework might be useful; designed for testing microservice architectures.
2. Dragan updated wiki and testing procedures; need to migrate to Google Forms.  Expect to make release candidate soon.  Need to improve channels of communications with end users to solicit ideas/feedback.

Next sprint

1. Suggestion is to start on 20 February.
2. Have freedom to use some of our sprints for internal needs / technical debt.
3. Ideas
1. Jena upgrade (Jena 4, Java 11)
2. TDB backup utility
3. Improve SPARQL triple store connection performance
4. Move Vitro/VIVO languages into core

Installer

1. Michel: Why not have multiple installers separate from the main repository?  Different users will prefer different installers.  UQAM has a separate installer repository, but synchronization can be a problem.

Draft notes in Google Docs

Task List

Previous Tasks 

• 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