MoodleDocs - User contributions [en]

Overview

2011-03-30T20:21:11Z

Jonathannewman: /* The key players */

A lot of people ask how the development of Moodle operates. This page should give you a working overview that should help in understanding a lot of other developer documentation.

==The key players==

;Martin Dougiamas: Martin is the lead developer of Moodle. Generally he tries to facilitate democracy and meritocracy but occasionally has to make executive decisions on things.

;Moodle HQ: The mostly-Australian team of developers who are directly funded by the Moodle project to work full-time on core developments. Developers include Martin Dougiamas (moodler), Eloy Lafuente (stronk7), Petr Skoda (skodak), Mathieu Petit-Clair (scyrma), Nicolas Connault, Donsheng Cai, Jérôme Mouneyrac, Helen Foster (wildgirl) and occasionally Jamie Pratt (jamiesensei). Pictures of everyone can be found here: http://moodle.com/hq/.

;Catalyst: The team of developers working for Moodle clients via Catalyst Ltd in New Zealand, resulting in a lot of core development. Core developers include Matt Clarkson, Peter Bulmer, Aaron Barnes, Jonathan Harker, Francois Marier, Piers Harding, Dan Marsden, and Simon Coggins. The legacy of former Catalyst core developers includes Martin Langhoff, Penny Leach (mjollnir), Donal McMullan, Luke Hudson, and Jonathan Newman.

;Open University: The team of developers working on Moodle implementations at Open University in the UK. Developers include Tim Hunt, Sam Marshall, Nick Freear, Thanh Le and Jenny Gray.

There are many other people contributing to Moodle in many ways, these are just the main groups currently working on core development. See [http://moodle.org/cvs the full list of people with write access to Moodle]

==Moodle versions==

Moodle major releases occur roughly 6 months or more apart, on no fixed schedule. Each major release increments the version number by 0.1. Minor releases (no new features, just fixes) on each stable branch can occur at any time, whenever enough bug fixes have been made to justify them. The full details can be seen in the [[Release notes]].

The current development version is always on the trunk of CVS (i.e. HEAD), while stable branches are split off for every major version (e.g. MOODLE_18_STABLE).

==How we develop the Roadmap==

The [[Roadmap]] lists the features being developed for the next version. This list is derived mostly from the issues with large numbers of votes in the Moodle [[Tracker]], so please vote for what you want! Other influences include general discussion and feature requests at Moodle Moots and in the Moodle forums.

==Release cycles==

Generally a cycle works like this:
;Rapid Development:Long period of several months adding code to the HEAD version of Moodle. At the same time, all fixes that don't involve database changes or radical core changes are backported to the last two or three stable branches.
;Head Freeze:At some point Martin Dougiamas declares a freeze on new work for a while to stabilise the core. All database changes and all major core changes need to have explicit permission from Martin. All developers should be wrapping up work on new features and fixing bugs in new code. This period may be 1 or 2 weeks.
;Beta period:Once the HEAD version becomes fairly stable, Martin declares a BETA version and this point is marked on HEAD as MOODLE_XX_BETA (e.g. MOODLE_19_BETA). Install packages are generated daily from the latest version for wider testing and feedback via the tracker. The freeze continues, testing and bug fixing continues. This testing period may be anywhere from 2 to 6 weeks.
;Major release:When the core code passes all the testing we can throw at it, the MOODLE_XX_BETA flag is moved up to mark the current point as a branch point, and a new stable branch named MOODLE_XX_STABLE is created. Packages are created, and the release is announced.

Then it all starts again!

Moodle HQ is committed to supporting the two most recent stable versions. That is, at any point in time:

* We work on the next version but don't provide production support
* We support the most recent stable version with constant bug fixes
* We support the previous recent stable version, but mostly only serious bugs and security issues
* We don't support any older versions

==Quality control==

Issue tracking is an important part of a continuous quality control process. It involves reporting of problems (bugs), ideas for improvement and new features. Unlike most proprietary software programs, Moodle issue reporting and tracking information is open to everyone. Moodle's issue tracking system is called the [[Tracker]].

All Moodle users are encouraged to be active participants when it comes to testing. Anyone with a Tracker user account can create, view, comment on, vote, and watch bugs.

===Testers===

Testers are responsible for verifying the accuracy of changes made by developers. Testers choose which bugs they want to test, according to their area of expertise, and use the QA Assignee field to identify themselves as the tester.

If the bug passes testing, then the tester changes the status of the bug from 'resolved' to 'closed'. If the bug fails testing, or if the fix is incomplete, then the tester reopens the bug.

A Moodle release will be deemed ready when all "blocker" bugs fixed for a particular version have been closed.

===Weekly Code Review===

Every Tuesday (all time zones), testers and core developers stop developing new code and focus on reviewing changes made to the stable releases in the past week (both at a code level and an interface level).

This process is intended to improve the quality of the latest download packages and to catch any new bugs that might have been created while fixing old ones.

The latest stable packages are tagged as MOODLE_19_WEEKLY (these tags are updated after the weekly review is over).

See [[Weekly Code Review]] for more details.

==Coding Standards==

The full [[Coding|Coding Guide]] gives all the details, but here are some of the major things your code needs to hit:

===XMLDB===

All our database schema are created using the XML ''install.php'' files, and upgraded using database-agnostic commands in ''upgrade.php'' files. Any version of any part of Moodle can be smoothly upgraded to any later version in this fashion (on a wide variety of supported databases).

===XHTML===

All output from Moodle must be compliant with XHTML Strict 1.0, and also compliant with all common accessibility guidelines (such as W3C WAG).

===Forms===

All forms should use the Moodleforms library if possible. This results in a standardised accessible output that designers can style consistently and well.

===Parameters===

All parameters should be checked using require_param() and optional_param() which will safely clean all incoming data for use and provide defaults to your code. Moodleforms will do this automatically for you.

===Output===

All textual output should be output using the format_text or format_string functions. This will ensure that text is cleaned and filtered appropriately.

===Access===

All permissions-checking should use the "Access library" to check against current capabilities. The most common function you'll use is has_capability() which checks the permissions of the current user in an efficient way to see if they are allowed to do this specific operation. Do not check for specific roles in your code (e.g. teacher/student) as that will make your code useless.

===Other core libraries===

The other major libraries you should get familiar with are:
# ''moodlelib.php'' - a useful bin of all kinds of useful functions and constants
# ''datalib.php'' - all the functions you need to interface with the database
# ''weblib.php'' - all the functions you'll need to create and output XHTML

===Plugins===

Moodle has about 22 different types of plugins last time I counted. Plugins can generally be self-contained in a single directory containing scripts, images, stylesheets and language files all in one package that can be dropped into the Moodle script directory in the right place. After that the admin just needs to visit the admin page to install them.

Most plugins work in one of two ways, they either provide a ''lib.php'' filled with common functions and some scripts with standard names, or they subclass a proto-plugin and override a few method functions to achieve their goals.

The best way to learn is to pick an example from the core code that is similar to what you want to do and start playing with it. There are also some template plugins to help get you started.

==Development processes==
Not all Moodle development happens exactly like this, but it really should. :-)

===Major Development===
A major development is a significant piece of new code, adding new functionality to Moodle.

====Make sure it's a good idea====
Firstly, you should look at the roadmap and talk the idea over with some Moodle developers to see if someone else is working on it already and whether others think the general idea has merit. Use the forums if you wish, or whatever means you have. If you have a client, you may need to work with them to work out what they REALLY want (perhaps it isn't actually a new development for Moodle).

====Create a specification in Moodle Docs====
Start a new page in the Moodle Docs wiki, similar to [[Grades]]. Your page should outline the database table design, the GUI, the hows and whys etc. Include as much detail as you need (even mock screenshots) but try to keep it clear and logically organised.

====Seek and absorb community feedback====
Post about the new page in the appropriate forums on [http://moodle.org/course/view.php?id=5 Using Moodle] to help draw attention to it and to stimulate some discussion around your development. The more feedback you have the better, especially if it includes a wide variety of users (developers, teachers, students etc).

Edit your page in response to the feedback, or invite people to do so themselves. try to evolve the specification into something that all users are happy with. Sometimes it's worth working harder to find the "best" way to do something without adding Yet Another Option.

====Set up tasks in the Moodle Tracker====
Once the specification has settled down, it's time to start work. Create a new task for yourself in the Moodle Tracker, and add sub-tasks in roughly chronological order for all the different parts of the job. This not only helps you keep track of where you are, but allows the community to "watch you" develop and to help you where they can. If there are different people working on different parts, you can assign subtasks to different people. It's really very convenient to use once you get the hang of it.

====Use CVS and link commits to Tracker====
If possible, develop the code in an open code repository (and preferably Moodle CVS!). If you need CVS write access to the core code or the contrib repository, use the "Apply for CVS Access" tab on http://moodle.org/cvs. Gaining access to the main core code is quite difficult, but we are generally very free with access to the contrib area.

Every time you make a commit, include a detailed message about the new code and always include a Moodle Tracker bug number (e.g. MDL-7777). This will ensure that the Moodle Tracker is able to detect your commit and attach it to the relevant bug report.

====Comment on milestones in forums and tracker====
If you hit a major milestone, or want testers to try something, feel free to post about it in the relevant forum on Using Moodle. The more people you can attract to look and try out your code the better it will be, trust me.

====Respond to bug reports====
Of course you need to listen to your users (well, most of them :-)). Encourage people to file bugs, and fix them. If you need help setting up a project category in the Tracker contact support@moodle.com. This will ensure that all your bugs are easy to find and to track.

===Minor Development===

For smaller modules, fixes, improvements and other issues.

====Create a new issue in the tracker====

You should definitely create an issue in the tracker to describe your development and to act as a focus point for all discussion. You can reference the bug number from forum discussions and in commit messages etc. This way everyone can easily find out exactly what they are talking about.

====Attach a patch====

If you have some code, please attach it to the tracker issue, or if it's on your own site then link to it from the tracker issue. Don't attach code in the Moodle forums ... it will "rot" quickly there and just clogs up moodle.org with useless old code.

====Promote the patch====

By all means draw attention to your work in the Moodle forums (mentioning the bug number) or email developers directly to help make them aware of it. You can also add developers as "watchers" to the tracker issue if you want, this means they will get email for every change on the issue.

==See also==

* [[Finding your way into the Moodle code]]
* [[Working with the Community]]
* [[Guidelines for contributed code]]

[[Category:Overview]]
[[Category:Quality Assurance|Overview]]
[[Category:Processes|Overview]]

[[ru:Development:Краткий обзор]]

Course completion

2009-08-24T03:47:00Z

Jonathannewman: Data structures: shortened table names course_completion_criteria_completions and course_completion_aggregation_methods to meet the minimum table length requirements

{{Moodle 2.0}}This is a SPECIFICATION for a feature in Moodle 2.0 that is still under development

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''': MDL-2631 Course credits and tracking of student's completion
* '''DISCUSSION''': [http://moodle.org/mod/forum/discuss.php?d=126016 http://moodle.org/mod/forum/discuss.php?d=126016]
* '''COMMENTS''': [[Development_talk:Course_completion]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]], [[Aaron Barnes]] and others

=Overview=
We need to flag when the "student" has finished a course. :-)

We need to allow several types of criteria to determine how a "student" can complete a course:
* '''Manual self completion''': A "student" can mark her/himself complete a course.
* '''Manual completion by''': An "admin", "teacher", "tutor", etc can mark a student complete for a course.
* '''Activity completion''': A "student" completes an activity, building on [https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] developed for 2.0 by Sam Marshall from OU.
* '''Course grade''': A "student" meets or exceeds a passing grade in the course.
* '''Date''': After a specified date all "students" are marked as completed in a course.
* '''Duration after enrolment''': After a specified about of time after enrolment (e.g., 12 weeks), a "student" is automatically marked as complete in a course.
* '''Unenrol''': After being unenroled, a "student" is marked complete for the course. Useful for external enrolment plugins.

We need to record when and how a "student" meets each criteria in a course.

We need to regularly aggregate the results for the criteria, measure progress, and check to see if a "student" has completed a course.

We need to show:
* A "student" the necessary criteria to complete a course
* A "student" how s/he is progressing in a course along the necessary criteria
* A "teacher" how his/her students are progressing in a course and which students have completed it

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable completion tracking" setting (found in the Site Administration block's Advanced features / optional subsystems settings page) for activity completion. We need to change the setting's name and add another setting for course completion.

'''Proposed changes:'''
* Rename the setting "Enable activity completion tracking" (the setting will continue to allow activity completion to be enabled in all courses)
* Create a new setting named "Enable course completion tracking" (the setting will allow course completion to be enabled in all courses)

==Course settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides a fieldset (named "Student progress") which contains a setting (named "Completion tracking") which enables/disables activity completion in a course. We need to rename the setting to describe activity completion and add a setting to enable course completion.

"Enable completion tracking" setting (found in the Site Administration block's Advanced features / optional subsystems settings page) for activity completion.

'''Proposed changes:'''
* Rename the setting "Completion tracking" to "Activity completion tracking" (the setting will continue to make activity completion features available in the courses)
* Create a new setting named "Course completion tracking" (the setting will make course completion features available in the course)

==Course completion settings==
When course completion is enabled in a course (see above), a menu item labeled "Completion" will appear in the course Administration block on the main course page. When a user clicks on the "Completion" link, the course completion admin page will display the criteria described below and in the mockup also below:

[[Image:Edit_course_completion_settings.png|thumb|600px|Edit course completion settings]]

===Criteria enabling===
We need to allow criteria to be enabled.

We need some rules about enabled criteria in a course:
* Each criteria (e.g., "Manual self completion", "Manual completion by", etc) can be enabled
* By default, all criteria are not enabled

===Criteria aggregation===
We need to define overall aggregation methods for the criteria type. We also need to a consistent set of aggregation methods for criteria types which have more than one possible option to determine an individual user's course completion:
* "Manual completion by" // more than one role can be enabled to determine if a student has completed the course
* "Activity completed" // more than one activity completion can be selected to determine if a student has completed the course

Aggregation methods:

{| border="1" cellpadding="2" cellspacing="0"
|'''Method'''
|'''Required to complete the criteria type'''
|'''Example'''
|'''Info'''

|-
|'''All'''
|All of the enabled child criteria must be completed
|Not applicable
|

|-
|'''Any'''
|Any one (1) of the enabled child criteria must be completed
|Not applicable
|

|-
|'''Fraction'''
|A fraction of the enabled child criteria must be completed
|0.25,0.5,0.9
|

|-
|'''Units'''
|A specified number of the enabled child criteria must be completed
|2,3,4
|A unit of 1 is equivalent to 'any'. A unit equal to the number of enabled child criteria is equivalent to 'all'.
|}

===Criteria types===
====Manual self-completion====
'''Action:'''
* A "student" can manually indicate that s/he has completed a course via the course's [https://docs.moodle.org/en/Development:Course_completion#Block Completion progress block].
'''Tracked:'''
* The day/time when the "student" marked him/herself complete.

====Manual completion by====
'''Action:'''
* A user assigned to the role in the course will see a checkbox in the [https://docs.moodle.org/en/Development:Course_completion#Report Completion progress report], which will allow him/her to manually "Mark complete" each applicable student enrolled in the course.

'''Tracked:'''
* The roleid of the user who marked the "student" complete.
* The userid of the user who marked the "student" complete.
* The day/time when the user marked the "student" as complete in the course.

'''Notes:'''
# The Completion progress report will respect:
#* '''Separate groups:''' A "teacher" will only be able to see and mark complete students in her/his group(s) if separate groups is enabled.
#* '''Role assignments on the USER-level context:''' A "Tutor" or "Mentor" will only be able to see and mark complete users assigned to him/her.
# The criteria can be met only once by the role:
#* If more than one user is assigned to the role and has the capability of marking the user complete
#* After a "student" has been marked complete one time by a user in the role, the [https://docs.moodle.org/en/Development:Course_completion#Report Completion progress report] will not provide a checkbox in the "Mark complete" column when viewed by any user in the role in the course.
# We really be relying on role capabilities and permissions for this.

====Activities completed====
'''Action:'''
* A "student" will meet the criteria when completing the specified activity, per the activity's 'Activity Completion' settings.

'''Tracked:'''
* The cmid, module type, and activity/resource name for each activity.
* The day/time when the criteria was detected as complete.

'''Note:'''
# The list of activities/resources will contain:
#* Each activity/resource in the course with "Completion tracking" enabled within the activity/resource.
#* The type of each activity followed by the activity name (i.e., "[mod name] - [activity/resource name]"). See the mockup on this page (or for a basic example: "Quiz - Derivatives").
# If "Activity completion" is not enabled for the site, the "Activities completed" field set will not appear on the page.
# If "Activity completion" is enabled for the site and not enabled for the course, the "Activities completed" field set will appear and it will only contain this message:
#:''"Activity completion must be enabled for this course."''
# If "Activity completion" is enabled for the site and course, and there are no activities in the course, the "Activities completed" field set will appear and it will only contain this message:
#:''"Currently, there are no activities in this course"''
# If "Activity completion" is enabled for the site and course, and there are activities but none have activity completion enabled, the "Activities completed" field set will appear and it will only contain this message:
#:''"Currently, none of the activities in this course have defined activity completion settings."''

====Course grade====
'''Action:'''
* A "student" will meet the criteria when earning a total course grade above the passing grade.

'''Tracked:'''
* The day/time when the user's course grade was evaluated as having exceeded the passing grade.

'''Note:'''
* The passing grade can also be updated via the course's "Grade to pass" setting found in the Grader report's edit page for the top level category for the course.
* Once a student has completed the course, both the "Passing grade" setting on the course page and the "Grade to pass" setting in the top level category for the course will be locked. A message about locking will appear on the settings page for the top level category for the course.

====Date====
'''Action:'''
* A "student" enroled in the course will automatically meet the criteria after a specified date.

'''Tracked:'''
* The day/time when specified day was evaluated as having passed.

====Duration after enrolment====
'''Action:'''
* A "student" will meet the criteria after the specified number of days after his/her enrolment.

'''Tracked:'''
* The day/time when the "student" marked him/herself complete.

====Unenrolment====
'''Action:'''
* A "student" will meet the criteria when being unenroled from the course.

'''Tracked:'''
* The day/time when the "student" was unenroled from the course.

===Notifications===
====Enable====
If enabled, a "student" will receive notification when s/he has completed the course via the completion criteria.

====Notify====
Users assigned to each selected role in the course will receive notification when each "student" completes the course.

===Locking===
When the first student has completed the course, the course completion criteria settings will be locked. The course settings can be unlocked (via an "Unlock course completion options" button), however a warning message will be displayed stating that unlocking the settings requires deleting all prior course completion data for the course. Once the completion data is deleted, the settings become unlocked (i.e., un-greyed out).

This is consistent with activity completion in 2.0, in which activity completion settings are locked when a user first completes an activity. Activity completion settings can be unlocked after all completion activity is deleted.

==Activity settings==
If activity completion is enabled and activity completion is a criteria for course completion, then all activity completion settings will be locked once a student has completed the course. In this case, unlocking an activity's completion settings will require deleting both the activity's completion data and the course's completion data.

If an activity is being tracked for course completion, we should add a warning/confirmation screen when an "admin" attempts to delete it. The message should say, "[Activity name] is currently a criteria for course completion. Are you sure you want to delete it?" [Delete anyway] / [Cancel]. If the "admin" confirms, the activity will be deleted however completion data for users who completed it will still remain tracked.

Should the activity completion data remain?
Should the course completion data be re-aggregated?

=Data structures=
[[Image:Course_completion_data_model.png|thumb|400px|Course completion data model]]

===course===
The course table will require the following new fields. 'enablecompletion' will now be used for activity and course completion:

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''completionnotify'''
|int(1)
|
|Notify users when they complete this course

|}

