Feature Wiki

Information about planned and released features

Tabs

Export Preconditions set between Objects in Courses and Groups

Is part of Improving Exports of Course and Groups

1 Initial Problem

In education time and ressources are critical factors. Preparing attractive adaptive courses with preconditions requires a lot of work. Disseminating adaptive course templates is an efficient approach. 

  • Offering simple workflows like importing and reusing templates of adaptive courses is very important to ensure uptake of adaptability.  
  • Adaptive course adress educational problems like a heterogenous knowledge distribution in the student body because of non-traditional students.

Currently the XML-Export omits important parts of a course or group: Preconditions set between objects in the course or group are linked to the original objects once exported. Someone needs to re-set all of them. 

The re-working of an exported/imported course or group leads to frustation and "not using" adaptive courses.  

Following an Precondition Export (workflow example) e.g. to adress different types of learners (AS IT IS NOW).  If you want to structure your learning content according to different paths, groups or contents, it is essential to use preconditions. Following steps and problems will demonstrate the creation and actual workaround:

  • There is an introducing content page, it links to a Test object A. 
  • User works through Test A. He/ She is fail or passed.   [by ending test, forewarded by link to main-view Container-object course/group/"bin" ]
    • Upon failing she is presented with Test B. 
    • Upon passing she will presented with  Content C/Test C.    
  • Test B may carry more preconditions.  [...]

The educator wants to give his course-structure to a colleague:

  • He / She exports the course and downloads his XML-file (.zip)
  • He / She imports the XML and opens the imported course. Now he / she has to edit: all preconditions are lost, he/she must compare existing preconditions and re-configure learning progress, and the preconditions itself. This maybe very well a few dozens of entries.

2 Conceptual Summary

Preconditions of an object within the course or group must be exported. (SM)

3 User Interface Modifications

3.1 List of Affected Views

No changes.

3.2 User Interface Details

No changes.

3.3 New User Interface Concepts

No changes.

3.4 Accessibility Implications

No changes.

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 Privacy

No changes.

6 Security

No changes.

7 Contact

8 Funding

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

9 Discussion

10 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}

Privacy

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

Approval

Approved at {date} by {user}.

Last edited: 29. Apr 2024, 09:05, Tödt, Alexandra [atoedt]