• last updated 1 hour ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Improved handling of autosaved revisions

- reject autosave attempts when time for a student is up

(works for synchronized and non-synchronized exams)

- include submissions with autosaved content in exam protocol (even when state is "initial")

  1. … 3 more files in changeset.
avoid potential loss of submission data on "publish" operations

  1. … 1 more file in changeset.
no need to ask answer_manager for package_id

add missing variable which was deleted during the refactoring of the exam protocol

add bulk-notification functionality to participants_table

  1. … 1 more file in changeset.
strengthen parameter checking

  1. … 3 more files in changeset.
Handling of mutual overwrites in answer workflows

Mutual overwrites occur in answer workflows when a user manages to

open multiple browswer instances/or tabs on the same exam.

In case there was an mutual overwrite, the position as provided by the

instance attributes might deviate from the position, based on which

the actual form data was generated. So, for validating and updating

one has to change the position to the one from the form data (when

this differs). Note that the randomizer depends on property

"position" as well.

The new version avoids that the user might accidencially overwrite his

data and closes on mutual overwrite automatically the older instance

window.

Bumped version number to 5.10.0d38

  1. … 2 more files in changeset.
Refactored exam protocol renderers

The new code reduces the sinze of inclass-exam.wf significantly by

moving the exam protocol into test-item-procs.tcl. In the same step,

the largish function was split up, the rendering functions of

submissions are now named consistently, and there are now different

functions for rendering single items vs. many items, making the

single-item rendering reusable. Additionally, the answer manager is

documented in a more eye-friendly and modular way.

  1. … 1 more file in changeset.
improve comments

provide an analysis method for cleared input (callable for swas via method blank-inputs)

  1. … 1 more file in changeset.
provide means to show submissions of students per test item

  1. … 1 more file in changeset.
added exam-overview

  1. … 4 more files in changeset.
make grading checke configurable via URL, make calculations more robust

CVS: ----------------------------------------------------------------------

  1. … 1 more file in changeset.
added policy for supporting view of revisons, used more detailed message key values for supporting rounding by points or revisions

  1. … 3 more files in changeset.
fix typo

decativate prevention of multiple tabs for exam protocol (and maybe other listings)

fix last commit (many thanks to Thomas Renner)

make actions changed from the background state-safe

added support for pagination buttons, visited buttons and flagged buttons

  1. … 6 more files in changeset.
make question manager configurable

fix regression test which was broken due to last change (move of links to answer panel)

  1. … 1 more file in changeset.
moved answer status into answer_panel (similar to downstream),

made sensitivity of inspect links automatically updating (like downstream)

made templating easier and refactored code

  1. … 2 more files in changeset.
Plug the proctoring-display include to the inclass-exam via a web-callable method

  1. … 1 more file in changeset.
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

added functionality to prevent opening the same exam in multiple tabs

  1. … 1 more file in changeset.
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.

  1. … 1 more file in changeset.
don't use numbers as object names for actions; don't show "1" for navigation, when there is a single question

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