Feature Wiki

Information about planned and released features

Tabs

Storing Specific Values for Competence Levels

1 Initial Problem

Users are assigned with competence levels. These have no discrete sub-entities. This does not allow for chart drawing. 

2 Conceptual Summary

  • We would like the result of a competentce measurement or appraisal to allow for greater precision.
  • We want to indicate "how much" of a competence level was mastered.
  • This "progress made" within a competence level provides a "data point" on that very competence level.
  • This data point would allow for drawing line charts in the future. 

3 User Interface Modifications

3.1 List of Affected Views

This feature does not have its own screen. However, the data is required for the feature Timebased Competence Chart. The data must be able to be output from the sources (test & survey) and processed by the recipient (competence management).

3.2 User Interface Details

no.

3.3 New User Interface Concepts

no.

4 Technical Information

Killing, Alexander [alex], 7 May 2019: Internally the levels of a competence will be "mapped" to positive values starting from 1 for the lowest level, e.g.

1: little competence
2: medium competence
3: high competence.

Consuming components may now not only provide a fullfilled level (e.g. 2 medium) but additionally the percentage of fullfillment of the next level (e.g. 0.9). This will internally result in a value of 2.9.

5 Contact

6 Funding

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

7 Discussion

Killing, Alexander [alex], 7 May 2019: I support this request, but I am unsure if the general goal (to calculate with these values) is conceptually sound. In German: Dies scheint eine "Verhältnisskalierte Daten" zu erzeugen, wo eigentlich keine sind!?

JourFixe, ILIAS [jourfixe], 07 MAY 2019 : We highly appreciate the suggestion to store the competence record values to re-use them in future features as suggested above. Accepted for 6.0.

JourFixe, ILIAS [jourfixe], 03 FEB 2020 : We still like this suggestion and re-schedule this feature for 7. This feature has no impact on the user interface. ILIAS only stores the results and make them available for external re-use. In addition, we ask for a streamlining of the threshold handling (currently different in survey and test). It does not make sense to have a percentage threshold that goes over 100 (see also Mantis 22458).

8 Implementation

Nothing currently changed on the UI level. ilBasicSkill::writeUserSkillLevelStatus got an additional parameter float $a_next_level_fulfilment = 0.0.

Test Cases

Test cases completed at 27 OCT 2020 by Zenzen, Enrico [ezenzen]

  • The specific values are currently not visualized anywhere. The test cases for this feature will be submitted as soon as the values are displayed.

Approval

Approved at 2020-11-03 by Falkenstein, Rob [rob]

Last edited: 23. Nov 2020, 14:14, Killing, Alexander [alex]