Page History

...

1. Announcements
   1. VIVO Triple Store Roadmap Proposal - communication with community regarding moving forward with the plan

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

   2. Symplectic's Harvester... now open source, what next?
2. Performance testing different VIVO / triple store configuration
   1.  

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

   2. Fuseki as alternate triple store
   3. Ingest performance results, loading/inferencing OpenVIVO data :(4.4M triples)
      1. VIVO
      2. TDB - total time: 9m 22s
      3. RAW TDB – total time: 43s, 45s, 43s (3 replications)
      4. RAW TDB2 – total time: 31s, 32s, 31s (3 replications).  TDB2.tdbloader warned about 3 IRI with port numbers under 80 in the data.
      5. VIVO SDB - total time: 1h 44m 33s
      6. Fuseki (backed by TDB - local machine) - total time: 1h 31m 36s
      7. Fuseki (backed by TDB - remote machine) - total time: 1h 31m 33s
   4. Read performance tests - Connect with VIVO Scholars?
3. 2020 Sprint Planning
   1. VIVO-i18n - Canadian French Initiative
   2. Doodle closing on Friday, Feb 28
4. Pruning legacy Vitro/VIVO GitHub branches

   
   

   No Format

   In an effort to reduce the number of abandoned or out-dated branches in the VIVO and Vitro GitHub repositories, we will be taking a multi-phased approach at pruning branches: - All branches that predate the VIVO 1.6 release will be removed (i.e. all branches from 2013 and before) - Of the remaining branches, those with no commits ahead of the 'master' branch will be removed - Of the remaining branches, detailed review of branch content will determine whether the branch should be removed/retained - Release maintenance branches will be retained If you have an interest in ensuring that any of the branches in Vitro or VIVO are retained, please let that be known.

   
   

5. 1.11.1 maintenance release - security patch
6. Vitro pull-requests

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

       - looks good

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

...