===course_completion_aggr_meth===
This new table will be populated with the aggregation method for "Overall criteria", "Manual completion by", and "Activities completed".

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the course completion aggregation relates to

|-
|'''criteriatype'''
|int(20)
|null
|The criteria type's integer constant ('role', 'activity') or null if 'overall' course aggregation.

|-
|'''method'''
|int(1)
|1
|'1'='all', '2'='any', '3'='fraction', '4'='unit'.
|-

|'''value'''
|number(10)
|null
|null for 'all' and 'any', 0..1 for 'fraction', int > 0 for 'unit'
|}

===course_completion_criteria===
This new table will be populated with each criteria in each course for course completion:

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the course completion criteria relates to

|-
|'''itemname''' (not implemented)
|varchar(100)
|null
|The name of the item (e.g. "Mark yourself complete", "Teacher marks you complete", "[Activity name]", "[postenrol] days after enrolment", "Official Date: [date]". Used for all item types except unenrol.

|-
|'''criteriatype'''
|int(20)
|
|The criteria type's integer constant ('self', 'role', 'mod', 'grade', 'enrolperiod', 'date', 'postenrol').

|-
|'''module'''
|varchar(100)
|null
|The name of the module (e.g., 'scorm', 'quiz', 'feedback'). Used only if criteriatype='mod'.

|-
|'''moduleinstance'''
|int(10)
|null
|The id of the activity/resource module or role. Used only if criteriatype='mod'.

|-
|'''enrolperiod'''
|int(10)
|null
|The number of seconds after enrolment. Used only if criteriatype='enrolperiod'.

|-
|'''date'''
|int(10)
|null
|The timestamp of the date for course completion. Used only if criteriatype='date'.

|-
|'''gradepass'''
|number(10)
|null
|The course grade required to complete this criteria. Used only if criteriatype='grade'.

|-
|'''role'''
|int(10)
|null
|The role id that can mark 'student's as complete in the course. Used only if criteriatype='role'.

|-
|'''lock''' (currently unused)
|int(10)
|null
|Date this criteria was locked
|}

===course_completion_crit_compl===
This new table will be populated with records for each user as they complete each course completion criteria.

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user who has completed the course

|-
|'''course'''
|int(10)
|
|The id of the completed course

|-
|'''criteriaid'''
|int(10)
|
|The id of the completion criteria this references

|-
|'''gradefinal'''
|number(10)
|null
|The final grade for the course (if referenced criteria type='grade').

|-
|'''unenroled'''
|int(10)
|null
|Timestamp when the user was unenroled (if referenced criteria type='unenrol').

|-
|'''deleted''' (currently unused)
|int(1)
|null
|The course was deleted

|-
|'''timecompleted'''
|int(10)
|null (should be notnull)
|Timestamp when the user completed the criteria
|}

===course_completion_notify===
This new table will be populated with the roles which should be notified for this course

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the condition applies to

|-
|'''role'''
|int(10)
|
|The id of the role that should be sent a notification when a course has been completed

|-
|'''message'''
|text
|
|HTML formatted message to be sent to the user assigned to the role.

|-
|'''timesent'''
|int(10)
|
|Timestamp of when the notification was sent

|}

===course_completions===
This new table will be populated with a record for a user when s/he meets course completion criteria selected/enabled for a course.

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user who has completed the course

|-
|'''course'''
|int(10)
|
|The id of the completed course

|-
|'''deleted''' (currently unused)
|int(1)
|null
|The course was deleted

|-
|'''timenotified'''
|int(10)
|null
|Timestamp when the user was notified

|-
|'''timeenroled'''
|int(10)
|
|Timestamp when the user enroled in the course

|-
|'''timecompleted'''
|int(10)
|null (should be notnull)
|Timestamp when the user completed the course

|}

=Evaluating completion=
Since the gradebook aggregation is performed via cron, it makes sense that course completion is also evaluated by cron.

This creates an issue in which the progress block will not instantly not show course completion after the necessary criteria has been met by a "student". However, this can be solved by adding some instructional text to say "may take a few minutes to update".

=Role capabilities=
{| border="1" cellpadding="2" cellspacing="0"
|'''Feature'''
|'''Description'''
|'''Capability'''

|-
|Progress block
|Mark self-complete in progress block
|block/progress:markselfcomplete

|-
|Progress report
|View course progress report
|coursereport/progress:view

|-
|Progress report
|Mark users complete in course progress report
|coursereport/progress:markcomplete

|}

=Course reporting=
==Completion progress report==
[[Image:Completion_report.png|thumb|600px|Course completion progress report]]

