Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Outcomes: Difference between revisions

From MoodleDocs
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.


This page is an initial place to discuss options for storing and managing moodle metadata.  These are just suggestions and are made by a person who does not know moodle internals.
In short it works like this:


There are several steps to managing a complex applications metadata:
#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.
# Document the key "Data Element Concpets" and their structure.  This would include high-level concepts such as Course, Student, Teacher etc.
#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)
# Document data element properties associated with each concept.  Properties should always be associated with a concept.
#Teachers can choose a subset of list B for each activity in Moodle (list C, D, E etc).
# Store this metadata in a metadata "registry", a centrally managed place to store metadata
#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.
# Create a system that allows users to modify and update metadata
#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
There are several ways to approach this.
##reporting for students about which outcomes they are yet to achieve
 
##smart course selection (find me a course to teach me "xxxxx")
* There are metadata registry standards such as ISO/IEC 11179. This standard has a wide number of interpretations.
##reporting for admins about all students on the system and where they are up to.
* There are other education metadata standards such as IMS global and the School Interoperability Framework (SIF)
* Once the metadata is stored in a consistant place and format, transforms can be made to extract portions of the metadata using reports or transforms
* A metadata registry can be the heart of a model-driven architecture
 
Most systems attempt to seperate the semantics from the representation of metadata.
# Semantics tell us the meaning of a data element but are free from version or constraints
# Representations of the metadata tell us what table and column metadata appears in each version of Moodle and what the limitations are in a specification
 
Many metadata managment systems use a 3-part data element name:
 
  ClassPropertyTerm
 
Were Class is the concept, property is a property of that concept and Term is a Representation term such as Count, Date, ID, Indicator, Text
 
For example:
 
CourseDescriptionText
 
==Questions==
* Where can we get a list of key moodle conceptual data elements and their definitions?
 
* How do we set up a data stewardship role so individuals take responsiblity for maintaining subsets of all the data elements?
 
* What should the highest level data elements be? Course, Enrollment, Organization, Person, Quiz
 
==See also==
* [[Metadata:MoodleCore]] LOM application profile for Moodle course
* [[Thing]] A root data element of a metadata registry
* [http://en.wikipedia.org/wiki/Metadata_registry Wikipedia entry for Metadata registry]
* [http://en.wikipedia.org/wiki/ISO/IEC_11179 Wikipedia entry for ISO/IEC 11179 ]
* [http://en.wikipedia.org/wiki/Data_element Wikipedia entry for Data element]
* [http://en.wikipedia.org/wiki/Representation_term Wikipedia entry for Representation term]
* [http://en.wikipedia.org/wiki/Data_element_name Wikipedia entry for Data element name ]
* [http://en.wikipedia.org/wiki/Data_element_definition Wikipedia entry for Data element definition ]
 
==Example of a K-12 education metadata registry for ==
* [http://education.state.mn.us/datadictionary Minnesota (US) Department of Education Data Dictionary]




[[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:

  1. 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.
  2. 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)
  3. Teachers can choose a subset of list B for each activity in Moodle (list C, D, E etc).
  4. 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.
  5. When students complete a given course, the outcomes for that course are recorded against the user's name. This allows:
    1. reporting by student of which outcomes they have completed
    2. reporting for students about which outcomes they are yet to achieve
    3. smart course selection (find me a course to teach me "xxxxx")
    4. reporting for admins about all students on the system and where they are up to.
Retrieved from "https://docs.moodle.org/dev/index.php?title=Outcomes&oldid=2086"
Powered by MediaWiki