Upgrading from 1.8.x to 1.9.x

There are no ontology changes, and no significant changes to the code. However, there are a few small changes that you will need to make to your configuration in order for everything to work - in particular, see the Upgrading VIVO (*) change.

You will also need to move your customisations into the new Maven structure.

Maven Structure

The 

Code / Environment Changes

Capability Map

The Capability Map is only linked from the main menu bar, which is dynamically generated from statements in the triple store. The file that includes those definitions is only loaded once during the first startup of VIVO.

In order to add a menu entry to an instance during an upgrade, the easiest way is to add a page via the administration functions.

First, go to "Site Administration" (e.g. after logging in as an administrator, the "Site Admin" link at the top), and then choose "Page Management", and click on the "Add Page" button.

Provide a title, select "This is a menu page", and give a name to the menu entry.

For "Pretty URL", you must enter the following:

/vis/capabilitymap

You will need to choose a content type - select "Fixed HTML" and then enter anything you like in the fields as they won't be displayed.

A complete configuration should look like this.

Once saved, you should see the new entry in the menu bar, and be able to navigate to the capability map.

Freemarker 2.3.23

The Freemarker library has been updated to 2.3.23. The only known code conflict - edu.cornell.mannlib.vitro.webapp.freemarker.config.FreemarkerConfigurationImpl.java - has been updated to have the correct method signature for getTemplate(). This is unlikely to affect any custom templates, however you should make a note to check them.

web.xml

There are two important changes that need to be made to 

head.ftl

applicationSetup.n3

web.xml - servlets and filter

head.ftl (meta tags)

applicationSetup.n3 - new ImageProcessor

Capability Map menu entry