[Building Sakai] Culling duplicates from SAM_ITEMGRADING_T

[Karen Tsao]

Hi Jushua,

The reason the script only cleans up null SUBMITTEDDATE records is we can
successfully reproduce duplicates with null SUBMITTEDDATE (SAM-758). If you
have duplicates that have not null SUBMITTEDDATE, these must be created in
other flow which we haven't found. Are these old data or some are lately
created?

Are these SUBMITTEDDATE different? How about other fields, eg, score? If
they are all the same except the SUBMITTEDDATE, I think it should be ok to
remove the earliest duplicates. But, I am not 100 % confident. Maybe you
can try this in your QA instance first?

Not sure if there are other schools encountered this issue. If yes, hope
they can give you some feedback.

Thanks,
Karen

The script does include a commented-out statement for those particular
> entries:
>
>  delete from sam_itemgrading_t where itemgradingid in (
>         select MIN(g.itemgradingid) from sam_itemgrading_t g where
>         g.agentid = r.agentid and
>         g.publisheditemid = r.publisheditemid and
>         g.assessmentgradingid = r.assessmentgradingid and
>         g.publisheditemtextid = r.publisheditemtextid
>         GROUP BY g.PUBLISHEDITEMID, g.AGENTID, g.ASSESSMENTGRADINGID,
> g.PUBLISHEDITEMTEXTID
>
> This seems pretty reasonable, to delete the earliest submission.
>
> Josh
>
> _______________________________________________
> 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"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130321/0e772a53/attachment.html