Thank you for taking on this project, Martin
GRADEKEEPER CODE GENERATOR SOFTWARE
As I think about how our current gradebook software works, it does not provide the functionality that I am suggesting except through an export of the data and it may well be especially with this first attempt to improve the gradebook that the best idea is to have a powerful export feature whereby the snapshot could be exported and maintained outside of Moodle. However, I have not had a chance to carefully review the information in MoodleDocs about this. As I understand the gradebook functionality being developed it will be great for assessing the current grade but it will not allow for snapshots. Hence, what I am looking for is a snapshot whereby the grade is copied to a separate table. I would not want the entering of the grade in the 4th Week to impact the activity grade for the 3rd Week Grade Check. Then in the 4th Week they complete the assignment and the grade is entered. A student may have not completed an assignment for the 3rd Week Grade Check and have a zero on an assignment. I would need an assignment to be in 3rd Week Grade Check, 6th Week Grade Check, etc. The first semester is made up of six 3-week grading periods. Is it possible to have an activity in more than one grade category? The reason I was suggesting a separate table for a snapshot was to keep the history at a given point in time. I will look more closely at it to make sure I understand it. Martin - It is likely that what I am talking about with grading periods will be covered with grade categories.
GRADEKEEPER CODE GENERATOR MANUAL
For automatic grading (such as quiz questions) the notes would be handled automatically ('regraded by quiz'), but for a manual override, the teacher could be forced to explain ('spoke with student and we did extra work'). The 'version' field would numerically show the grading changes and the 'notes' could offer an explanation. Is there a way we could add a few fields to maintain that marking history? I could see value in a 'version' field and a 'notes' field.
In the proposed solution, when a grade is changed the times it was changed and the user that changed it are recorded but the old information is lost. The plan is that this is handled by the manual grade lock, or should that information go back to the assignment?Īnother function that I could see as valuable would be retaining a history. So, an interface exists somewhere that a user can override a grade for an assignment. Will the gradebook communicate back to the modules ever? An example would be where an external system is integrated with Moodle that communicates grade information back to a module - I know this is rare, but it does come up. what is the grade for this user for this activity), but I guess the event system will handle that providing the gradebook itself has all the necessary informational funtions. I was initially thinking that there would be more 'required' functions added to the module API to handle getting grades (e.g. I'm looking forward to your comments and questions! Nevertheless, your input on these aspects in the spec is very welcome too, as it's going to be difficult to cram all this functionality into an accessible, simple interface. I hope we start having a lot of community-contributed plugins to do graphing and all kinds of funky things. Extensions like "gradebook 2 plus" will in future be very easy to write as clean plugins, efficiently drawing from the exact same database of grades and just displaying them differently.
The actual interface is LESS important at this stage because we will have a new plugin structure for displays/reports (as well as import/export!). Note also that numerical grades, scale-based grades AND outcomes-based rubrics are all supported in this model.
Note the new events API which will take care of modules notifying each other of important grading events. The most important things to look at are the underlying structures for storing data and the mechanisms for transferring grades. Our draft spec for the new Gradebook in 1.9 has been evolving based on all the feedback I've been getting and I'm now seeking wider community input before Moodle HQ start implementing it for 1.9 over the next couple of months.
0 kommentar(er)
