...
Note: The second VIVO 1.6 release candidate is currently undergoing testing, with testing of a third release candidate expected by November 15. No date has been set for the VIVO v1.6 release pending completion of all tests of the application and data migration from version 1.5.2.
...
The recently completed CTSAconnect project (http://ctsaconnect.org) has refactored, extended, and restructured the VIVO (http://vivoweb.org) and eagle-i (https://www.eagle-i.net) ontologies into a unified an integrated semantic framework. By combining information about researchers, research resources, and clinical expertise in a single, modular structure, VIVO-ISF provides a more flexible and extensible ontology for both the VIVO and eagle-i applications and for innovative downstream applications consuming this growing pool of richly-structured semantic data, including Plumage (https://github.com/CTSIatUCSF/plumage) and CTSAsearch (http://research.icts.uiowa.edu/polyglot/). While end users of VIVO will see more continuity than change, the VIVO-ISF ontology aligns more consistently with the Basic Formal Ontology (http://www.ifomis.org/bfo) and better positions VIVO for interoperability with other international ontologies. The modular structure of VIVO-ISF also affords gives adopting sites more flexibility in determining scope and domain focus.
...
VIVO 1.6 does not yet offer full support for editing of all content in multiple languages – only the primary labels for entities. VIVO's RDF add and remove import functions will allow full replication of content in multiple languages, however, for situations where multiple language support is essential.
...
For the first time, VIVO 1.6 exposes data additionadd, update, and delete actions through an authenticated web service, allowing . This allows more seamless interfacing to data ingest tools and opening up allows new options for external applications to read and write as well as read VIVO data. We anticipate that web services will increase the already rapid pace of development of tools working alongside VIVO to provide extended visualization, editing, reporting, analysis, disambiguation, or repository services. Chris Barnes from the University of Florida is leading a new VIVO Apps & Tools working group highlighting existing tools and featuring biweekly calls to address new functionality.
...
Two VIVO adopters have contributed code to support faster page rendering for VIVO when a user is not logged in to edit, allowing VIVO profiles to scale as necessary with much less effect on responsiveness. VIVO pages now carry standard HTTP caching headers that web servers and/or more specialized caching libraries can exploit to deliver content that has not changed nearly instantaneouslyunchanged content in an instant.
VIVO's search indexing has also been extended to support re-indexing a specific subset of data known to have changed, allowing more efficient processing of incremental updates to publications or other content. Responses to linked data requests are faster and more concise, and include a link to the "terms of use" statement modifiable provided by the implementing institution.
...
In addition to the above major features, VIVO 1.6 includes many updated libraries, including an upgrade to the Apache Solr search engine, and offers implementing sites additional control over building, deployment, access control, and supplementing VIVO pages with additional queries and reports. VIVO's internal SPARQL query endpoint may be configured for authorized access and now supports HTTP content negotiation and JSON-LD.
...