Yes, good one. I've added all that to the core API.
I'm not sure about locking on a per-module basis ... with this function the assignment can easily detect what is changeable for a given assignment and disable the individual outcomes in the GUI that are locked.
Martin Dougiamas
Posts made by Martin Dougiamas
Hi, Bruno
History - I think there is enough data in the grade_history table now to do that (and you can do it as a custom report) but it's going to be quite a job ... I'm not even sure if plotting grades vs time is really going to be meaningful.
Cross-course events - are you saying that you want the "overall" grade from one course to appear as a column (grade_item) in another course? Hmm ...
Overall reports - yes, no problem. I also want to see a report based on the outcomes specifically (across courses) that will be an excellent way of seeing what each student has done and can do.
History - I think there is enough data in the grade_history table now to do that (and you can do it as a custom report) but it's going to be quite a job ... I'm not even sure if plotting grades vs time is really going to be meaningful.
Cross-course events - are you saying that you want the "overall" grade from one course to appear as a column (grade_item) in another course? Hmm ...
Overall reports - yes, no problem. I also want to see a report based on the outcomes specifically (across courses) that will be an excellent way of seeing what each student has done and can do.
My feeling is to leave metacourses alone and perhaps just add an ability in the GUI to "subscribe" to grade_items in other courses (which would make things completely flexible and people could choose whatever combinations they liked). You'd need appropriate permissions of course.
Some thought would have to be given about students ... my guess is that adding a column will NOT affect the rows, so that you only always see the grades for students enrolled in the current context.
Some thought would have to be given about students ... my guess is that adding a column will NOT affect the rows, so that you only always see the grades for students enrolled in the current context.
Yes, we should talk about pass/fail too.
Does it make sense to add this column to every grade_item as well?
It could just be a simple float value which would get compared against the normalised final value for each grade stored in grade_grades_value.
In the GUI it would be easy to colour cells green or red depending on the converted value (even for rubric scales). If the cutoff is == grademin (the default) then we can just ignore it and do no coloring.
I think this would be simple to implement, so I've added 'gradepass' to grade_items and grade_categories. This would also work for calculated columns.
Does it make sense to add this column to every grade_item as well?
It could just be a simple float value which would get compared against the normalised final value for each grade stored in grade_grades_value.
In the GUI it would be easy to colour cells green or red depending on the converted value (even for rubric scales). If the cutoff is == grademin (the default) then we can just ignore it and do no coloring.
I think this would be simple to implement, so I've added 'gradepass' to grade_items and grade_categories. This would also work for calculated columns.
Great! I really hope this work can be refactored into Gradebook plugins in 1.9 (probably one report and one export plugin).