Have you tried component correctness yet? When students are asked to do multiple tasks on a screen, the dashboard summary view might be too general to give you a complete understanding of correctness on that screen. Component correctness can help provide a clearer and more nuanced picture of student thinking.
Take, for example, this summary view, which tells us that the majority of the students really struggled with this screen:
But when we switch to teacher view and select “Show Correctness,” it reveals that most students were successful on questions 1 through 3, and many students seem to have difficulty with just the fourth question:
Opening up a student’s screen confirms this:
Getting Fancy
Component correctness is great by itself in most cases, but what happens when overall screen correctness isn’t based on what's in the component at any given time? Take for example, screens that offer repeated practice like this one:
This screen is marked correct once a single correct answer is found, which means that any input after this will be marked correct regardless of whether it is actually correct or not.
We can fix that with something we call a “dashboard summary graph.” Here’s how it works:
Create a graph that displays the statistics you want to see. Here we’re looking at correct responses.
Place the graph below your visible graph display to hide it from the mini screen.
Mark the graph as hidden: true and make any necessary CL connections.
Use the hasResponse sink to indicate that the graph has a response once the first challenge has been completed.
Once you have the summary graph set up, fix correctness:
Add the screen level correctness to the summary graph.
Add the current challenge correctness to the math input, then mark the math input as readOnly: true. Fun fact: Component correctness ignores readOnly.
