Learning level can always be changed by the tutor

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

There is a need for a possibility that the tutor can set the status Passed, although the setting is set that the status is determined by the object.

2 Conceptual Summary

If the learning progress mode is set in such a way that only the tutor can set the status, no status is adopted from the object. If the tutor wants to change the status, the learning progress mode must be changed first. When the tutor has finished editing the learning progress manually, he must not forget to change the learning progress mode to "Status is set based on objects...". Otherwise it can happen that course participants complete the course but the status is not set.

3 User Interface Modifications

3.1 List of Affected Views

If the checkmark is set at "passed" and save is clicked, the learning progress should be changed immediately, regardless of the setting of the learning progress mode.

In this case, only the checkbox "Disable learning progress" would be sufficient or the rights are given to the tutor in the course.

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

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: mgerber Manuel Gerber
  
• Maintainer: Stefan Meyer
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

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