-
Notifications
You must be signed in to change notification settings - Fork 317
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
Mean of a question across instances #9698
Comments
I believe that will make the page too crowded, and the calculation required to perform that would impact the loading time of the page. This is usually the landing page for instructor view of an assessment, so the page should be lean and fast. If you feel this is a valid approach, I think a different page should be used for it. |
Would the question statistics table or the detailed question statistics table in the question_statistics page be viable? |
The original intention for this column was to show the "difficulty" of each question, to help instructors balance difficulties within pools, arrange the assessment so that questions start easy and then work up to hard, etc. I still this that this is something we need and that this is the right page for it. However, I agree that we don't want to be calculating this on the fly. Ideally we'd store this in a question stats table and update this as needed in the background (we should be doing the same for the instance question stats). Exactly what this column should show is also up for debate. Ideally I think we want to show (at least) two values per question:
The overall goal would be to show a predicted mean score (or maybe distribution of scores) for an exam, to help guide instructors when they are assembling questions into an assessment. Of course there are lots of unanswered questions above about exactly how to do this. Other factors such as shared questions make this even more complicated, but also more useful. I'm eager to try and work some of these things out. But as a first step, I think just getting some overall difficulty measure like (1) above would be great. |
A simple formula for difficulty estimation in multiple choice questions is P=R/T, where: P = difficulty Further iterations taking into account weighted questions could be seen as P = ∑Res/T*100, where: P = difficulty |
After analyzing the detailed question statistics provided by PrairieLearn we discussed a potential enhancement that could aid instructors in quickly understanding the difficulty level of questions. This feature would automatically categorize questions into "easy," "medium," or "hard" based on their median scores and the percentage of perfect scores achieved by students. Here’s a brief explanation of the proposed system:
This feature could be implemented as an additional analytic tool within the instructor dashboard, providing at-a-glance insights that can inform instructional adjustments and future question design. It would also be valuable for identifying outliers and ensuring that assessments are well-calibrated to measure a range of abilities effectively. Our first idea would be to implement this feature as an extra column in the question stats page, just as we did with the median. We would like to know what you think of this iteration and any suggestions would be more than welcome. |
A few corrections to this previous suggestion: Categorize the thresholds in order to not have a problem with multiple dimensions, here is a first draft of what they could be:
|
After discussion with the core dev group we feel that this issue is too complex for implementation at this point. Instead we recommend focusing on #9699 as originally discussed. |
In the instructorAssessmentQuestions tab, a method showing mean across all instances where the question is used will help professors and instructors have a direct comparison between the questions performance in the current assessment and the questions performance in general, making it an easy comparison for professors assessment of the class' academic situation. See image below:
The method will be implemented in the Mean across all instances column
The text was updated successfully, but these errors were encountered: