This documentation relates to an old version of VIVO, version 1.11.x.
Looking for another version? See all documentation.
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.
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.
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.
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.
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
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:
- VIVO webapp
The vivo-docker2 can be cloned and deployed with custom configuration.
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:
- Log in to VIVO with the ability to edit
- Go to a profile and verify the options for claiming are there
- Click on the claiming links - you should be claiming articles for the profile that you came from
- 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)
- Go to a co-author profile and claim the publication for them, verifying that the publication now links them as an author.
Ralph O'Flinn , University of Alabama, Birmingham