[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides a "Completion progress report". The report can be found via on "Reports" menu item link in the course Administration block and when "Completion tracking" is enabled for the site and course.

The report shows:
* A column for each of the activities/resources in the course with "Completion tracking" enabled"
* A row for each user enroled in the course
* The completion status for each activity

'''Proposed changes:'''
* Include in the report all enabled criteria for course completion (e.g., "Manual self completion", "Manual completion by", as well as the activities etc)
* Each user's status for completion of each criteria, indicated by a status icon
* Allow the completion admin page to determine which activities are shown in the report
* Allow the list of users to be sortable, searchable, and filterable (by group, groupings, and/or user profile fields).
* Allow user profile fields (standard and custom) can be added/removed as columns in the list.
* When rolling over the each icon, additional details (including the completion date) will display.

See the mockup to the right with all course completion criteria appearing (i.e., all criteria types have been enabled in a course).

As described further above, display rules for separate groups will apply. If separate groups is enabled for the course, a "teacher" will only see students and completion data for users in the group(s) that she/he is assigned to.

Options for exporting completion data to CSV, ODF or Excel will be available. Completion dates will be included in the export.

A column labeled "Mark complete" will appear containing a checkbox for each student if the user viewing the report is assigned to a role that is allowed to manually indicate that the students have completed the course.

Not shown in the mockup, however we should display the specified values under the applicable heading in the report for each of the following feilds:
* Period after enrolment
* Passing grade
* Date (for completion)

==Gradebook==
# If "Passing grade" is enabled as a criteria for course completion, a grader should have the option of seeing completion status (i.e., "complete" / "not complete") as a column in the grader report.
# If a user assigned to a role that is enabled for "Manual completion by", the user should have the option of manually indicating which students have completed the course, a "Mark complete" column will appear to the right of the "Course total" column with a checkbox for each student who has not yet completed the course.

We should also provide an option to show course completion status in gradebook exports. Field options will include:
* Completion status (e.g., "Complete", "Not complete")
* Completion date

==Completion progress block==
[[Image:Course_completion_progress_block.png|thumb|190px|Course completion progress block]]

If completion is enabled for the site and a course, a completion block will be available to be added to the course.

The block will allow a "student" to see:
* The completion criteria for completing the course
* His/her status for completion of each criteria (similar to the Completion progress report)
* His/her overall completion status for the course (complete / not complete)

If all of the enabled criteria are required, the introduction text should say:
:''"All of the criteria below needed"''

If any of the enabled criteria are required, the introduction text should say:
:''"Any of the criteria below needed"''

If the current user can self complete the course, the block will provide an "I've completed this course" button (if the user has not already marked him/herself complete).

Activity completion criteria/status (if enabled for course completion) should be included in the block. See [http://tracker.moodle.org/browse/MDL-16466 MDL-16466] ("Activities on the course page do not convey to student that completion is expected or available for the activity").

==User (course) profile==
Activity and course completion criteria/status data should appear in a user's "Outline report" and "Complete report" in the user profile area, which is being reworked for 2.0 separately from this spec.

=Site reporting=

==User (site) profile==
[[Image:Course_completion_user_profile_activity.png|thumb|400px|Mockup of the user profile page with Course completion report]]

Activity and course completion criteria/status data should appear in a user's profile area.

It would make sense for courses to be grouped by:
* Courses in progress
* Courses completed
* Courses not yet started

For each course, the required criteria and status should appear.

==My Moodle==
Activity and course completion criteria/status data should appear with the course and course activity listings. My Moodle is being reworked for 2.0 separately from this spec.

=Cron=
A cron function will check the criteria and update the course_completion_completions table as necessary. Here's a breakdown of the tasks for each criteria, and will need to be optimised for performance and scalability across all courses:

* '''Manual self completion:''' Cron not needed, performed directly from the Completion progress block.
* '''Manual completion by:''' Cron not needed, performed directly via the Completion progress report.
* '''Course grade:''' Compare the course grade to the passing grade.
* '''Unenrol:''' Compare course_completion->unenroled to role_assignments->timeend for the "student" role in the course.
* '''Date:''' Compare the current date to the specified date.
* '''Duration after enrolment:''' Compare the current date to the role_assignments->timestart + the specified period after enrolment.
* '''Activity completion:''' Evaluate the necessary records in the course_modules_completion table.
* '''Course completion:''' Aggregate the necessary fields in course_completion table, updating the timecompleted field with the current timestamp if the user has met the necessary criteria.
* '''Notifications:''' Send out them out to the user (if enabled) and to users in the selected role.

=Backup and restore=
* The new completion fields in the course table will be included in the backup.
* Entries in the course_completion_items, course_completion_aggregation_methods, and course_completion_notify tables for the course should also be included in the backup.
* When user data is included in a course backup, the backup will also include records in the course_completion_completions table for the course.

Competencies

2009-08-21T01:35:50Z

Jonathannewman: User interface: "Competencies summary" user profile page - added link descriptions

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

=="Add/edit competencies" admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

=="Add / edit a competency" admin page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add or edit a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=="Add / edit competency depth" admin page==
[[Image:Competencies_depth_add.png|thumb|400px|Mockup of the Add competency depth admin page]]

An "admin" will be use this page to add / edit a new competency depth, with the following settings:
* Depth full name
* Depth short name
* Description

Also, the depth level will be displayed

=="Add / edit competency evidence" admin page==
[[Image:Competencies_evidence_add_edit.png|thumb|400px|Mockup of the Add / edit competency evidence admin page with Example 1 competencies]]

An "admin" will be use this page to view / add / edit evidence for a competency. The top of the page should display the existing general data for the competency, the number of "students" who have achieved the competency, and a table showing data and functionality for each evidence item:
* The name of the competency evidence (which links to the evidence item in context, e.g., the course if course completion is specified, etc)
* The type of evidence
* The activity (if the evidence is an activity outcome or activity grade)
* The weight of the evidence
* Options to edit or remove the evidence
* The number of "students" who have achieved the evidence

An "Add new competency evidence" button should link to the "Add new competency evidence" admin page.

=="Competencies summary" user profile page==

[[Image:Competencies_user_profile_activity.png|thumb|400px|Mockup of user profile page with Example 1 competencies]]

An "student" or a user with permission to view a student's competencies will be able to view the proficiency status for each competency as a table with the following columns:
* Competency depth(s)
* Evidence items
* Proficiency
* Scale

Each competency name should link to a pop-up containing the competency details (full name, description, aggregation method, scale, and meta data) and list of evidence items.

Each number of competency items should link to a pop-up containing a list of evidence items.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Allow competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-21T01:24:25Z

Jonathannewman: User interface: added "Add new competency evidence" button to the "Add / edit competency evidence" admin page

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

=="Add/edit competencies" admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

=="Add / edit a competency" admin page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add or edit a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=="Add / edit competency depth" admin page==
[[Image:Competencies_depth_add.png|thumb|400px|Mockup of the Add competency depth admin page]]

An "admin" will be use this page to add / edit a new competency depth, with the following settings:
* Depth full name
* Depth short name
* Description

Also, the depth level will be displayed

=="Add / edit competency evidence" admin page==
[[Image:Competencies_evidence_add_edit.png|thumb|400px|Mockup of the Add / edit competency evidence admin page with Example 1 competencies]]

An "admin" will be use this page to view / add / edit evidence for a competency. The top of the page should display the existing general data for the competency, the number of "students" who have achieved the competency, and a table showing data and functionality for each evidence item:
* The name of the competency evidence (which links to the evidence item in context, e.g., the course if course completion is specified, etc)
* The type of evidence
* The activity (if the evidence is an activity outcome or activity grade)
* The weight of the evidence
* Options to edit or remove the evidence
* The number of "students" who have achieved the evidence

An "Add new competency evidence" button should link to the "Add new competency evidence" admin page.

=="Competencies summary" user profile page==

[[Image:Competencies_user_profile_activity.png|thumb|400px|Mockup of user profile page with Example 1 competencies]]

An "student" or a user with permission to view a student's competencies will be able to view the proficiency status for each competency as a table with the following columns:
* Competency depth(s)
* Evidence items
* Proficiency
* Scale

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Allow competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-21T01:06:59Z

Jonathannewman: Ideas for the future: removed two ideas related to IDP and course completion

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

=="Add/edit competencies" admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

=="Add / edit a competency" admin page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add or edit a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=="Add / edit competency depth" admin page==
[[Image:Competencies_depth_add.png|thumb|400px|Mockup of the Add competency depth admin page]]

An "admin" will be use this page to add / edit a new competency depth, with the following settings:
* Depth full name
* Depth short name
* Description

Also, the depth level will be displayed

=="Add / edit competency evidence" admin page==
[[Image:Competencies_evidence_add_edit.png|thumb|400px|Mockup of the Add / edit competency evidence admin page with Example 1 competencies]]

An "admin" will be use this page to view / add / edit evidence for a competency. The top of the page should display the existing general data for the competency, the number of "students" who have achieved the competency, and a table showing data and functionality for each evidence item:
* The name of the competency evidence (which links to the evidence item in context, e.g., the course if course completion is specified, etc)
* The type of evidence
* The activity (if the evidence is an activity outcome or activity grade)
* The weight of the evidence
* Options to edit or remove the evidence
* The number of "students" who have achieved the evidence

=="Competencies summary" user profile page==

[[Image:Competencies_user_profile_activity.png|thumb|400px|Mockup of user profile page with Example 1 competencies]]

An "student" or a user with permission to view a student's competencies will be able to view the proficiency status for each competency as a table with the following columns:
* Competency depth(s)
* Evidence items
* Proficiency
* Scale

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Allow competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-21T00:49:12Z

Jonathannewman: User interface: Added "Competencies summary" user profile page mockup

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

=="Add/edit competencies" admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

=="Add / edit a competency" admin page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add or edit a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=="Add / edit competency depth" admin page==
[[Image:Competencies_depth_add.png|thumb|400px|Mockup of the Add competency depth admin page]]

An "admin" will be use this page to add / edit a new competency depth, with the following settings:
* Depth full name
* Depth short name
* Description

Also, the depth level will be displayed

=="Add / edit competency evidence" admin page==
[[Image:Competencies_evidence_add_edit.png|thumb|400px|Mockup of the Add / edit competency evidence admin page with Example 1 competencies]]

An "admin" will be use this page to view / add / edit evidence for a competency. The top of the page should display the existing general data for the competency, the number of "students" who have achieved the competency, and a table showing data and functionality for each evidence item:
* The name of the competency evidence (which links to the evidence item in context, e.g., the course if course completion is specified, etc)
* The type of evidence
* The activity (if the evidence is an activity outcome or activity grade)
* The weight of the evidence
* Options to edit or remove the evidence
* The number of "students" who have achieved the evidence

=="Competencies summary" user profile page==

[[Image:Competencies_user_profile_activity.png|thumb|400px|Mockup of user profile page with Example 1 competencies]]

An "student" or a user with permission to view a student's competencies will be able to view the proficiency status for each competency as a table with the following columns:
* Competency depth(s)
* Evidence items
* Proficiency
* Scale

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-21T00:44:04Z

Jonathannewman: User interface: Normalised page titles

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

=="Add/edit competencies" admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

=="Add / edit a competency" admin page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add or edit a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=="Add / edit competency depth" admin page==
[[Image:Competencies_depth_add.png|thumb|400px|Mockup of the Add competency depth admin page]]

An "admin" will be use this page to add / edit a new competency depth, with the following settings:
* Depth full name
* Depth short name
* Description

Also, the depth level will be displayed

=="Add / edit competency evidence" admin page==
[[Image:Competencies_evidence_add_edit.png|thumb|400px|Mockup of the Add / edit competency evidence admin page with Example 1 competencies]]

An "admin" will be use this page to view / add / edit evidence for a competency. The top of the page should display the existing general data for the competency, the number of "students" who have achieved the competency, and a table showing data and functionality for each evidence item:
* The name of the competency evidence (which links to the evidence item in context, e.g., the course if course completion is specified, etc)
* The type of evidence
* The activity (if the evidence is an activity outcome or activity grade)
* The weight of the evidence
* Options to edit or remove the evidence
* The number of "students" who have achieved the evidence

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Course completion

2009-08-20T05:37:07Z

Jonathannewman: User (site) profile: added mock-up and additional spec details

{{Moodle 2.0}}This is a SPECIFICATION for a feature in Moodle 2.0 that is still under development

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''': MDL-2631 Course credits and tracking of student's completion
* '''DISCUSSION''': [http://moodle.org/mod/forum/discuss.php?d=126016 http://moodle.org/mod/forum/discuss.php?d=126016]
* '''COMMENTS''': [[Development_talk:Course_completion]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]], [[Aaron Barnes]] and others

=Overview=
We need to flag when the "student" has finished a course. :-)

We need to allow several types of criteria to determine how a "student" can complete a course:
* '''Manual self completion''': A "student" can mark her/himself complete a course.
* '''Manual completion by''': An "admin", "teacher", "tutor", etc can mark a student complete for a course.
* '''Activity completion''': A "student" completes an activity, building on [https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] developed for 2.0 by Sam Marshall from OU.
* '''Course grade''': A "student" meets or exceeds a passing grade in the course.
* '''Date''': After a specified date all "students" are marked as completed in a course.
* '''Duration after enrolment''': After a specified about of time after enrolment (e.g., 12 weeks), a "student" is automatically marked as complete in a course.
* '''Unenrol''': After being unenroled, a "student" is marked complete for the course. Useful for external enrolment plugins.

We need to record when and how a "student" meets each criteria in a course.

We need to regularly aggregate the results for the criteria, measure progress, and check to see if a "student" has completed a course.

We need to show:
* A "student" the necessary criteria to complete a course
* A "student" how s/he is progressing in a course along the necessary criteria
* A "teacher" how his/her students are progressing in a course and which students have completed it

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable completion tracking" setting (found in the Site Administration block's Advanced features / optional subsystems settings page) for activity completion. We need to change the setting's name and add another setting for course completion.

'''Proposed changes:'''
* Rename the setting "Enable activity completion tracking" (the setting will continue to allow activity completion to be enabled in all courses)
* Create a new setting named "Enable course completion tracking" (the setting will allow course completion to be enabled in all courses)

==Course settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides a fieldset (named "Student progress") which contains a setting (named "Completion tracking") which enables/disables activity completion in a course. We need to rename the setting to describe activity completion and add a setting to enable course completion.

"Enable completion tracking" setting (found in the Site Administration block's Advanced features / optional subsystems settings page) for activity completion.

'''Proposed changes:'''
* Rename the setting "Completion tracking" to "Activity completion tracking" (the setting will continue to make activity completion features available in the courses)
* Create a new setting named "Course completion tracking" (the setting will make course completion features available in the course)

==Course completion settings==
When course completion is enabled in a course (see above), a menu item labeled "Completion" will appear in the course Administration block on the main course page. When a user clicks on the "Completion" link, the course completion admin page will display the criteria described below and in the mockup also below:

[[Image:Edit_course_completion_settings.png|thumb|600px|Edit course completion settings]]

===Criteria enabling===
We need to allow criteria to be enabled.

We need some rules about enabled criteria in a course:
* Each criteria (e.g., "Manual self completion", "Manual completion by", etc) can be enabled
* By default, all criteria are not enabled

===Criteria aggregation===
We need to define overall aggregation methods for the criteria type. We also need to a consistent set of aggregation methods for criteria types which have more than one possible option to determine an individual user's course completion:
* "Manual completion by" // more than one role can be enabled to determine if a student has completed the course
* "Activity completed" // more than one activity completion can be selected to determine if a student has completed the course

Aggregation methods:

{| border="1" cellpadding="2" cellspacing="0"
|'''Method'''
|'''Required to complete the criteria type'''
|'''Example'''
|'''Info'''

|-
|'''All'''
|All of the enabled child criteria must be completed
|Not applicable
|

|-
|'''Any'''
|Any one (1) of the enabled child criteria must be completed
|Not applicable
|

|-
|'''Fraction'''
|A fraction of the enabled child criteria must be completed
|0.25,0.5,0.9
|

|-
|'''Units'''
|A specified number of the enabled child criteria must be completed
|2,3,4
|A unit of 1 is equivalent to 'any'. A unit equal to the number of enabled child criteria is equivalent to 'all'.
|}

===Criteria types===
====Manual self-completion====
'''Action:'''
* A "student" can manually indicate that s/he has completed a course via the course's [https://docs.moodle.org/en/Development:Course_completion#Block Completion progress block].
'''Tracked:'''
* The day/time when the "student" marked him/herself complete.

====Manual completion by====
'''Action:'''
* A user assigned to the role in the course will see a checkbox in the [https://docs.moodle.org/en/Development:Course_completion#Report Completion progress report], which will allow him/her to manually "Mark complete" each applicable student enrolled in the course.

'''Tracked:'''
* The roleid of the user who marked the "student" complete.
* The userid of the user who marked the "student" complete.
* The day/time when the user marked the "student" as complete in the course.

'''Notes:'''
# The Completion progress report will respect:
#* '''Separate groups:''' A "teacher" will only be able to see and mark complete students in her/his group(s) if separate groups is enabled.
#* '''Role assignments on the USER-level context:''' A "Tutor" or "Mentor" will only be able to see and mark complete users assigned to him/her.
# The criteria can be met only once by the role:
#* If more than one user is assigned to the role and has the capability of marking the user complete
#* After a "student" has been marked complete one time by a user in the role, the [https://docs.moodle.org/en/Development:Course_completion#Report Completion progress report] will not provide a checkbox in the "Mark complete" column when viewed by any user in the role in the course.
# We really be relying on role capabilities and permissions for this.

====Activities completed====
'''Action:'''
* A "student" will meet the criteria when completing the specified activity, per the activity's 'Activity Completion' settings.

'''Tracked:'''
* The cmid, module type, and activity/resource name for each activity.
* The day/time when the criteria was detected as complete.

'''Note:'''
# The list of activities/resources will contain:
#* Each activity/resource in the course with "Completion tracking" enabled within the activity/resource.
#* The type of each activity followed by the activity name (i.e., "[mod name] - [activity/resource name]"). See the mockup on this page (or for a basic example: "Quiz - Derivatives").
# If "Activity completion" is not enabled for the site, the "Activities completed" field set will not appear on the page.
# If "Activity completion" is enabled for the site and not enabled for the course, the "Activities completed" field set will appear and it will only contain this message:
#:''"Activity completion must be enabled for this course."''
# If "Activity completion" is enabled for the site and course, and there are no activities in the course, the "Activities completed" field set will appear and it will only contain this message:
#:''"Currently, there are no activities in this course"''
# If "Activity completion" is enabled for the site and course, and there are activities but none have activity completion enabled, the "Activities completed" field set will appear and it will only contain this message:
#:''"Currently, none of the activities in this course have defined activity completion settings."''

====Course grade====
'''Action:'''
* A "student" will meet the criteria when earning a total course grade above the passing grade.

'''Tracked:'''
* The day/time when the user's course grade was evaluated as having exceeded the passing grade.

'''Note:'''
* The passing grade can also be updated via the course's "Grade to pass" setting found in the Grader report's edit page for the top level category for the course.
* Once a student has completed the course, both the "Passing grade" setting on the course page and the "Grade to pass" setting in the top level category for the course will be locked. A message about locking will appear on the settings page for the top level category for the course.

====Date====
'''Action:'''
* A "student" enroled in the course will automatically meet the criteria after a specified date.

'''Tracked:'''
* The day/time when specified day was evaluated as having passed.

====Duration after enrolment====
'''Action:'''
* A "student" will meet the criteria after the specified number of days after his/her enrolment.

'''Tracked:'''
* The day/time when the "student" marked him/herself complete.

====Unenrolment====
'''Action:'''
* A "student" will meet the criteria when being unenroled from the course.

'''Tracked:'''
* The day/time when the "student" was unenroled from the course.

===Notifications===
====Enable====
If enabled, a "student" will receive notification when s/he has completed the course via the completion criteria.

====Notify====
Users assigned to each selected role in the course will receive notification when each "student" completes the course.

===Locking===
When the first student has completed the course, the course completion criteria settings will be locked. The course settings can be unlocked (via an "Unlock course completion options" button), however a warning message will be displayed stating that unlocking the settings requires deleting all prior course completion data for the course. Once the completion data is deleted, the settings become unlocked (i.e., un-greyed out).

This is consistent with activity completion in 2.0, in which activity completion settings are locked when a user first completes an activity. Activity completion settings can be unlocked after all completion activity is deleted.

==Activity settings==
If activity completion is enabled and activity completion is a criteria for course completion, then all activity completion settings will be locked once a student has completed the course. In this case, unlocking an activity's completion settings will require deleting both the activity's completion data and the course's completion data.

If an activity is being tracked for course completion, we should add a warning/confirmation screen when an "admin" attempts to delete it. The message should say, "[Activity name] is currently a criteria for course completion. Are you sure you want to delete it?" [Delete anyway] / [Cancel]. If the "admin" confirms, the activity will be deleted however completion data for users who completed it will still remain tracked.

Should the activity completion data remain?
Should the course completion data be re-aggregated?

=Data structures=
[[Image:Course_completion_data_model.png|thumb|400px|Course completion data model]]

===course===
The course table will require the following new fields. 'enablecompletion' will now be used for activity and course completion:

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''completionnotify'''
|int(1)
|
|Notify users when they complete this course

|}

===course_completion_aggregation_methods===
This new table will be populated with the aggregation method for "Overall criteria", "Manual completion by", and "Activities completed".

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the course completion aggregation relates to

|-
|'''criteriatype'''
|int(20)
|null
|The criteria type's integer constant ('role', 'activity') or null if 'overall' course aggregation.

|-
|'''method'''
|int(1)
|1
|'1'='all', '2'='any', '3'='fraction', '4'='unit'.
|-

|'''value'''
|number(10)
|null
|null for 'all' and 'any', 0..1 for 'fraction', int > 0 for 'unit'
|}

