Target Ranges for Competence Profiles

Back to Overview Page

1 Initial Problem

Competence profiles can only be assigned to a single level. Competence profiles often define a minimum and a maximum level. The target value is therefore not a single level but a target profile range.

2 Conceptual Summary

Profiles should allow a target range of a minimum required level and a maximum required level.

To realize this, there are some arrangements to be made:

• In Competence Management, it must be possible to assign several levels of the same competence to a competence profile.

  If a value is skipped, i.e. only the checkboxes of the 2nd and 4th level are activated, the checkbox of the 3rd level is automatically activated. A "gapy" range is not possible.

• On the personal desktop, users are shown several levels (range) of the same Competence as Target Levels under Achievements>>Competences>>Assigned Profiles.
  
  If resources are assigned to competence levels, users will be given the following hint below the target level.

  • You need to improve this competence. The following resources provide learning material aligned to your target competence level.
  If a target range has been created for the competence, the resources that have to be processed in order to achieve the minimum target are displayed.

• In screens offering a gap analysis (by now: competence results in tests and surveys) ILIAS has to treat every competence requirement as fulfilled that is within the defined range.

3 User Interface Modifications

3.1 List of Affected Views

Administration >> Competence Management

• 'Assigned Competence Levels'-Tab in Competence Profiles
• 'Assign Level'-Workflow in Competence Profiles

• Achievements > Competences >> Assigned Profiles

• svy/svy_results/svy_eval_competences
• skill// (in tests via button "Show Competence Results"!)

3.2 User Interface Details

Administration >> Competence Management

Personal Desktop >> Achievements >> Competences >> Assigned Profiles

Results in Tests and Surveys

3.3 New User Interface Concepts

none.

4 Technical Information

5 Contact

• Author of the Request: Bromberger, Norbert [bromberger], Zenzen, Enrico [ezenzen]
• Maintainer: Famula, Thomas [tfamula]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

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

• Handelkompetent
• Qualitus

7 Discussion

Glaubitz, Marko [mglaubitz], 2018-10-14: We would be very happy if this feature was to be implemented, because we face the same challenge.

Killing, Alexander [alex], 10 July 2019: I support the general idea.

• We need to clarify how existing profiles should be migrated. Would they all contain a one level range or should the levels be extended to the top?
• How shoud the spider web be tackled?

JourFixe, ILIAS [jourfixe], 29 JUL 2019 : We highly appreciate this suggestion and schedule the feature for 6.0.

Kunkel, Matthias [mkunkel], 20 JAN 2020 : We still like to have this feature and re-schedule it for ILIAS 7.

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