We will meet and chat with Mark Schlager, in TAPPED IN 2, in the EdPsy 387 Room. We'll meet with him at 6 pm (CDT) - please get to the room a few minutes before that.

Post your reactions in WebBoard by June 21 to the Schlager et al. paper and our discussion with Mark in the Schlager et al. conference. Put the URL of your posting in C-Base.

Skim through the articles in the "Guidelines" web site http://lrs.ed.uiuc.edu/guidelines . Find one to read in depth, and post your reactions in WebBoard. Search the web for a learning project that you find valuable for learning. Post in WebBoard a description. Find one that you can participate in as part of EdPsy 490 NET, the CTER course you'll be taking in July. One good place to look is the Global Schoolhouse Project Registry.

Enter your troubleshooting log entries to this point into the Troubleshooting Knowledgebase.

Read some of the "memorable troubleshooting stories" at http://cternt1.ed.uiuc.edu/troublestories/, rate some of the stories, pick your favorite story, and then enter a memorable troubleshooting story of your own.

Read Phil Agre's "Building an Internet Culture", especially the part about Julian Orr's research on Xerox technicians.

Reflect on your own troubleshooting, and post in WebBoard your description of how you handle technical troubles.

Read the Levin & Miyake paper (optionally go through the audio narrated Powerpoint).

As part of your own reflection on your troubleshooting, react to the Levin & Miyake paper, describing how your troubleshooting is similar and/or different from the process described there. Also reflect on the toubleshooting log and knowledgebase and the memorable troubleshooting stories, and how they do or do not help in your own troubleshooting. Pick your most memorable troubleshooting story (from the Memorable Troubleshooting site by someone else) and say a little about what makes it memorable for you.

Post in WebBoard a progress report for your major project. What have you done so far? What do you plan to do? What barriers have you encountered?

Respond to at least two progress reports that don't already have two responses, giving constructive feedback.