Configuring the Semantic Editor module

Note: There are two versions of the editor module: wisski_editor that works together with wisski_textproc and the newer wisski_textedit that relies on wisski_textmod. The configuration is mainly the same. Where the wisski_textedit differs, it will be marked in parantheses

The Semantic Editor module extends the TinyMCE visual editor by providing buttons and functionality for annotating object references in text and the links between them. Referenced objects are always linked to one of the pathbuilder groups defined in the information space. Therefore, before starting to annotate text, you need to define the groups of the objetcs that you want to annotate.

The Semantic Editor module can be configured via the Admin tab "Site Configuration" -> "WissKI module settings" -> "Editor". (For textedit: "Site Configuration" -> "WissKI module settings" -> "Text handling" -> "Editor") The admin page can be divided into two parts which are described below.

Rendering of annotations

Editor settings groups

In the first frame, you can configure the rendering of annotations in the text. For each defined group you may define a color for the annotated text and an icon that preceeds the annotation. If you have installed the 3rd party Drupal modules Colorpicker or JQuery Colorpicker, there will appear a nice color picker dialog for selecting a color. Otherwise you will have to enter the RGB color hexcode like in HTML and CSS. Both color and icon are optional, nonetheless you should provide at least one of the both to make annotations visible and outstanding in your texts.

For a basic installation, you should define a color and/or an icon for each group for which you want to make annotations. Note that, of course, you may define more groups than you actually want to use for annotation. For groups that you don't use in the editor you don't need to specify a color and icon.

Advanced configuration: The appearance of annotations in the text can be altered by editing the CSS files template_default.css, template_group.css, and template_group_no_icon.css.

Editor settings

Editor settings settings
The second frame groups various settings concerning how and which annotations can be created and displayed as well as encoding options. For a basic installation, only the third and fourth option is important set appropriately:

  • Place groups You may select one or more groups that represent places IB Imageand that at least for some instances provide coordinate information for geo-referencing (see the resp. fields of the Vocabulary Control module). When hovering over annotations belonging to that groups, the infobox will show up with a map showing the place according to the coordinate information.
  • Input format This is the Drupal Input format that the semantic editor uses. If the pre-configuration during the module installation ran correctly, you should not need to alter this. (Not available in textedit, see ... -> "Text Handling" -> "Paths")
  • Show triples before store When saving a text a table of all triples extracted from the text's annotations will be displayed together with the possibility to not store the extracted triples. Normally, this is useful for debugging purposes and may be disabled on production sites. (Not available in textedit. If you have installed and configured wisski_texttrip, instead there is a tab called "Extractable triples" for the text node.)
  • Groups of which instances may be created Like form-based input, the editor let's you distinguish between closed and open groups, .i.e groups that have a fixed/defined set of instances (e.g. gender, departments, ...) and groups of which the user may create new instances. In this field you should select the groups that are considered open. The editor will always provide the possibility to create a new instance of these groups by displaying a menu item on the side menu, marked with an asterisk (*). In order to correctly create triples for such groups, a vocabulary for that group backed on the local data must be defined.
  • Encode entities also in RDFa WissKI uses an HTML class-based approach to store the annotations in the text. Enabling this option will also include RDFa attributes in the text for refering to the mentioned objects/entities. This allows RDFa parsers and harvesters to read the annotations inluded in the text.