-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting wrong data from the report #3
Comments
Hi guys, I think the report is assuming that all the records on the mdl_grade_grades_history are generated by an user submission, but this is not fully truth. When some student makes a submission for an assignment or quiz, the platform inserts a record related with that activity on the grade_grades_history table but also generate more entries for the other activities on the course with a null grade. |
I just wanted to follow up on this and let you know that Guillermo and myself are willing to help provide steps to reproduce if necessary. Thank you. |
Carteret Community College would like to use this block but are finding that the report is inaccurate, that Bb Open LMS (our current host) will not support it, and we are therefore at a bit of a loss regarding getting the report fixed -- has any progress been made or will any progress be made toward addressing report accuracy? |
The comment here, https://github.com/remotelearner/moodle-block_censusreport/blob/MOODLE_34_STABLE/lib.php#L893, indicates that the intention of the report is to return the student's most recent grade but earliest submission date as the completion date. This makes sense. The shortcoming is in the initial pull of grades history data. The query filters out actions attributed to system, but there are other non-system events which create grades history events which are not the result of the student making a submission or an instructor grading that submission. In particular, Moodle commonly creates empty grades records. The creation of these records are recorded in grades history and are being captured by the Census report and treated as student submissions. I think the problem could be rectified by excluding grades history records where finalgrade is NULL. This should probably be done at least on the queries in these two locations: STEPS TO REPLICATE:
OBSERVED BEHAVIOR: EXPECTED BEHAVIOR:
OBSERVED BEHAVIOR: EXPECTED BEHAVIOR: This screenshot highlights a few variations of the issue. Brant Brown - enrolled on 6/5, has never logged in Lance Johnson - enrolled on 6/5, submitted quiz on 6/6 Henry Rodriguez - enrolled on 6/5, submitted quiz on 6/5 Steve Trachsel - enrolled on 6/6, has never logged in |
Hi guys,
When I generate the report several times, in some occasions I get different result from them even if the parameters are equal (course, start date and end date). Also I want to know what is the expected behaviour on the following scenario:
An user answered an activity on September and the teacher reviewed it on October. If I generate the report for the September month, I get an entry with the activity submission and the date is from September when the user uploaded its work. If I generate the report of October, I get an entry with the activity submission but the date is when the teacher grade the activity. Is this the expected result?
The text was updated successfully, but these errors were encountered: