Dockerized VIVO update doesn't lead to update of home/rdf directory

[litvinovg]

Describe the bug home/rdf directory contains serialized triples to load into graphs on startup. It has to be updated on VIVO deployment, but if VIVO_HOME volume is already exists it will not be updated, which could lead to issues. In VIVO 1.15.0 migration from previous authorization mechanisms was created, which occurs on first startup after update. To run properly it requires authorization policies and predefined datasets (loaded from home/rdf directory) to be present. Otherwise VIVO might not work properly.

To Reproduce Steps to reproduce the behavior:

1. Install dockerized VIVO 1.14.3, check that VIVO works and home volume has been created.
2. Update dockerized VIVO image to 1.15.0
3. Check that updated VIVO doesn't work properly anymore.

Expected behavior Updated VIVO should work properly.

Potential solutions Potential workaround could be to create multiple volumes instead of one HOME volume. That volumes could be: config tdbModels tdbContentModels

Environment (please complete the following information):

• OS: [e.g. Windows, Linux]
• Browser [e.g. chrome, safari]
• Tomcat version [e.g. 8, 9]
• VIVO version [e.g. 1.11.0, 1.12.0]
• Apache Solr or ElasticSearch version

Additional context Add any other context about the problem here.

[litvinovg]

To properly update dockerized VIVO one would need to copy contents of home/rdf directory before the first start after update of the docker image.

[litvinovg]

In case you have already updated to 1.15 and don't have backups you can fix it this way:

• Get back to 1.14 image or any other prior image
• log into VIVO as a root user
• Go to Site admin -> Ingest tools -> Manage Jena Models - Configuration models
• Remove http://vitro.mannlib.cornell.edu/default/access-control graph Now you can update 1.15 image and update home/rdf directory before first application startup