Quiz scores are not always reliable
Hello
I am using Dokeos 2.0. I noticed that sometimes, the scores for some users do not correspond to the results the user actually got. This happens for any user.
For instance, a user had 3 attempts on a quiz. For the first one he got 56% of correct answers, then 100% for the next attempts. However, on his tracking data, his global score is 7%. Some other people have a score of 200%.
My quizzes are integrated in modules, and not in assessments.
We met this problem in around 10% of the cases. Has anybody met this problem also? Or would there be something wrong in the way I set up the quiz?
Thank you in advance for your help!
Best regards
Florent
- Vous devez vous identifier ou créer un compte pour écrire des commentaires

Quiz scores are not always reliable
Scores reliability
Hello Mohan
Thank you very much for your reply! I'm glad to read this bug is fixed.
Do you know when version 2.2 will be available?
In the meantime, is this bug something we can fix by ourselves in the source code of version 2.0?
Thank you
Florent
fixing scores in Dokeos 2.0?
Hi Mohan
Thank you very much for your reply. I'm happy to see this bug is fixed.
Do you know when Dokeos 2.2 would be available?
In the meantime, is there a way to fix this bug in Dokeos 2.0 by ourselves?
Thank you in advance.
Best regards
Florent
Hi,
Scores problem
Hi,
I also have score calculation problem.
For example, on a "reasoning" question, with 3 correct answers among 4, for 10 points :
With good answsers, the quiz correction displays 10/10. But the user mark attemped repport, it displays 9/10.
In the database, in 'track_e_attempt' table, I have marks=9.99 for this question.
(I think is't because there is 10 points for 3 good answers, so 10/3=9.99).
Is this bug will also be corrected with version 2.2 ?
And when the final 2.2 release will be avalaible ?
JmC
Score Problem
Thanks for your anwser. But
Thanks for your anwser.
But is it safe to put that beta version on final server ?
Generally, the beta should not be put into operation ...
JmC
RE:
is this bug something we can fix by ourselves in the source code of version 2.0?