Old Release

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

Overview

VIVO 1.13.0 does not contain ontology changes (comparing to VIVO 1.12.2) or require a data migration or modifications to the Solr setup.  However, please note that upgrading to VIVO 1.13.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.  Moreover, upgrading to VIVO 1.13.0 from a version of VIVO prior to 1.10 requires installation of Solr as a free-standing application.

What's New

Uploading of files associated with individuals in VIVO

Adds an option for uploading a file and link it with an individual in VIVO. For instance, it might be associated with a book (http://purl.org/ontology/bibo/Book). The associated file might be deleted by user with appropriate privilege (administrator or self-editor), or downloaded by a visitor. It is possible to configure allowed MIME types and maximal file size.

Password authentication on external smtp servers

VIVO can be configured to send email using an smtp service of customer choice.  Prior to VIVO 1.13.0 it wasn't possible to set up a non-standard port of SMTP server, neither username and password for SMTP authentication. Since 1.13.0, it is possible by configuring runtime properties email.port, email.username, email.password.

Please find out how to do that at the minimum configuration wiki page.  

Additional features to the SPARQL Update API - Add POST body support

The API supports sending data via an 'update' parameter. Prior to v1.13.0, this was the only method of sending SPARQL update data. Since 1.13.0, VIVO also supports sending data via the POST message body. To use this method, you must set the request content type to application/sparql-update. This method parses the data as an input stream and may offer a performance improvement for large amounts of data. 

Online translation editor

Adds option for VIVO and Vitro localization on website with downloading results in .properties file. This should simplify process of Vitro and VIVO interface translation. A VIVO administrator can enable online translation checkbox in Developer's panel. After that, an online translator panel will appear at the left side of the screen with extracted all labels of the certain page. The translation of those labels can be entered in input fields and at the end the user can export translations in a form of a property file. 

Localization for the Russian language and for the Serbian Language

The VIVO 1.13.0 has been extended to support Russian and Serbian localizations. Hopefully, this will improve adoption of the platform in Serbia and Russian-speaking countries. 

Deletion of individuals and linked objects

Adds functionality to delete individuals and specify SPARQL Query to also delete individual dependent objects. This is some form of controlled cascade deletion which will allow for much easier GDPR compliance. 

Resolved Issues

Bug

  • [3612] - Freemarker error thrown related to microformats
  • [3647] - ChangeListeners get the same model change
  • [289] - I18n regression fix
  • [3714] - Remove/correct portal annotations in i18n files that do not use the correct language tags
  • [3728] - Creating integer literals stored as int
  • [3727] - Backend property editor does not support language tags
  • [3717] - Language tags are added to string data properties when created via the web interface
  • [3723] - Display of the associated department in a concept profile in VIVO 1.12 and VIVO 1.13
  • [3733] - Editor can't edit contributors to a grant
  • [3736] - Public descriptions of data properties in verbose property display
  • [3737] - Individual pages in French interface are broken
  • [3738] - The public description displayed in verbose property display mode is independent of the locale
  • [3739] - The property vivo:grantDirectCosts can't be moved to the property group "none" via Data Property Editing Form

New Feature

  • [3588] - Interface translation is difficult due to lack of translation context (online translation editor) 
  • [3603] - Add a way to upload documents into VIVO/Vitro
  • [3608] - Localization of VIVO in the Serbian language in Latin alphabet
  • [3609] - Localization of VIVO in the Russian language
  • [3429] - SPARQL Update API doesn't support sending update string as non-form-encoded POST body

Task

  • [250] - Creating Locale with specified Language script
  • [3686] - Remove Spring Framework dependency

Improvement

  • [3696] - Change name of output of Jena Models from "ingest" to something meaningful
  • [3693] - Mitigation of orcid-api-client security vulnerabilities
  • [3689] - Prevent copying pom files to home directory
  • [3684] - Bump spring-beans from 4.3.11.RELEASE to 5.3.18 in /api
  • [3548] - Improvements to removing individuals

Release managers

Acknowledgements

  • No labels

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