Versions Compared

Old Version 3

changes.mady.by.user Graham Triggs

Saved on

compared with

New Version 4

changes.mady.by.user Graham Triggs

Saved on

Key

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

...

Initially developed at the University of Melbourne, the code has been updated to remove dependencies on third party search engines. In this implementation, it is using the improved visualisation architecture that was present in 1.8.1. This means that the results are coming straight out of the triple store; however, the results may be subject to caching, in the same way as the Map of Science, Temporal Graph, etc.

Note
titleNotes for Upgrading Installations

The capability map is only linked to from the menu bar. As this is configured through the triple store, and the initial definitions are in a file that only gets loaded the first time VIVO is run, upgrading applications will not have the link present.

To access the capability map in an upgraded VIVO, you need to browse to the following url path:

<vivo>/vis/capabilitymap

This can be added to an existing application's menu bar via the Site Admin pages.

...

Adapted for VIVO 1.9 by: Graham Triggs; DuraSpace.

Maven Project Structure

To make it easier for new developers to get started with VIVO, the custom Ant scripts have been replaced with standard Maven project structures.

Both Vitro and VIVO have been migrated. As a developer, when you clone the projects from GitHub, you should place them in directories next to each other. E.g.:

Code Block
/projects
  /Vitro
    /pom.xml
    /api
    /....
  /VIVO
    /pom.xml
    /api
    /...
 

With this layout, you only need to tell your IDE to load or import the pom.xml in the "VIVO" project, and it will automatically load in all of the other projects, including Vitro, setting up your IDE ready to start work with full autocompletion, etc.

Maven Based Installer

As a result of the move to Maven, there is now an "installer" project, which will assemble the application and home directories, and copy them to your Tomcat and installation / home directories.

The installer will automatically download all of the necessary dependencies - including pre-built Vitro and VIVO code - in order to complete the installation.

This installer also provides a natural place for sites to add their customisations: e.g. a custom theme or even additional Java classes in the web application; RDF in the home directory, etc.

Resolved Issues