From Drupal to a basic WissKI System

For this part of the installation tutorial a fully installed Drupal system is a prerequisite. The first step is to download the desired modules of the WissKI-Software from github at As a special service we also provide a direct download link for a full release with all modules in the download area. The current version can be downloaded there.

To install WissKI switch extract the WissKI release to the subdirectory sites/all/ of your drupal installation. The command for the current version would be:

fichtner@server-wisski:/srv/www/htdocs/biodat/sites/all> tar xvfz wisski_lagavulin.tar.gz 

After unpacking the WissKI package there sould be three subdirectories in your sites/all directory: modules, themes and libraries. Now take your browser and go back to your installed Drupal. Go to "Administer" then "Site building" and "modules".

File 139

Here you can add additional modules to your current Drupal installation. As WissKI is a set of software modules for Drupal, the WissKI modules have to be enabled there. For a basic WissKI System please activate the following modules:

  • Menu per Role
  • WissKI
  • WissKI Find Module
  • WissKI Jit Visualization
  • WissKI Navigator Module
  • WissKI Pathbuilder API
  • WissKI Simple Reasoner API
  • WissKI Special Pages
  • WissKI TripleStore Backend

We also suggest using the "admin menu" module as it simplifies the access to the setting of your drupal installation. After activating the modules go to the "Administer", "Site building" and klick on "Themes". There you should see the theme needed for the display of data stored in the WissKI software called "BlendedMalts". Activate it and choose it as a standard for new users. Now your site should look similar to this:

File 140

Congratulations, you just installed your first WissKI system. The system now is fully installed. The WissKI modules added a control menu at "Administer", "Site configuration" you should see "WissKI module settings". Start configuring the system by initialising it with an owl-dl ontology by your choice, preferable a domain ontology based on the Erlangen CRM or a version of the Erlangen CRM directly. At the time of this tutorial the current version of the Erlangen CRM is Version 120111 which can be found at Copy the link, and go to the Ontology tab in the WissKI settings.

File 141

Now hit the Read Ontology button right under the input field. Now the ontology is downloaded by the system, analyzed, processed and will be available once this process has finished. This could take some minutes. In case of a white page or other problems make sure to set your max_execution_time of php to an appropriate value. You can find more information on this topic here.

Now you can use the Pathbuilder to describe which data is stored and viewed in the system and how it is mapped to the concepts and properties of the cidoc crm. At first you should think about the typical concepts you need to manage. Usually museums have to handle museum objects like paintings, archeological objects, sculptures etc. These museum objects usually were made by human persons at a certain time and a certain place. So the basic starting form probably handles museum objects and gathers information on the creation of the objects. We provide a basic template for such a form in our Pathbuilder template area. As a starting point just go there and copy the link of the basic template for Museum Objects and Persons. Please care: Path definitions are depending on the correct version of your ontology. The paths for Erlangen CRM 120111 only work with the Erlangen CRM 120111! Now go to the Pathbuilder located at the Pathbuilder tab in the WissKI module settings. Currently there should be no paths in your system. On the bottom of the page paths can be exported and imported. Click on the import link and you copy the address of the desired template to the textfield. Hit the "Load Import File"-button afterwards.

File 145

Now you should see a lot of paths. Hit the "Save Configuration"-button below to enable the forms. Now you are done and you can create persons and museum objects in your system. This should only be used as a starting point and the paths supplied as a demo should not be used for real data!