Note:

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

Gradebook improvements: Difference between revisions

From MoodleDocs
No edit summary
(more flexible export plugins)
Line 14: Line 14:


==Tracking of submission dates==
==Tracking of submission dates==
==Exports: more flexibility==
Two aspects of the 1.9 export plugin have been criticised by some of Catalyst's clients:
* the fact that grade exports are tied to a course
* the default user profile columns are not all needed and some custom ones would be necessary
Therefore I propose the following changes:
* removing the export plugin dependency on a single course by converting to an array of courses (see [http://tracker.moodle.org/browse/MDL-17420] )
* making the user-related columns customisable (see [http://tracker.moodle.org/browse/MDL-17346])


==See also==
==See also==


* [[Tim's_Gradebook_thoughts|Tim's Gradebook thoughts]].
* [[Tim's_Gradebook_thoughts|Tim's Gradebook thoughts]].

Revision as of 04:42, 9 December 2008

Moodle 2.0


Same aspects of gradebook were not fully solved in 1.9.x, this page tries to summarize potential improvements

Aggregation of hidden grades

Overlook problem partially solve after the database freeze - workaround was to recalculate the grades on the fly so that users that can the hidden grades are ignored. This approach is expensive and can not be used in conditional activities, grade exports, etc.

Solution is to add new flag into grade categories - aggregate hidden grades. Having two values for each grade would be too complex, selective agrragation should solve most of the problems and should be reasonably backwards compatible.

Final grading in activities

Effectiveness of grading interface

Tracking of submission dates

Exports: more flexibility

Two aspects of the 1.9 export plugin have been criticised by some of Catalyst's clients:

  • the fact that grade exports are tied to a course
  • the default user profile columns are not all needed and some custom ones would be necessary

Therefore I propose the following changes:

  • removing the export plugin dependency on a single course by converting to an array of courses (see [1] )
  • making the user-related columns customisable (see [2])

See also