VIVO 1.15.0 does not contain VIVO core ontology changes (comparing to VIVO 1.14.0) or require a data migration or modifications to the Solr setup. However, please note that upgrading to VIVO 1.15.0 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.15.0 from a version of VIVO prior to 1.10 requires installation of Solr as a free-standing application. The VIVO 1.15.0 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.
Extended search ontology has been introduced. This ontology enables configuration of searching. Filters for refining search results can be defined. Search results can be sorted by different criteria, i.e. by relevance or by some field such as date or name. At the end, type of objects (classes) and instances which can be searchable for different roles can be defined. The feature is documented at Using Search.
This feature enhances the flexibility of access control by using attributes to define and evaluate access policies, replacing Java-based policies with configurable N3 files. A new access control ontology has been introduced. This approach enables more control over definition of permissions for roles in VIVO. Technical key updates include modifications to policy datasets, authorization requests, and startup listeners. This release ensures migration from both current VIVO instances and the Advanced Role Management system. For more details, refer to the Authorization.
The public option for resetting password which a user can carry out individually without administrator has been implemented. The option is based on sending an email with a secured link for resetting the user password. The feature is documented at Editing Your Account.
A module enabling tracking of changes being made in the triple store has been implemented. Changes made by users and non-person entities are recorded in a triple store, with the users ID (URI), the time, and the changes that have been made. More info about this feature can be found at The VIVO audit module.
Researcher and organization individual pages can be private, i.e. visible only for users with certain permissions (not for anonymous users, i.e. visitors). The feature is documented at Private individual pages.