===course_completion_criteria===
This new table will be populated with each criteria in each course for course completion:

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the course completion criteria relates to

|-
|'''itemname''' (not implemented)
|varchar(100)
|null
|The name of the item (e.g. "Mark yourself complete", "Teacher marks you complete", "[Activity name]", "[postenrol] days after enrolment", "Official Date: [date]". Used for all item types except unenrol.

|-
|'''criteriatype'''
|int(20)
|
|The criteria type's integer constant ('self', 'role', 'mod', 'grade', 'enrolperiod', 'date', 'postenrol').

|-
|'''module'''
|varchar(100)
|null
|The name of the module (e.g., 'scorm', 'quiz', 'feedback'). Used only if criteriatype='mod'.

|-
|'''moduleinstance'''
|int(10)
|null
|The id of the activity/resource module or role. Used only if criteriatype='mod'.

|-
|'''enrolperiod'''
|int(10)
|null
|The number of seconds after enrolment. Used only if criteriatype='enrolperiod'.

|-
|'''date'''
|int(10)
|null
|The timestamp of the date for course completion. Used only if criteriatype='date'.

|-
|'''gradepass'''
|number(10)
|null
|The course grade required to complete this criteria. Used only if criteriatype='grade'.

|-
|'''role'''
|int(10)
|null
|The role id that can mark 'student's as complete in the course. Used only if criteriatype='role'.

|-
|'''lock''' (currently unused)
|int(10)
|null
|Date this criteria was locked
|}

===course_completion_criteria_completions===
This new table will be populated with records for each user as they complete each course completion criteria.

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user who has completed the course

|-
|'''course'''
|int(10)
|
|The id of the completed course

|-
|'''criteriaid'''
|int(10)
|
|The id of the completion criteria this references

|-
|'''gradefinal'''
|number(10)
|null
|The final grade for the course (if referenced criteria type='grade').

|-
|'''unenroled'''
|int(10)
|null
|Timestamp when the user was unenroled (if referenced criteria type='unenrol').

|-
|'''deleted''' (currently unused)
|int(1)
|null
|The course was deleted

|-
|'''timecompleted'''
|int(10)
|null (should be notnull)
|Timestamp when the user completed the criteria
|}

===course_completion_notify===
This new table will be populated with the roles which should be notified for this course

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the condition applies to

|-
|'''role'''
|int(10)
|
|The id of the role that should be sent a notification when a course has been completed

|-
|'''message'''
|text
|
|HTML formatted message to be sent to the user assigned to the role.

|-
|'''timesent'''
|int(10)
|
|Timestamp of when the notification was sent

|}

===course_completions===
This new table will be populated with a record for a user when s/he meets course completion criteria selected/enabled for a course.

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user who has completed the course

|-
|'''course'''
|int(10)
|
|The id of the completed course

|-
|'''deleted''' (currently unused)
|int(1)
|null
|The course was deleted

|-
|'''timenotified'''
|int(10)
|null
|Timestamp when the user was notified

|-
|'''timeenroled'''
|int(10)
|
|Timestamp when the user enroled in the course

|-
|'''timecompleted'''
|int(10)
|null (should be notnull)
|Timestamp when the user completed the course

|}

=Evaluating completion=
Since the gradebook aggregation is performed via cron, it makes sense that course completion is also evaluated by cron.

This creates an issue in which the progress block will not instantly not show course completion after the necessary criteria has been met by a "student". However, this can be solved by adding some instructional text to say "may take a few minutes to update".

=Role capabilities=
{| border="1" cellpadding="2" cellspacing="0"
|'''Feature'''
|'''Description'''
|'''Capability'''

|-
|Progress block
|Mark self-complete in progress block
|block/progress:markselfcomplete

|-
|Progress report
|View course progress report
|coursereport/progress:view

|-
|Progress report
|Mark users complete in course progress report
|coursereport/progress:markcomplete

|}

=Course reporting=
==Completion progress report==
[[Image:Completion_report.png|thumb|600px|Course completion progress report]]

[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides a "Completion progress report". The report can be found via on "Reports" menu item link in the course Administration block and when "Completion tracking" is enabled for the site and course.

The report shows:
* A column for each of the activities/resources in the course with "Completion tracking" enabled"
* A row for each user enroled in the course
* The completion status for each activity

'''Proposed changes:'''
* Include in the report all enabled criteria for course completion (e.g., "Manual self completion", "Manual completion by", as well as the activities etc)
* Each user's status for completion of each criteria, indicated by a status icon
* Allow the completion admin page to determine which activities are shown in the report
* Allow the list of users to be sortable, searchable, and filterable (by group, groupings, and/or user profile fields).
* Allow user profile fields (standard and custom) can be added/removed as columns in the list.
* When rolling over the each icon, additional details (including the completion date) will display.

See the mockup to the right with all course completion criteria appearing (i.e., all criteria types have been enabled in a course).

As described further above, display rules for separate groups will apply. If separate groups is enabled for the course, a "teacher" will only see students and completion data for users in the group(s) that she/he is assigned to.

Options for exporting completion data to CSV, ODF or Excel will be available. Completion dates will be included in the export.

A column labeled "Mark complete" will appear containing a checkbox for each student if the user viewing the report is assigned to a role that is allowed to manually indicate that the students have completed the course.

Not shown in the mockup, however we should display the specified values under the applicable heading in the report for each of the following feilds:
* Period after enrolment
* Passing grade
* Date (for completion)

==Gradebook==
# If "Passing grade" is enabled as a criteria for course completion, a grader should have the option of seeing completion status (i.e., "complete" / "not complete") as a column in the grader report.
# If a user assigned to a role that is enabled for "Manual completion by", the user should have the option of manually indicating which students have completed the course, a "Mark complete" column will appear to the right of the "Course total" column with a checkbox for each student who has not yet completed the course.

We should also provide an option to show course completion status in gradebook exports. Field options will include:
* Completion status (e.g., "Complete", "Not complete")
* Completion date

==Completion progress block==
[[Image:Course_completion_progress_block.png|thumb|190px|Course completion progress block]]

If completion is enabled for the site and a course, a completion block will be available to be added to the course.

The block will allow a "student" to see:
* The completion criteria for completing the course
* His/her status for completion of each criteria (similar to the Completion progress report)
* His/her overall completion status for the course (complete / not complete)

If all of the enabled criteria are required, the introduction text should say:
:''"All of the criteria below needed"''

If any of the enabled criteria are required, the introduction text should say:
:''"Any of the criteria below needed"''

If the current user can self complete the course, the block will provide an "I've completed this course" button (if the user has not already marked him/herself complete).

Activity completion criteria/status (if enabled for course completion) should be included in the block. See [http://tracker.moodle.org/browse/MDL-16466 MDL-16466] ("Activities on the course page do not convey to student that completion is expected or available for the activity").

==User (course) profile==
Activity and course completion criteria/status data should appear in a user's "Outline report" and "Complete report" in the user profile area, which is being reworked for 2.0 separately from this spec.

=Site reporting=

==User (site) profile==
[[Image:Course_completion_user_profile_activity.png|thumb|400px|Mockup of the user profile page with Course completion report]]

Activity and course completion criteria/status data should appear in a user's profile area.

It would make sense for courses to be grouped by:
* Courses in progress
* Courses completed
* Courses not yet started

For each course, the required criteria and status should appear.

==My Moodle==
Activity and course completion criteria/status data should appear with the course and course activity listings. My Moodle is being reworked for 2.0 separately from this spec.

=Cron=
A cron function will check the criteria and update the course_completion_completions table as necessary. Here's a breakdown of the tasks for each criteria, and will need to be optimised for performance and scalability across all courses:

* '''Manual self completion:''' Cron not needed, performed directly from the Completion progress block.
* '''Manual completion by:''' Cron not needed, performed directly via the Completion progress report.
* '''Course grade:''' Compare the course grade to the passing grade.
* '''Unenrol:''' Compare course_completion->unenroled to role_assignments->timeend for the "student" role in the course.
* '''Date:''' Compare the current date to the specified date.
* '''Duration after enrolment:''' Compare the current date to the role_assignments->timestart + the specified period after enrolment.
* '''Activity completion:''' Evaluate the necessary records in the course_modules_completion table.
* '''Course completion:''' Aggregate the necessary fields in course_completion table, updating the timecompleted field with the current timestamp if the user has met the necessary criteria.
* '''Notifications:''' Send out them out to the user (if enabled) and to users in the selected role.

=Backup and restore=
* The new completion fields in the course table will be included in the backup.
* Entries in the course_completion_items, course_completion_aggregation_methods, and course_completion_notify tables for the course should also be included in the backup.
* When user data is included in a course backup, the backup will also include records in the course_completion_completions table for the course.

Competencies

2009-08-20T01:49:54Z

Jonathannewman: User interface: Added "Add / edit comptency evidence" admin page spec and mockup

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

==Add a competency page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

==Add / edit a competency depth page==
[[Image:Competencies_depth_add.png|thumb|400px|Mockup of the Add competency depth admin page]]

An "admin" will be use this page to add / edit a new competency depth, with the following settings:
* Depth full name
* Depth short name
* Description

Also, the depth level will be displayed

==Add / edit a competency evidence==
[[Image:Competencies_evidence_add_edit.png|thumb|400px|Mockup of the Add / edit competency evidence admin page with Example 1 competencies]]

An "admin" will be use this page to view / add / edit evidence for a competency. The top of the page should display the existing general data for the competency, the number of "students" who have achieved the competency, and a table showing data and functionality for each evidence item:
* The name of the competency evidence (which links to the evidence item in context, e.g., the course if course completion is specified, etc)
* The type of evidence
* The activity (if the evidence is an activity outcome or activity grade)
* The weight of the evidence
* Options to edit or remove the evidence
* The number of "students" who have achieved the evidence

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-20T01:24:52Z

Jonathannewman: User interface: Added "Add a comptency depth page" spec and mockup

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

==Add a competency page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

==Add / edit a competency depth page==
[[Image:Competencies_depth_add.png|thumb|400px|Mockup of the Add competency depth admin page]]

An "admin" will be use this page to add / edit a new competency depth, with the following settings:
* Depth full name
* Depth short name
* Description

Also, the depth level will be displayed

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-20T01:02:51Z

Jonathannewman: User interface: moved "Add / edit competencies" mockups to the Add/edit competencies admin page

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

==Add a competency page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-20T01:01:35Z

Jonathannewman: User interface: Edited caption on "Add/edit competency admin page" mockup

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==

[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with competencies from Example 1 framework)]]

