...
Documentation specific to VIVO-ISF lives on this wiki and will continue to evolve as the VIVO-ISF Ontology Working Group, led by Melissa Haendel and Brian Lowe, receives feedback from the rollout. Communities of interested are forming within the working group and will lead implementation of corrections, improvements, and expansion of the VIVO-ISF ontology for future releases. Please join the biweekly ontology working group calls.
To understand the VIVO-ISF changes from previous releases, we call particular attention to the VIVO 1.5 to VIVO-ISF change diagrams. Upgrading VIVO from version 1.5.x to version 1.6 includes an automated data migration process that should convert all existing VIVO content to the new ontology structure, but any local data ingest processes will almost certainly need to be modified to generate data compatible with the new ontology. We recommend backing up the VIVO 1.5 database and performing a provisional upgrade on a test server to confirm that the upgrade will complete smoothly – please see the VIVO 1.6 upgrade documentation for more details.
...
Chris Barnes from the University of Florida is leading a new VIVO Apps & Tools working group showcasing existing tools via demos and discussions on biweekly calls, as well as addressing opportunities and requirements for new tools and applications beneficial to the VIVO community.
...
In other performance-related improvements, responses to linked data requests are more concise, hence faster, and include a link to the VIVO "terms of use" statement provided . The terms of use text should be modified by the implementing institution as a way to clarify any local conditions on usage of the information in the responseVIVO that is included in response as determined by visibility settings for page display in VIVO.
Look and feel
VIVO keeps the same overall look and feel while featuring a new and more dynamic home page including rotating features highlighting individual research areas, researchers, and departments as well as more prominent statistics on key content elements. An optional map view highlighting the global, national, or regional geographic research focus may also be activated and all new home page features may be customized to local preference.
And many more improvements
In addition to the above major features, VIVO 1.6 includes many new development and debugging features offering implementing sites additional control over deployment, access control, and customization of VIVO pages with additional queries and reports. .
Jim Blake has implemented a developer mode that can be configured on startup and modified while running, having several notable features:
- Adding HTML comments to each Freemarker template, so you can see what each template contributes to the page by viewing the source of the page in the browser
Defeat the Freemarker template cache, so each template is read from disk on each request
Turn on logging of custom list view configuration files to note in the log each time a list view other than the default is used
Defeat the cache of language-specific text strings, so the language file is read from disk on each request
Turn on logging of all SPARQL queries to include the elapsed time spent on the query, in seconds, the name of the method on RDFService that received the query, the format of the result stream from the RDFService method, and the text of the query. A stack trace may optionally also be added to the log.
VIVO's internal SPARQL query endpoint may be configured for authorized access and now supports HTTP content negotiation and JSON-LD.For additional detail on these and other improvements, please review the full VIVO 1.6 Release Notes.