[samigo-team] samigo-team Digest, Vol 4, Issue 3

Tue Oct 18 04:55:40 PDT 2011

Hi all,

I know the original info on Samigo settings (thanks Lynn) got sent out
awhile ago, but here is some similar info related to the "allow
retake" button. This is pulled from an article I wrote for our
knowledge base on using "allow retake," based on my research (version
2.7.1):

**If the due date/retract date for an assesment has not yet passed,
the CLE will only display the "Allow retake?" link if a student has
submitted an assessment the maximum number of times allowed for the
item. In addition, if you have selected an unlimited number of
submissions allowed for an item, the CLE will NOT display the "Allow
retake" link for any student.

**You may use the the "Allow retake" link as many times as you would
like. After you allow a retake and a student submits the assessment,
the CLE will once again display the link for that student.

**If the due date for an assessment has passed and you chose to accept
late submissions, the CLE will display the “Allow retake” link for any
student who has submitted the assessment at least once. If the due
date has passed and you chose NOT to accept late submissions, the CLE
will display the "Allow retake" link for all students--even for those
who did not submit.

**The CLE may display "Allow retake" links for students even if the
assessment has been retracted. In this case, you may click on a link
and allow a retake, but the assessment will NOT be available to the
student.

Best,
Jim Mezzanotte
rSmart

