EOL: Install latest version of VIVO, fix any errors that pop up

[daniels303]

Should be worked on by Ted and John.

[jja]

Not Ted but Don could work on this if he wanted/has time...

[jja]

To clarify: the point of my last comment is that Ted should not be tasked with the upgrade, but if Don is available then he is an alternative to me.

The point of the reference from #12 is that upgrading should resolve #12 .

[dwstott]

Will look into what will be involved/affected next week.

[dwstott]

Should be able to upgrade to v1.9.1 with configuration and Maven changes, without doing a complete reinstall. https://wiki.duraspace.org/display/VIVODOC19x/Upgrading+VIVO Am checking this out on wombat-dev.

[dwstott]

1.9.2 vivo running on vivo-dev.eol.ucar.edu for testing

[heesuchang]

We will be upgrading to version 1.9.3, which is the last 1.9.X version.

[dwstott]

Configuration changes made. In process of updating java and maven on vivo-dev, then will try the first build on testing vm.

[dwstott]

Configurations made to build v1.9.3 with new maven structure and our own Vivo customizations. Have a war file; will test with Tomcat.

[heesuchang]

Version 1.9.3 upgrade of existing code tested and running on http://vivo-dev.eol.ucar.edu/vivo_full Configurations for stage-specific build have been made. Progress tracked on "feature/rel-1.9.3" branch

[jja]

Since this was merged to develop but then broke our deploy of #24, I've fixed it on develop and it's running on http://vivo.dev.eol.ucar.edu/vivo/

[cbsnyder]

The separating datasets and publications feature #24 has been integrated into the new version of VIVO and merged into the develop branch. This is now running on the dev instance http://vivo.dev.eol.ucar.edu/vivo/

[cbsnyder]

Worked with John to fix a small VIVO submodule reference problem that I created by mistake. The cleaned up version of develop has been deployed to vivo.dev.

[dwstott]

updated vivo.dev to 1.9.3

[dwstott]

updated prod vivo to v1.9.3