28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 5: Student In<strong>format</strong>ion Toolbook<br />

This process worked because a person's email is accessible not only via an email program (like Pegasus), but also<br />

directly as text files. Because the folders for this course were given names, it is possible for Toolbook to to open and<br />

read them. The Toolbook page shown above is the one for the <strong>in</strong>structor. Discussion items orig<strong>in</strong>at<strong>in</strong>g from the<br />

<strong>in</strong>structor wound up on this page. A series of conta<strong>in</strong>ers were arrayed along the bottom of the page, with names which<br />

correspond to email folders. When there is content <strong>in</strong> these conta<strong>in</strong>ers, they are green; otherwise they are grey. When<br />

right-clicked, they enlarge so that the memos conta<strong>in</strong>ed <strong>in</strong> them can be read. When left-clicked, a program is run which<br />

imports the correspond<strong>in</strong>g email memos <strong>in</strong>to the conta<strong>in</strong>er for each student. Note that this load<strong>in</strong>g was a non-destructive<br />

process for the email folder (though it cleared the correspond<strong>in</strong>g Toolbook conta<strong>in</strong>ers first), so if a mistake is made, one<br />

can simply reload the email.<br />

The conta<strong>in</strong>ers of the top l<strong>in</strong>e of this bottom row conta<strong>in</strong>ed form data. This k<strong>in</strong>d of <strong>in</strong><strong>format</strong>ion looks different and was<br />

treated differently. The "exam_1,a4" button <strong>in</strong> the middle of the page scored exams, put scores <strong>in</strong> the conta<strong>in</strong>er to the<br />

right of the button, wrote an html feedback file for each <strong>in</strong>dividual, and created summary <strong>in</strong><strong>format</strong>ion about how well<br />

the class did on each question. After scor<strong>in</strong>g, the <strong>in</strong>structor reviewed questions with which <strong>in</strong>dividuals tended to have<br />

difficulty, and decided whether the question should be counted or not. Based on this, the <strong>in</strong>structor sometimes modified<br />

the exam scor<strong>in</strong>g process and reran the scor<strong>in</strong>g.<br />

After updat<strong>in</strong>g student pages, a program was run which created an html file which provided detailed <strong>in</strong><strong>format</strong>ion about<br />

what has been received from students, scores on exams (with l<strong>in</strong>ks to detailed feedback), and a summary of how the<br />

person was do<strong>in</strong>g to date. This <strong>in</strong><strong>format</strong>ion was publicly available from "posted scores" on the mg301 desktop, but<br />

published by "alias", as described earlier, so as to ma<strong>in</strong>ta<strong>in</strong> confidentiality.<br />

Feedback was also elicited from students for the purpose of improv<strong>in</strong>g the course. This occurred naturally, as students<br />

encountered difficulties and sought help, but <strong>in</strong> addition some short discussions on how to improve the course were also<br />

scheduled, <strong>in</strong>clud<strong>in</strong>g an end-of-semester evaluation.<br />

Student Response<br />

The course is halfway through its first semester, so more will be learned by the course's conclusion. At this po<strong>in</strong>t it is<br />

possible to identify both difficulties encountered by students as well as benefits which the course is provid<strong>in</strong>g.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!