When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

==Add a competency page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-20T00:59:09Z

Jonathannewman: User interface: Added default "Add/edit competencoes

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==

[[Image:Competencies_add_edit_default.png|thumb|400px|Mockup of the Add/edit competencies admin page (default)]]

[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page (with sample competencies)]]

When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

==Add a competency page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-20T00:43:06Z

Jonathannewman: User interface: Added "Add a comptency admin page" spec

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=

==Site Administration block==
[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page]]

When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

==Add a competency page==
[[Image:Competencies_add.png|thumb|400px|Mockup of the Add competencies admin page]]

An "admin" will be use this page to add a new competency, with the following settings:

''General settings''
* Parent competency
* Competency full name
* Competency short name
* Competency ID number
* Description
* Aggregation method
* Scale
* Proficiency expected

''Custom depth level settings''
* Form elements based on custom fields for selected depth level (based on the parent competency)
* Changing the selected parent competency should update the custom fields shown, if the depth level of the parent changes

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-19T01:05:26Z

Jonathannewman: /* User interface */

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=
[[Image:Competencies_add_edit.png|thumb|400px|Mockup of the Add/edit competencies admin page]]

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T23:58:19Z

Jonathannewman: User interface: Added "Add/edit comptencies admin page" spec

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=
[[Image:Competency_home.png|thumb|400px|Competencies in the Site Administration block]]

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

==Add/edit competencies admin page==
An "admin" can use this page to add and edit competencies and competency depth levels, using buttons and features available in a table.

'''Buttons'''
* An "Add a new competency" button will link to the "Add a competency" admin page.
* An "Add a new depth level" button will link to the "Add a depth level" admin page.

'''Table rows'''
* A "plus" / "minus" icon will appear on the right of each row in the table, allowing all child competencies to be shown or hidden.

'''Table columns'''
* A default, top-level competency depth named "Competency" will appear in a table as a column on the left. The default competency depth name can be changed (e.g., "Competency Area", "Standard", "Development Area", etc).
* When a new competency depth is added, it will appear as column to the right of the next highest competency depth level.
* Appearing to the right of the competency depth level columns will be the following "standard" interface columns: "Evidence items", "Edit", and "Move competency to".

Below are more specifics on the table columns and content:
* ''[Competency depth level 0 name]'', ''[Competency depth level 1 name]'', ''[Competency depth level 2 name]'', ... ''[Competency depth level n name]''
** Columns of depth levels will be ordered from highest/top-level (on the left) to the lowest (on the right).
** An edit icon will appear beside each competency depth name, and will link to the "Edit competency depth" page (which will allow an "admin" to change the name of the competency depth name).
** The competency name will be displayed, and will link to a page containing meta data and possibly summary proficiency achievement stats about the competency.
* ''Evidence item''
** By default the number of evidence items will be "0". The number shown will link to the "Add / edit evidence items" admin page for the given competency.
* ''Edit''
** Three icons appear providing the following functionality:
*** "edit" icon points to the "Edit competency" page for the competency
*** "delete" icon points to a confirmation page for deleting the competency
*** "up" / "down" icons will appear beside child competencies when a parent has two or more child competencies. A competency can only be moved up or down with respect to a parent competency.Only the down arrow will appear for the highest child competency, and only the up arrow will appear for the lowest child competency.
* ''Move competency to''
** A drop down menu appears containing all parent competencies at the next highest depth.
** Competencies can only be moved from one parent to another parent in the same depth level.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T22:54:48Z

Jonathannewman: User interface: Site Administration block - added more detail

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=
[[Image:Competency_home.png|thumb|400px|Competencies in the Site Administration block]]

==Site Administration block==
When competencies are enabled, a "Competencies" menu item should appear in the Site Administration block. An "Add / edit competencies" option should appear when "Competencies" is clicked. The "Add / edit competencies" will point to the "Add / edit competencies" admin page.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T03:45:51Z

Jonathannewman: User Interface: Added new section and Site Admin block mockup

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=User interface=
[[Image:Competency_home.png|thumb|400px|Competencies in the Site Administration block]]

=Site Administration block=
When competencies are enabled, a "Competencies" menu item should be available from the Site Administration block.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T03:07:28Z

Jonathannewman: Definitions: Competency evidence type - removed course outcome, which can't be evaluated

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T03:06:15Z

Jonathannewman: Definitions: competency -- removed reference to folksonomy

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T03:05:23Z

Jonathannewman: Definitions: clarified scale and scale values (and examples)

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using scale values.

Example scales:
"Average-based scale"
"Competency-based scale"

'''Scale values''': Descriptor or numeric values that comprise a scale. A scale value can have a id number (code) and description.

Example scales values (with descriptors and numerical values) for the scale examples above:
"Below average [1], Average [2], Above average [3]
"Not yet competent [0], Competent [100]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:54:45Z

Jonathannewman: Goals: edited various other sections

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency and a competency evidence item
# Aggregating measured proficiency
#* Allow "admins" to specify aggregation methods for each competency
#* Reporting
#** Allow "admins" to view competency results for all students
#** Allow "teachers" to view student measured proficiencies related to evidence in his/her courses.
#** Allow "students" to view their own competency results (via either their personal profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:49:43Z

Jonathannewman: Goals: edited linking competencies and evidence items

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Linking competencies and evidence items
#* Allow "admins" to easily attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#* Allow "course creators" to attach competencies to evidence ''within a course'':
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:47:52Z

Jonathannewman: Goals: edited 'easy navigation' section

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure
#** Expanding/collapsing competencies
#** Sorting/searching/filtering by competency meta data
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:46:21Z

Jonathannewman: Goals: edited measured amount of abstraction

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to map related competencies on a given depth level
#* Allow "admins" to define custom info fields on a given depth level
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:42:29Z

Jonathannewman: Goals: removed redundant goals related to parent-child and related competencies

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:41:24Z

Jonathannewman: removed questions and questions categories as a competency evidence type

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:39:27Z

Jonathannewman: Ideas for the future: added idea to allow competencies to be tagged

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).
# Allow competencies to be tagged (in a folksonomy) using Moodle's tag/lib.

[[Category:Project]]

Competencies

2009-08-18T02:37:18Z

Jonathannewman: /* competency_depth_info_field */

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''depthid'''
|int(10)
|
|The id of the competency depth for the field. Foreign key to the competency_depth table's id

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-18T02:35:29Z

Jonathannewman: /* competency_depth_info_field */

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category. Foreign key to the competency_depth_info_category table's id field
|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-18T02:32:56Z

Jonathannewman: Data structure: competency_depth table - added 'level' field

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|-
|'''level'''
|int(2)
|
|The actual depth level, starting at 0
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-18T02:31:23Z

Jonathannewman: Data structure: competency table edit - proficiencyexpected is a foreign key to a scale value

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, foreign key to the scale_value table's id

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-18T02:28:59Z

Jonathannewman: Data structure: competency table edit - changed 'depth' field name to 'depthid'

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depthid'''
|int(10)
|
|The id of the depth level the competency belongs to

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-18T02:27:10Z

Jonathannewman: data structure: scale table needed a clearer description

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===
Scales (introduced in Moodle 1.9) give a scale value a single attribute: text (i.e., the name of the scale value like "below standard," "meets standard," "above standard"). Scale values can be particularly useful if given attributes including: numerical equivalent, idnumber (code id), and a description. The new attributes will require a new table.

''Proposed changes:'' Create a new table 'scale_values' that includes a foreign key to the 'scale' table, and migrate the 'scale' field values from the 'scale' table (as serialised text) to the 'scale_values' table (as separate records). A sort order field will be used to track ranking (starting with the lowest with a sortorder of 0).

Below is the proposed 'scale' table, and further below is the proposed 'scale_value' table.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-18T02:10:25Z

Jonathannewman: Goals: edits to connecting competencies and evidence items

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a ''site-level competency view''):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence ''in a course'':
#** Course grade
#** Completion of the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-18T02:07:44Z

Jonathannewman: Goals: competencies just ordered in a hierarchy with related terms - use taglib for folksonomy?

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy
#* Allow "admins" to define related competencies
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Course completion

2009-08-18T02:04:20Z

Jonathannewman: /* Data structures */

