Overview

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. 

What's New

Search Facets

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.

The improved role management

The role management module is based on Attribute based access control from VIVO 1.15.0. For this purpose, an ontology has been introduced. This approach enables more control over definition of permissions for certain roles. More details about advance role management can be found at Authorization. 

I forgot my VIVO password

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 Profile.  

Audit tool

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. 

Private individual page

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.

Resolved Issues

Bug

  • [3902] - CodeQL GitHub action is broken
  • [3913] - log4j security vulnerability
  • [3922] - Capability map in the nemo theme
  • [3915] - Mac M1 chip
  • [3923] - Incorrect reuse of value sets
  • [3938] - Problem with A-Z sort in search results
  • [3905] - Links in README files do not work
  • [3958] - Date time interval doesn't allow end date to be equal start date
  • [3959] - Claimed publication date precision saved as string literal
  • [3970] - Sparql query data getter invalid substitution errors appear in log files
  • [3973] - Google image charts API not working anymore
  • [3977] - Remove string literals from configuration graphs results in error

New Feature

  • [3860] - Extended search
  • [3906] - Setting VIVO locale by using the individual page URL parameter
  • [3027] - Advanced role management
  • [3770] - I forgot my vivo password
  • [3832] - Audit tool
  • [3929] - Private individual page
  • [3914] - Remove trash icon for some specific data types

Improvement

  • [3814] - Definition of code style
  • [3918] - Mitigate vulnerability of Captcha feature
  • [3935] - Update of robots.txt to disallow access to forms
  • [3939] - Add bind address option to .env docker-compose
  • [3969] - Update Freemarker version
  • [3979] - It takes too much time to remove blank statements
  • [3984] - Remove Google Fonts from Tenderfoot
  • [3985] - Remove Google Fonts from TPF implementation

Release managers

Acknowledgements

  • No labels

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