Triplestore Indexer

Introduction

This Drupal 8 or 9's module provide a system to get the Json-LD representation (which is established from JSON-LD REST Services module) of any content type and taxonomy in Drupal and index that into Blazegraph.

Requirement

• Server side: a Tomcat Server with Blazegraph installed as Triplestore. See the installation guide.
• Client side: a Drupal 8 or 9 website with required modules:
  • JSON-LD REST Services module
  • Advanced Queue
  • Rest UI
• Setup RDF mapping for your content types and taxonomy at admin/config/development/configuration. Please see the instruction.
• Enable serialization for JSON-LD presentation for content nodes and taxanomy by visit admin/config/services/rest or Configuration > Web Services > REST (as Screenshot below)

Configuration

• Download the module to your Drupal site.
• Enable the module by Extend > Custom or using drush en triplestore_indexer.
• Go to Configuration > System > Triplestore Indexer.
• Fill out the configuration form (please see screenshot below)

• Server URL: Blazegraph server URL, eg. http://example.com:8080/blazegraph or http://example.com:8080/bigdata/
• Namespace: see detail at here.
• Method of authentication:
  • Basic/Digest: see the setup guide. If your Tomcat server has an authentication enabled, enter username and password.
  • None: please proceed to the next step.
• Method of operation:
  • Drupal Entity Hooks: By default this option selected, the indexing will be executed immediately after a node or a taxonomy term is created, update, or deleted. (WARNING: it may effect the performance of the site if many nodes/taxonomy terms are being ingested in bulk.)
  • Advanced Queue: Highly Recommended, when a node or a taxonomy term is created, updated, or deleted, the indexing operation will be added to a queue which can be configured to run with Cron job or Drupal Console commnad (eg. drupal advancedqueue:queue:process default). You can create a seperated queue if needed, then enter the new queue's machine name with default in the "Queue" text field below.

    Enabling Indexing/Deleting

  • To enable indexing/deleting of media, node, or taxonomy term, you must make use of the Context module
• Go to Structure > Context
  • Create a Context and choose the Conditions that should be true for the indexing/deleting action to proceed
  • Under Reaction add a Reaction and pick Triplestore Index Reaction or Triplestore Delete Reaction
  • In the Action form that shows up for the Reaction, just pick the corresponding one that you would like
  • Ensure the context is enabled and then save