Note
The next version of VIVO, due in fall of 2018 or spring of 2019 is expected to carry a "2.0" version tag, consistent with Semantic Versioning and indicative of changes to the API, including changes to the ontology, defining how data is represented on input to VIVO and output from VIVO.
on-going
Are you interested in contributing effort to one or more of the items below? Please contact Andrew Woods or Mike Conlon. VIVO is able to move forward with items for which there is effort in sprints. See Sprint 2 - Proposed Tasks.
Ideas under consideration
Items without JIRA may be more speculative.
- Interface
- Support for ORNG widgets (230+) out of the box. Based on work of UCSF and U of Wollongong
- Addition of DOI, ORCiD, and PubMed real-time additions based on work of OpenVIVO
- Improved internationalization support
- Visualizations based on work at Cornell
- Generate CiteProc output, use CSL create markup - https://en.wikipedia.org/wiki/CiteProc
- Data Services
- Cross-linking work based on work of EarthCollab and Cornell
- Architecture
- Implementation of Elastic Search or Funnelback or Solr as selectable search engines based on work of U Colorado
- Search engine facet configuration based on work of DCO, Colorado, UNAVCO and Cornell
- Vitro clean-up and improvements based on the work of Cornell
- providing JSON output through API
- Ontology
- Domain definition and processes. See Ontology Improvement Task Force
- Domain modularization and selectable loading of domain modules
- Ontology editing enhancements based on work of Cornell
- Data Management
- See Data Loader Task Force
- Upgrade VIVO Harvester to use Jena 3.1
- System Administration and Development
- Improved build processes for customizations and development
- Other improvements and bug fixes
