battis.net and I'm all out of bubble gum…

Click to download a PDF of this. Feel free to reuse it — just let me know, especially if you make any particularly effective tweaks.

This policy has been gestating for some time, and I started to formulate it in conversation with one of my students who had had a brush with the academic dishonesty fairy. I presented it in class last week, and I realized that it is as good a representation as I have of my homework policy. I’m not really interested in coming up with a suitably punitive formula for docking grades for lateness, and I don’t particularly care about negotiating reasonable extensions. Mostly, like my students, I just don’t want to be bothered. But, by golly, there are things that bother me, and it would be good to steer clear of them. And it’s worth knowing how they rank in my worldview. And this expresses it.

Better not to do your work than to cheat or plagiarize to finish your work. Better to ask for an extension at the last minute than to just not do the work. But noticeably better to ask for the extension in a timely manner.

I’m pretty sure that this both made sense to and stuck with my ninth graders.

October 29th, 2012

Posted In: Teaching

Tags: , , , ,

One of my responsibilities at Jewish Day School is to write a weekly “tech tips” column for the online faculty news. This is one such tip. This one is, perhaps, particularly our-setup-specific (My Classes, Handins, Returns, etc.), but I think that the core ideas are worth sharing to the world.

One of the real challenges that we confront when teaching in a digital classroom is that there are a tremendous number of documents, spread across a tremendous number of computers, often in tremendously varying states of completion. A team of faculty is coalescing around digital portfolios this spring, and file management is the single greatest challenge that we’re looking at initially.

With that in mind, it seems timely to suggest some best practices for working with files in the My Classes folder on FirstClass:

  • Email attachments hurt. If students are turning in their work an email attachments, it counts against their disk quota (which is pretty slim by this point in the year). And you have to open each and every single message to download the attachment so that you can read it. That’s a recipe for frustration. Instead, have your students upload their files directly to the Handins folder — they can just drag them from their computer desktop into the FirstClass folder (or choose Upload… from the File menu in FirstClass). Files in the My Classes folder do not count against anyone’s disk quota. The best part: you can now select a group of files in your Handins folder and drag them to your computer desktop to download all of them all at once (no more opening every individual email).
  • File names matter. Ask your students to include both the name of the assignment and their name in the name of the file that they’re uploading. If the students don’t put their name on their files, it’s a hassle to figure out who turned in what. And likewise, if they don’t put the assignment on the file, you’ve got to open the file to find out. The file names don’t need to be Homeric epics: “Feb. 18 Essay – Seth B.doc” works great as a file name.
  • Students can’t cheat from the Handins folder. They aren’t able to open other people’s work (or even their own), nor can they remove their work once it’s turned in (so no coming back with an “improved” version after the fact). In fact, the only person who can open the files in the Handins folder is… the teacher.
  • Students need to be told about the Returns folder. Every class has a Returns folder that has an individual folder for each student in the class. You can drag files you are returning to those students directly into those folders (from, say, your computer desktop). Only the student whose folder it is can open the folder and read the files (and they can’t change them). Plus, now you don’t have student files cluttering up your inbox and counting against your disk quota as email attachments!
  • Be clear, but firm. You’re teaching technical skills, and your students won’t get it right at first. Help them to turn in their files correctly (i.e. in a way that is easy for you to work with), rather than fixing their mistakes. Every mistake you fix will end up being a mistake you have to fix every time.

Obviously, the list goes on, but these five best practices should help cut through some of the chaos and confusion accompanied by the proliferation of documents produced by a digital classroom!

February 18th, 2010

Posted In: "Tech Tips" Column

Tags: , , , , , , ,

css.php