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 web.xml change.

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

...

It is recommended that you treat the "installer" (or standard distribution) project(s) as a third tier, and keep local customisations customizations only in those these project(s).

For Java files, you can place them directly in the "webapp/src/main/java" directory - these will be compiled and included into your web application as class files. As class files are loaded ahead of jars in WEB-INF/lib, this even allows you to completely overwrite and replace classes that are supplied by the VItro Vitro / VIVO jars.

Your theme - and any other template modifications, etc. - should be placed in the "webapp/src/main/webapp" directory.

Any additional dependencies that you need can be added to the webapp/pom.xml, and they will be retrieved from Maven central and included in the packaged application.

Making changes to the home directory

In order to add files to your home directory - e.g. to include additional filegraph RDF - they should be added to the "home/src/main/resources" directory.

...

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 these definitions is only loaded once during the first startup of VIVO.

...

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

AltMetrics on Profiles

...