Date

02 Nov 2021

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. Brian Lowe 
2. Dragan Ivanovic  
3. Georgy Litvinov 
4. William Welling 
5. Naveen Sadhu
6. Veljko Maksimovic
7. Huda Khan 
8. Ralph O'Flinn 
9. Benjamin Gross 
10. Michel Héon 
11. Florian Kotschka

Agenda

1. Questions/Issues/Pull Requests
   1. Naveen Sadhu opened an issue ticket
      1. https://github.com/vivo-project/VIVO/issues/3602
   2.   The Slack discussion about TPF API
      1. https://vivo-project.slack.com/archives/C8RL9L98A/p1635330190012300 

   3. PRs

      1. Translations of VIVO/Vitro into Russian

         1. https://github.com/vivo-project/Vitro-languages/pull/54

         2. https://github.com/vivo-project/VIVO-languages/pull/104
      2. Creating Locale with specified Language script
         1. https://github.com/vivo-project/Vitro/pull/250

      3. Translations of VIVO/Vitro into Serbian

         1. https://github.com/vivo-project/Vitro-languages/pull/55

         2. https://github.com/vivo-project/VIVO-languages/pull/105
   4. UQAM project
      1. replacement of the Jena-TDB in VIVO with AWS-Neptune
2. Discussion about sprints' topics
   1. https://docs.google.com/document/d/1hJSWAa3ENoFOYyp0GyvDqBdehra3AmFBAD9X2dX3cSo/edit?usp=sharing
   2. Georgy's proposed ontology for dynamic api https://docs.google.com/document/d/1vtNIVEYWdBgV11N-wiPk_UNKpiFQ4sKetJ8elJ6xy2E/edit#

1. 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

Dragan: Short recap from leadership meeting

Naveen’s issue:
Dragan: Is the issue record specific? Have you tried loading any other records?
Brian: It might be an issue with the TDB version, with a lot of concurrent reading and writing. We should investigate whether this is a problem with TDB or VIVO.
Ralph: Saw this issue before when interacting with special/foreign characters.
Neveen: How to pinpoint the problem
Ralph: Try loading data in smaller batches
Dragan: Try to change the character encoding within your environment.
Brian: Set ABox re-computer logging to DEBUG level. If the exception always happens at the same point (same record), then the problem probably lies within that record. Otherwise the problem could be with TDB and concurrency.

Vitro PR for scripts.
Georgy: Some entry files still have en-US tags within vivo-languages PR for Serbian localization.
Dragan: This should be a topic for committers meetings, except for when someone who isn't in the committers group creates a PR.
Georgy talked about his Russian localization, and said he tested and fixed mistakes he found. Also suggested to move all translation “properties” into one file.

Talk about AWS-Neptune (cloud based triple store) and its history.
William: Not in favour of depending on AWS, Ralph agrees.
Brian: RDFInterface should not depend on Jena classes. Also RDFInterface should make it possible to change and swap underlying triple stores that are used to store data.
William: Agrees with using interfaces which are agnostic to implementation, but isn’t sure the vivo source code is agnostic to those implementations. Therefore it wouldn't be so easy to make triple stores interchangeable.
Brian: We should revert newer changes added to the RDF interface that depend on Jena which make this interface ‘dirty’. The RDF interface should not depend on Jena library at all.
Michel: Talked about integrating VIVO with AWS Neptun within the UQAM network. Will integration with neptun slow down/degrade performance of VIVO?
Brian: It should not. No reason why TDB would perform better than Neptune. The connection with Neptun should be native, and not through HTTP SPARQL endpoint. RDF service needs to be implemented for Neptun, maybe also RDFServiceFactory, but not sure.
Michael: Is the procedure of implementing RDF Service documented somewhere?
Brian: No.
Michael: If I write this documentation, where should it be posted?
Ralph & Brian: Inside VIVO Technical documentation. Under ‘Extending and Localizing VIVO’ section.
Brian: In future we should create wiki/documentation for developers, where this should end up eventually.
Ralph & Brian: Maybe it should be better to put it under the ‘Reference’ section, and rebrand that section as ‘Developer Reference’ or ‘Development’.
Michel: What is a general rule for documentation? What is the procedure for adding new wiki pages?
Ralph: Up till now we just talked about it in the meetings, and whoever wanted to create a new wiki page, did it.
Michel: We should have a new documentation section for developers.
Dragan: I agree with the ‘rebranding’ of ‘Reference’ section into ‘Development’ section. However, I will think a little bit about reorganization of VIVO Technical documentation sections. 

Dragan: Georgys presentation will be postponed for the next meeting.

Draft notes on Google Drive

Task List

•  Dragan Ivanovic to think about reorganizing/rebranding sections of VIVO Technical documentation (wiki)