You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 10 Next »

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).


Data Flow


Restore


Restores can be done by running the restore_volumes.sh script in the scripts folder of the git repository. You can edit the restore script accordingly as the script is highly documented. You only have to update the following specific parts:


  1. Ensure that the docker services are not currently running
  2. The caliper root folder. In the case of the test instance, it’s /opt/caliper_internal_test/caliper (Line 19)
  3. The Google Cloud Storage (GCS) bucket. In the case of the test instance this value is fao-datalab-backups (Line 20)
  4. Backup timestamp (Line 25). This is the timestamp of the backup you want to use from the GCS bucket.
  5. The GCS storage directory (Lines 34 and 62). In this case it’s …/caliper/internal/test


The restore_volumes.sh script, deletes the existing data folders if any, downloads the backup files from GCS and extracts them to the relevant data folder paths.

From VocBench to ShowVoc

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

  1. Go to: "Global Data Management / Export data"
  2. In Deployment, choose "Deploy to triple store", Deployer = "ShowVoc Deployer". The deployment can be configured either as "Deploy to new project" or "Deploy to existing project".

    For New project, instructions follow (screenshot below).




  3. After selecting Deploy to new project, click Configure:
    1. add the URL of the Semantic Turkey associated to your ShowVoc: http://showvoc:1979/ (this is the hostname configured by Docker, it should be the same in the corresponding installation).
    2. username and password of a user with admin rights
    3. name of the new project to create
    4. Core repository configuration = "GraphDB 10+ (remote only)" (does not need to be configured)
    5. click OK



  4. Click Submit



  5. Now, to have the project visible in ShowVoc, you need to login to ShowVoc, as an administrator, and go to the "Administration dashboard" and make the project Public (now is Staging):



  6. Make the project Public



  7. After having selected Public, a window is prompted where you need to check the boxes to Create index and Create dataset metadata for the project.


Now, you can log out and go back to the home page of ShowVoc where you will find the new dataset.


Important. When you deploy to an existing project, you still need to go to the ShowVoc admin dashboard and update indexes and recompute the metadata.




How to simplify the process described above. [Instructions not tested yet]

In VocBench, it is possible to create a super user account and save its credential as default. In this way, when you submit a new dataset from VocBench to ShowVoc, you will no longer prompted to insert your credential. The same solution can be applied to the configuration of the triple store when deploying new projects. This can be done in the section Administration in VocBench.



Then, go configure the ShowVoc linked. See the steps below.



At step 3:

  • select scope SYSTEM:

Click button Submit (not visible in the screenshot) to save the data just inserted.

Then, go to scope PROJECT and as "Core repository configuration" select " GraphDB 10+ (remote only)". Click submit again.

If you now redo all steps, you will find all fields populated, except for the one of the project. Note that the credentials are not shown, nor they are ever eturned to the client.

Unfortunately, the name of the project needs to be inserted every time. In order to avoid mistakes, it is advisable to use the same project name for VocBench and for ShowVoc.

 

From VocBench to Fuseki

<Craig>