Feature Wiki

Information about planned and released features

Tabs

Reducing Options for ‘Learning Objectives Driven Courses’

Page Overview

[Hide]

repercussions for presentation need to be mocked

Transfer Learning Objective Course to KS Component

Auch weg:

  • nur Fragen anzeigen die richtig waren
  • Schnittstelle zum Test entfällt
  • nur noch ganze Objekte als Lerninhalt zuordnen 

Es bleibt

  • Schnittstelle Kurssettings
  • Schnitstelle Lernfortschritt
  • Schnittstelle Inhaltspräsentation
  • unklar PE für Lernzieldeko? 

1 Initial Problem

Th LOC sounded better in a grant application than it held up in everyday use: most teachers evaded its complexity. After the optes project ended the use evaporated. Three or four organisations were identified who still use optes LOC.

The Learning Objective Drive is the most important source of bugs for the course. It heeps complexity on the components course and tests.

There are many options for configuring the LOC. These options should be reduced,

  • to reduce bug load, 
  • to reduce test load, 
  • to reduce complexity for better maintainbility
  • and to allow for easier use.

There are two main sources of the over-complexity:

  1. the distinction of placement and achievement test to allow for before-after comparison
  2. assigning questions of one and the same test to different learning objectives / comprehensive tests over all learning objectives.

To allow for in depth discussion and organiations to re-work their existing courses this was not pushed for ILIAS 12. There is pain in maintaining the LOC This needs to be adressed in ILIAS 13 or abandonned.

screenshot of settings

2 Conceptual Summary

The didactic core of the LOC is 

  • Supporting a Test-Out-Strategy / homogenizing a cohorts level of knowledge
  • Connecting learning objectives with content and connectng learning objectives with tests
  1. Comprehensive Tests covering all objectives are removed, since they specifically add complexity. 
  2. Initial Tests are offered as Placement Tests, only. 

Settings to be abandonned

  • The „Initial Test is Start Object“ is abandoned. To reach the effect preconditions, page editor can be used.
  • Initial tests as Achievement tests will no longer be offered.
  • Before-after comparison is abandoned.

Migration of presentation

  • Learning objectives accordions remain. One or more objects can be assigned to a learning objective. If parts of an object (questions, chapters) were assigned, now the entire object is assigned.
  • Objects will no longer vanish after completion.
  • One or more objects is selected to trigger the learning progress of the learning objective.

Migrationof settings

  • Learning Objective Courses with „comprehensive test covering all objectives“ need to be re-configured manually. There will be no automatic migration.
  • A university made a dry-run migration to understand how this would play out for them and they managed to migrate in ok time and acceptable results.
  • With ILIAS 13 the settings will no longer be offered.
  • Existing courses will be reverted to „unconfigured“.

3 User Interface Modifications

3.1 List of Affected Views

  • Course > Learning Objectives > Settings
  • Course > Learning Objectives > Learning Objectives 
  • Course > Learning Objectives > Initial Test (abandonned) 
  • Course > Learning Objectives > Final Test 
  • Course > Learning Objectives > Start Object (abandonned)

3.2 User Interface Details

Settings

Kann das einfach mit dem recht "Edit Settings" laufen? Dann  kan das ganze Formular weg.

Learning Objektives
Form for Capturing Learning Objetive Data

3.3 New User Interface Concepts

No new user interface concepts are suggested. 

3.4 Accessibility Implications

No forseeable accessibility issues.

4 Additional Information

4.1 Involved Authorities

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

4.4 Security

No forseeable security issues.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Tödt, Alexandra [atoedt]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

Feature Workshops were held on July, 6th 2026, August 4th 2026 and September 29th 2026

We discussed the options

  1. Exactly one test / other object per learning objective triggers the learning progress. There is not longer before-after comparison. The display of improvement was replaced by plugins in all known cases.
  2. Only Placement Test per objective and Final Test per objective. The placement test triggers suggested objects. Final test triggers learning progress. Before-after comparison would be possible.
  3. The comprehensive tests over all objectives are considered a non-option, because they are the source of complexity. This is the main obstable to maintainabilityassigning questions of the same test to different learning objectives: Which test run is triggering= Which learning objective has which result? 
    • In the one higher education institution that attened and checked found only one LOC in which a comprehesive intial test was used.
  4. Abandon Learning Objective Driven Course altogether: creating individual courses with individual tests. 

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.

Full Screen

Last edited: 2. Oct 2026, 15:46, Tödt, Alexandra [atoedt]