Thanks for the thoughts.
I see the metadata/outcomes system, the grades system, and the portfolio system as being separate subsystems, but thank you for bringing up the relationships, as that should be discussed.
Firstly, the actual student-submitted material and *grades* will still be there, attached to the activities, and that's what provides the information about what/how specific outcomes were addressed. The metadata/outcomes/competencies just 'tags' the activities, but of course you can use this relationship to access the underlying grades/submissions/actions (depending on what that activity supports).
eg, an assignment tagged with a typical outcome statement like "Use analytical thinking to draw reasonable conclusions from observations" will have a grade attached to it.
Right now activities only have a single grade, but it makes sense that the next step for grading should allow multiple grades per submission: one per outcome (assuming the teacher in question is USING outcomes, because not everyone will be).
I would really like to see some clear consensus on how all these separate "rubric" grades can be managed. Are they boiled down into a single grade per submission via a formula? Or should all these "component" grades end up in the gradebook for manipulation/combination at that level? Should the final grades for a course also be expressed in outcomes or not?
And yes, portfolios can use this information too.
Please feel free to help refine the specs in the wiki and flesh it out!
http://docs.moodle.org/en/Development:Outcomes
http://docs.moodle.org/en/Development:Grades
Martin Dougiamas
Posts made by Martin Dougiamas
As far as I know "login as" is working ... can you file a bug in the tracker with details to reproduce the bug you saw?
In Moodle 1.7 and later it's very easy!
1) Go to Presets in the database you already set up.
2) Click "Save as preset" and give it a name.
3) Create a new database, and during setup, select the preset you made.
1) Go to Presets in the database you already set up.
2) Click "Save as preset" and give it a name.
3) Create a new database, and during setup, select the preset you made.
Note that we are STILL waiting for sourceforge to do the final step (which would take two minutes at most).
Sorry about the confusion.
The answer is rather simple though.
1) Don't assign any roles for the students manually (at site level or otherwise).
2) Make sure the courses settings use the "site default" enrolment method (should be internal enrolment by default).
That's it. You can still add enrolment keys etc as well if you want, just like always.
About the teachers who appear on the course list as tutors in 1.7 they are simply all people with "moodle/course:update" capability. You can still hide individual people by checking the "hide" box when you assign them a role there.
In 1.8 there is a new admin setting that lets you explicity choose which roles you want to come up as a "course manager" (which is a lot simpler).
The answer is rather simple though.
1) Don't assign any roles for the students manually (at site level or otherwise).
2) Make sure the courses settings use the "site default" enrolment method (should be internal enrolment by default).
That's it. You can still add enrolment keys etc as well if you want, just like always.
About the teachers who appear on the course list as tutors in 1.7 they are simply all people with "moodle/course:update" capability. You can still hide individual people by checking the "hide" box when you assign them a role there.
In 1.8 there is a new admin setting that lets you explicity choose which roles you want to come up as a "course manager" (which is a lot simpler).