What's New in 1.12.0
Ease of enabling additional interface languages

Adding additional interface languages to VIVO no longer requires editing pom.xml files or reinitializing the triple store of an existing installation.  Languages may be added simply by editing runtime.properties alone and restarting Tomcat.  During the restart, the appropriate RDF content for the enabled languages is automatically loaded and merged into an existing installation's triple store.  See Enabling Interface Languages in VIVO as an Administrator for more information.

Multilingual content editing

While previous versions of VIVO allowed the addition of labels to entities in multiple languages, VIVO 1.12.0 now makes all content – including ontology metadata and site administration settings such as page titles and links – editable in multiple languages.  The values entered in each editing form are saved according to the language currently selected in VIVO's interface.  See Using VIVO's Internationalization (i18n) Features for more information.

Improved translations and internationalization of forms and visualizations

Translations have been improved for a number of interface elements and previous gaps in internationalization, especially in editing forms and visualizations such as the Capability Map, have been filled in.

Miscellaneous improvements and bugfixes

VIVO 1.12.0 brings a number of important improvements such as reduced profile page load times for sites containing multilingual content, upgraded Jena dependencies that permit larger batches of triples to be updated in a single SPARQL UPDATE request, and TPF (Triple Pattern Fragment) server compatibility with the TDB triple store.

For the complete list of issues resolved, see https://wiki.lyrasis.org/display/VIVODOC112x/Release+Notes#ReleaseNotes-ResolvedIssues

  • No labels