-
Notifications
You must be signed in to change notification settings - Fork 26
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
feature request: hash to confirm completion #159
Comments
Happy to add hash generation to the tutorials. How does the following generic prompt look? And I'm guessing you'd want As for adding a "nonce", I think that would have to be implemented in learnrhash and then we can use a version of the functions that implements the output. I'm not sure if that's in scope for learnrhash, but I assume it might be. Tagging @rundel to chime in on that. |
That sounds great. I don't actually really care about checking the answers. I'd just like to be able to at least sort of verify that they did it. |
An idea that comes to mind is to modify / extend the |
@rundel That sounds good to me. |
Before the "Congratulations" page, there is now a "Submit" page that generates a hash that can be submitted. As per the discussion in OpenIntroStat#159, I modified the encoder_ui to require students to enter a name and ID. This name and ID are then encoded in the hash (as an "identifier" type), so that submitted names and IDs could theoretically be used to track tutorial completion.
…pletion Hash Generation feature added (OpenIntroStat#159)
Before the "Congratulations" page, there is now a "Submit" page that generates a hash that can be submitted. As per the discussion in OpenIntroStat#159, I modified the encoder_ui to require students to enter a name and ID. This name and ID are then encoded in the hash (as an "identifier" type), so that submitted names and IDs could theoretically be used to track tutorial completion.
#192 creates the following "Submit" page for all existing tutorials: This hash can be decoded to something that looks like the following: This code requires students to enter a name and ID before generating the hash and encodes that information in the hash as a new "identifier" type. Note that these "identifier" answers could be used to check the submitted names and IDs in an effort to track student progress (e.g., for participation marks). |
Issue closed with PR 192 |
Before the "Congratulations" page, there is now a "Submit" page that generates a hash that can be submitted. As per the discussion in OpenIntroStat#159, I modified the encoder_ui to require students to enter a name and ID. This name and ID are then encoded in the hash (as an "identifier" type), so that submitted names and IDs could theoretically be used to track tutorial completion.
Before the "Congratulations" page, there is now a "Submit" page that generates a hash that can be submitted. As per the discussion in OpenIntroStat#159, I modified the encoder_ui to require students to enter a name and ID. This name and ID are then encoded in the hash (as an "identifier" type), so that submitted names and IDs could theoretically be used to track tutorial completion.
I would love to have any way of verifying that students completed these, even something as simple as this.
I would be cool too if there was a random nonce (? I think I am using this term correctly?) appended, to discourage rampant cheating. For example, if the correct hash for completing the tutorial is:
536c43f3fe936e0804cc5e3b363d2279
Then have the thing randomly generate, say, a four-character hash that can be appended. Then student A will see:
536c43f3fe936e0804cc5e3b363d2279af83
and student B will see:
536c43f3fe936e0804cc5e3b363d22797b2c
That way, I'll still be able to tell that they did it by verifying the first part of the hash, but then if they cheat and text the hash to another student I will know.
The text was updated successfully, but these errors were encountered: