Feature Wiki

Information about planned and released features

Tabs

Automated Feedback on Learner Activities

Page Overview

[Hide]

1 Initial Problem

We would like to offer an automated system feedback in ILIAS to motivate or help the student in critical learning-situations. This requirement comes from the optes project but might be interesting for all projects with self-studying phases.

Some situations were a feedback could be helpful are listed here:

The student:

  • regularly works with ILIAS
  • does not spend more time on the system
  • breaks off the ILIAS course
  • does not do the entrance test
  • makes only little learning progress
  • makes great learning progress
  • makes many mistakes
  • makes no mistakes for a long time
  • does not participate repeatedly in the sessions of the study group or (online) consultation hours
  • does not use the ePortfolio
  • regularly uses the ePortfolio
  •  works remarkably long without interruption
  • still has mathematical deficits at the beginning of his studies

2 Conceptual Summary

Some examples for an automatic feedback from the system:

Trigger / Event

Automatically given feedback

When content has been edited for more than three days in a week*

Note in which the behavior is highlighted positively

If there was no content processing within two weeks*

Note, if you have any problems, contact a learning companion or also transferable learning modules

If no login has taken place for five weeks*

to ask for reason: first give them short answer alternatives to choose (no desire, no time, other expectations, etc.) and ask if he is ready for more detailed feedback

If a week after registration / reminder the test has not yet been made*

Reminder and indication that the test allows a more targeted preparation and saves time

If less than 10% positive change occurred within one week in the skill matrix*

Note on learning support and / or test.

If there was more than 30% positive change within one week in the skill matrix*

Note in which the learning progress is appreciated.

If over 50% of the tasks were answered incorrectly*

Note that the error can be used positively and information on how to handle frustration. Also a reference to learning support and help offers.

When 10 or 20 consecutive tasks have been answered correctly*

Note in which the success is appreciated.

If no participation was made on two consecutive dates for online sessions*

note/Email in which the reasons were asked and reference to help offers or interdisciplinary learning modules for time management etc.

If no entry was made after two weeks of editing the optes content*

Note with information on the benefits and benefits of ePortfolio work.

When five ePortfolio contributions have been made*

Note in which the behavior is highlighted positively

If no interruption took place after two hours of processing

Note on importance of breaks for the learning process

* Thresholds not yet finalized

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

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

  • Author of the Request: Victoria Marquardt, Christian Schmidt, Universität Hamburg, optes-Projekt TP8
  • Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
  • Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

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: 2. Jun 2018, 09:42, Kunkel, Matthias [mkunkel]