...

1. Benjamin Gross 
2. Andrew Woods
3. Brian Lowe 
4. Ralph O'Flinn 
5. Don Elsborg
6. Mike Conlon
7. Huda Khan
8. Steven McCauley
9. Michel Héon
10. Alexander (Sacha) Jerabek 
11.  Nicolas Dickner
12. Rachid Belkouch

Agenda

1. Announcements
   1. VIVO Triple Store Roadmap Proposal
      1. VIVO-1741 - Change default content triplestore to TDB RECEIVED
      2. Retaining a VIVO/Jena/Triplestore Java API bridge
         1. RDFService interface
            1. What performance tests would help illustrate differences between implementations?
   2. VIVO Scholar town hall meeting notes - Friday, Feb 21st @10am ET
2. 2020 Sprint Planning- VIVO Sprints
   1. VIVO-i18n - Canadian French Initiative
3. Symplectic's Harvester... now open source, what next?
4. Pruning legacy Vitro/VIVO GitHub branches
5. Vitro pull-requests
   1. authorization update for self editors - no JIRA

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1658

       - looks good
6. Vitro (asynchronous, JMS-style) messaging
   1. RDF Delta patch messaging - 

      Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1718

...

Draft notes in Google-Doc

1. Announcements
1. VIVO Triple Store Roadmap Proposal
   1. Mostly positive response - Moving forward - Will set a date for moving the proposal forward
   2. Look at performance issues - native vs SPARQL with http(s)
   3. Each triple store would have their special needs
   4. Most triple stores support one of the following APIs: rdf4j or Jena
      1. Much like a JDBC connection
   5. Categories of performance tests:
      1. Query - large construct
      2. Query - n+1 problem, iterate list of people for 'label'
      3. Ingest - insert/update/delete all at once
      4. Ingest - update to individual triples, multiple times
   6. Relevant references from develop slack channel for performance:
      1. https://link.springer.com/content/pdf/10.1007%2F978-3-642-13489-0_21.pdf
      2. https://medium.com/wallscope/comparison-of-linked-data-triplestores-developing-the-methodology-e87771cb3011
      3. https://www.w3.org/wiki/LargeTripleStores
2. VIVO Scholar town hall meeting notes - Friday, Feb 21st @10am ET
   1. Come one, come all!
2. 2020 Sprint Planning
   1. VIVO-i18n - Canadian French Initiative
      1. A hosted, reference implementation of the i18n VIVO will be online by the time of the sprint 
      2. Elements of the i18n sprint
         1. Need to build unit tests/integration tests
            1. Need to test Editing, JSP files for bugs
         2. SPARQL commands need to be updated to support i18n languages
            1. Standardize location of sparql
         3. Issue with labels: Labels do not always match between languages (e.g. word order)
         4. Extracting text from: FTL and JSP files
      3. What does success look like here?
         1. Language plugins (like Eclipse)
            1. No Java file updates should be required for any given "language plugin"
            2. Language-specific files: FTL, .properties, ontology
      4. Michel will be migrating initial code from bitbucket to github
      5. Dates for sprint... to be organized with participants (and broader community of interest soon!)

Actions