SemanticWeb Connector

Installation and Configuration

Copyright ©

Mindbreeze GmbH, A-4020 Linz, 2018.

All rights reserved. All hardware and software names used are brand names and/or trademarks of their respective manufacturers.

These documents are strictly confidential. The submission and presentation of these documents does not confer any rights to our software, our services and service outcomes, or any other protected rights. The dissemination, publication, or reproduction hereof is prohibited.

For ease of readability, gender differentiation has been waived. Corresponding terms and definitions apply within the meaning and intent of the equal treatment principle for both sexes.

InstallationPermanent link for this heading

Before installing the SemanticWeb connector, make sure to verify that the Mindbreeze server is already installed and that this connector is also included in the Mindbreeze license.

Installing the connector pluginPermanent link for this heading

The SemanticWeb connector is available as a ZIP file. This file must be registered as follows in the Mindbreeze server via the management UI or mesextension.exe REST client:

mesextension --interface=plugin --type=archive --file=SemanticWebConnector-<version>.zip install

PLEASE NOTE: A re-installation can also update the connector.

Uninstalling the connector pluginPermanent link for this heading

To uninstall the SemanticWeb Connector connector, first delete all instances in the configuration and then remove the plugin via the management UI or execute the following command:

mesextension --interface=plugin --type=archive --file= SemanticWebConnector -<version>.zip uninstall

Configuring MindbreezePermanent link for this heading

Click the “Indices” tab and then click the “Add new index”  icon to create a new index (optional).

Enter the index path. If necessary, adjust the display name of the index service and the associated filter service.

Add a new data source with the “Add new custom source”  icon (located at the bottom right).

URL”: defines the location of the data source (Turtle file) to be indexed, for example, file:///d:/data/example.ttl with Windows or file:///data/example.ttl with Linux. If the data source is on a Windows Share, then it should be mounted locally.

SparQL Query”: For example:

PREFIX skos: <>

PREFIX umls: <>

PREFIX rdfs:  <>

PREFIX xsd: <>

SELECT ?key ?title ?code ?cui ?tui ?sty


  ?key skos:prefLabel  ?title .

  ?key skos:notation  ?code  .

  OPTIONAL {?key umls:cui  ?cui }

  OPTIONAL {?key umls:tui ?tui }  

  OPTIONAL {?key umls:hasSTY ?sty }


The results of the SparQL query (solutions) are indexed as single documents with metadata. It is important that the query has a variable named "key" which is then used as the document key; other variables are indexed as metadata.

  • Source Name”: is the variable name in the SparQL.
  • Mapped Name”: is the metadata name in the index. “mes:key “, "modificationdate” and " title” can also be used as the mapped name, which are not indexed as metadata but as document key, change date, or title of the indexed document.
  • Format”:
    • Auto”: The field object type in the solution object is converted to the corresponding Mindbreeze metadata type.
    • String”: The string representation of the field object type in the solution object is used.
    • Number”: If the field object type is not the "Number" type, the string representation of the field is converted to Number.
    • Date”: If the field object type is not the "Calendar" type, the string representation of the field is converted to Calendar.