The workbench for designing and executing POI workflows
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
command
common
docs
project/site
rpc-server
webapp
workflows @ 1406b49
.gitignore
.gitmodules
.travis.yml
LICENSE
README.md
docker-compose.yml.example
pom.xml

README.md

Slipo Workbench -- Project

Build Status

Design and execute workflows on POI datasets.

1. Build

1.1 Prepare resources

1.1.1 Configure modules

Each module must be configured by supplying configuration files under <MODULE>/src/main/recources/config directory. The documentation (along with examples) on module-specific configuration options can be found at a module's directory (see README and config-examples for each one).

1.1.2 Prepare vendor data

If vendor-supplied data are used (e.g. ontologies, classification schemes), they must be copied under common/vendor directory. After packaging common module, these data will be accessible as normal classpath resources (rooted under /common/vendor).

For further details on the content of mentioned configuration files (e.g. a classification for transformation), you should refer to the documentation of each specific tool.

1.1.2.1 Prepare vendor data : configuration profiles for Triplegeo

This kind of vendor data provides configuration profiles (schema-To-RDF mappings and classifications) to be used inside a Triplegeo transformation. The data is expected to be found under the following directory hierarchy:

  • triplegeo/config/profiles/<PROFILE-NAME>/config.properties: base configuration expressed as properties
  • triplegeo/config/profiles/<PROFILE-NAME>/mappings.(yml|ttl): schema-to-RDF mappings
  • triplegeo/config/profiles/<PROFILE-NAME>/classification.csv: a classification scheme

The PROFILE-NAME can be used to reference a mapping/classification inside Triplegeo configuration (without having to specify a filesystem path for it).

1.1.2.2 Prepare vendor data : configuration profiles for Limes

This kind of vendor data provides configuration profiles (property expressions, metrics and thresholds) to be used while inside Limes interlinking operation. The data is expected to be found under the following directory hierarchy:

  • limes/config/profiles/<PROFILE-NAME>/config.properties: base configuration expressed as properties
1.1.2.3 Prepare vendor data : configuration profiles for Fagi

This kind of vendor data provides configuration profiles (rules, output names and formats) to be used while inside Fagi fusion operation. The data is expected to be found under the following directory hierarchy:

  • fagi/config/profiles/<PROFILE-NAME>/config.properties: base configuration expressed as properties
  • fagi/config/profiles/<PROFILE-NAME>/rules.xml: the ruleset controlling fusion
1.1.2.4 Prepare vendor data : configuration profiles for Deer

This kind of vendor data provides configuration profiles (execution graph, output names and formats) to be used while inside Deer enrichment operation. The data is expected to be found under the following directory hierarchy:

  • deer/config/profiles/<PROFILE-NAME>/config.properties: base configuration expressed as properties
  • deer/config/profiles/<PROFILE-NAME>/spec.ttl: the execution graph expressed in RDF (Turtle) language.

1.2. Build

Create temporary directories to be used for unit/integration tests from several modules of this project (if default locations do not suit you, edit <MODULE>/src/main/resources/config/application-testing.properties accordingly):

mkdir -p ~/var/slipo-workbench/jobs ~/var/slipo-workbench/catalog/ ~/var/slipo-workbench/workflows/ ~/var/slipo-workbench/temp

Build the project:

mvn clean install

Prepare docker-build context directories (if planning to build docker images):

ant -f rpc-server/build.xml prepare-docker-build
ant -f webapp/build.xml prepare-docker-build