Authority Files

WissKI allows to enhance local data with authority files information. This post gives a short intro and manual how to include an authority file. For your own project, you may, however, want or need to adapt things a bit. Authority files can be seen as and accessed through simple WissKI SALZ adapters. So, you have to set up an adapter that makes the authority file accessable to WissKI.

Easy case:

If the authority file provides a SparQL endpoint you may well use the standard SparQL pathbuilder adapter, add a pathbuilder for it, and define appropriate groups and paths. Again, depending on your scenario, that may be sufficient.

Not-so-easy case:

If you want to access data that is not available through an endpoint, you may try another adapter or write a new one. For the case that the authority file entries are available as LOD -- i.e. each entry has a URI and RDF data can be obtained by querying the URI or a similar URL, the WissKI Authority File module provides the Simple LOD adapter. This adapter can only be used to access information for a given URI. You can not search the data pool / authority file with this adapter. Also, it is read-only, of course. Below, you can see a sample configuration for accessing GeoNames. Additionally, at the moment there are specialized legacy modules for accessing GeoNames and the GND of the German National Library.

With these adapters you can also add pathbuilders and define groups and paths. You should do that for every type of entity you want to access. Again below, there is a screenshot of a PB for Geonames.

It is important that the authority file group is connected to the same bundle as the corresponding group of your local pathbuilder. (Select the right bundle on the Configure Field page of the group.) Now, when an entity of that bundle is loaded, data from both adapters, the local and the authority file, will be fetched.

Linking local entities with authority file entries:

In order to get the right data sets, the local entity and the authority file entry must be linked. This is done by stating hat the local URI and the remote one as equivalent. (In the local triple store, both URIs must be made owl:sameAs.)

  The authority file module provides a way of linking both using a pathbuilder group. Unfortunately, there is no default plug-n-play configuration. You have to set it up manually:

  1. Create a pathbuilder group for authority file entries (and one for authority files, optionally)
  2. Refer to the entry group in other groups for entities that shall have authority file information.
Sample configuration of Simple LOD adapter
Sample configuration of Simple LOD adapter for


Pathuilder for Geonames
Pathbuilder for (The paths only differ in the datatype property)
Authority File and Entry Group
Example of an authority file entry PB group. The most important path is the entry URI (Normdaten-URI). In case you don't want a mere URI, use also the field for the entry ID (Normdaten-ID) and and the authority file (Normdatei). The group for authority files is not mandatory but may be helpful.
Interpret authority file entry information
This action defines how to interpret authority file name and ID to generate a canonical URI.
Link the authority file URI to the local record.
Link the authority file URI to the local record. This action defines where the URI can be found.