First page Back Continue Last page Overview Graphics
Presentation for Global vs Analytic User
Notes:
The slide shows the paths in the concept tree for global & analytical users.
In order to provide these paths “setDefault” element can be used in the strategy description to set the default value for the “suitability” attribute of the concepts. In this way the author specifies the condition when the concept becomes desirable for the user.This is a “generic” condition which will be applied to all the concepts of the domain model. It can include information about the user’s LS, about the domain model concepts, for example “knowledge” about the concept or type of the concept.
The author can also specify the level up to which the breadth-first or depth-first order is provided for the user (personal.upToLevel). Therefore after the user has read the concepts above this level all the concepts at a lower level become desirable.
The meaning of this “generic” condition (see author/authorfiles/nvs/GlobalVersusAnalytic.xml) will be described further.
In AHA! there exist different templates for the concepts. The template determines which attributes the concept has, and whether it must have a resource (file) associated with it or not. For example, an abstract concept does not have a resource. A page concept must have a resource, like file:/AHAtutorialLS/xhtml/readme. The templates are listed in /aha/author/authorfiles/templatelist.txt and are xml files in the directory /aha/author/authorfiles/templates.
For a current purpose we add 2 more templates:
“leaf page concept” which is the same as “page concept” .
“node page concept” which is the same as “page concept” but it uses “visited update” relationship instead of “knowledge update”.
The concept relationship types are listed in /aha/author/authorfiles/crtlist.txt and are xml files in the directory /aha/author/authorfiles/crt.
When a “leaf” concept is accesses its “knowledge” and the “visited” attributes are updated. (In case the concept is desirable the values of both attributes are set to 100, otherwise the “knowledge” attribute is set to 35 meaning that the user gained only partial knowledge about the concept). Knowledge update is propagated to higher level concepts.
(Notes continued on next slide...)