Index: openacs-4/packages/assessment/www/doc/item_types.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/item_types.adp,v diff -u -r1.4.2.5 -r1.4.2.6 --- openacs-4/packages/assessment/www/doc/item_types.adp 6 Aug 2024 09:43:17 -0000 1.4.2.5 +++ openacs-4/packages/assessment/www/doc/item_types.adp 2 Sep 2024 08:01:11 -0000 1.4.2.6 @@ -212,7 +212,7 @@ -Only site-wide admins will get to see the following question types: +Only site wide admins will get to see the following question types:
The answer to this question will be stored in the database. The concept here is to support bidirectional interchange of data Index: openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp,v diff -u -r1.5.2.3 -r1.5.2.4 --- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 6 Aug 2024 09:43:17 -0000 1.5.2.3 +++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 2 Sep 2024 08:01:11 -0000 1.5.2.4 @@ -11,8 +11,8 @@
To create an assessment is necessary to have create permissions over the assessment instance. This permission can be inherit or can -be granted by a site-wide administrator. This permissions can be -managed by the site-wide administrator following the Permissions +be granted by a site wide administrator. This permissions can be +managed by the site wide administrator following the Permissions link in the assessment admin page.
To create triggers is necessary to have admin permissions over an assessment. The admin permission is inherit to the user that creates an assessment and also can be granted by the assessment Index: openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.adp,v diff -u -r1.4.2.2 -r1.4.2.3 --- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.adp 6 Aug 2024 09:43:17 -0000 1.4.2.2 +++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.adp 2 Sep 2024 08:01:11 -0000 1.4.2.3 @@ -9,7 +9,7 @@ rightLink="ch02s03" rightLabel="Next">
To be able to administrate actions the user must have site wide admin privileges. To admin actions the user must follow the link "Action Administration" in the assessment admin page.
Register User: create a new user account in the system.
Event Registration: register the user to an event.
Add to Community: register the user to dotlrn and also to a @@ -18,7 +18,7 @@ action":
The action is formed mainlly by four things:
Name: the desire name that gives an idea of what the action do.
Description: short explanation of what the action do, and how -its done.
Tcl code: the code that its executed to performe the action.
Parameter: this are the variables needed in the tcl code, that +its done.
Tcl code: the code that its executed to perform the action.
Parameter: this are the variables needed in the tcl code, that depends of the user.
After the action is created, a link to add the parameters is shown.
When the link is followed, then a form to create the parameter @@ -30,7 +30,7 @@
To delete an action the link "delete" in the action administration page must be followed:
Before deleting an action, a confirm message will be displayed, the action will not be deleted if there is some reference to this -action (i.e. a trigger that wil execute this action).
To be able to administrate actions the user must have site wide admin privileges. To admin actions the user must follow the link "Action Administration" in the assessment admin page.
Register User: create a new user account in the system.
Event Registration: register the user to an event.
Add to Community: register the user to dotlrn and also to a dotlrn class/community.
Actions can be also created, following the link "Add new action":
The action is formed mainlly by four things:
Name: the desire name that gives an idea of what the action do.
Description: short explanation of what the action do, and how its done.
Tcl code: the code that its executed to performe the action.
Parameter: this are the variables needed in the tcl code, that depends of the user.
After the action is created, a link to add the parameters is shown.
When the link is followed, then a form to create the parameter is shown, there are two types of parameters:
Name: this will take the value from a response given by the user to an item of the assessment.
Query: for this type of parameter, the field query is used, and the parameter will take the value or values that the query returns.
To delete an action the link "delete" in the action administration page must be followed:
Before deleting an action, a confirm message will be displayed, the action will not be deleted if there is some reference to this action (i.e. a trigger that wil execute this action).