Page History

...

1. The Search Field is a dynamic and powerful way of searching the knowledgebase. While typing here, field 7 shows all frames (partially) corresponding to your search string.
   
   
2. The Switch View Buttons are the back and forward buttons of the Knowledge Browser, comparable to those in standard HTML-browsers. By pushing the button between the back and forward buttons ('Class List'),  field 3 can be switched between a tree view mode , list view mode (default) and domain view mode (see below).
   
   
3. The Class Tree shows the knowledgebases currently opened, and the classes they contain. Furthermore, it provides access to the integrated support system by means of the Quaestor node. Show flash demo... 
   
   
4. The Frame in focus/Browse field window shows the frame (parameter, relation, constraint,...) currently selected in the knowledge browser. Clicking once on a parameter, makes field 7 show the Expressions in which the current parameter is present, double clicking makes sure it shows the relations that can be used to determine current Parameter.
   
5. The View description describes what is shown in field 7.
   
   
6. The View Options pulldown menu provides extended options to the data shown in field 7. For example, one might only want to view parameters in relations, containing attributes or subgoals etc.
   
   
7. The Parameter, Relations and Constraints window shows the contents of the knowledgebase, depending on the view options selected in field 4 and 6. It's the central place to add and edit knowledge.

Together with the Frame Viewer and Slots & Properties, the Knowledge Browser is the most significant component of the user interface for a Knowledge Engineer and offers all the necessary possibilities to search, view and modify knowledge (with the proper user rights). 

...

• Intrinsic functions: .
• Attributes: .
• Dimensions: .
• Constants: .
• Reserved or standard parameters: .
• Normal parameters:  or . The red cross means that additional information is required to make the parameter properly defined.
• Top goal (after double clicking a goal parameter): .
• Normal relations:  or . The red icon means that the relation is either switched of or corrupt.
• Constraints: .
• Taxonomy parameters: .
• Taxonomy entities: .
• Taxonomy relations: .
• Optional library functions: . This information is only shown in a Library node below the Quaestor node the Quaestor node when a library is available.
• Optional library attributes: . Again this information is only shown in a Library node below the Quaestor node the Quaestor node when a library is available.

...

1. Type the name of an attribute by starting with @, or select an attribute from the overview in the Quaestor node;
2. Select the attribute in field 7, the short presentation of the function is shown in field 4;
3. Click on field 4: all (taxonomy) parameters and relations are shown containing the attribute.

...

Therefore, browsing Taxonomy related knowledge in the Knowledge Browser will result in interaction with the QTaxonomy node in the Dataset of the Workbase (or the solution based on this Taxonomy when "Show hidden data" in the Tools>Options... window is not selected) to show where the parameter or relation is instantiated.

Browsing for taxonomy parameters and relations in the Knowledge Browser works the same as for normal parameters and relations. The flash demo below show the connection between browsing in the Knowledge Browser and the Taxonomy tree in the Workbase (with "Show hidden data" in the Tools>Options... switched on).

Furthermore, the demo show that switching on the option "Connect Workbase to Knowledge Browser" under the Appearance tab of the Tools>Options window will enable you to see the (Taxonomy) relations in the Knowledge Browser related to the selection in the QTaxonomy node.

...

You can also remove frames. However, a knowledge base is always protected against this modification as this might have influence on the projects used with the knowledge base. "Under water" the frames are represented by numbers (pointers), when you delete a frame, these pointers are renumbered. And as a result projects with this old numbering will not work properly anymore (you will be warned). Therefore, when you want to remove a frame, you have to remove the delete protection (File>Allow deleting frames ).

Furthermore, you are able to group relevant parameters and relations in classes in the class tree. You can create a new class and arrange existing classes in the class tree on the left side of the Knowledge Browser and drag and drop parameters and relations in these classes.
The purpose of classes is to organise your parameters. You do this by selecting any existing class and press the right mouse button.

...

Class.Sub-Class.Sub-Class….

In this window the class "Top Goals/Undifined" is selected. 

...

To reorder the classes you have to press the button between the forward and back buttons of the knowledge browser (field 2). This button will switch the class tree view between Class List,  Domains and Class Tree view (the default view). Please note that button has the name of the view you will switch to (and not the present view). In the Class List mode you will see all classes presented in a syntax showing sub-classes after a dot. So, a sub-class of "Top Goals/Undefined" class is presented as "Top Goals/Undefined.sub-class". You can simply drag and drop the presented class entries in order to manipulate the order of classes and sub-classes. The only class you cannot move is "Top Goals/Undefined".

Please look at the KE Tutorials for more details. 

Remarks 

• Please realise that when editing a constraint, you will edit this constraint for all relations it is connected to.
• Furthermore, realise that if you do not try to connect possible existing constraints first, you will end up with numerous amount of the same constraints that you cannot delete without destroying projects after you have release your knowledge base. Therefore, when you need a constraint to a relation, first try to connect an existing one and or modify an existing constraint before creating a new one; 
• It is also important to realise that renaming of a parameter will automatically modify relations and constraints they are part of.However, parameters in dataslots and between quotes will not automatically be renamed. You have to use the Search & Replace... option (in the right mouse window) to make sure these parameters are also renamed.
• In addition to all the actions above, please use the right click mouse menu to see all kinds of additional options such as a knowledge base clipboard to copy knowledge.

General User Interface