Improvement of global Self Evaluation

This feature is based on the BR 0035316: Self-evaluation is not possible in competence profiles in courses/groups. The described issue will be conceptualized and discussed in the following in order to get the best possible solution.

1 Initial Problem

If the "Hide competence target without self-assessment" setting is enabled in the administration, users will not see competence targets until they have completed a self-assessment.

Self-assessment can be done through a survey or in the global view "Achievement " Competenies " Assigend Profiles" via the Actions menu. Since competence profiles in courses and groups only refer to the context of the course or group, no global self-assessment can be made here. The actions menu is not displayed.

However, if there is no survey in the course or group and the setting is still activated, users will not be able to view their competence targets and edit the competence profile (see screenshot).

2 Conceptual Summary

2.1 Option 1

Within courses and groups, only the competence entries generated by a repository object within the course or group are displayed. "Global" self-assessments do not have a repository object as their origin, are given a special role, and are also displayed in courses and groups.

Competence profiles in courses and groups are given an action menu so that self-assessment can be done here as well.

2.2 Option 2

The ability to self-assess to a competency/"global" self-assessment is removed. Self-assessments can now only be made via surveys. 

3 User Interface Modifications

3.1 List of Affected Views

• Achievements » Competences » Assigned Competence Profiles
• Courses and Groups » Competences » Show

3.2 User Interface Details

None.

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

None.

4 Technical Information

None.

5 Privacy

None.

6 Security

None.

7 Contact

• Author of the Request: Zenzen, Enrico [ezenzen]
• Maintainer: Famula, Thomas [tfamula]
• 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}

Approval

Approved at {date} by {user}.