CHECKLIST FOR SATURDAY, OCTOBER 6

CHECKLIST

FOR OCTOBER 6, 2012 (5:00PM)

DAY 5

We will be meeting online again

Topic – Miscue analysis- retellings

Reading: Beers, Chapter 4

DUE:

v  Please make sure you’ve listened, coded, and uploaded your recorded miscues for the two stories (A Fishy Story and Nothing) by Wednesday, October 3 (6:00 PM).

Ø  Please scan a copy of your miscue markings (if you don’t have a scanner available you can take photos of your work as long as we can ALL read your miscue markings clearly

Ø  Post your two (2) miscue marking stories (both: A Fishy Story AND Nothing) to your SMALL online group discussion area on D2L by Wednesday, October 3, (6:00 PM).

v  By Saturday, October 6 (5:00 PM) look at how others in YOUR SMALL GROUP recorded miscues for these two stories (children).

v  As a group have an online discussion about similarities and differences in how miscues were recorded.

v  After identifying similarities and differences discuss why you made the marking you did. 

• Please engage in an online conversation (D2L small online group discussion area) in relation to your practice miscue coding (Nothing and A Fishy Story). 

Here is a friendly reminder of the directions printed on the Day 4 Blog (last week). 

• PRINT: Print a copy of each of the following: a) A Fishy Story, AND b) Nothing by Jon Agee.  I have already prepared triple-spaced, typed versions of these texts for our coding use. You can locate them in D2L-Content-Miscue Analysis Practice Sheets. 
• CLICK: Click on the story you are going to listen to below. 
• LISTEN, FOLLOW ALONG, CODE MISCUES: Listen, follow along and code miscues as if the reading is happening in live time.  Afterwards you may go back and code any miscues that you may have missed.  You are more than welcome to go back as many times as you would like.  I would just like you to try it once all the way through without stopping.  
• SCAN: Please scan a copy of your miscue markings (if you do not have access to a scanner you can take photos of your work as long as we [even old people like me] can ALL read your miscue markings). 
• POST: Post your two (2--both) miscue coding sheets (both stories--A Fishy Story AND Nothing) to your online discussion group area found on D2L by WEDNESDAY, OCTOBER 3, 6:00 PM 
• VIEW: By SATURDAY, OCTOBER 6 (5:00 PM) look at how others in your group recorded miscues.  
• DISCUSSION: This is not so you can catch others doing it wrong it is to be an opportunity to discuss with others how they went about the process.  It is to be an opportunity to learn from others.  Thus, as a group have an online discussion (on D2L-- your group discussion area) about similarities and differences you see in how coding was done between the members of your group. 
• COACHING/COLLABORATIVE LEARNING: After identifying similarities and differences discuss why miscues were coded the way they were.  If this was being done in a face-to-face class I would allow you to get into your groups to discuss similarities and differences.  After seeing and hearing how and why some one else coded the miscues in the manner they did I would allow you to make changes to your document.  You do not need to go back and make those changes for us to see, but if you would like to on your paper, so you have it as a record feel free to do so.  The purpose of the activity is to practice coding miscues collaboratively.  Please use these space to practice, coach and learn from each other.