Review Mode for Learning Progress in all Objects

1 Requirements

Imagine the following scenario (reported in http://www.ilias.de/mantis/view.php?id=10756):

• Course with object, e.g., SCORM module.
• Course learning progress (LP) is determined automatically by the SCORM module.
• "Passed" status of course is set automatically by LP.
• Course member opens Course and SCORM -> Course LP is "In Progress".
• Course administrator sets member passed -> Course LP is still "In Progress".

• In my understanding, when the course administrator sets the member "passed", the member's LP should be synchronized to "Completed" because otherwise:
  • The course will not appear in LP overviews as "Completed" for the member although in fact he/she doesn't have to do any more in the course.
  • The "Date of Last Status Change" will not be the date when the "Passed" status was achieved although in fact this is what in such a case the trainer or HR staff will be interested in.
    
• However, currently this only works for the course LP mode "Manual By Tutor".The problem why this hasn't been implemented is that a "Completed" status of the course would be overwritten again by any status change of a Course object.

• To make this useful, ILIAS would need some kind of (global) setting: "Once an object is completed, this cannot be changed back again".This would work in a way similar to the 'Review' mode in SCORM modules (s. http://www.ilias.de/docu/goto_docu_pg_46550_3363.html).Maybe also the proposals from the the article Extended review mode management for SCORM 2004 could be taken into account.

2 Status

• Scheduled for: Not scheduled yet
• Funding: Required
• Development: Feature is to be developed by tbd

3 Additional Information

• If you want to know more about this feature, its implementation or funding, please contact: suittenpointner (at) qualitus (dot) de

4 Discussion

Zenzen, Enrico [ezenzen], 24 AUG 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

5 Implementation

...