New Quizzes - Open Entry, Contains "Answer" Issue

[chanley12]

In New Quizzes, when choosing Open Entry for Fill in the Blank questions, there are options for 'Contains' and 'Exact Match'.  If I choose the 'Contains' option, put in the answer as "word", and then a student answers "Word", Canvas marks it wrong.

In my mind, case sensitivity should apply to the 'Exact Match' option, not the 'Contains' option.  As long as they spell it correctly, it doesn't matter if the 'n' is capitalized.

Is there a different way to set these up?  Or can this be a system-wide update in Canvas?  If there wasn't an 'Exact Match' option, I could see the reason for this, but since there is, it seems silly to me that all the student responses in the question shown below were marked wrong because of capital letters when they do 'contain' the correct answer.

 

[MatthewClifft]

Hi Chanley12, 

Thank you for reaching out. I took a look, but from what I found the closest option would be to set it to "close enough", set the Levenshtein parameter to 0 (meaning it has to be "word", and not words or wword), and ignore case sensitivity. This would achieve the result you're wanting, but outside of that, you will want to add both "word" and "Word" to your acceptable answers under the "contains" option.

This is functioning exactly as intended, though not as desired in this case. 

[chanley12]

Thanks for the suggestion.  I'm thinking the Levenshtein parameter would only work if "word" was the only thing I was looking for.  "Contains" means a student could have anything else before and after "word" and it would be counted correct, which is why I don't think it should be case sensitive.  The other workaround I was using is just taking the first letter off the answer so the system is only looking for "ord", which removes the need to worry about the capital or lowercase W.

[tfilipiak1]

I have the same problem.  ONLY the exact match option should be case sensitive...period!  This needs to change immediately.  I have hundreds of fill-in-the blank questions like this in the various courses I teach.  

Now with New (sucky) Quizzes, I can't even get what I want for a simple question like this.  It worked in "Old Quizzes" perfectly.  Now in new quizzes, open entry sucks. 

Just another example how programmers think new is better when actually new sucks....