Semi-automatic reconciliation of missing/duplicate answers (Feature #383)
Description
One feature I think would help in using AMC for large classes is to assist a little more in resolving data capture problems.
What I'm thinking is of enhancing the Manual data capture window with information from the marking/report stages. In the ods reports, cells are highlighted to indicate missing and duplicate answers. I'd like to see the Manual Data Capture window use this same information by implementing "Next Error" and "Previous Error" buttons to allow the user to jump rapidly between pages where there are missing or duplicate answers. This would dramatically speed up finding and correcting these kinds of errors in large classes.
Pressing "Next Error" would jump to the next page where a duplicate or missing answer was located. It would show the scan image and allow for manual selection of the answer that the student intended to select. In that way, correcting such an error would take just two clicks.
The buttons could be greyed out if the marking hadn't yet been done.
Bonus points if the answer boxes in question are highlighted on the scan image!
History
Updated by Carl Michal over 8 years ago
I made an attempt at adding this feature to the gui. I am a complete novice when it comes to perl, and this is likely quite obvious from the code.
After applying this patch, a couple of new buttons are added to the Manual Scan window. After 'Marking,' you can now go back to the manual scan window and jump through all the questions
where the 'why' code is V or E. Answers can then be filled in by hand (mouse) if the student's intention was obvious. All answers associated with the question are highlighted in green boxes.
A couple of runs here with large classes shows this really speeds up tracking down issues in the response sheets.
The patch applies cleanly to 1.2.1 in the AMC-perl/AMC directory.
- File add_assisted_conflict_resolution5.patch added
Updated by Alexis Bienvenüe over 8 years ago
Thanks for your suggestion and patch.
I tried to highlight these boxes with hg:5ccfd744ba0c.
I think we have to make a difference between V and E, because E is always an error, but in some cases a lot of students don't check any boxes for a question, because they don't know the answer at all (and perhaps some negative scores can be obtained for very bad answers, so a random answer is not a good thing).
Can you adapt your patch to the development version (mercurial repository)?
Updated by Carl Michal over 8 years ago
Thanks for the feedback!
I suppose one could have a preference setting to choose which of E and V are highlighted? I actually prefer it the way it is, I want to find all instances where there are too many or too few responses and verify the student's intention. Even if you expect some V's, I would want to check that its not just a response that is too light to be detected.
I will try to update to apply to the current development version.
It will probably be a couple of weeks till I can get back to this.
Updated by Carl Michal over 8 years ago
Adapting to the current development version was actually very quick. It turns out that some of what I did to draw boxes around the missing/duplicate answers was already done in the development version, but in a more robust way, so this patch is a little smaller.
No work done on preferences - that's a bit out of scope for me.
- File add_assisted_conflict_resolution6.patch added
Updated by Alexis Bienvenüe over 8 years ago
Thanks for the patch: integrated with commit hg:841ac79b2862.
Updated by Alexis Bienvenüe about 8 years ago
- Target version set to 1.3.0
- % Done changed from 0 to 100
- Status changed from New to Closed