Index: openacs-4/packages/assessment/tcl/apm-callback-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/tcl/apm-callback-procs.tcl,v diff -u -r1.7 -r1.8 --- openacs-4/packages/assessment/tcl/apm-callback-procs.tcl 7 Aug 2017 23:48:03 -0000 1.7 +++ openacs-4/packages/assessment/tcl/apm-callback-procs.tcl 25 Jan 2018 12:23:47 -0000 1.8 @@ -9,7 +9,7 @@ ad_proc -private inter_item_checks::apm_callback::package_install { } { - Does the integration whith the notifications package. + Does the integration with the notifications package. } { db_transaction { @@ -29,7 +29,7 @@ ad_proc -private inter_item_checks::apm_callback::package_uninstall { } { - Remove the integration whith the notification package + Remove the integration with the notification package } { db_transaction { Index: openacs-4/packages/assessment/tcl/as-install-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/tcl/as-install-procs.tcl,v diff -u -r1.44 -r1.45 --- openacs-4/packages/assessment/tcl/as-install-procs.tcl 7 Aug 2017 23:48:03 -0000 1.44 +++ openacs-4/packages/assessment/tcl/as-install-procs.tcl 25 Jan 2018 12:23:47 -0000 1.45 @@ -127,7 +127,7 @@ content::type::attribute::new -content_type {as_item_sa_answers} -attribute_name {data_type} -datatype {string} -pretty_name {Data Type} -column_spec {varchar(20)} content::type::attribute::new -content_type {as_item_sa_answers} -attribute_name {case_sensitive_p} -datatype {boolean} -pretty_name {Case Sensitive} -column_spec {char(1)} content::type::attribute::new -content_type {as_item_sa_answers} -attribute_name {percent_score} -datatype {number} -pretty_name {Percent Score} -column_spec {integer} -content::type::attribute::new -content_type {as_item_sa_answers} -attribute_name {compare_by} -datatype {string} -pretty_name {Comparasion} -column_spec {varchar(20)} +content::type::attribute::new -content_type {as_item_sa_answers} -attribute_name {compare_by} -datatype {string} -pretty_name {Comparison} -column_spec {varchar(20)} content::type::attribute::new -content_type {as_item_sa_answers} -attribute_name {regexp_text} -datatype {string} -pretty_name {Regexp} -column_spec {varchar(20)} content::type::attribute::new -content_type {as_item_sa_answers} -attribute_name {allowed_answerbox_list} -datatype {string} -pretty_name {Allowed Answerbox List} -column_spec {varchar(20)} Index: openacs-4/packages/assessment/tcl/as-session-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/tcl/as-session-procs.tcl,v diff -u -r1.12 -r1.13 --- openacs-4/packages/assessment/tcl/as-session-procs.tcl 7 Aug 2017 23:48:03 -0000 1.12 +++ openacs-4/packages/assessment/tcl/as-session-procs.tcl 25 Jan 2018 12:23:47 -0000 1.13 @@ -285,7 +285,7 @@ -session_points -assessment_points } { - Notify listeners that something interesting happend with this assessment session. + Notify listeners that something interesting happened with this assessment session. } - 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.3 -r1.4 --- openacs-4/packages/assessment/www/doc/as_items.adp 25 Jan 2018 12:18:49 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/as_items.adp 25 Jan 2018 12:23:47 -0000 1.4 @@ -276,7 +276,7 @@ eg)

Depending on the presentation_types -additonal attributes (presentation_type +additional attributes (presentation_type attributes) come into play (are added as attributes to the CR item type) (mark: this is not feature complete. It really is up to the coder to decide what attributes each widget should have, Index: openacs-4/packages/assessment/www/doc/as_items.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/as_items.html,v diff -u -r1.11 -r1.12 --- openacs-4/packages/assessment/www/doc/as_items.html 25 Jan 2018 12:16:34 -0000 1.11 +++ openacs-4/packages/assessment/www/doc/as_items.html 25 Jan 2018 12:23:47 -0000 1.12 @@ -393,7 +393,7 @@ textarea dimensions ("rows=10 cols=50" eg)

-Depending on the presentation_types additonal +Depending on the presentation_types additional attributes (presentation_type attributes) come into play (are added as attributes to the CR item type) (mark: this is not feature complete. It really is up to the coder to decide Index: openacs-4/packages/assessment/www/doc/display_types.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/display_types.adp,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/display_types.adp 25 Jan 2018 12:18:49 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/display_types.adp 25 Jan 2018 12:23:47 -0000 1.4 @@ -4,7 +4,7 @@

Overview

Displaying items to users has a couple of -challanges. First of all the display of a single item can be +challenges. First of all the display of a single item can be different for each item_type (and even within a type). Second of all, the display of items within a section can be different from assessment to assessment. Last but not least, the whole assessment @@ -58,7 +58,7 @@ specific date set by the author; see this example) -

Depending on the presentation_types additonal +

Depending on the presentation_types additional attributes (presentation_type attributes) come into play (are added as attributes to the CR item type) (mark: this is not feature complete. It really is up to the coder to decide what Index: openacs-4/packages/assessment/www/doc/display_types.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/display_types.html,v diff -u -r1.6 -r1.7 --- openacs-4/packages/assessment/www/doc/display_types.html 25 Jan 2018 12:16:34 -0000 1.6 +++ openacs-4/packages/assessment/www/doc/display_types.html 25 Jan 2018 12:23:47 -0000 1.7 @@ -8,7 +8,7 @@

Overview

-Displaying items to users has a couple of challanges. First of all the +Displaying items to users has a couple of challenges. First of all the display of a single item can be different for each item_type (and even within a type). Second of all, the display of items within a section can be different from assessment to assessment. Last but not least, the @@ -65,7 +65,7 @@ this example)

-Depending on the presentation_types additonal +Depending on the presentation_types additional attributes (presentation_type attributes) come into play (are added as attributes to the CR item type) (mark: this is not feature complete. It really is up to the coder to decide 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.2 -r1.3 --- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 7 Aug 2017 23:48:04 -0000 1.2 +++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 25 Jan 2018 12:23:47 -0000 1.3 @@ -17,7 +17,7 @@ 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 necesary +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.

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.2 -r1.3 --- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html 14 Mar 2005 15:48:12 -0000 1.2 +++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.html 25 Jan 2018 12:23:47 -0000 1.3 @@ -1,3 +1,3 @@ - 1. Manage Permissions
1. Manage Permissions
Prev Chapter 2. User Manual Next

1. Manage Permissions

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 necesary 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.

Prev Up Next
Chapter 2. User Manual Home 2. Actions Administration
\ No newline at end of file + 1. Manage Permissions
1. Manage Permissions
Prev Chapter 2. User Manual Next

1. Manage Permissions

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.

Prev Up Next
Chapter 2. User Manual Home 2. Actions Administration
\ No newline at end of file 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.2 -r1.3 --- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.adp 7 Aug 2017 23:48:04 -0000 1.2 +++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.adp 25 Jan 2018 12:23:47 -0000 1.3 @@ -17,7 +17,7 @@

Actions can be also created, following the link "Add new action":

The action is formed mainlly by four things:

  1. Name: the desire name that gives an idea of what the action -do.

  2. Description: short explaination of what the action do, and how +do.

  3. Description: short explanation of what the action do, and how its done.

  4. Tcl code: the code that its executed to performe the action.

  5. 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 Index: openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.html,v diff -u -r1.2 -r1.3 --- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.html 14 Mar 2005 15:48:12 -0000 1.2 +++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s02.html 25 Jan 2018 12:23:47 -0000 1.3 @@ -1,3 +1,3 @@ - 2. Actions Administration

2. Actions Administration
Prev Chapter 2. User Manual Next

2. Actions Administration

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.

  1. Register User: create a new user account in the system.

  2. Event Registration: register the user to an event.

  3. 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:

  1. Name: the desire name that gives an idea of what the action do.

  2. Description: short explaination of what the action do, and how its done.

  3. Tcl code: the code that its executed to performe the action.

  4. 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:

  1. Name: this will take the value from a response given by the user to an item of the assessment.

  2. 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).

Prev Up Next
1. Manage Permissions Home 3. Trigger Definition
\ No newline at end of file + 2. Actions Administration
2. Actions Administration
Prev Chapter 2. User Manual Next

2. Actions Administration

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.

  1. Register User: create a new user account in the system.

  2. Event Registration: register the user to an event.

  3. 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:

  1. Name: the desire name that gives an idea of what the action do.

  2. Description: short explanation of what the action do, and how its done.

  3. Tcl code: the code that its executed to performe the action.

  4. 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:

  1. Name: this will take the value from a response given by the user to an item of the assessment.

  2. 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).

Prev Up Next
1. Manage Permissions Home 3. Trigger Definition
\ No newline at end of file Index: openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp 25 Jan 2018 12:18:49 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp 25 Jan 2018 12:23:47 -0000 1.4 @@ -64,7 +64,7 @@
  • Times
      -
    • Availabilty: 2 date widgets (from, and to). This will set the +
    • Availability: 2 date widgets (from, and to). This will set the time the time the survey will become visible for the respondees. It is overridden by the parameter enabled (if a accessment is not enabled, it will never be visible, regardless of date).
    • How often can a accessment be taken: Number of times a survey Index: openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html 25 Jan 2018 12:16:34 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.html 25 Jan 2018 12:23:47 -0000 1.4 @@ -95,7 +95,7 @@
    • Times
        -
      • Availabilty: 2 date widgets (from, and to). This will set the +
      • Availability: 2 date widgets (from, and to). This will set the time the time the survey will become visible for the respondees. It is overridden by the parameter enabled (if a accessment is not enabled, it will never be visible, regardless of date). Index: openacs-4/packages/assessment/www/doc/user_interface/index.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/index.adp,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/user_interface/index.adp 25 Jan 2018 12:18:49 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/user_interface/index.adp 25 Jan 2018 12:23:47 -0000 1.4 @@ -79,7 +79,7 @@ class result will depend on the result of all the tests a respondee did in addition to any manual grades the professor can come up with. Providing a clean UI for this is going to be the -challange.

        +challenge.

        Furthermore the grading package offers to transfer scores (which are stored as integer values) into a grade (e.g. the american A-F scheme, or the German 1-6). This is where it Index: openacs-4/packages/assessment/www/doc/user_interface/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/index.html,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/user_interface/index.html 25 Jan 2018 12:16:34 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/user_interface/index.html 25 Jan 2018 12:23:47 -0000 1.4 @@ -79,7 +79,7 @@ result of all the answers (aggregated). A class result will depend on the result of all the tests a respondee did in addition to any manual grades the professor can come up with. Providing a clean UI for this is -going to be the challange.

        +going to be the challenge.

        Furthermore the grading package offers to transfer scores (which are stored as integer values) into a grade (e.g. the american A-F scheme, or the German 1-6). This is where it gets the name from I'd say ;). Index: openacs-4/packages/assessment/www/doc/user_interface/tests.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/tests.adp,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/user_interface/tests.adp 25 Jan 2018 12:18:49 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/user_interface/tests.adp 25 Jan 2018 12:23:47 -0000 1.4 @@ -4,7 +4,7 @@ A test is a special kind of accessment that allows the respondee's -answers to be rated immediatly. Unless otherwise stated, all pages +answers to be rated immediately. Unless otherwise stated, all pages described are admin viewable only.

        • @@ -142,7 +142,7 @@
        Human grading will display all the questions -and answers of response along with the possibility to reevalutate +and answers of response along with the possibility to reevaluate the points and give comments. The header will display the following information:
          Index: openacs-4/packages/assessment/www/doc/user_interface/tests.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/tests.html,v diff -u -r1.3 -r1.4 --- openacs-4/packages/assessment/www/doc/user_interface/tests.html 25 Jan 2018 12:18:49 -0000 1.3 +++ openacs-4/packages/assessment/www/doc/user_interface/tests.html 25 Jan 2018 12:23:47 -0000 1.4 @@ -8,7 +8,7 @@ A test is a special kind of accessment that allows the respondee's -answers to be rated immediatly. Unless otherwise stated, all pages +answers to be rated immediately. Unless otherwise stated, all pages described are admin viewable only.
          • Settings @@ -205,7 +205,7 @@
          Human grading will display all the questions and answers of -response along with the possibility to reevalutate the points and give +response along with the possibility to reevaluate the points and give comments. The header will display the following information:
          • Title of the test Index: openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp,v diff -u -r1.2 -r1.3 --- openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp 7 Aug 2017 23:48:04 -0000 1.2 +++ openacs-4/packages/assessment/www/doc/user_interface/user_experience.adp 25 Jan 2018 12:23:47 -0000 1.3 @@ -13,7 +13,7 @@ assessment.
            • Is the user allowed to take the survey at all (acs_permission check)
            • Are all conditions for the taking of the -assessment fullfilled
            • Is there still a try for the user +assessment fulfilled
            • Is there still a try for the user left
          • Starttime of the response will be @@ -68,7 +68,7 @@ mine" checkbox. This will be stored in addition to the test.
          • Notifications shall be send to the admin, staff and respondee.
          • If we shall display the results to the -respondee immediatly after finishing the assessment, show it to him +respondee immediately after finishing the assessment, show it to him / her. Display the comments along depending on the settings.
          • If we have a special score, show this result to the user (e.g. if 90% means "you are a dream @@ -80,7 +80,7 @@ various modes which he can select before the first section will be displayed.
              -
            • Normal mode: The adminsitrator is treated +
            • Normal mode: The administrator is treated as a normal respondee, the response will be stored in the system.
            • Test mode: The administrator sees the survey as a normal respondee, the response will not be stored in Index: openacs-4/packages/assessment/www/doc/user_interface/user_experience.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/user_experience.html,v diff -u -r1.1 -r1.2 --- openacs-4/packages/assessment/www/doc/user_interface/user_experience.html 29 Jul 2004 09:35:12 -0000 1.1 +++ openacs-4/packages/assessment/www/doc/user_interface/user_experience.html 25 Jan 2018 12:23:47 -0000 1.2 @@ -18,7 +18,7 @@ check)
            • Are all conditions for the taking of the assessment -fullfilled +fulfilled
            • Is there still a try for the user left
              • @@ -87,7 +87,7 @@
            • Notifications shall be send to the admin, staff and respondee.
              • -
            • If we shall display the results to the respondee immediatly after +
            • If we shall display the results to the respondee immediately after finishing the assessment, show it to him / her. Display the comments along depending on the settings.
              • @@ -103,7 +103,7 @@ An administrator can take the survey in various modes which he can select before the first section will be displayed.
                -
              • Normal mode: The adminsitrator is treated as a normal respondee, +
              • Normal mode: The administrator is treated as a normal respondee, the response will be stored in the system.
              • Test mode: The administrator sees the survey as a normal