[Building Sakai] samigo auto submit

[Sam Ottenhoff]

One additional note: do *not* run the quartz job if there is a chance
of a student taking the assessment in between the due data and the
retract date.  The student's assessment will submit, and the student
will receive a data discrepancy error:

  https://jira.sakaiproject.org/browse/SAM-1088

--Sam

On Tue, Jul 26, 2011 at 8:22 PM, Karen Tsao <ktsao at stanford.edu> wrote:
> Hi Mukul,
>
> At Stanford, we run it once a day at midnight.
>
> I would like to emphasize this is a way to help those students who save
> their assessments but forget to submit it. It should not be the main/normal
> way to submit assessments. So normally there should be none or very small
> amount of un-submitted assessments to get submitted by the auto-submit job
> everyday.
>
> We didn't do detailed performance testing. However, we know there will be
> performance impact and that is why we make this as a quartz job and run it
> at midnight (the low load period). And we have no bad performance reported.
>
> Thanks,
> Karen
>
> On Tue, Jul 26, 2011 at 4:40 PM, Mukul Tiwari <mtiwari at rsmart.com> wrote:
>>
>> I'm wanting to know what the frequency of the cron job associated
>> with samigo.autoSubmit.enabled=true should ideally be and if anyone has seen
>> any performance issues with it.
>> _______________________________________________
>> 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"
>