Open Elscha opened 11 months ago
Points from our meeting on the Skill Levels:
We need a property in the Skill to hold the ID that matches the skill levels for the same skill. It can be the name of the skill (In case we guarantee the name matching during the creation of the skills), or it can be a unique ID.
We use that ID to retrieve all levels for the same skill. For example, we use ID= 2 from the Skill A (Level 1) to get all skill levels with ID= 2.
A skill level can learned by a combination of different skill levels as children. For example, Skill A (Level 3) can learned by learning Skill B (level 1), Skill C (level 3), Skill D (level 3), and Skill D (level 2).
A discussion point,
@kschmid
Actual Situation
Skills
have an attributelevel
, which is currently ignored by the algorithm.Target Situation
The level should implicitly refer to a taxonomy, which the user has into his mind, e.g., Bloom taxonomy. With this in mind, the user may create multiple skills with the same name, but with different levels. Higher levels include automatically all lower levels of the same name (w.r.t. the
Repository
that defines theSkills
).Purpose
User may define the "same" Skills (same name) multiple times, on different Levels and may assign them to separate
LearningUnits
. For instance:for
,while
,do while
,for each
Skills
such as LOOPS (REMEMBER), LOOPS (UNDERSTAND), ... but they may be created if necessary.Modifications to the Algorithm
The algorithm must check if a
Skill
at least on the specified level is fulfilled. If theSkill
was already learned on a higher level then specified, the user does not need to learn also the lower level again.