Superiors manually create competence records

1 Initial Problem

Superiors are one of the most relevant sources of appraisal for team members. However this important estimate of competence development cannot be recorded in ILIAS.

2 Conceptual Summary

Superiors can create a competence record for a team member in Organisations. This record is marked as "Performance Rating" and gets a separate entry from "Appraisal".

• "Performance Ratings" pay into Competence Profile Fulfillment as every other type of formation. If another type of formation leads to the fulfillment of the profile and the performance rating rates the user lower the profile remains fulfilled.

2.1 More Specific Types of Formations

The type of formation "Appraisal" encompasses competence records from 360° surveys, manually created by course tutors and automatically assigned upon the completion of a ressource. It makes no sense to pile on even more meaning thus the types of formations should henceforth be split up into more categories. Existing data remains as it is and is not migrated. New data will be categoried as follows:

Labels were chosen thus existing an newly created competence records can be displayed alongside each other without getting confused.

3 User Interface Modifications

3.1 List of Affected Views

• Organisation > Staff List > New Action

3.2 User Interface Details

• Rate Performance sollte, wie die Selbst-Evaluation, sowohl in den Profilen als auch in der Liste der Kompetenzen möglich sein.

• Vorgesetztenname als "Quellobjekt" oberhalb auflisten.
• Dopplung Reiter "Competence Profiles" und "Profiles"?

3.3 New User Interface Concepts

None

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

Competence Service: See https://github.com/ILIAS-eLearning/ILIAS/blob/trunk/Services/Skill/PRIVACY.md

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: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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}.