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. As a special service we also provide a direct download link for a full release with all modules here in the download area, currently only available for WissKI D6 - WissKI on Drupal 6.

To install WissKI extract the WissKI release to the subdirectory sites/all/ of your drupal installation. The command for the current WissKI D6 version would be:
server-projektdb:/srv/www/htdocs/wisski-gardens/sites/all # tar xvfz wisski_fratnolc.tar.gz

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

Drupal installation

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 on Drupal 6 please activate the following modules:

  • Menu per Role
  • WissKI
  • WissKI Find Module
  • WissKI Jit Visualization
  • WissKI Navigator Module
  • WissKI Pathbuilder API
  • WissKI Image Module
  • 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 settings of your drupal installation. After activating the modules go to the "Administer" menu, "Site building" and click 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:

WissKI theme

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 initializing it with an owl-dl ontology by your choice, preferable a domain ontology based on the Erlangen CRM (ECRM) or a version of the Erlangen CRM directly. At the time of this tutorial the current version of the ECRM is version 150218 which can be found at http://erlangen-crm.org/150218/. Copy the link and go to the Ontology tab in the WissKI settings.

Ontology tab

Hit the "Read Ontology" button right under the input field. 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 Erlangen CRM. At first you should think about the typical concepts you need to manage. For example, museums usually 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 templates area. As a starting point just go there and copy the link of the basic template for Museum Objects and Persons. Please take care: Path definitions are depending on the correct version of your ontology. The paths for ECRM 120111 only work with the ECRM 120111! However, for current module versions an ECRM version independent template is available. 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.

Import of paths

Click on the import link and copy the address of the desired template to the textfield. Afterwards hit the "Load import file" button.

Pathbuilder paths

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

In order to be able to use the text based input method, you have to set up controlled vocabularies and the semantic editor. Please follow the instructions of the Vocabularies Guide and Semantic Editor Guide.