{{Moodle 2.0}}This is a SPECIFICATION for a feature in Moodle 2.0 that is still under development

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''': MDL-2631 Course credits and tracking of student's completion
* '''DISCUSSION''': [http://moodle.org/mod/forum/discuss.php?d=126016 http://moodle.org/mod/forum/discuss.php?d=126016]
* '''COMMENTS''': [[Development_talk:Course_completion]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]], [[Aaron Barnes]] and others

=Overview=
We need to flag when the "student" has finished a course. :-)

We need to allow several types of criteria to determine how a "student" can complete a course:
* '''Manual self completion''': A "student" can mark her/himself complete a course.
* '''Manual completion by''': An "admin", "teacher", "tutor", etc can mark a student complete for a course.
* '''Activity completion''': A "student" completes an activity, building on [https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] developed for 2.0 by Sam Marshall from OU.
* '''Course grade''': A "student" meets or exceeds a passing grade in the course.
* '''Date''': After a specified date all "students" are marked as completed in a course.
* '''Duration after enrolment''': After a specified about of time after enrolment (e.g., 12 weeks), a "student" is automatically marked as complete in a course.
* '''Unenrol''': After being unenroled, a "student" is marked complete for the course. Useful for external enrolment plugins.

We need to record when and how a "student" meets each criteria in a course.

We need to regularly aggregate the results for the criteria, measure progress, and check to see if a "student" has completed a course.

We need to show:
* A "student" the necessary criteria to complete a course
* A "student" how s/he is progressing in a course along the necessary criteria
* A "teacher" how his/her students are progressing in a course and which students have completed it

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable completion tracking" setting (found in the Site Administration block's Advanced features / optional subsystems settings page) for activity completion. We need to change the setting's name and add another setting for course completion.

'''Proposed changes:'''
* Rename the setting "Enable activity completion tracking" (the setting will continue to allow activity completion to be enabled in all courses)
* Create a new setting named "Enable course completion tracking" (the setting will allow course completion to be enabled in all courses)

==Course settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides a fieldset (named "Student progress") which contains a setting (named "Completion tracking") which enables/disables activity completion in a course. We need to rename the setting to describe activity completion and add a setting to enable course completion.

"Enable completion tracking" setting (found in the Site Administration block's Advanced features / optional subsystems settings page) for activity completion.

'''Proposed changes:'''
* Rename the setting "Completion tracking" to "Activity completion tracking" (the setting will continue to make activity completion features available in the courses)
* Create a new setting named "Course completion tracking" (the setting will make course completion features available in the course)

==Course completion settings==
When course completion is enabled in a course (see above), a menu item labeled "Completion" will appear in the course Administration block on the main course page. When a user clicks on the "Completion" link, the course completion admin page will display the criteria described below and in the mockup also below:

[[Image:Edit_course_completion_settings.png|thumb|600px|Edit course completion settings]]

===Criteria enabling===
We need to allow criteria to be enabled.

We need some rules about enabled criteria in a course:
* Each criteria (e.g., "Manual self completion", "Manual completion by", etc) can be enabled
* By default, all criteria are not enabled

===Criteria aggregation===
We need to define overall aggregation methods for the criteria type. We also need to a consistent set of aggregation methods for criteria types which have more than one possible option to determine an individual user's course completion:
* "Manual completion by" // more than one role can be enabled to determine if a student has completed the course
* "Activity completed" // more than one activity completion can be selected to determine if a student has completed the course

Aggregation methods:

{| border="1" cellpadding="2" cellspacing="0"
|'''Method'''
|'''Required to complete the criteria type'''
|'''Example'''
|'''Info'''

|-
|'''All'''
|All of the enabled child criteria must be completed
|Not applicable
|

|-
|'''Any'''
|Any one (1) of the enabled child criteria must be completed
|Not applicable
|

|-
|'''Fraction'''
|A fraction of the enabled child criteria must be completed
|0.25,0.5,0.9
|

|-
|'''Units'''
|A specified number of the enabled child criteria must be completed
|2,3,4
|A unit of 1 is equivalent to 'any'. A unit equal to the number of enabled child criteria is equivalent to 'all'.
|}

===Criteria types===
====Manual self-completion====
'''Action:'''
* A "student" can manually indicate that s/he has completed a course via the course's [https://docs.moodle.org/en/Development:Course_completion#Block Completion progress block].
'''Tracked:'''
* The day/time when the "student" marked him/herself complete.

====Manual completion by====
'''Action:'''
* A user assigned to the role in the course will see a checkbox in the [https://docs.moodle.org/en/Development:Course_completion#Report Completion progress report], which will allow him/her to manually "Mark complete" each applicable student enrolled in the course.

'''Tracked:'''
* The roleid of the user who marked the "student" complete.
* The userid of the user who marked the "student" complete.
* The day/time when the user marked the "student" as complete in the course.

'''Notes:'''
# The Completion progress report will respect:
#* '''Separate groups:''' A "teacher" will only be able to see and mark complete students in her/his group(s) if separate groups is enabled.
#* '''Role assignments on the USER-level context:''' A "Tutor" or "Mentor" will only be able to see and mark complete users assigned to him/her.
# The criteria can be met only once by the role:
#* If more than one user is assigned to the role and has the capability of marking the user complete
#* After a "student" has been marked complete one time by a user in the role, the [https://docs.moodle.org/en/Development:Course_completion#Report Completion progress report] will not provide a checkbox in the "Mark complete" column when viewed by any user in the role in the course.
# We really be relying on role capabilities and permissions for this.

====Activities completed====
'''Action:'''
* A "student" will meet the criteria when completing the specified activity, per the activity's 'Activity Completion' settings.

'''Tracked:'''
* The cmid, module type, and activity/resource name for each activity.
* The day/time when the criteria was detected as complete.

'''Note:'''
# The list of activities/resources will contain:
#* Each activity/resource in the course with "Completion tracking" enabled within the activity/resource.
#* The type of each activity followed by the activity name (i.e., "[mod name] - [activity/resource name]"). See the mockup on this page (or for a basic example: "Quiz - Derivatives").
# If "Activity completion" is not enabled for the site, the "Activities completed" field set will not appear on the page.
# If "Activity completion" is enabled for the site and not enabled for the course, the "Activities completed" field set will appear and it will only contain this message:
#:''"Activity completion must be enabled for this course."''
# If "Activity completion" is enabled for the site and course, and there are no activities in the course, the "Activities completed" field set will appear and it will only contain this message:
#:''"Currently, there are no activities in this course"''
# If "Activity completion" is enabled for the site and course, and there are activities but none have activity completion enabled, the "Activities completed" field set will appear and it will only contain this message:
#:''"Currently, none of the activities in this course have defined activity completion settings."''

====Course grade====
'''Action:'''
* A "student" will meet the criteria when earning a total course grade above the passing grade.

'''Tracked:'''
* The day/time when the user's course grade was evaluated as having exceeded the passing grade.

'''Note:'''
* The passing grade can also be updated via the course's "Grade to pass" setting found in the Grader report's edit page for the top level category for the course.
* Once a student has completed the course, both the "Passing grade" setting on the course page and the "Grade to pass" setting in the top level category for the course will be locked. A message about locking will appear on the settings page for the top level category for the course.

====Date====
'''Action:'''
* A "student" enroled in the course will automatically meet the criteria after a specified date.

'''Tracked:'''
* The day/time when specified day was evaluated as having passed.

====Duration after enrolment====
'''Action:'''
* A "student" will meet the criteria after the specified number of days after his/her enrolment.

'''Tracked:'''
* The day/time when the "student" marked him/herself complete.

====Unenrolment====
'''Action:'''
* A "student" will meet the criteria when being unenroled from the course.

'''Tracked:'''
* The day/time when the "student" was unenroled from the course.

===Notifications===
====Enable====
If enabled, a "student" will receive notification when s/he has completed the course via the completion criteria.

====Notify====
Users assigned to each selected role in the course will receive notification when each "student" completes the course.

===Locking===
When the first student has completed the course, the course completion criteria settings will be locked. The course settings can be unlocked (via an "Unlock course completion options" button), however a warning message will be displayed stating that unlocking the settings requires deleting all prior course completion data for the course. Once the completion data is deleted, the settings become unlocked (i.e., un-greyed out).

This is consistent with activity completion in 2.0, in which activity completion settings are locked when a user first completes an activity. Activity completion settings can be unlocked after all completion activity is deleted.

==Activity settings==
If activity completion is enabled and activity completion is a criteria for course completion, then all activity completion settings will be locked once a student has completed the course. In this case, unlocking an activity's completion settings will require deleting both the activity's completion data and the course's completion data.

If an activity is being tracked for course completion, we should add a warning/confirmation screen when an "admin" attempts to delete it. The message should say, "[Activity name] is currently a criteria for course completion. Are you sure you want to delete it?" [Delete anyway] / [Cancel]. If the "admin" confirms, the activity will be deleted however completion data for users who completed it will still remain tracked.

Should the activity completion data remain?
Should the course completion data be re-aggregated?

=Data structures=
[[Image:Course_completion_data_model.png|thumb|400px|Course completion data model]]

===course===
The course table will require the following new fields. 'enablecompletion' will now be used for activity and course completion:

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''completionnotify'''
|int(1)
|
|Notify users when they complete this course

|}

===course_completion_aggregation_methods===
This new table will be populated with the aggregation method for "Overall criteria", "Manual completion by", and "Activities completed".

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the course completion aggregation relates to

|-
|'''criteriatype'''
|int(20)
|null
|The criteria type's integer constant ('role', 'activity') or null if 'overall' course aggregation.

|-
|'''method'''
|int(1)
|1
|'1'='all', '2'='any', '3'='fraction', '4'='unit'.
|-

|'''value'''
|number(10)
|null
|null for 'all' and 'any', 0..1 for 'fraction', int > 0 for 'unit'
|}

===course_completion_criteria===
This new table will be populated with each criteria in each course for course completion:

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the course completion criteria relates to

|-
|'''itemname''' (not implemented)
|varchar(100)
|null
|The name of the item (e.g. "Mark yourself complete", "Teacher marks you complete", "[Activity name]", "[postenrol] days after enrolment", "Official Date: [date]". Used for all item types except unenrol.

|-
|'''criteriatype'''
|int(20)
|
|The criteria type's integer constant ('self', 'role', 'mod', 'grade', 'enrolperiod', 'date', 'postenrol').

|-
|'''module'''
|varchar(100)
|null
|The name of the module (e.g., 'scorm', 'quiz', 'feedback'). Used only if criteriatype='mod'.

|-
|'''moduleinstance'''
|int(10)
|null
|The id of the activity/resource module or role. Used only if criteriatype='mod'.

|-
|'''enrolperiod'''
|int(10)
|null
|The number of seconds after enrolment. Used only if criteriatype='enrolperiod'.

|-
|'''date'''
|int(10)
|null
|The timestamp of the date for course completion. Used only if criteriatype='date'.

|-
|'''gradepass'''
|number(10)
|null
|The course grade required to complete this criteria. Used only if criteriatype='grade'.

|-
|'''role'''
|int(10)
|null
|The role id that can mark 'student's as complete in the course. Used only if criteriatype='role'.

|-
|'''lock''' (currently unused)
|int(10)
|null
|Date this criteria was locked
|}

===course_completion_criteria_completions===
This new table will be populated with records for each user as they complete each course completion criteria.

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user who has completed the course

|-
|'''course'''
|int(10)
|
|The id of the completed course

|-
|'''criteriaid'''
|int(10)
|
|The id of the completion criteria this references

|-
|'''gradefinal'''
|number(10)
|null
|The final grade for the course (if referenced criteria type='grade').

|-
|'''unenroled'''
|int(10)
|null
|Timestamp when the user was unenroled (if referenced criteria type='unenrol').

|-
|'''deleted''' (currently unused)
|int(1)
|null
|The course was deleted

|-
|'''timecompleted'''
|int(10)
|null (should be notnull)
|Timestamp when the user completed the criteria
|}

===course_completion_notify===
This new table will be populated with the roles which should be notified for this course

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''course'''
|int(10)
|
|The id of the course that the condition applies to

|-
|'''role'''
|int(10)
|
|The id of the role that should be sent a notification when a course has been completed

|-
|'''message'''
|text
|
|HTML formatted message to be sent to the user assigned to the role.

|-
|'''timesent'''
|int(10)
|
|Timestamp of when the notification was sent

|}

===course_completions===
This new table will be populated with a record for a user when s/he meets course completion criteria selected/enabled for a course.

{| border="1" cellpadding="2" cellspacing="0"
!Field
!Type
!Default
!Info

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user who has completed the course

|-
|'''course'''
|int(10)
|
|The id of the completed course

|-
|'''deleted''' (currently unused)
|int(1)
|null
|The course was deleted

|-
|'''timenotified'''
|int(10)
|null
|Timestamp when the user was notified

|-
|'''timeenroled'''
|int(10)
|
|Timestamp when the user enroled in the course

|-
|'''timecompleted'''
|int(10)
|null (should be notnull)
|Timestamp when the user completed the course

|}

=Evaluating completion=
Since the gradebook aggregation is performed via cron, it makes sense that course completion is also evaluated by cron.

This creates an issue in which the progress block will not instantly not show course completion after the necessary criteria has been met by a "student". However, this can be solved by adding some instructional text to say "may take a few minutes to update".

=Role capabilities=
{| border="1" cellpadding="2" cellspacing="0"
|'''Feature'''
|'''Description'''
|'''Capability'''

|-
|Progress block
|Mark self-complete in progress block
|block/progress:markselfcomplete

|-
|Progress report
|View course progress report
|coursereport/progress:view

|-
|Progress report
|Mark users complete in course progress report
|coursereport/progress:markcomplete

|}

=Course reporting=
==Completion progress report==
[[Image:Completion_report.png|thumb|600px|Course completion progress report]]

[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides a "Completion progress report". The report can be found via on "Reports" menu item link in the course Administration block and when "Completion tracking" is enabled for the site and course.

The report shows:
* A column for each of the activities/resources in the course with "Completion tracking" enabled"
* A row for each user enroled in the course
* The completion status for each activity

'''Proposed changes:'''
* Include in the report all enabled criteria for course completion (e.g., "Manual self completion", "Manual completion by", as well as the activities etc)
* Each user's status for completion of each criteria, indicated by a status icon
* Allow the completion admin page to determine which activities are shown in the report
* Allow the list of users to be sortable, searchable, and filterable (by group, groupings, and/or user profile fields).
* Allow user profile fields (standard and custom) can be added/removed as columns in the list.
* When rolling over the each icon, additional details (including the completion date) will display.

See the mockup to the right with all course completion criteria appearing (i.e., all criteria types have been enabled in a course).

As described further above, display rules for separate groups will apply. If separate groups is enabled for the course, a "teacher" will only see students and completion data for users in the group(s) that she/he is assigned to.

Options for exporting completion data to CSV, ODF or Excel will be available. Completion dates will be included in the export.

A column labeled "Mark complete" will appear containing a checkbox for each student if the user viewing the report is assigned to a role that is allowed to manually indicate that the students have completed the course.

Not shown in the mockup, however we should display the specified values under the applicable heading in the report for each of the following feilds:
* Period after enrolment
* Passing grade
* Date (for completion)

==Gradebook==
# If "Passing grade" is enabled as a criteria for course completion, a grader should have the option of seeing completion status (i.e., "complete" / "not complete") as a column in the grader report.
# If a user assigned to a role that is enabled for "Manual completion by", the user should have the option of manually indicating which students have completed the course, a "Mark complete" column will appear to the right of the "Course total" column with a checkbox for each student who has not yet completed the course.

We should also provide an option to show course completion status in gradebook exports. Field options will include:
* Completion status (e.g., "Complete", "Not complete")
* Completion date

==Completion progress block==
[[Image:Course_completion_progress_block.png|thumb|190px|Course completion progress block]]

If completion is enabled for the site and a course, a completion block will be available to be added to the course.

The block will allow a "student" to see:
* The completion criteria for completing the course
* His/her status for completion of each criteria (similar to the Completion progress report)
* His/her overall completion status for the course (complete / not complete)

If all of the enabled criteria are required, the introduction text should say:
:''"All of the criteria below needed"''

If any of the enabled criteria are required, the introduction text should say:
:''"Any of the criteria below needed"''

If the current user can self complete the course, the block will provide an "I've completed this course" button (if the user has not already marked him/herself complete).

Activity completion criteria/status (if enabled for course completion) should be included in the block. See [http://tracker.moodle.org/browse/MDL-16466 MDL-16466] ("Activities on the course page do not convey to student that completion is expected or available for the activity").

==User (course) profile==
Activity and course completion criteria/status data should appear in a user's "Outline report" and "Complete report" in the user profile area, which is being reworked for 2.0 separately from this spec.

=Site reporting=

==User (site) profile==
Activity and course completion criteria/status data should appear in a user's "Outline report" and "Complete report" in the user profile area, which is being reworked for 2.0 separately from this spec.

==My Moodle==
Activity and course completion criteria/status data should appear with the course and course activity listings. My Moodle is being reworked for 2.0 separately from this spec.

=Cron=
A cron function will check the criteria and update the course_completion_completions table as necessary. Here's a breakdown of the tasks for each criteria, and will need to be optimised for performance and scalability across all courses:

* '''Manual self completion:''' Cron not needed, performed directly from the Completion progress block.
* '''Manual completion by:''' Cron not needed, performed directly via the Completion progress report.
* '''Course grade:''' Compare the course grade to the passing grade.
* '''Unenrol:''' Compare course_completion->unenroled to role_assignments->timeend for the "student" role in the course.
* '''Date:''' Compare the current date to the specified date.
* '''Duration after enrolment:''' Compare the current date to the role_assignments->timestart + the specified period after enrolment.
* '''Activity completion:''' Evaluate the necessary records in the course_modules_completion table.
* '''Course completion:''' Aggregate the necessary fields in course_completion table, updating the timecompleted field with the current timestamp if the user has met the necessary criteria.
* '''Notifications:''' Send out them out to the user (if enabled) and to users in the selected role.

=Backup and restore=
* The new completion fields in the course table will be included in the backup.
* Entries in the course_completion_items, course_completion_aggregation_methods, and course_completion_notify tables for the course should also be included in the backup.
* When user data is included in a course backup, the backup will also include records in the course_completion_completions table for the course.

Competencies

2009-08-12T04:22:53Z

Jonathannewman: removed typo

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-12T02:43:42Z

Jonathannewman: /* Data structures */

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Settings=
==Site settings==
[https://docs.moodle.org/en/Development:Conditional_activities#Completion_tracking_2 Activity Completion] provides an "Enable outcomes" setting (found in the Site Administration block's Advanced features / optional subsystems settings page). We need to keep outcomes, however we will need to add competencies.

'''Proposed changes:'''
* Create a new setting named "Enable competencies" (the setting will allow competencies to be defined)

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}
'''Bold text'''

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-06T04:07:10Z

Jonathannewman: data structures: added a competency_depth table

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth===

Data for a competency depth level.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the depth level

|-
|'''fullname'''
|varchar(255)
|
|Full name for the depth level

|-
|'''description'''
|text
|
|Description for the depth level

|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-05T04:03:25Z

Jonathannewman: Example frameworks: fixed typo

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data above fits into the proposed schema.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-05T02:43:57Z

Jonathannewman: /* Example frameworks */

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency'''
'''full name'''
|'''Competency'''
'''evidence'''
|'''Competency'''
'''aggregation method'''
|'''Competency
'''weight'''
|'''Competency'''
'''proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|none
|all
|20%
|80%

