Feature Wiki

Information about planned and released features

Tabs

Errortext: mark single characters

Page Overview

[Hide]

1 Initial Problem

It is not possible to check for single characters (including space characters) as errors. It is also not possible to use rtl-languages or code as errortext.

2 Conceptual Summary

I would suggest to add the following options / workflows:
  1. Choose if words (default setting) or single characters should be selected by the learner in the frontend
  2. Allow space characters to be included as errors if needed (but keep the default settings for faster question editing)
    • If space characters are to be included decide between a) additional selection (words/characters + space) and b) spaces as only form of error
  3. Add options concerning the form of text input and change the text processing accordingly:
    1. left to right text as default
    2. right to left text
    3. code input
To have single characters and space characters as possible errors is useful for a variety of language test scenarios for example to test punctuation skills. To allow for the full scale of usage scenarios the integration of rtl-languages as well as code would be highly appreciated. Both require additional changes of the question type function though: rtl-language output has to be sorted accordingly; code input has to be escaped and it would require a solution for the # and []-characters that are used to mark the errors (since they could also be part of the code itself)

3 User Interface Modifications

3.1 List of Affected Views

Backend (question settings)
  1. setting: "type of error" as radio buttons with two options "words" (default selection) and "single characters"
  2. conditional setting: "Allow space characters as errors". If selected with subsettings "space characters additionally" and "only space characters"
    • help-block text: "Please select if space characters can be selected additionally to words/characters or if space characters are the only possible selection"
  3. dropdown "type of text input"
    • left to right language (default seting)
    • right to left language
    • code
Backend (errortext analysis, answer options)
The analysis and further handling of marked characters or words has to be adjusted according to the settings above

Frontend
The display of and ability to select words/characters has to be adjusted according to the settings.

3.2 User Interface Details

preview errortext settings ui

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.
  • ...

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}
  • {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.

Last edited: 18. Jul 2017, 16:20, Grießer, Melanie [mgriesser]