The installation via Docker Compose follows the approach – one Semantic Turkey and one GraphDB dedicated, respectively, to ShowVoc and VocBench. This means that the two systems have separate projects. On the contrary, in the deployment we previously had (made and managed by Andrea), VocBench and ShowVoc use the same Semantic Turkey and the same GraphDB, with the consequence that to publish a project it was enough to add the user showvoc-public (but on the project dashboard one still need to create/update the various indexes).

Backup

<Craig>Backups of the dockerised caliper system can be made by simply copying the data folders. From the root of the caliper system folder (this is the caliper folder of the git repository) these data folders are:

• volumes - this is the data folder associated to Fuseki
• showvoc-docker/volumes - this data folder contains both the data for ShowVoc and VocBench

Backups can be done by running the backup_volumes.sh script in the scripts folder of the respository. You can edit the backup script accordingly as the script is highly documented. You only have to update the following specific parts:

1. Google Cloud Storage (GCS) bucket that you have access to and want to use. (Line 23). In the case of the test instance this value is fao-datalab-backups.
2. The full system directory where the caliper instance is installed, in the case of the datalab caliper internal test instance, this is /opt/caliper_internal_test/caliper. (Line 20)
3. GCS storage directory. (Line 51). In this case …/caliper/internal/test

The backup script archives both data directories and uploads the archives to Google Cloud Storage. The archives follow these conventions:

1. Fuseki - fuseki_volume_<BACKUP_TIMESTAMP>.tar.gz
2. ShowVoc/VocBench - vocs_volume_<BACKUP_TIMESTAMP>.tar.gz

From VocBench to ShowVoc

To make a VB project visible in ShowVoc, that must be “deployed”. To do that,

...