Using Plugins¶
Multiple GraphDB features are implemented as plugins based on the GraphDB Plugin API. As they vary in functionality, you can find them under the respective sections in the GraphDB documentation.
Plugin |
Description |
|---|---|
Exploring and searching semantic similarity in RDF resources. |
|
An algorithm that identifies the more important or more popular entities in the repository by examining their interconnectedness. |
|
Defining and executing JavaScript code, further enhancing data manipulation with SPARQL. |
|
Tracking changes within the context of a transaction identified by a unique ID. |
|
Generation of inference closure from a specific named graph at query time. |
|
Finding out how a given statement has been derived by the inferencer. |
|
Exploring complex relationships between resources. |
Several of the plugins enable you to create and access user-defined indexes. They are created with SPARQL, and differ from the system indexes in that they can be configured dynamically at runtime. Any user with write access to a given repository can define such an index.
These are:
Plugin |
Description |
|---|---|
Suggestions for the IRIs` local names in the SPARQL editor and the View Resource page. |
|
GeoSPARQL is a standard for representing and querying geospatial linked data for the Semantic Web from the Open Geospatial Consortium (OGC). The plugin allows the conversion of Well-Known Text from different coordinate reference systems (CRS) into the CRS84 format, which is the default CRS according to the OGC. |
|
Support of 2-dimensional geospatial data that uses the WGS84 Geo Positioning RDF vocabulary (World Geodetic System 1984). |
|
Accessing past states of your database through versioning of the RDF data model level. |
|
Calling of text mining algorithms and generation of new relationships between entities. |
|
Providing transactional sequences for GraphDB. A sequence is a long counter that can be atomically incremented in a transaction to provide incremental IDs. |
The GraphDB Connectors are such indexes as well.
Activate/deactivate plugins¶
GraphDB plugins can be in active or inactive state. This means attaching and detaching them to/from GraphDB on a fundamental level.
From the Workbench¶
For most of the plugins, this can be done from the Workbench in . By default, all plugins available there are activated.
Note
The Provenance plugin needs to be registered first in order to be activated. Once registered, it will appear in the list.
If you deactivate a plugin, you will not be able to enable it. For example:
In , deactivate Autocomplete.
If you go to , you will get the following error message:
With a SPARQL query¶
To activate a plugin with a query from the SPARQL editor, run:
INSERT DATA { <u:a> <http://www.ontotext.com/owlim/system#startplugin> "plugin-name".}
To deactivate it:
INSERT DATA { <u:a> <http://www.ontotext.com/owlim/system#stopplugin> "plugin-name".}
Note
Spell out the plugin names the way they are displayed in the Workbench page shown above.
List plugins and their state¶
To get a list of all plugins and their current state (active/inactive), run:
SELECT ?plugin ?state { ?plugin <http://www.ontotext.com/owlim/system#listplugins> ?state .}
Enable/disable plugins¶
Some of the plugins also have an enabled and disabled state, provided that they have been activated before that. These include:
Autocomplete index¶
The index can be enabled both from in the Workbench and with a SPARQL query.