• last updated 23 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
fix attachments for short_text_interaction

improve spelling and whitespace changes

added support to "Answer_manager.get_answers" to return also non-exericse specific attributes

extend role manager to include rel_type based roles (especially useful for DotLRN)

    • -17
    • +106
    ./tcl/xowf-form-field-procs.tcl
include recent site-wide pages, modernize code

add prototype pages

file select-group-members.form.page was initially added on branch oacs-5-10.

    • -0
    • +0
    ./resources/prototypes/select-group-members.form.page
file topic-assignment.wf.page was initially added on branch oacs-5-10.

    • -0
    • +0
    ./resources/prototypes/topic-assignment.wf.page
file select-topics.form.page was initially added on branch oacs-5-10.

    • -0
    • +0
    ./resources/prototypes/select-topics.form.page
file select-group-students.form.page was initially added on branch oacs-5-10.

    • -0
    • +0
    ./resources/prototypes/select-group-students.form.page
reduce the max interval between screen captures from 60s to 30s during proctoring

allow opening the exam-review also for exams, which are not autogradable

whitespace changes

perform proper login for all tests

remove unneeded line

added functionality to prevent opening the same exam in multiple tabs

Update italian localization

    • -0
    • +76
    ./catalog/xowf.it_IT.ISO-8859-1.xml
Perform proper login with the test user such that session_ids and cookies are correctly setup

Update message keys

    • -5
    • +84
    ./catalog/xowf.es_ES.ISO-8859-1.xml
Delete duplicated message keys

fix passing of question number

Added substitution values for short text answers

This change adds the possibility to provide randomized substitution values to short

text questions via value sets.

Value sets are a means for a content developer to provide multiple matching answers which are inserted into the text before an exercise is shown to the end user. One can e.g. provide for a calculation exercise several input and some output values, such that the students get different calculation exercises provided. These values can also be used for the correct-when clauses.

The content developer can use percent-code delimited elements when defining the exercise:

---

Assume, you want to download a %x.what% with the size of %x.size% over a %x.type% connection with a rate of %x.rate% from %univ%.

---

and also in "correct when"

---

%x.secs%

---

the value sets can be provided via an extra field for the short-text questions and have the form

of a Tcl dict:

---

univ {WU-Vienna TU-Vienna "University of Vienna"}

x {

{type "ADSL" rate "256 kbit/s" size "235 MB" secs 5300 what "Powerpoint file"}

{type "ADSL" rate "512 kbit/s" size "5.6 MB" secs 91 what "PDF file"}

{type "4G" rate "80 Mbit/s" size "270 MB" secs 27 what "PDF file"}

{type "4G" rate "40 Mbit/s" size "650 MB" secs 32 what "Lecturecast Video" }

{type "5G" rate "1 Gbit/s" size "520 MB" secs 4 what "Powerpoint file" }

{type "5G" rate "1 Gbit/s" size "1.5 GB" secs 12 what "Lecturecast Video" }

}

---

In this example, every student will get a randomly chosen value for the university (%univ%)

and matching elements containing the answer (e.g. download time of "270 MB" over "80 Mbit/s" is 27 seconds).

The download time is used in the correct when part, such that auto-correction can be applied.

When a student answers this exercise, the system provides random choices that are substituted in the text.

For every variable ("univ", "x", ..) different random values are used for the student.

Certainly, for other students, other numbers and results will be provided.

Note, that this value sets can be used for numeric an non-numeric exercises.

Current limitations:

- only defined for short-text questions (can be in general also for other question types)

- no elaborate user interface for entering value sets (or a thorough validator) is provided.

use test user_id instead of current user for running tests

Added two types of grading schemes (in addition to "exact") to ordering exercises:

- "position": count elements as correct, when these are on the correct position

- "relative": count elements as correct, if the neighboring element is correctly before the actual element

The results are adjusted by the same guessing correction as in the "ggw" scheme for MC exercises.

Example:

- desired order: 1,2,3,4

- provided answer: 3,1,2,4

- scheme "exact": 0%

- scheme "position": 0 0 0 1

- scheme "relative": 0 1 1 (correctly ordered 1<2 and 2<4)

A minor refactoring was also performed to ease code reuse.

    • -1
    • +1
    ./www/prototypes/TestItemReorder.form.page
  1. … 1 more file in changeset.
include "topic-assignment.wf" in list of displayed workflow types

    • -1
    • +1
    ./www/prototypes/assessment-index.page
fix typo

extend regression test: provide tests of the basic life-cycle steps of the inclass-exam

don't use numbers as object names for actions; don't show "1" for navigation, when there is a single question

added test cases, improved test coverage

edit-item workflow: remove "view" form swa actions