Service that produces and publishes a dump file of the current state of deltas. It publishes according to the DCAT v2 standard. Api is provided by mu-resource. Files are hosted by mu-file.

Per cache-graph to manage, you will need an instance of the service, suppose here it is related to leidinggevenden. To add the service to your mu.semte.ch stack, add the following snippet to docker-compose.yml:

A config.json needs to be present under /config/config.json

{
  "http://redpencil.data.gift/id/jobs/concept/JobOperation/deltas/deltaDumpFileCreation/leidinggevenden" : {
    "dcatDataSetSubject": "http://data.lblod.info/datasets/delta-producer/dumps/LeidinggevendenCacheGraphDump",
    "targetGraph": "http://redpencil.data.gift/id/deltas/producer/loket-leidinggevenden-producer",
    "fileBaseName": "dump-leidinggevenden",
    "targetDcatGraph": "optional graph where the information of the data set should reside",
    "targetFilesGraph": "optional graph where the meta data of the ttl should reside"
  }
}

services:
  delta-producer-dump-file-publisher-leiddingevenden:
    image: lblod/delta-producer-dump-file-publisher:x.x.x
    volumes:
      - ./config/delta-producer/dump-file-publisher:/config
      - ./data/files:/share

This service works by receiving deltas from the delta-notifier. It should be configured as such :

  {
    match: {
      predicate: {
        type: 'uri',
        value: 'http://www.w3.org/ns/adms#status'
      },
      object: {
        type: 'uri',
        value: 'http://redpencil.data.gift/id/concept/JobStatus/scheduled'
      }
    },
    callback: {
      url: 'http://delta-producer-dump-file-publisher-leiddingevenden/delta',
      method: 'POST'
    },
    options: {
      resourceFormat: 'v0.0.1',
      gracePeriod: 1000,
      ignoreFromSelf: true
    }
  }

Provided environment variables by the service. These can be added in within the docker declaration.

Will be served by mu-resource. See e.g. https://github.com/kanselarij-vlaanderen/app-themis/blob/master/config/resources/dcat.json for the api definition.

For a more detailed look in how to develop a microservices based on the mu-javascript-template, we would recommend reading "Developing with the template"

Paste the following snip-it in your docker-compose.override.yml:

delta-producer-dump-file-publisher:
  image: semtech/mu-javascript-template:1.4.0
  environment:
    NODE_ENV: "development"
  volumes:
    - /absolute/path/to/your/sources/:/app/

• period clean up of deprecated datasets
• eventually add dcat:Dataset to dcat:Catalog
• upate logic to remove the need for one instance per cache graph to maintain
• add as a result container a link to the data set uri. So we can click through in jobs dashboard

In case the publication graph is residing in a different endpoint as the default database, you can add

{
  "publicationGraphEndpoint": "http://different/endpoint"
}

All other queries will keep using the default database.