[Building Sakai] Samigo autoscore maxed out

[Geng, Kelly]

No, we didn't. I think when we tried to run the upgrade script, it failed
on the unique constraints because there already had duplicates in that
table. We were planning but never got to clean the duplicates. However,
when I look at the comments in that ticket, it seems to me that the cleanup
script is only dealing with cases when there are 2 same answers stored for
the same question, but we also have some single-selection multiple choice
questions having 2 different answers stored for the student. The display
code shows both answers ( 1 correct and 1 incorrect) and adds the points.
Is there a way to clean up those duplicates as well, say, to keep only the
latest one? I know there are multi-selection questions which need to be
differentiated from this case but I wonder whether some other tables can be
joined to pick those out?

Thanks!

Kelly


On Tue, Sep 17, 2013 at 9:43 AM, Sam Ottenhoff <ottenhoff at longsight.com>wrote:

> Kelly,
>
> Do you have the database index as described in SAM-775?
>
> https://jira.sakaiproject.org/browse/SAM-775
>
>
> On Mon, Sep 16, 2013 at 11:57 PM, Karen Tsao <ktsao at stanford.edu> wrote:
>
>> Hi Kelly,
>>
>> We just had one same report last week. However, we have not been able to
>> reproduce it yet. The questions that cause this problem are all multiple
>> choice single correct questions. How about you? Also, have you tried to
>> reproduce this issue?
>>
>> Thanks,
>> Karen
>>
>>
>>
>> On Mon, Sep 16, 2013 at 2:13 PM, Geng, Kelly <gengx at miamioh.edu> wrote:
>>
>>> Hi All,
>>>
>>> We got reported today that a couple of students in a class got a 22 out
>>> 20 on an auto-scored 10-question (2 points per question) quiz in Samigo. I
>>> checked the sam_itemgrading_t and saw 2 records with the same correct
>>> answers for the student. Apparently the scores were added twice to the
>>> final score.
>>>
>>> Has anyone else seen this? We are running 2.9.x r126207. This can be a
>>> severe issue because instructors won't notice the double-adding until it
>>> maxes out. Shouldn't only 1 score (latest probably) be counted for each
>>> item if nothing else can be done to prevent the double-recording?
>>>
>>> --
>>> Kelly
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>


-- 
Kelly
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130917/9fda0538/attachment.html