Help:Knowledge unit

Definition

A knowledge unit is a coherent and documented collection of the knowledge components of a learning topic that always occur together in learning or competence description.

Concept

In the TALQ project a structure for competence description (the sectoral layer) is developed where Skills, Knowledge and Autonomy / attitude are underlaying to the competences. While the Skills are mostly unique, and described as part of the competence description, the Knowledge and Autonomy / attitude descriptions are often reusable.

Therefore they are described in separate units that can be linked to the competence.

This has several advantages, the knowledge units can be:

• reused in the competences
• used to write a syllabus, where the inverse relation with competences gives context to the “theory”
• related to each other based on “prerequisite knowledge” , in order to include fundamental knowledge that is not directly related to a competence
• structured in “knowledge fields” clustering knowledge in logical groups.
• enriched with teaching tips, learning materials, evaluation methods, sources, …
• used to develop concrete learning materials and exercises.

Example

Five steps to reduce risk

Size or volume of a knowledge unit

The size or volume, in other words how much knowledge is contained in a unit, needs to be considered carefully to ensure the reusability of the blocks and to fulfill the requirements described above. This is not an abstract science, but needs an approximation method. To support the development, some questions can guide you to critically look at the results.

• Do the knowledge components always occur together in relation to a single competence?
• Do the knowledge components fit in a syllabus structure?
• Are they belonging to the same knowledge field, the same topic?
• Can the knowledge unit be described in a single concept that is concrete and understandable, in other words, can it have a clear title?
• Does the unit has a “teachable size”, does it limits to one topic?
• Do units fit together, are there no overlaps or gaps?

Properties used

Below, all the properties used to describe a knowledge unit are described, including remarks on syntax, links to value lists and required values. (Properties with an * are essential for the functioning of the system)

Header

Label or Title*

The label or title represents the knowledge unit. It should be clear to the readers

* Type: Monolingual 
* Syntax: Nouns 

Description

The description is a short sentence that defines the title, it helps the readers to understand the exact meaning.

* Type: Monolingual
* Syntax: One or two sentences (limited to 240 characters)

Alternative label

Can be used to give alternative names or ways of writing for searching purposes.

* Type: Monolingual, multiple values possible
* Syntax: Nouns 

Technical properties

Instance of*

Technical field to represent the type of information in the Item

* Type: Item
* Value: “Knowledge” (Q4)

Part of value list*

Technical field to make the Item part of a value list.

* Type: Item
* Value: “Knowledge value list” (Q40)

General information

Scope note

Can be used to clarify boundaries of a unit.

* Syntax: starts with “includes” or “excludes”
* Type: Monolingual

Knowledge detail

The knowledge components of the unit Avoid to merge multiple components in one entry

For readability, the level of knowledge is only defined if it os not "Understand", which inplies that is is used in function of the competence. If the level is lower, a sentence can start with "basiscs of".

* Type: Monolingual
* Syntax: Nouns with specifications, Multiple values possible

Level

Qualifier of Knowledge detail

Defines the level of knowledge expected. If no level is provided, it is expected to be "Understand", which inplies that is is used in function of the competence.

* type:item
* value list

Example

Qualifier of Knowledge detail

presents examples of a knowledge detail to clarify the bounderies.

* Type: Monolingual
* Syntax: Nouns with specifications, Multiple values possible

Evaluation criteria

* Type: Monolingual
* Syntax: Verb with specifications, Multiple values possible

Structuring information

Knowledge field*

* Type: Item
* Value list: Knowledge field value list (Q16)

Unique identifier

Orders the knowledge units in a field Good practice is to use multiples of 10, to be able to insert units later.

* Type: String
* Syntax: numeric value (two didgits)

Prerequisite knowledge

Refers to other knowledge units that are needed to understand / teach this unit.

* Type: Item
* Value list:  Knowledge value list (Q40)

Underlaying to competences

(inverse property label of knowledge (P29))

Shows what competences use this knowledge

* type: Inverse property label

Assessment

Evaluation methods

Defines appropriate evaluation methods

* Type: Item
* value list:

Training

Teaching tips

Describes teachnig tips from colleagues

* Type: Monolingual
* Syntax: One or two sentences (limited to 240 characters), Multiple values possible

Learning materials

Refers to existing teaching materials

* Type:
* Syntax:

References

References

a reference to a paper document used to develop this profile

* Type: string
* value: text, reference spcification

Reference document

a link to a document uploaded in the database (a document can be pdf, picture, etc.)

* Type: external identifier
* Value: name of the uploaded document

Source URL

a link to a source used to create this item

* Type: URL
* Value: URL of the source
* Syntax: include the full URL, including the prefix (HTTP etc.)

Owner*

Technical field to represent the owner of the Item

* Type: Item
* Value list: Owner (Q435)

Bulk uploads

For large and existing sets of information, bulk uploads by means of Excell files is a faster way to enter the information.

You can download an example file to adapt here. The excell file integrates 3 levels of information:

• the knowledge field (Green)
• the knowledge unit (Black)
• the knowledge components (Blue)

Some basic rules to make importing easier:

• use a new line for each type of information. fields, units and components should never occur on the same line.
• the writing of elements you refer to has to be identical, use the "=" function if needed. If an item already exists in the database, copy the Qnumber