|-
|1
|"Type"
|"Reading"
|none
|all
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|none
|all
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|none
|all
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|activity outcome "Recognizing pairs of rhyming words and producing rhymes"

activity outcome "Blending and segmenting syllables and onset-rimes"

activity outcome "Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'")"
|all
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|none
|all
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|activity outcome: "Distinguishing between printed letters and words"

activity outcome: "Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality"

activity outcome: "Identifying the first and last parts of a word (beginning/end of the word)"

activity outcome: "Identifying key parts of a book: front and back, print, illustrations"

|all
|50%
|80%
|}

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data below would fit into the proposed schema.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-05T02:26:07Z

Jonathannewman: Example frameworks: moved example into a table

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is based roughly on the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

{| border="1" cellpadding="2" cellspacing="0"
|'''Depth level'''
|'''Depth name'''
|'''Competency short name'''
|'''Competency full name'''
|'''Competency aggregation method'''
|'''Competency weight'''
|'''Competency proficiency expected'''

|-
|0
|"Curriculum"
|"Literacy"
|all
|none
|20%
|80%

|-
|1
|"Type"
|"Reading"
|all
|none
|20%
|100%

|-
|2
|"Standard"
|"Standard 1.1 Reading Strategies"
|all
|none
|20%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies: Phonological Awareness"
|all
|none
|100%
|80%

|-
|4
|"Code"
|"RK: 1 - Applies phonological knowledge and skills by..."
|all
|none
|50%
|80%

|-
|3
|"Strategy"
|"Early Reading Skills and Strategies - Concepts of Print"
|all
|none
|50%
|80%

|-
|4
|"Code"
|"RK: 2 - Demonstrates understanding of concepts of print during shared or individual reading by..."
|all
|none
|50%
|80%
|}

activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data below would fit into the proposed schema.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-05T02:04:00Z

Jonathannewman: /* Role capabilities and permissions */

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is an excerpt from the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

competency -> "Curriculum" : "Literacy" : aggregation method "all" : weight none : proficiency expected "80%"
competency -> "Type" : "Reading" : aggregation method "all" : weight "20%" : proficiency expected "80%"
competency -> "Standard 1.1" : "Reading Strategies" : aggregation method "all" : weight: "20%" : proficiency expected "80%"
competency -> "Early Reading Skills and Strategies" : "Phonological Awareness" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 1" : "Applies phonological knowledge and skills by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
competency -> "Early Reading Skills and Strategies" : "Concepts of Print" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 2" : "Demonstrates understanding of concepts of print during shared or individual reading by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data below would fit into the proposed schema.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-05T02:03:38Z

Jonathannewman: /* Example frameworks */

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is an excerpt from the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

competency -> "Curriculum" : "Literacy" : aggregation method "all" : weight none : proficiency expected "80%"
competency -> "Type" : "Reading" : aggregation method "all" : weight "20%" : proficiency expected "80%"
competency -> "Standard 1.1" : "Reading Strategies" : aggregation method "all" : weight: "20%" : proficiency expected "80%"
competency -> "Early Reading Skills and Strategies" : "Phonological Awareness" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 1" : "Applies phonological knowledge and skills by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
competency -> "Early Reading Skills and Strategies" : "Concepts of Print" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 2" : "Demonstrates understanding of concepts of print during shared or individual reading by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data below would fit into the proposed schema.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-05T02:03:20Z

Jonathannewman: Example frameworks: added introductory info to example 1

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==

'''Example 1:''' Competency hierarchy with activity outcomes as evidence

The example data below is an excerpt from the [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading.

competency -> "Curriculum" : "Literacy" : aggregation method "all" : weight none : proficiency expected "80%"
competency -> "Type" : "Reading" : aggregation method "all" : weight "20%" : proficiency expected "80%"
competency -> "Standard 1.1" : "Reading Strategies" : aggregation method "all" : weight: "20%" : proficiency expected "80%"
competency -> "Early Reading Skills and Strategies" : "Phonological Awareness" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 1" : "Applies phonological knowledge and skills by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
competency -> "Early Reading Skills and Strategies" : "Concepts of Print" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 2" : "Demonstrates understanding of concepts of print during shared or individual reading by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

See [https://docs.moodle.org/en/Development:Competencies_example here] for how the data below would fit into the proposed schema.

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Example frameworks=
There are an enormous number of example competency frameworks published online. I've randomly selected a comprehensive example [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading, and detailed [https://docs.moodle.org/en/Development:Competencies_example here] how it would fit into the proposed schema.

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-05T01:02:35Z

Jonathannewman: data structures: added data model diagram

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==
'''Example 1:''' Competency hierarchy with activity outcomes as evidence

competency -> "Curriculum" : "Literacy" : aggregation method "all" : weight none : proficiency expected "80%"
competency -> "Type" : "Reading" : aggregation method "all" : weight "20%" : proficiency expected "80%"
competency -> "Standard 1.1" : "Reading Strategies" : aggregation method "all" : weight: "20%" : proficiency expected "80%"
competency -> "Early Reading Skills and Strategies" : "Phonological Awareness" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 1" : "Applies phonological knowledge and skills by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
competency -> "Early Reading Skills and Strategies" : "Concepts of Print" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 2" : "Demonstrates understanding of concepts of print during shared or individual reading by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

=Data structures=

[[Image:Competency_data_model.png|thumb|400px|Competencies data model]]

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Example frameworks=
There are an enormous number of example competency frameworks published online. I've randomly selected a comprehensive example [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading, and detailed [https://docs.moodle.org/en/Development:Competencies_example here] how it would fit into the proposed schema.

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-08-04T22:46:56Z

Jonathannewman: data structure: added description field to competency_relations table

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==
'''Example 1:''' Competency hierarchy with activity outcomes as evidence

competency -> "Curriculum" : "Literacy" : aggregation method "all" : weight none : proficiency expected "80%"
competency -> "Type" : "Reading" : aggregation method "all" : weight "20%" : proficiency expected "80%"
competency -> "Standard 1.1" : "Reading Strategies" : aggregation method "all" : weight: "20%" : proficiency expected "80%"
competency -> "Early Reading Skills and Strategies" : "Phonological Awareness" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 1" : "Applies phonological knowledge and skills by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
competency -> "Early Reading Skills and Strategies" : "Concepts of Print" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 2" : "Demonstrates understanding of concepts of print during shared or individual reading by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

=Data structures=

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''description'''
|text
|
|Info about how competencies are related

|-
|'''competencyid1'''
|int(10)
|
|The id of a competency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Example frameworks=
There are an enormous number of example competency frameworks published online. I've randomly selected a comprehensive example [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading, and detailed [https://docs.moodle.org/en/Development:Competencies_example here] how it would fit into the proposed schema.

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-07-31T05:00:06Z

Jonathannewman: data structure: competency_evidence removed field proficiencyexpected

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==
'''Example 1:''' Competency hierarchy with activity outcomes as evidence

competency -> "Curriculum" : "Literacy" : aggregation method "all" : weight none : proficiency expected "80%"
competency -> "Type" : "Reading" : aggregation method "all" : weight "20%" : proficiency expected "80%"
competency -> "Standard 1.1" : "Reading Strategies" : aggregation method "all" : weight: "20%" : proficiency expected "80%"
competency -> "Early Reading Skills and Strategies" : "Phonological Awareness" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 1" : "Applies phonological knowledge and skills by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
competency -> "Early Reading Skills and Strategies" : "Concepts of Print" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 2" : "Demonstrates understanding of concepts of print during shared or individual reading by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

=Data structures=

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid1'''
|int(10)
|
|The id of a comptency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Example frameworks=
There are an enormous number of example competency frameworks published online. I've randomly selected a comprehensive example [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading, and detailed [https://docs.moodle.org/en/Development:Competencies_example here] how it would fit into the proposed schema.

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]

Competencies

2009-07-31T04:58:49Z

Jonathannewman: data structure: competency table - changed aggregation field name to aggregationmethod

{{Moodle 2.0}}'''Note''': This page outlines ideas for the Competencies feature planned for Moodle 2.0. It's a ''specification under construction''! If you have any comments or suggestions, please add them to the [[Development talk:Progress tracking|page comments]].''

* '''PROJECT STATE: Proposal'''
* '''MAIN TRACKER ISSUE''':
* '''DISCUSSION''': Not yet announced on Moodle.org
* '''COMMENTS''': [[Development_talk:Competencies]]
* '''AUTHOR''': [[User:Jonathan Newman|Jonathan Newman]] with help from [[Matt Clarkson|Matt Clarkson]] and others

=Overview=
To support the range of different types of competency frameworks used by organisations, competencies in Moodle 2.0 needs to expand on the 1.9 outcomes architecture.

==Goals==
# Measured amount of abstraction
#* Allow "admins" to organise competencies in a hierarchy, folksonomy (tags), or hybrid
#* Allow "admins" to specify parent-child relations between competencies and related competencies
#* Allow "admins" to create unlimited hierarchical levels
#* Allow "admins" to describe competencies on a given depth level consistently with custom meta data fields and categories
# Easy navigation
#* Allow "admins" to view the competency structure (expanding/collapsing competencies, sorting/searching/filtering by competency meta data)
#* Allow "admins" to easily add new competencies and meta-data
# Connecting competencies and evidence items
#* Allow "admins" to attach allowed evidence (course, activity, etc) to a competency (from a competency view):
#** One or more course grades
#** One or more course completions (e.g., when completing course A, course B, and course C)
#** One or more activity outcomes, from one or more courses
#** One or more activity completions (e.g., when completing activity x in course A and activity y in course B, and activity z in course C)
#* Allow "course creators" to attach competencies to evidence in a course they are assigned to:
#** Course grade
#** Completion the course
#** Activity grade
#** Completion of an activity in the course
# Portability
#* Allow "admins" to import competencies (using import plugins) into a Moodle install
#* Allow "admins" to export competencies (using export plugins) from a Moodle install
# Specifying expected proficiency levels
#* Allow "admins" to assign an expected proficiency level (i.e., competency scale value) to a competency evidence item
# Aggregating measured proficiency level for each user
#* Allow "admins" to specify aggregation methods for each competency:
#** All child competencies or evidence
#** Any child competencies or evidence
#** A specific number of child competencies or evidence
#** A percentage of child competences or evidence
#** Sum of weighted child competencies or evidence
#** Average of weighted child competencies or evidence
#* Reporting
#** Allow "admins" to view competency results for all students across all courses.
#** Allow "teachers" to view student competency results within his/her courses.
#** Allow "students" to view their own competency results (within a course, or via their profile or My Moodle).
# Specifying weights
#* Allow "admins" to assign weight to a competency or a competency evidence item
# Scalability
#* Store and retrieve data efficiently to allow the scalability to very large numbers of courses, users, competencies, evidence, etc
# Extensibility
#* Use a plugin architecture for evidence types

==General requirements==
# We'll need to access and use the existing site-wide Outcomes [https://docs.moodle.org/en/Development:Grades#grade_outcomes Outcomes tables]
# We'll need to use the tables that indicate completion status for courses (these are not yet in place) [https://docs.moodle.org/en/Development:Course_completion Course Completion]
# We need to get aggregate information about the course outcomes and aggregate grades for each user from the gradebook API

==Definitions==
'''Scale''': A way to measure a competency using descriptors and/or numerical '''scale values'''.

Example scales using descriptors values:
"Below average, Average, Above average"
"Not competent, Competent"

Example scales using numerical values:
"1, 2, 3, 4, 5"
"0, 100"
"0.0, 0.5, 1.0"
"0, 500, 1000"

Example scales using descriptors and numerical values:
"Poor [1], Below average [2], Average [3], Above average [4], Excellent [5]"
"Not yet competent [0], Competent [100]"
"Not yet competent [0.0], Not yet performing [0.5], Competent [1.0]"

'''Competency''': A measurable knowledge, skill, ability, attitude or other learning-related characteristic which a student may have. Competencies can be organised into a hierarchy (i.e., category-based), folksonomy (tag-based), or a hybrid of both.

Example hierarchy of competencies:
top-level competency: "Literacy"
-> child competency: "Reading Comprehension"
-> child competency: "Responding to Text"
-> child competency: "Initial Understanding of Literary Text"
-> child competency: "Demonstrate initial understanding of elements of literary texts (including text read aloud, reading independently"

'''Competency evidence type''': A form of evidence that can be accepted as evidence that a competency has been achieved. Examples:
Activity grade
Activity completion
Activity outcome
Course completion
Course grade
Course outcome
Question results
File (diploma)

'''Competency evidence''': A competency can be measured by one or more competency evidence types. Evidence can be stated to include the evidence type, evidence date, and measured value. Examples:
"Quiz - 4:00pm May 28, 2009 - Grade 90% out of 100%"
"Certificate - Public Speaking Institute - 4:00pm May 28, 2009 - Passed."
"File - College Diploma - 4:00pm May 28, 2009 - Bachelor of Science Computer Science"

'''Expected proficiency level''': The expected (or required) rating (based on a scale descriptor or numerical value) for a competency. Examples:
"Average"
"5"
"50%"
"Passed"

'''Measured proficiency level''': A user's observed, scored, reported proficiency level for a competency.
"Above average"
"8"
"80%"
"Passed"

'''Competency weighting''': Child competencies can be assigned weights which can be used for aggregating either sums or averages of child competencies. Examples:

Example with percentage weights
-> top-level competency: "Communication"
-> child competency: "Written Communication" : weight: 60%
-> child competency: "Oral Communication" : weight: 40%

==Example frameworks==
'''Example 1:''' Competency hierarchy with activity outcomes as evidence

competency -> "Curriculum" : "Literacy" : aggregation method "all" : weight none : proficiency expected "80%"
competency -> "Type" : "Reading" : aggregation method "all" : weight "20%" : proficiency expected "80%"
competency -> "Standard 1.1" : "Reading Strategies" : aggregation method "all" : weight: "20%" : proficiency expected "80%"
competency -> "Early Reading Skills and Strategies" : "Phonological Awareness" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 1" : "Applies phonological knowledge and skills by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Recognizing pairs of rhyming words and producing rhymes : weight: "33%"
activity outcome -> Blending and segmenting syllables and onset-rimes (e.g., “cup-cake,” “s-at”) : weight: "33%"
activity outcome -> Isolating phonemes in single-syllable words (e.g., "tell me the first sound in 'mop' "; "tell me the last sound in 'mop,'" "tell me the middle sound in 'mop'") : weight: "33%"
competency -> "Early Reading Skills and Strategies" : "Concepts of Print" : aggregation method "all" : weight: "100%" : proficiency expected "80%"
competency -> "RK: 2" : "Demonstrates understanding of concepts of print during shared or individual reading by..." : aggregation method "all" : weight: "50%" : proficiency expected "80%"
activity outcome -> Distinguishing between printed letters and words : weight: "25%" : proficiency expected "80%"
activity outcome -> Following text with finger-pointing (e.g., charts, simple books), demonstrating left-to-right and top-to-bottom directionality : weight: "25%"
activity outcome -> Identifying the first and last parts of a word (beginning/end of the word) : weight: "25%"
activity outcome -> Identifying key parts of a book: front and back, print, illustrations : weight: "25%"

=Data structures=

===scale===

The scale feature introduced in Moodle 1.9 needs to be expanded to provide numerical equivalents for each scale value. We'll need to create a new table 'scale_values' that includes a foreign key of the 'scale' table, and remove the 'scale' field from the 'scale' table. Here is how the modified 'scale' table will look:

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''courseid'''
|int(10)
|
|Id of the course, which the scale belongs to

|-
|'''userid'''
|int(10)
|
|Id of the user who last modified the scale

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale was modified
|}

===scale_values===

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''scaleid'''
|int(10)
|
|Id of the scale that the scale value describes

|-
|'''name'''
|varchar(255)
|
|Name of the scale value

|-
|'''idnumber'''
|varchar(100)
|
|Optional id, code number or local identifier for the scale value (used for reporting).

|-
|'''description'''
|text
|
|Description of the scale value

|-
|'''numeric'''
|number(8)
|
|Numerical value for the scale value

|-
|'''sortorder'''
|int(10)
|
|The order for the scale value

|-
|'''timemodified'''
|int(10)
|
|Timestamp of when the scale value was modified
|}

