Future Release

This documentation covers a future release of VIVO, version 1.11.x.
If you are able to help contribute to this documentation, please contact sysadmin at duraspace dot org
Looking for another version? See all documentation.

Skip to end of metadata
Go to start of metadata

Overview

Please review the upgrade notes carefully

Upgrading to VIVO 1.11.0 from a previous version of VIVO should not require a data migration, but does require the new installation to have a standalone Solr server. See installation notes for details.

There are no ontology changes, and data produced by 1.11.0 is compatible with 1.6 - 1.9 (and vice versa). It is not required to upgrade to this release prior to subsequent releases. Please see Upgrading VIVO for more details.

What's New

Triple Pattern Fragments (TPF)

TPF presents a lightweight means of obtaining triples from a linked data application as a web service, with very low overhead, and high reliability (it only pattern matches for triples, there are no arbitrary complex queries, so individual requests can not have a high impact on the server). Since the TPF endpoint does not currently enforce visibility settings for classes or properties set in VIVO, the service is turned off by default. In order to enable the TPF endpoint, a "tpf.activeFlag" property must be added to the runtime.properties file with a value of "true". For this property to take effect, the Tomcat server must be restarted.

tpf.activeFlag = true

See Triple Pattern Fragments

 Related ticket

VIVO-1614 - Getting issue details... STATUS

Multi-Lingual Improvements

Several additions and improvements have been made to VIVO's internationalization (i18n). Most notably, the German language translation has been added to the VIVO and Vitro language repositories, and the Internationalization configuration documentation has been updated by community users.

 Related tickets

VIVO-1524 - Getting issue details... STATUS

VIVO-1630 - Getting issue details... STATUS

VIVO-1659 - Getting issue details... STATUS

VIVO-1661 - Getting issue details... STATUS

Externalized Search Index

This release takes another step towards the longer-term goal of modularizing and decoupling VIVO components. In order to allow VIVO to use the latest versions of Solr that may be hosted centrally, this release no longer deploys with a bundled search index, but rather provides for connecting to an external one. As a part of this update, early (non-production) testing has been explored around supporting ElasticSearch as an alternative to Solr.

See configuration instructions.

 Related tickets

VIVO-1587 - Getting issue details... STATUS

VIVO-1589 - Getting issue details... STATUS

VIVO-1592 - Getting issue details... STATUS

VIVO-1596 - Getting issue details... STATUS

VIVO-1600 - Getting issue details... STATUS

VIVO-1612 - Getting issue details... STATUS

ORCiD API

This release includes an improvement to the ORCiD integration that streamlines the process of connecting a VIVO profile with the associated ORCiD profile based on whether the VIVO installation is using the 'public' or 'member' ORCiD API.

The following elements have been added to the runtime.properties configuration:

orcid.apiLevel = public | member
 Related ticket

VIVO-1670 - Getting issue details... STATUS

Docker

In conjunction with the effort to modularize and decouple VIVO components, this release also demonstrates that modularization by establishing Docker infrastructure for deploying the following modules as separate containers:

  • Solr
  • MariaDB
  • VIVO webapp

The vivo-docker2 can be cloned and deployed with custom configuration.

$ docker-compose up
 Related tickets

VIVO-1679 - Getting issue details... STATUS

VIVO-1680 - Getting issue details... STATUS

VIVO-1682 - Getting issue details... STATUS

VIVO-1685 - Getting issue details... STATUS

Publication Claiming

New functionality drawn from OpenVIVO has been added in the 1.11.0 release for claiming publications from both PubMed and CrossRef. To use these features:

  1. Log in to VIVO with the ability to edit
  2. Go to a profile and verify the options for claiming are there
  3. Click on the claiming links - you should be claiming articles for the profile that you came from
  4. Enter IDs, check that the publications are returned as expected, and confirming creates new publications and user links (note that if the DOI or PMID is already present, then the claim interface will return the existing publication from VIVO, not the external metadata)
  5. Go to a co-author profile and claim the publication for them, verifying that the publication now links them as an author.
 Related ticket

VIVO-1415 - Getting issue details... STATUS

Issues Resolved

Sub-task

 Ticket

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Bug

 Tickets

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

New Feature

 Tickets

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Task

 Tickets

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Improvement

 Tickets

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Code Task

 Ticket

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Documentation

 Tickets

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh


Release Managers

Ralph O'Flinn , University of Alabama, Birmingham

Contributors

alessandro galasso
Andrew Woods
Brian Lowe
Christian Hauschke
Don Elsborg
Kitio Fofack
Graham Triggs
Harry Thakkar
Svantje Lilienthal
Laura Wrubel
Manuel Schwarz
Benjamin Gross
Mike Conlon
Ralph O'Flinn
Stefan Wolff
William Stanley Welling

  • No labels