Old Release

This documentation relates to an old version of VIVO, version 1.14.x.
Looking for another version? See all documentation.

Overview

VIVO 1.14.x does not contain VIVO core ontology changes (comparing to VIVO 1.13.0) or require a data migration or modifications to the Solr setup.  However, please note that upgrading to VIVO 1.14.x from a version of VIVO prior to 1.10 requires a triple store unload, use of provided utilities to upgrade, and a reload.  See Upgrading VIVO from 1.9 to 1.10.  Moreover, upgrading to VIVO 1.14.x from a version of VIVO prior to 1.10 requires installation of Solr as a free-standing application. The VIVO 1.14.x supports two ways of defining user interface labels, via property files (as it was supported in previous versions), and via triplets in the graph in accordance with UI labels vocabulary introduced in VIVO 1.14.0. 

What's New

Simplified process for installation and customization

The VIVO-languages and Vitro-languages projects are not needed anymore for the installation of VIVO (or Vitro). Customization of UI labels can be specified in local custom ttl files by using private-use language subtags (such as de_DE_x_tib, or fr_CA_x_uqam). Those changes can be made in separated directory in VIVO_HOME, which won't be affected (deleted, overwritten) by any further upgrade of VIVO to newer version. 

Eliminating language specific FTL files

Phrases sensitive on gender and plural-related transformation of words, and other variations related to other morphological changes in different languages have been replaced with more generic changes insensitive on those linguistic transformations. This eliminates need for some language-specific FTL files, especially in the case of loading data from the graph, and improve user-experience.  

Simplified process of supporting new languages

Up to VIVO 1.13.0, adding of a new user interface language required changes in VIVO-languages and Vitro-languages projects in different directories for web application property files and for data which should be preserved in graph. Moreover, it required changes of couple Maven specific files (pom.xml), meaning it required a technical person included in the process of adding new language. Starting from the VIVO 1.14.0, adding of new language can be performed by a translator requiring only a basic knowledge of the ontology notation. 

Improvement of performance for startup of VIVO

The operations of loading and removing sample data, adding and removing model, clearing statements have been improved more than 5 times comparing to VIVO 1.13.0 and prior versions.  

Faux data properties

Besides support faux object properties, VIVO from 1.14.0 also supports faux data properties. 

Resolved Issues

The list of changes can be found at VIVO 1.14.0 release and Vitro 1.14.0 release

Release managers

Acknowledgements

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.