The VIVO DuraSpace Project is pleased to announce the release of VIVO 1.7 with several significant updates and improvements. . VIVO 1.7 introduces new features as well as improvements to existing features and services. In contrast to VIVO 1.6, however, VIVO 1.7 does not include changes to the VIVO-Integrated Semantic Framework (VIVO-ISF) ontology that required data migration or changes to local data ingest procedures or to visualization or analysis tools drawing directly on VIVO data.
VIVO 1.7 notably includes the results of the an ORCID Adoption and integration grant and supports Integration Grant (http://goo.gl/fLIuVb) to support the creation and verification of ORCID iDs from inside VIVO.. VIVO now offers the opportunity for a researcher to add and/or confirm his or her global, unique researcher identifier directly with ORCID (http://orcid.org) without the necessity of applying through other channels and re-typing the 16-digit identifier. We anticipate that this facility will help promote ORCID iDs more widely and expand adoption for the benefit the entire research community.
VIVO 1.7 also incorporates several updates to key software libraries core to in VIVO, including updating the Apache Jena Project libraries that support provision the default VIVO triple store .With VIVO 1.7 the from Jena 2.6.4 to Jena 2.10.1. The Apache Solr library used by VIVO has been updated to Solr 4.7.2 and the programming interface to Solr has been modularized to allow substitution of an alternative search engine such as ElasticSearch or FunnelBack.indexing libraries based on specific desired features.
The SPARQL web services introduced in VIVO 1.6 have been extended to support full read-write capability and content negotiation through a single interface. The The ability to export or "dump" the entire VIVO knowledgebase for analysis by external tools has also been improved to scale better with triple store size, and there have been improvements to the ability for an external application to request lists of RDF by type in VIVO to facilitate linked data applications.
The VIVO 1.7 release also reflects input from VIVO Project sponsors requesting a regular release schedule, currently anticipated to follow a 6-month pattern one minor release and one more major release each year. We hope this pattern will make it easier for adopters to anticipate new features and plan for changes that sometimes affect other data ingest processes, tools, visualizations, and/or analysis beyond VIVO itself.