• last updated 5 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
re-introduce check for empty string to avoid an empty list entry in the spec

fix typo

- added anchor title for configuration button

- reduced verbosity

Improved configurability of inclass exam

- added modal window for showing all configuration options

- depending on the state of an exam (whether students have stated

working on the exam or not) different options can be

altered. E.g. the grading scheme can be adjusted at any time, since

it is not visible to students prior to exam review.

- improved configurability of form-fields:

. new feature: fc_repository for shared definitions

(can be reused in the same configuration on multiple occasions)

. when form-constraints are defined with an empty short-spec,

the system tries to look this up from the fc_repository.

- extended answer manager:

. new method: student_submissions_exist

. renamed methods

. "student_submissions" -> "submissions"

(since result my include as well test run results)

. "get_answers" -> "get_answer_attributes"

to better distinguish from "submissions"

- base "merge_constraints" on dicts

- prefer forwarder over instance variable for referring

the question manager(QM)

- extended Message keys with "Configuration"

- added missing German translations in message keys

- bump version to 5.10.1d17

use same idom for loading named forms as on other places

improve styling in exam protocol

Added support for user-supplied grading schemes

Grading schemes provide a means to map achieved percentages to a numeric grade.

In the current versions, a fixed number of 5 grades is supported.

A grading scheme consists of a grounding scheme and grading boundaries.

- A grading scheme can be selected at exam definition time

- Lecturers can define their own grading schemes and reuse these between exams

- Available grounding schemes:

* no rounding (recommended for small exams, e.g. 5 minutes or 2 points)

* by percent (the calculated percentages are rounded to the provided number of digits)

* by points (the calculated points are rounded to the provided number of digits)

- The grounding precision can be defined by the user (e.g. to 2 digits)

- The grading boundaries represent percentages boundaries necessary for a certain grade

- When selecting no grading scheme, no grading information is provided in the exam protocol

(just percentages)

More changes:

- allow grading also, when student has not submitted the exam

- added percentage information in the grading-box (esp. useful for composite questions)

- renamed predefined grading schemes to more neutral terms

- provide easy-to-type names for question-manager, answer-manager and form-loader

- new utility for more robust list-comparions

- defined validating form-field type for grading boundaries

    • -5
    • +18
    ./catalog/xowf.de_DE.ISO-8859-1.xml
    • -3
    • +17
    ./catalog/xowf.en_US.ISO-8859-1.xml
file edit-grading-scheme.wf was initially added on branch oacs-5-10.

    • -0
    • +0
    ./lib/edit-grading-scheme.wf
file grading-procs.tcl was initially added on branch oacs-5-10.

    • -0
    • +0
    ./tcl/grading-procs.tcl
file edit-grading-scheme.wf.page was initially added on branch oacs-5-10.

    • -0
    • +0
    ./resources/prototypes/edit-grading-scheme.wf.page
reduce verbosity

support grading passed in via property

improve spelling

Document public api

added input validation for points in modal dialog

assessment-index.page: replace "delete" button by "archive" button for exams.

To reduce the likelihood that someone accidentally deletes a fresh exam,

the "delete" button was replaced for exam-instances by an "archive" button.

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

  1. … 3 more files in changeset.
Added option to download results on an exam

The download is in form of an CSV file and consists of one line per

question/sub-question and including comments. This feature can be

selected after the exam was evaluated once via running the

exam-protocol.

Limit display of questions in exam-protocol to max-items, when this is specified

Offer just edit-interaction elements as test items; prefer simple title

    • -2
    • +2
    ./www/prototypes/assessment-index.page
revert change, since it is not clear from the description what it was for

Rename domNode argument to dom_node

tDOM defines a ::domNode command in the global namespace, which might potentially conflict with the argument name. Also, in certain configurations the api-doc machinery will treat the argument as a command usage and try to enforce e.g. the naming convention on it in acs-tcl.naming__proc_naming automated test.

added required argument to calc_grade (many thanks to Markus Moser for noting)

Bump version number after spelling changes in message keys

improve robustness when processing legacy questions

Added support for manual grading and individual feedback

- Lecturers can provide points and feedback comments

directly via exam protocol

- Grading is allowed, when student has submitted the exam or

the exam is not open

- Composite questions are graded at the sub-question level

- Manual grading have a higher priority than automatic grades

- Manual grading/comments can be undone by clearingfield

(showing then missing points, automated computed points, ...)

- Grades and comments are included in the exam review for

students ("Einsicht").

- Grading interactions are implemented as AJAX calls

(no need for redrawing the exam protocol, immediate feedback)

remove quotes to avoid nested list interpretation

Add basic doc to public api

check if minutes are set

fix default values for short-text items