Versions Compared

Old Version 2

changes.mady.by.user Dragan Ivanovic

Saved on

compared with

New Version Current

changes.mady.by.user Dragan Ivanovic

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 newly defined UI labels vocabulary introduced in VIVO 1.14.0. 

Table of Contents

What's New

Simplified process for installation and customization

The VIVO-languages and Vitro-languages projects are not needed anymore for the installation of VIVO (or Vitro). Customization of UI labels can be specified in local custom ttl files by using private-use language subtags (such as de_DE_x_tib, or fr_CA_x_uqam). Those changes can be made in separated directory in VIVO_HOME, which won't be affected (deleted, overwritten) by any further upgrade of VIVO to newer version. 

Eliminating language specific FTL files

Phrases sensitive on gender and plural-related transformation of words, and other variations related to other morphological changes in different languages have been replaced with more generic changes insensitive on those linguistic transformations. This eliminates need for some language-specific FTL files, especially in the case of loading data from the graph, and improve user-experience.  

Simplified process of supporting new languages

Up to VIVO 1.13.0, adding of a new user interface language required changes in VIVO-languages and Vitro-languages projects in different directories for web application property files and for data which should be preserved in graph. Moreover, it required changes of couple Maven specific files (pom.xml), meaning it required a technical person included in the process of adding new language. Starting from the VIVO 1.14.0, adding of new language can be performed by a translator requiring only a basic knowledge of the ontology notation. 

Improvement of performance for startup of VIVO

The operations of loading and removing sample data, adding and removing model, clearing statements have been improved more than 5 times comparing to VIVO 1.13.0 and prior versions.  

Faux data properties

Besides support faux object properties, VIVO from 1.14.0 also supports faux data properties.  

Configuration of usage of Map of Science visualization

A flag visualization.mapOfScience with possible values enable and disable has been introduced in runtime.properties. VIVO adopters/implementers can disable usage of Map of Science. 

Resolved Issues

Bug

  • [328] - Remove "Other" special case from ChildVClassesWithParent
  • [3154] - Term of use page page is in English
  • [3175] - Labels on Preferred title deletion form
  • [3176] - Labels on Preferred title Edition form
  • [3042] - Making Capability Map i18n Compliant
  • [3541] - i18n: Error messages not displayed in correct language if locale changed
  • [349] - i18n fixes for Processing RDF form
  • [3774] - Small typo in a js file
  • [3790] - Improved safety for visualisation cahes queries
  • [3869, 3864] - Some freemarker templates don't have escaped values
  • [3850] - Tenderfoot template possibly broken
  • [3847] - First class group label always have en-US tag
  • [3865] - Faux property participant doesn't work
  • [3871] - Upload ontology data that contains blank nodes doesn't work
  • [3884] - Some inferred TBox axioms are not removed when the underlying assertions are deleted
  • [3889] - JFactTBoxReasonerTest sometimes fail
  • [3893] - Language selector doesn't work in Vitro
  • [3894] - Autocomplete form for organization name doesn't work

New Feature

  • [3760] - Adopting i18n bean to read translations from triple store instead from property files
  • [3800] - Support local extension subtag in the language tag
  • [352] - Support for faux data properties 
  • [356] - Support for combining parameters and apostrophe in UI labels
  • [3821] - Enabling/disabling Map of Science visualization

Improvement

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

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. 

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

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
  • [3792] - Clear statements and remove actions in Manage Jena models menu take too much time
  • [3605] - First time loading on HDD with journaling file system can take a lot of time
  • [3572] - Get rid of language specific ftl files
  • [332] - Fixes for new individual form
  • [333] - Move search help page translations to properties
  • [3777] - Move qr codes about page translations to n3 configurations
  • [3778] - Moving translations for map of science from ftl files to property files
  • [334] - Decouple email templates and translations
  • [2923] - Replace hard coded text with tags (label keys) in all templates
  • [2921] - Support plurals in all languages
  • [338] - Language-neutral help text in autocomplete forms
  • [3762] - Moving VIVO/Vitro-languages repositories into VIVO/Vitro repositories
  • [353] - Adding English as default language
  • [3853] - Removing itextpdf dependency
  • [3885] - Improved delay when logging in
  • [3886] - Added some missed UI labels
  • [3896] - Mitigation of Capability map vulnerability

Release managers

Acknowledgements