Background

The planning for VIVO 1.5 is happening as we speak, with a number of development components already identified in the VIVO development Jira space, many with specific work tasks assigned for them.

High-order goals for the release include the following, which certainly cannot be completed in their entirety:

• Further integrating mini-grant work from the Stony Brook, ORCID, HUBzero, Duke, and Digital Vita mini-grants into VIVO, whether in VIVO itself or as separate applications, services, or add-on functionality
• Modifying VIVO core code to allow the use of any triple store technology, to take advantage of special features and/or performance of alternatives to Jena’s SDB.
• Designing and implementing the first stages of an extension architecture for VIVO with an emphasis on discrete service bundles, to better support adding functionality to VIVO and providing data from VIVO to other applications in ways accessible to non-Java developers.
• Adding support in VIVO’s editing and display for owl:sameAs assertions to facilitate disambiguation of apparent duplicate data while retaining provenance.
• Improving support for data integrity maintenance in conjunction with data ingest and updating – detecting malformed and orphaned data and removing older data when appropriate
• Providing closer integration of the Harvester with VIVO to shorten the data ingest learning curve and capture provenance and any necessary auditing information.
• Developing an improved data caching system for visualizations
• Integrating national researcher networking display into VIVO and further leveraging network connectivity into individual pages
• Enhancing the VIVO linked data index builder and its associated services

Timing

We expect to finish development on VIVO 1.5 in late May and complete testing for the release of VIVO 1.5 in the latter part of June, 2012.

Contributing materials

• The Weill Cornell team has identified a set of user stories that apply to the 1.5 release and beyond. These are being reviewed by the development team for breakout into distinct tasks and assignment of priorities. Watch the VIVO implementation Jira space for candidate features to be prioritized.
• Development Call 20120105 of how to improve full lifecycle data management in VIVO
• Notes from the January 12, 2012 development call presentation on a Vitro extension architecture
• Development Components for VIVO 1.5