Development:Outcomes: Difference between revisions
From MoodleDocs
Mark Burnet (talk | contribs) mNo edit summary |
(Deleting all that stuff because it has little to do with what we're really doing.) |
||
Line 1: | Line 1: | ||
'''Feature description:''' Build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula. | '''Feature description:''' Build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula. | ||
In short it works like this: | |||
#The admin for the site imports (or types!) a long list of short text statements (outcomes or metadata). These are like the "official" tags that we have now in blogs. Let's call it list A. | |||
#Teachers can choose a subset of list A to apply to their course. The course is now tagged with metadata representing the outcomes of that course (list B) | |||
# | #Teachers can choose a subset of list B for each activity in Moodle (list C, D, E etc). | ||
#Teachers can (at course level) generate a report showing the overall coverage of list B among all the activities. This way it's easy to see if a particular outcome has been forgotten or not covered well enough. It also forces the teacher to think hard about course design, which is a good thing. | |||
#When students complete a given course, the outcomes for that course are recorded against the user's name. This allows: | |||
##reporting by student of which outcomes they have completed | |||
##reporting for students about which outcomes they are yet to achieve | |||
##smart course selection (find me a course to teach me "xxxxx") | |||
##reporting for admins about all students on the system and where they are up to. | |||
# | |||
[[Category:Developer]] | [[Category:Developer]] | ||
[[Category:Future]] | [[Category:Future]] |
Revision as of 07:41, 23 January 2007
Feature description: Build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula.
In short it works like this:
- The admin for the site imports (or types!) a long list of short text statements (outcomes or metadata). These are like the "official" tags that we have now in blogs. Let's call it list A.
- Teachers can choose a subset of list A to apply to their course. The course is now tagged with metadata representing the outcomes of that course (list B)
- Teachers can choose a subset of list B for each activity in Moodle (list C, D, E etc).
- Teachers can (at course level) generate a report showing the overall coverage of list B among all the activities. This way it's easy to see if a particular outcome has been forgotten or not covered well enough. It also forces the teacher to think hard about course design, which is a good thing.
- When students complete a given course, the outcomes for that course are recorded against the user's name. This allows:
- reporting by student of which outcomes they have completed
- reporting for students about which outcomes they are yet to achieve
- smart course selection (find me a course to teach me "xxxxx")
- reporting for admins about all students on the system and where they are up to.