...

1. Reviewing / merging
   1. authorization update for self editors - updates?
      1. Back-porting to 1.11.1?
2. Branch pruning policy announcement
3. Sprint planning: i18n
4. Triple store recommendation - moving forward
   1. Volunteer for the one-character change? 

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

   2. Decoupled triplestore:

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

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

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

      4. Running performance tests
      5. Exploring native connections (Jena, RDF4j)
5. Architectural diagrams - discuss at a future date
   1. VIVO Components
   2. VIVO Ecosystem

Notes

Actions

•  Type your task here, using "@" to assign to a user and "//" to select a due date

1.11.1 release

1. Once https://github.com/vivo-project/Vitro/pull/106 has been merged, we should cherry-pick the commit into the 1.11-maint branch and release 1.11.1

Branching Policy

1. Is there significance to the feature branches? - not really
2. The VIVO 1.6 release was significant
3. Would it make sense to propose removing non-maint branches before the 1.6 release?
   1. Dec 14, 2013
4. That would mean pruning below row 34 of the "Vitro" tab in the branches spreadsheet
5. We can then take an incremental approach to branch removal from 2014 to the present
6. ACTION: Andrew to send out proposal to vivo-tech with the above suggestion

i18n

1. Consolidate languages?
   • Agreement that consolidation is helpful
2. Can we standardize updates to labels with i18n properties?
3. Focus
   • language aware editing
   • Not: label ordering

Triplestores

1. Defining relevant tests
   1.  Reads
      1. Pages: large number of associated triples (Australia)
      2. SPARQL Query API
   2. Writes
      1. SPARQL Update API
   3. Reindex
   4. Inference
2. Mike has test data generator?
   1. https://github.com/mconlon17/vivo-sample-data-generator ?
   2. https://github.com/mconlon17/vivo-sparql-benchmarking - may also be helpful?
3. Let's finish documenting tests/procedures for "Triple store performance test procedures" by end of next week!
   1.  

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

Actions

•  Andrew to send out branch-pruning proposal to vivo-tech

Previous Actions

•  Huda Khan to review: 

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

•  Brian Lowe to review: 

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

•   Ralph O'Flinn to review: 

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