Difference between revisions of "Competencies"

Jump to: navigation, search
(New page: ==Introduction== The outcomes and scales architecture introduced in Moodle 1.9 provide a solid foundation for competency management, particularly of course outcomes. To model the range of ...)
 
 
(142 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Introduction==
 
The outcomes and scales architecture introduced in Moodle 1.9 provide a solid foundation for competency management, particularly of course outcomes. To model the range of different types of competency frameworks used by organisations, Moodle 2.0's competency architecture needs to allow:
 
  
* Competencies to be independent of courses and activities. Some examples:
+
{{obsolete}}
** Completing three specific course fulfills one competency
+
<div class="alert alert-info">
** Providing electronic example (e.g., a scanned computer science diploma fulfills A-D competencies)
+
Competencies has been added as a feature for the 3.1 release. This specification is very old - a more up-to-date specification can be found here: https://docs.moodle.org/dev/index.php?title=Competency_Based_Education
  
* Competencies to be organised into frameworks on a site level in unlimited ways, allowing:
+
For the API see: https://docs.moodle.org/dev/index.php?title=Competency_API
** Taxonomies (i.e., categories)
 
** Folksonomies (i.e., tags)
 
** Hybrids of both
 
  
* Multiple competency frameworks in the same Moodle instance
+
Thankyou to the people who contributed to this earlier specification. This page has now been removed to prevent confusion with the newer specification/feature. You can view older versions of this page in the history.
* Competencies to rely on outcome types
+
</div>
* Competencies to be gained by various methods (or types of evidence):
+
 
** Achieving one or more outcomes in one or more courses
+
[[Category:Project]]
** Completing one or more courses (i.e., when completing course A, course B, and course C)
 
** Completing one or more activities (i.e., when completing activity x in course A and activity y in course B, and activity z in course C)
 
** Exceeding the aggregate result threshold for a question category within an evaluation (i.e., feedback using quiz)
 
** Exceeding the aggregate result threshold for a question category within an assessment (i.e., quiz)
 
** Electronic file (a diploma, external certification)
 
*** User file area (via the file API)
 
*** External repository (via the portfolio API)
 
*** ePortfolio (via the repository API)
 
** Comment / testimony / reference
 
* Competencies to be attached to standard/custom user profile fields (e.g., 'level' - "First year student", or 'major' - "English")
 
* Competencies to be tied an individual user (either by user profile field or by drag and drop)
 
* Expected "evidence" and "competency proficiency levels" to be defined for links between standard/custom user profile field items and a competencies for each evidence type:
 
** Outcome level (i.e., scale value)
 
** A course's standard course completion criteria
 
** A course's standard course activity criteria
 
** Custom course completion criteria
 
** Custom activity completion criteria
 
** Aggregate result threshold for a question category
 
** Required electronic file
 
* Competencies to allow one or more types of evidence
 
* Custom metadata to be easily attached to competencies and standard/custom user profile fields items
 

Latest revision as of 08:11, 3 May 2016


Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable.

Competencies has been added as a feature for the 3.1 release. This specification is very old - a more up-to-date specification can be found here: https://docs.moodle.org/dev/index.php?title=Competency_Based_Education

For the API see: https://docs.moodle.org/dev/index.php?title=Competency_API

Thankyou to the people who contributed to this earlier specification. This page has now been removed to prevent confusion with the newer specification/feature. You can view older versions of this page in the history.