...
- Announcements
- VIVO Triple Store Roadmap Proposal - communication with community regarding moving forward with the plan
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1741
- Symplectic's Harvester... now open source, what next?
- VIVO Triple Store Roadmap Proposal - communication with community regarding moving forward with the plan
- Performance testing different VIVO / triple store configuration
-
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1743 - Fuseki as alternate triple store
- Ingest performance results, loading/inferencing OpenVIVO data:
- TDB - total time: 9m 22s
- SDB - total time: 1h 44m 33s
- Fuseki (backed by TDB - local machine) - total time: 1h 31m 36s
- Fuseki (backed by TDB - remote machine) - total time: 1h 31m 33s
- Read performance tests - Connect with VIVO Scholars?
-
- 2020 Sprint Planning
- 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.
- 1.11.1 maintenance release - security patch
- Vitro pull-requests
- looks goodJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1658
...