Index: openacs-4/packages/assessment/www/doc/as_items.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/as_items.adp,v diff -u -r1.8 -r1.9 --- openacs-4/packages/assessment/www/doc/as_items.adp 1 May 2018 08:45:53 -0000 1.8 +++ openacs-4/packages/assessment/www/doc/as_items.adp 4 Aug 2018 09:34:07 -0000 1.9 @@ -46,7 +46,7 @@ number of attributes from as_items into mapping tables where "override" values for these attributes can optionally be set by authors. If they choose not to set overrides, then the -values originally created in the as_item supercede.
+values originally created in the as_item supersede.Separately we will deal with Checks on
as_items. These will allow us to make checks on the input (is the
value given by the user actually a valid value??), branches (if we
@@ -383,7 +383,7 @@
-
Separately we will deal with Checks on as_items. These will allow us to make checks on the input (is the value given by the user actually @@ -515,7 +515,7 @@
Attributes of Assessments will include those previously included in Surveys plus some others:
The Assessment Package unites the work and needs of various members of the OpenACS community for data collection functionality within the OpenACS framework. We're using the term "Assessment" instead of -"Survey" or "Questionnaire" (or "Case Report Form" aka CRF, the term +"Survey" or "Questionnaire" (or "Case Report Form" a.k.a. CRF, the term used in clinical trials) because it is a term used by IMS and because it connotes the more generic nature of the data collection system we're focusing on.
@@ -27,7 +27,7 @@ Consortium's specs for Question and Test Interoperability and Simple Sequencing.Schedulers could also be teachers, curriculum designers, site coordinators in clinical trials, etc.
Schedulers could also be teachers, curriculum designers, site
Index: openacs-4/packages/assessment/www/doc/sequencing.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/sequencing.adp,v
diff -u -r1.3 -r1.4
--- openacs-4/packages/assessment/www/doc/sequencing.adp 25 Jan 2018 12:18:49 -0000 1.3
+++ openacs-4/packages/assessment/www/doc/sequencing.adp 4 Aug 2018 09:34:07 -0000 1.4
@@ -86,7 +86,7 @@
:item_4231 == 'red'". Additionally other variables
might be defined by the API at a later stage, e.g.
":percent_score", which would be replaced by the current
-percentage value (aka score) that subject had in the test so far
+percentage value (a.k.a. score) that subject had in the test so far
(taken from the as_session_table). It might be interesting to pass
these variables along in the API, this remains to be seen when
actually implementing the system.
Index: openacs-4/packages/assessment/www/doc/sequencing.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/sequencing.html,v
diff -u -r1.4 -r1.5
--- openacs-4/packages/assessment/www/doc/sequencing.html 25 Jan 2018 12:16:34 -0000 1.4
+++ openacs-4/packages/assessment/www/doc/sequencing.html 4 Aug 2018 09:34:07 -0000 1.5
@@ -112,7 +112,7 @@
":item_1234 == 'blue' AND :item_4231 == 'red'". Additionally other
variables might be defined by the API at a later
stage, e.g. ":percent_score", which would be replaced by the
-current percentage value (aka score) that subject had in the test so
+current percentage value (a.k.a. score) that subject had in the test so
far (taken from the as_session_table). It might be interesting to pass
these variables along in the API,
this remains to be seen when actually implementing the system.
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.4 -r1.5
--- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 1 May 2018 08:45:53 -0000 1.4
+++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 4 Aug 2018 09:34:07 -0000 1.5
@@ -16,7 +16,7 @@
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 -administrator. This permissions can be managed folloging the +administrator. This permissions can be managed follogging the Permission link that appears in the list of assessments.
Both links will lead the user to a page where the necessary permissions can be set.
Also the user can search for another user to manage his permissions:
After clicking OK, the user will appear in the list an the Index: openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html 25 Jan 2018 12:23:47 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html 4 Aug 2018 09:34:07 -0000 1.4 @@ -1,3 +1,3 @@
-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 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 administrator. This permissions can be managed folloging the Permission link that appears in the list of assessments.
Both links will lead the user to a page where the necessary permissions can be set.
Also the user can search for another user to manage his permissions:
After clicking OK, the user will appear in the list an the permissions can be set properly.
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 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 administrator. This permissions can be managed follogging the Permission link that appears in the list of assessments.
Both links will lead the user to a page where the necessary permissions can be set.
Also the user can search for another user to manage his permissions:
After clicking OK, the user will appear in the list an the permissions can be set properly.