On Tue, Oct 4, 2011 at 3:47 PM,
<samigo-team-request at collab.sakaiproject.org> wrote:
> Send samigo-team mailing list submissions to
>        samigo-team at collab.sakaiproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://collab.sakaiproject.org/mailman/listinfo/samigo-team
> or, via email, send a message with subject or body 'help' to
>        samigo-team-request at collab.sakaiproject.org
>
> You can reach the person managing the list at
>        samigo-team-owner at collab.sakaiproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of samigo-team digest..."
>
>
> Today's Topics:
>
>   1. starting a discussion about SAMigo Settings (Ward, Lynn E.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 4 Oct 2011 19:47:00 +0000
> From: "Ward, Lynn E." <leward at iupui.edu>
> Subject: [samigo-team] starting a discussion about SAMigo Settings
> To: Samigo Team <samigo-team at collab.sakaiproject.org>
> Message-ID: <CAB0DAEA.3DA81%leward at iupui.edu>
> Content-Type: text/plain; charset="windows-1252"
>
> Hi everyone,
>
> At today's call, I promised to forward a little write-up a did about some of the confusion our users have been experiencing related to assessment settings in SAMigo, along with some possible solutions.  I've pasted the relevant bits of the original Word doc below and attached a copy as well in case the formatting gets messed up in transit.    This is intended primarily as a conversation starter, so please give some thought to the Settings pain points are your institutions.  Also, I should mention that these observations reflect the behavior of our local instance, which is currently SAMigo 2.7 with some additional fixes and enhancements, including some 2.8 code that we merged locally.
>
> I will also be forwarding a note with a design for handling settings exceptions for individuals and groups, but I'll do that in a separate email.
>
> ===============================================================================================================
>
>
> Problem 4:  General confusion around Delivery Dates and Submission options
> Problem Description: Whether and for how long an assessment is available for students to take is determined by many different factors. The behavior around due dates and retract dates, described below, is complex and difficult to predict, especially when combined with other settings.  At IU this has  led to poor settings choices by instructors and ultimately creates submission problems for students.
>
> A.    Due Date
>
> On the surface, the Due Date is a simple concept, but as illustrated by the pointsbelow, the due date both impacts and is impacted by other Settings options in ways that are not always obvious.
>
> ?      For assessments that don?t accept late submissions, the Due Date determines both the latest date astudent can start AND the latest date a student can submit an assessment.  This duality of function allows for situations where a student starts an assessment only seconds before it closes.  After the Due Date, theassessment is no longer visible in the Take an Assessment Screen of the student view.
>
> ?      For assessments that accept late submissions, the Due Date determines the date after which any submission will be flagged as late.  The assessment continues to be visible in the student?s ?Take an Assessment? list after the Due Date has passed, but the date changes from black to red indicating the late status.  In the instructor view, the assessment moves from the Active to the Inactive group (NB: the assessment should probably remain active since student can still take it).
>
> ?      For timed assessments that don?t allow late submissions, the timer is automatically adjusted if the time between when the student started and the Due Date is less than the time limit.
>
> ?      For timed single submission assessments that allow late submissions, students get the full amount on the timer, even if the time between when the student started and the Due Date is less than the time limit.  Submitting after the due date marks the submission as late.  Currently the timer is not adjusted for the retract date.  However, for timed multisubmission assessments that allow late submissions, prior submitters who attempt to submit again are required to submit by the due date (even though first time submitters may continue working after the due date).  Prior submitters see the full amount on the timer even if the time between when they started and the Due Date is less than the time limit, giving them the impression they have more time to work than is actually available.
>
>
> B.    Retract Date/Status
>
> Use of the term ?retract? and associated behavior in Samigo is laden with ambiguity. To help clarify the purpose of the retract date, the following explanation was added beneath the field in Samigo 2.8.
>
>
>
> ?An assessment is not open to students to take after the retract date or after the 'Retract Now' button is pressed. However, assessments with feedback enabled (Feedback > Feedback Delivery) will continue to beaccessible to students who have taken and submitted them prior to the retraction. Students will see these assessments under their Submitted Assessment list.?
>
>
> The identical statement, however, applies equally to the Due Date when late submissions are not accepted.  In fact the Retract Date has no impact on assessments that don?t allow late submissions unless it occurs earlier than the Due Date.  In the case of assessments that do allow late submissions, the retract date functions as the late submission deadline.
>
>
>
> When Retract Now is used to withdraw an assessment immediately, the retracted item looks no different than any other item in the Inactive assessments list. In the following screenshot, for example, two inactive assessments have identical release and due dates.  To the instructor, it appears that both will be available to students on July 1.  But the second was retracted via the Retract Now option and won?t become available unless the instructor takes another action.
>
>
>
> [cid:39EC10C6-EDC4-4477-A396-5A6F6239F4E9]
>
>
>
> It?s also worth noting that the Retract Now option overwrites whatever value was in the Retract Date field (which may have been the late submission deadline) with the current date and time.  Confusing the matter further is the fact that, when an assessment is retracted immediately for editing, the Retract Date is not changed at all (if originally blank, it isleft blank; if it contains a date, the date is not updated).  Instead the assessment is flagged with a double red asterisk.  In this later case, it seems, retract is functioning as a status, not a date.
>
>
>
> For instructors, the action of retracting a test is often connected with making a change or correction to the assessment or permanently removing the assessment from the student view.   The inclusion of a ?Retract Date? in the delivery schedule muddies the purpose and meaning of the word.
>
>
>
> Current Retract Behaviors
>
>
>
> ?      The Retract Date is not displayed on any screen in the student view.  Thus, the student may not be aware of the latest possible start or submit dates.
>
> ?      The application allows instructors to enter a Retract Date without providing a due date, which doesn?t make sense unless the instructor has clicked Retract now.
>
> ?      For assessments without a Duedate, the Retract Date determines both the latest date a student can start AND the latest date a student can submit an assessment.   Here again, this dual purpose can lead to undesirable situations.
>
> ?      For assessments with a Due Date that don?t accept late submissions, the Retract Date has no affect on the availability of the assessment unless the retract date precedes the Due Date, which is itself an anomaly.
>
> ?      For assessments with a Due Date that accept late submissions, the Retract Date determines the latestdate a student can start AND the latest date a student can submit.
>
> ?      If the instructor clicks Retract Now, the value in the Retract Date field is replaced with the current date and time.  If the original value was intended as the late submission deadline, it must be re-entered when and if the assessment is re-activated.
>
> ?      If the instructor edits an in-progress assessment, the assessment is retracted, but the Retract Date field is unchanged, suggesting that it?s possible to retract an assessment without a value Retract Date.
>
> ?      Students continue to see retracted assessments in their list of Submitted Assessments.
>
> ?      In the instructor view of theassessments list, there is no visual distinction between assessments that are inactive as the result of an available date or due date and those that havebeen retracted.
>
> Proposed solution(s):  It?s not reasonable to expect instructors to understand and remember all of the nuances and dependencies among the Settings options described above.  To simplify and clarify the delivery settings and behavior, the following changes are suggested:
>
>
> A.    Revise the Delivery Dates Settings screen, renaming and using the current Retract Date field exclusively as a late submission deadline.   Reserve use of the word ?retract? to refer to a ?status? (as opposed to a date) for published assessments that overrides any and all date settings and completely removes all vestiges of the assessment from the student view.
>
> Settings > Delivery Dates
>
> [cid:5C52CADA-0C4A-49D4-93F4-8B19052FACC8]
>
> Notes:
>
> ?      Change the layout and prompts as shown above
>
> ?      The Retract Date and Late Handling (from the Submissions section of Settings) have been combined into a single section call Late Submissions.
>
> ?      If late submissions are accepted, the assessment remains in the Active (in-progress) grouping until the late submission date passes or all students have submitted.
>
> ?      If the user checks the ?Accept late submissions until? box without entering a due date, uncheck the box and display the error message: A Due Date is required if late submissions are accepted.
>
> ?      If the user enters a late submission deadline without checking the ?Accept late submissions until? box, remove the late submission date and display the error message:  ?Accept late submissions until? must be checked in order to enter a Late Submissions date.
>
> ?      If the late submission date is earlier than the due date, remove the late submission date and display the error message:  The Late Submissions date cannot be earlier than the Due Date.
>
> Settings > Delivery Dates - Published Assessment, Not Retracted
>
> [cid:A9168D3A-65C2-4113-9275-CE75EDF57A74]
>
> Notes:
>
> ?      Clicking Retract Now moves the assessment from the Active or Inactive list under Published Assessments, see item c below.
>
> ?      The retracted assessment does not appear in the student?s Take an Assessment list, regardless of the delivery dates.
>
> ?      The Allow retake option does not display in the Submission Status screen.
>
>
>
> Settings > Delivery Dates -  Published Assessment, Retracted
>
> [cid:7489022F-04EE-4700-A8DD-8A3634F33E61]
> Notes:
>
> ?      Clicking Republish returns the assessment to the Active (Open) or Inactive (Closed) list of published assessments, depending on the delivery dates and late submission setting (and whether Retake has been activated for one or more students.
>
>
>
>
> B.    Use something other than the late submission date to mark retracted assessments (for example, add a Boolean ?retracted? field), and create a separate category for retracted assessments under a under Published Assessments in the instructor view.
>
> Assessment List > Published Assessments ? Instructor View
>
> [cid:10F7EFDC-7311-4E40-9E97-255639323B48]
>
>
> Notes:
>
> ?      Published assessments are broken into three categories, Open (Active in generic Sakai), Closed (Inactive in generic Sakai, and Retracted
>
> ?      Retracted assessments should not display in the student view at all. If the student has submitted a retracted assessment, it should be removed from the Submitted Assessments list until the assessment is republished.
>
>
>
>
>
>
> C.     Moving the late submissions option to the Delivery Dates section of Settings as proposed in section A above necessitates changes to the Submissions section as follows:
>
> [cid:512062A3-4954-416B-9BE7-6FAF33DADEEE]
> Notes:
>
> ?      The late submission option nolonger appears in the Submissions section
>
> ?      If enabled via Sakai properties, the schedule for Automatic Submission process is determined by the DeliveryDates and Late Submissions settings as follows
>
> o   If late submissions are not accepted, in-progress assessments are auto-submitted after the due date.
>
> o   If late submissions are accepted, in-progress submissions are auto-submitted after the late submission date.
>
> ?      If late submissions are accepted and the late submission date is empty, remove the check from the Automatic submission box and display the error message: A Late Submissions date is required if Automatic Submission is enabled.
>
>
> D.    Longer term suggestion ? change submission deadlines to access deadlines.
>
> (Note: This suggestion would likely extensive changes to application, but would eliminate the functional ambiguity of the due and late submission dates [i.e., the same date serving as both the latest date an assessment can be started and completed]).  Our legacy tool, Original Test and Survey, takes a slightly different approach delivery dates.  Instead of due/late submission dates, the instructor is prompted for a Deny Access After date.  This date determines the latest date a student can see (and therefore start) an assessment.  As long as the student can see and start the assessment, they get the full-allotted time. If the assessment is untimed, the student can continue working until they logout, their session times out, orthey submit.   This approach completes solves the issue or students being locked out of untimed tests, identified as Problem 1 above.  It also makes the intended behavior of the delivery dates much more transparent to the instructor.  To accommodate late
>  submissions, the field labels fot the delivery dates could be:
>
> o   Deny Access Before
>
> o   Deny Access After
>
> o   Mark As Late If Started After
>
>
>
>
> ==========================
> Lynn Ward, Principal Systems Analyst
> Instructional Technology Systems and Services
> University Information Technology Services<http://uits.iu.edu/>
> Indiana University
> Information Technology and Communications Complex (IT 342J)
> 535 West Michigan Street, Indianapolis, IN 46202
> Phone: 317-278-5713  E-mail: leward at iupui.edu<mailto:leward at iupui.edu>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment.html
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 39EC10C6-EDC4-4477-A396-5A6F6239F4E9.png
> Type: image/png
> Size: 29055 bytes
> Desc: 39EC10C6-EDC4-4477-A396-5A6F6239F4E9.png
> Url : http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 5C52CADA-0C4A-49D4-93F4-8B19052FACC8.png
> Type: image/png
> Size: 18605 bytes
> Desc: 5C52CADA-0C4A-49D4-93F4-8B19052FACC8.png
> Url : http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment-0001.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: A9168D3A-65C2-4113-9275-CE75EDF57A74.png
> Type: image/png
> Size: 34212 bytes
> Desc: A9168D3A-65C2-4113-9275-CE75EDF57A74.png
> Url : http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment-0002.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 7489022F-04EE-4700-A8DD-8A3634F33E61.png
> Type: image/png
> Size: 34442 bytes
> Desc: 7489022F-04EE-4700-A8DD-8A3634F33E61.png
> Url : http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment-0003.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 10F7EFDC-7311-4E40-9E97-255639323B48.png
> Type: image/png
> Size: 63607 bytes
> Desc: 10F7EFDC-7311-4E40-9E97-255639323B48.png
> Url : http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment-0004.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 512062A3-4954-416B-9BE7-6FAF33DADEEE.png
> Type: image/png
> Size: 25322 bytes
> Desc: 512062A3-4954-416B-9BE7-6FAF33DADEEE.png
> Url : http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment-0005.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Settings Issues.docx
> Type: application/x-msword
> Size: 421197 bytes
> Desc: Settings Issues.docx
> Url : http://collab.sakaiproject.org/pipermail/samigo-team/attachments/20111004/404b2df7/attachment.bin
>
> ------------------------------
>
> _______________________________________________
> samigo-team mailing list
> samigo-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/samigo-team
>
>
> End of samigo-team Digest, Vol 4, Issue 3
> *****************************************
>