openeuropa/rdf_skos

Drupal module that contains the RDF SKOS entity types.

1.0.0 2024-02-14 13:52 UTC

Requires

• php: >=8.1
• drupal/core: ^10
• drupal/sparql_entity_storage: ^2.0.0-alpha12

Requires (Dev)

• composer/installers: ^1.11
• drupal/core-composer-scaffold: ^10
• drupal/drupal-extension: ^5.0
• drush/drush: ^12
• mikey179/vfsstream: ^1.6.10
• nikic/php-parser: ^4
• openeuropa/behat-transformation-context: ^0.2
• openeuropa/code-review: ^2.0.0-alpha6
• openeuropa/task-runner-drupal-project-symlink: ^1.0-beta6
• phpspec/prophecy-phpunit: ^2
• symfony/phpunit-bridge: ^6.2

EUPL-1.2

README

This module provides a dedicated entity type for SKOS modeling. The module requires access to a triplestore database, such as Virtuoso 7.

Upgrade from 0.11.0 to 1.0.0-alpha1

On 1.0.0-alpha1, the rdf_entity module dependency has been removed and instead the sparql_entity_storage module has been introduced (see the rdf_entity module's Readme for more information).

As suggested by the rdf_entity module itself, the following steps can be taken in order to update rdf_skos in production:

The update process needs to be split in three deployments, which will likely result into separate site releases.

First deployment

1. Before you update rdf_skos to 1.0.0-alpha1, require an empty version of the drupal/sparql_entity_storage module:

   $ composer require drupal/sparql_entity_storage:dev-empty-module
   

2. Deploy to production.
3. Enable the module (this can be part of the deployment procedure above, depending on your setup).

At this point your site's composer.json should look like this:

{
    ...
    "openeuropa/rdf_skos": "~0.11.0",
    "drupal/sparql_entity_storage": "dev-empty-module",
    ...
}

Second deployment

1. Remove the empty drupal/sparql_entity_storage module requirement from your composer.json.
2. Require drupal/rdf_entity with the new 1.0-alpha21 version and openeuropa/rdf_skos with the new 1.0.0-alpha1 version.
3. Deploy to production.
4. Uninstall the drupal/rdf_entity module (this can be part of the deployment procedure above, depending on your setup).

At this point your site's composer.json should look like this:

{
    ...
    "openeuropa/rdf_skos": "~1.0.0-alpha1",
    "drupal/rdf_entity": "~1.0-alpha21",
    ...
}

Third deployment

1. Remove the drupal/rdf_entity dependency.
2. Deploy to production.

At this point your site's composer.json should look like this:

{
    ...
    "openeuropa/rdf_skos": "~1.0.0-alpha1",
    ...
}

After these steps your site should have the latest version drupal/rdf_skos module using drupal/sparql_entity_storage and the drupal/rdf_entity module should no longer be in your codebase.

Technical details and constraints

The module allows loading SKOS concept schemes and concepts as entities in Drupal. The entities will be loaded from the graph IRIs specified in the related configuration.

Since all the graphs are passed to the methods for loading entities, this enforces the limitation of having unique IRIs (IDs in Drupalese) for the SKOS entities present in all the graphs.

Development setup

Initial setup

You can build the test site by running the following steps.

• Install Virtuoso. The easiest way to do this is by using the OpenEuropa Triple store development Docker container which also pre-imports the main Europa vocabularies.
• Install all the composer dependencies:

$ composer install

• Customize build settings by copying runner.yml.dist to runner.yml and changing relevant values, like your database credentials.

• Setup test site by running:

$ ./vendor/bin/run drupal:site-setup

This will symlink the module in the proper directory within the test site and perform token substitution in test configuration files such as behat.yml.dist.

Please note: project files and directories are symlinked within the test site by using the OpenEuropa Task Runner's Drupal project symlink command.

If you add a new file or directory in the root of the project, you need to re-run drupal:site-setup in order to make sure they are be correctly symlinked.

If you don't want to re-run a full site setup for that, you can simply run:

$ ./vendor/bin/run drupal:symlink-project

• Install test site by running:

$ ./vendor/bin/run drupal:site-install

Your test site will be available at ./build.

Using Docker Compose

Alternatively you can build a test site using Docker and Docker-compose with the provided configuration.

Requirements:

• Docker
• Docker-compose

You can make any alterations you need for your local Docker setup. However, the defaults should be enough to set the project up.

Run:

$ docker-compose up -d

Then:

$ docker-compose exec web composer install
$ docker-compose exec web ./vendor/bin/run drupal:site-install

Your test site will be available at http://localhost:8080/build.

To run the grumphp test:

$ docker-compose exec web ./vendor/bin/grumphp run

To run the phpunit test:

$ docker-compose exec web ./vendor/bin/phpunit

To run the behat test:

$ docker-compose exec web ./vendor/bin/behat

Working with content

The project ships with the following Task Runner commands to work with content in the RDF store, they require Docker Compose services to be up and running.

Purge all data:

$ docker-compose exec sparql ./vendor/bin/robo purge

Or, if you can run commands on your host machine:

$ ./vendor/bin/run sparql:purge

Import default data:

$ docker-compose exec sparql ./vendor/bin/robo import

Or, if you can run commands on your host machine:

$ ./vendor/bin/run sparql:import

Reset all data, i.e. run purge and import:

$ docker-compose exec sparql ./vendor/bin/robo purge
$ docker-compose exec sparql ./vendor/bin/robo import

Or, if you can run commands on your host machine:

$ ./vendor/bin/run sparql:reset