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 TDB - total time: 9m 22s
      2. RAW TDB – total time: 43s, 45s, 43s (3 replications)
      3. RAW TDB2 – total time: 31s, 32s, 31s (3 replications).  TDB2.tdbloader warned about 3 IRI with port numbers under 80 in the data.
      4. VIVO SDB - total time: 1h 44m 33s
      5. Fuseki (backed by TDB - local machine) - total time: 1h 31m 36s
      6. Fuseki (backed by TDB - remote machine) - total time: 1h 31m 33s
   4. Read performance tests - Connect with VIVO Scholars?
3. 2020 Sprint Planning- VIVO Sprints
   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

...

1. Symplectic's Harvester... now open source, what next?
   1. Ralph’s email response to Tom and Violeta’s queries on the develop email list

   2. “Yes back at the Symplectic NA Conference I spoke with Jonathan about opening the code and giving it a home. Over the next year they did some code cleanup and documentation and where able to announce at the Digital Science NA Conference in 2019 they were going to post it on GitHub. Now that is just an archive and they are not supporting it.  I have forked it over to my GitHub repo to continue to support it, but I have also forked from there to https://github.com/vivo-community/Vivo_Harvester_V2. I want the VIVO Community to know about this connector from Elements to VIVO so they can use it and even help in it's support.”

   3. Will be adding a new page under Apps and Tools Catalog for the Symplectic Harvester to go over use and support.

Performance testing different VIVO / triple store configuration

1. Running a totally clean VIVO, loading the file listed as sample data in GitHub (OpenVIVO data).  Ingesting the data using VIVO connected to multiple triple store options.  
2. Ingest performance results, loading/inferencing OpenVIVO data. (Ingesting the open vivo ttl file using the ingest option through the system admin interface using Site Admin -> Add or Remove RDF Data.  Ingest tried once for each of the following. Note that, when done through VIVO, inferencing is also occurring. Indexing seems to occur after the fact according to log files. ):
3. From VIVO-1743 above, the following comment describes the process for ingesting the data:

From the results above, it seems like TDB is faster than both SDB and Fuseki.

...