Skip to content
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

Add a new 'progress bar' rubric option. #2035

Open
FrenjaminBanklin opened this issue Nov 2, 2022 · 2 comments
Open

Add a new 'progress bar' rubric option. #2035

FrenjaminBanklin opened this issue Nov 2, 2022 · 2 comments
Labels
assessment document engine package Issues relating to the obojobo-document-engine package editor enhancement New feature or request faculty request front end high priority new mode adds a new type of mode/interface questions involves obojobo questions (practice/assessment/etc) scoring involves the use of score / scoring viewer

Comments

@FrenjaminBanklin
Copy link
Contributor

FrenjaminBanklin commented Nov 2, 2022

Alternative to/extension of #547.

Official name could use some work, but the idea is that an additional option would be added to the assessment rubric that would enable a new kind of assessment grading scheme.

In this new grading scheme some percentage 'progress' is awarded per question answered correctly, and upon reaching 100% the student would receive full credit for the assessment and it would conclude immediately. Answering a question incorrectly would remove some percentage of 'progress' from the current total. Answering all questions before achieving a 100% score would submit the final percentage as the score for the assessment, or at least use that percentage in all further rubric calculations.

The percentage awarded/lost per correct/incorrect answer should be individually customizable. Ideally using this option would also add a progress bar to the viewer side so students would be aware of their progress. It may make more sense if this option is in the assessment three-dot menu rather than the rubric, since the final score could still be subject to rubric modifications.

@FrenjaminBanklin FrenjaminBanklin added enhancement New feature or request questions involves obojobo questions (practice/assessment/etc) editor front end document engine package Issues relating to the obojobo-document-engine package viewer scoring involves the use of score / scoring faculty request new mode adds a new type of mode/interface assessment high priority labels Nov 2, 2022
@FrenjaminBanklin FrenjaminBanklin self-assigned this Nov 2, 2022
@FrenjaminBanklin
Copy link
Contributor Author

FrenjaminBanklin commented Nov 4, 2022

My first idea was to add a new option to the assessment rubric with additional controls for the completion threshold and points to add/subtract for correct/incorrect answers. I may still end up going back to that at some point, but after getting the editor set up properly (at least as far as I could tell) it was immediately obvious that almost all of the problems will be on the viewer side.

Chief among those problems is that this will necessarily require that questions be presented to students one at a time. Unfortunately it doesn't look like there are any mechanisms to facilitate this right now, so it'll have to be a whole new feature. For the moment I've abandoned the rubric changes and gone with a much simpler change to the assessment settings to enable a 'pace' setting, essentially allowing authors to choose 'all questions visible simultaneously' or 'one question visible at a time'.

Adjusting the question bank component to track a 'current question' and only display one at a time isn't necessarily difficult, but ideally the assessment's 'Submit' button would be a 'Next Question' button until all questions have been answered, then it becomes 'Submit' after the last question is answered. I'm still trying to figure out how best to add functionality for keeping track of what the 'current' question is across all of the disparate components that need that information to function properly, but it also occurs to me that this is going to play havoc with resuming attempts.

Currently if an assessment is started and the user leaves before they finish, they're able to resume their attempt but each question needs to be answered again. If questions are presented to students one at a time this will necessarily have to change - the state of their attempt will need to be updated every time they move on from one question to the next, and when resuming an attempt the assessment will have to start them off back at the correct question. Not to mention keep track of all of their answers up to that point so scoring still works. Any given attempt already has a row written into the database tracking which questions are chosen for that attempt, I'm thinking of trying to tap into that process to also keep track of which questions have been answered and what those answers are.

Curious if @zachberry and/or @iturgeon have any ideas to potentially make this less painful, since I imagine most of the existing assessment-related code was written by one or both of you. I'm trying to figure it out as I go without inadvertently breaking anything, but it isn't really clear where all the moving parts are.

FrenjaminBanklin added a commit to FrenjaminBanklin/Obojobo that referenced this issue Nov 8, 2022
…te. Currently state is saved to the database correctly, next is figuring out how to apply that state when resuming an assessment attempt.
FrenjaminBanklin added a commit to FrenjaminBanklin/Obojobo that referenced this issue Dec 14, 2022
…nent. Adjusting logic in QuestionBank to properly display a single question when the current question index is 0.
FrenjaminBanklin added a commit to FrenjaminBanklin/Obojobo that referenced this issue Dec 20, 2022
@stale
Copy link

stale bot commented Jun 18, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We do this to keep our backlog under control, but we thank you for your contributions.

@stale stale bot added the stale label Jun 18, 2023
@FrenjaminBanklin FrenjaminBanklin removed their assignment Aug 3, 2023
@stale stale bot removed the stale label Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assessment document engine package Issues relating to the obojobo-document-engine package editor enhancement New feature or request faculty request front end high priority new mode adds a new type of mode/interface questions involves obojobo questions (practice/assessment/etc) scoring involves the use of score / scoring viewer
Projects
None yet
Development

No branches or pull requests

1 participant