===competency===

A competency can be part of a hierarchy and can have evidence attached to it.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(100)
|
|The shortname for the competency

|-
|'''fullname'''
|varchar(255)
|
|The full name for the competency

|-
|'''description'''
|text
|
|The description of the competency

|-
|'''idnumber'''
|int(10)
|
|The id, code number or local identifier for the competency used for reporting

|-
|'''parentid'''
|int(10)
|
|The id of the parent competency

|-
|'''sortorder'''
|int(10)
|
|The order number of this competency (useful for ordering competencies for viewing/navigation/reporting)

|-
|'''depth'''
|int(10)
|
|The depth of the competency (beginning at 1)

|-
|'''path'''
|varchar(255)
|
|The path to the competency

|-
|'''aggregationmethod'''
|int(10)
|
|A constant representation one of the competency aggregation methods (any, all, unit, fraction, sum of weighted, average of weighted)

|-
|'''scaleid'''
|int(10)
|
|The scale used to measure the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The expected proficiency for the competency, a value from the scale

|-
|'''timecreated'''
|int(10)
|
|The time when the competency was created

|-
|'''timemodified'''
|int(10)
|
|The time when the competency was modified

|-
|'''usermodified'''
|int(10)
|
|The userid of the person who last modified the competency
|}

===competency_relations===

For tracking relations between competencies.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid1'''
|int(10)
|
|The id of a comptency

|-
|'''competencyid2'''
|int(10)
|
|The id of a related competency
|}

===competency_depth_info_field===

Data for a competency depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''shortname'''
|varchar(255)
|
|Shortname for the field

|-
|'''fullname'''
|text
|
|Full name for the field

|-
|'''datatype'''
|varchar(255)
|
|The type of field data

|-
|'''description'''
|text
|
|Description of the field

|-
|'''categoryid'''
|int(10)
|
|The id for the field category

|-
|'''sortorder'''
|int(10)
|
|The sort order for the field within its category

|-
|'''hidden'''
|int(1)
|
|The field should be hidden

|-
|'''required'''
|int(1)
|
|The field required

|-
|'''defaultdata'''
|text
|
|Default text for the selected parameter

|-
|'''param1'''
|text
|
|Parameter text

|-
|'''param2'''
|text
|
|Parameter text

|-
|'''param3'''
|text
|
|Parameter text

|-
|'''param4'''
|text
|
|Parameter text

|-
|'''param5'''
|text
|
|Parameter text
|}

===competency_depth_info_category===

A competency's depth level can have categories for its fields.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''name'''
|varchar(255)
|
|Shortname for the depth level category

|-
|'''sortorder'''
|int(10)
|
|The order number for this category

|}

===competency_depth_info_data===

Data for a depth level field.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''fieldid'''
|int(10)
|
|The id for the field

|-
|'''competencyid'''
|int(10)
|
|The id for the competency

|-
|'''data'''
|text
|
|The actual data for the competency field
|}

===competency_evidence_items===

A competency can be achieved by one or more forms of evidence.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|Auto incrementing

|-
|'''competencyid'''
|int(10)
|
|The id for the competency that this evidence describes

|-
|'''itemtype'''
|varchar(30)
|
|The type of evidence 'course/outcome', 'mod/outcome', 'course/completion', 'mod/completion', 'course/grade', 'mod/grade', 'question/category', 'file'

|-
|'''itemmodule'''
|varchar(30)
|
|The type of evidence 'quiz', 'scorm', etc
|-

|'''iteminstance'''
|int(10)
|
|The id for the evidence instance (ie, grade_outcome id, course id, course_modules id, grade_item id, quiz_question_instance id, files id)

|-
|'''weight'''
|num(10)
|
|The weight applied to this evidence item (for aggregation)

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was allowed

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed

|-
|'''usermodified'''
|int(10)
|
|The user who last modified this evidence
|}

===competency_evidence===

Track historical and current competency information for each user.

{| border="1" cellpadding="2" cellspacing="0"
|'''Field'''
|'''Type'''
|'''Default'''
|'''Info'''

|-
|'''id'''
|int(10)
|
|auto-incrementing

|-
|'''userid'''
|int(10)
|
|The id of the user

|-
|'''competencyid'''
|int(10)
|
|The id of the competency

|-
|'''proficiencyexpected'''
|int(10)
|
|The measured/evaluated proficiency level for the competency

|-
|'''proficiencymeasured'''
|int(10)
|
|The measured/evaluated proficiency level for the user

|-
|'''timecreated'''
|int(10)
|
|The time when this competency evidence was started

|-
|'''timemodified'''
|int(10)
|
|The time when this competency evidence was last changed
|}

=Plugin architecture=
'''Competency evidence type plugins'''

Each type of evidence will need its own methods for interacting with the competency architecture and will need to interact via a base competency evidence API. Below are the item types.

* Course completion
* Course grade
* Course outcome
* Activity completion
* Activity grade
* Activity outcome
* File

'''Report plugins'''

Similar to the gradebook, we need to allow development of report plugins for competencies.

'''Import/Export plugins'''

We need to be able to import and export data related to competencies.

'''Competency framework import/export'''
A competency framework should be able to be exported using an appropriate format in either xml and csv file format. There are some standards on exchanging competencies including:
* IEEE P1484.20.1 Standard on Reusable Competency Definitions and the IEEE Draft Standard on Simple Reusable Competency Map
* ISO/IEC PDTR 24763 Conceptual Reference Model for Competencies and Related Objects

'''Competency evidence import/export'''

There are a variety of standards for exchanging competencies evidence including:
* IMS Reusable Definition of Competency or Educational Objectives Spec (RDCEO)
* IMS Learner Information Package Spec (LIP)
* HR-XML Competencies (Measurable Characteristics) Recommendation, 2007 April 15

IMS RDCEO and LIP recommend formats as shown in the examples below (more [http://www.imsglobal.org/competencies/index.html IMS RDCEO here] and [http://www.imsglobal.org/profiles/index.html IMS LIP home]). Special thanks to Sarveswaran Kengatharaiyer (GSOC 2008 student for the Moodle Progress Tracker project) who developed these examples.

rdceo.identifier = rdceo434323
rdceo.title = Identify verbs in simple sentences
rdceo.description = “Identify verbs in simple sentences”
rdceo.definition.statement.
statementid = 123
statementname = Always
statementtext = Scale
statementtoken = scl55435
rdceo.definition.statement.
statementid = 124
statementname = Never
statementtext = Scale
statementtoken = scl55436
rdceo.definition.statement.
statementid = 125
statementname = Sometimes
statementtext = Scale
statementtoken = scl55437

lip.contenttype.referencial.sourceid.id = jenney_profile
lip.identification.cotenttype.referential.indexid = id123
lip.identification.name.partname.typename=Jenny
lip.competency
cotenttype.referential.indexid = j123
exrefrecord = rdceo434323
description = Always

HR-XML recommends a format like shown below in an example which uses recursive competencies (more [http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/Competencies.html#_Toc127531664 here]).
<Competency name="Communication Skills">
<Competency name="Written Communication Skills">
<CompetencyEvidence name="WRITTENTEST1-A" dateOfIncident="1995-01-01" lastUsed="2000-01-01">
<NumericValue minValue="3" maxValue="5" description="SEP-equivalent Skill-Level Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">35</NumericValue>
</CompetencyWeight>
</Competency>
<Competency name="Oral Communication Skills">
<CompetencyEvidence name="ManagerObservation" dateOfIncident="1996-01-01" lastUsed="2000-01-01">
<NumericValue minValue="1" maxValue="5" description="Company XYZ Skill Range">5</NumericValue>
</CompetencyEvidence>
<CompetencyWeight>
<NumericValue minValue="0" maxValue="100">65</NumericValue>
</CompetencyWeight>
</Competency>
</Competency>

=Logging=
All competency related changes should be logged in history tables.

=Role capabilities and permissions=

{| border="0" cellpadding="2" cellspacing="0"
|'''Description'''
|'''Capability'''

|-
|View competency competencies
|moodle/competency:viewcompetencies

|-
|View hidden competencies
|moodle/competency:viewhiddencompetencies

|-
|Manage competencies
|moodle/competency:managecompetencies
|}

=Example frameworks=
There are an enormous number of example competency frameworks published online. I've randomly selected a comprehensive example [http://education.vermont.gov/ Department of Education for the State of Vermont]'s [http://education.vermont.gov/new/html/pgm_curriculum/literacy/gle.html Grade 1 Expectations for Literacy] for Reading, and detailed [https://docs.moodle.org/en/Development:Competencies_example here] how it would fit into the proposed schema.

=Ideas for the future=
# Due dates for course completions and outcome completions can be assigned in an individual user's learning plan.
# A comment can be added to a user's learning plan item when a course or outcome is manually added or removed from it.
# Allowing competencies to be attached to an individual user (either by user profile field or by drag and drop).

[[Category:Project]]