Thought I would share this post from Google (thanks, MB, for forwarding it along) about a new technology Google is testing to facilitate online course design. According to Google’s Blog, their online course on Power Searching was so successful that they decided to adapt the technology they used to create a version for public use. It appears still to be in the testing phase but would seem to have a lot of potential. I don’t drink the Google kool-aid entirely but this seems like an area where they might excel.
September 30, 2012
September 28, 2012
I wrote a few weeks ago about how I was proudly using iCal to share student assignments. A few days ago I updated the calendar, strode into class, and declared that students now had another few weeks of assignments on their calendar. Or they didn’t. No updating. No lovely colored rounded rectangles. Nothing. I realized that downloading the file that put those assignments on their computer didn’t subscribe them to the calendar, and without a subscription they wouldn’t receive updates. So an edit to the previous post. Here’s the (new) process:
- still starting at iCloud with the shared calendar link
- copy the link and email it to students
- students go into their iCal to the Calendar menu and hit Subscribe….
- the link is then pasted into that window
- (hopefully this should do it…)
September 28, 2012
The age-old problem: how to track students’ volunteering for game show-type activities? I’ve used a bunch: Eggspert (which the kids loved, but just took too long to set up), the ol’ hand slapping the desk, raising the hand, even just shouting out. The best option I had was at my old school, Bancroft School in Worcester (MA), where the language lab would keep track of the order in which students used the ‘call’ button, so the call button in effect became the buzzer.
With the 1:1 I figured there had to be some sort of computer based way to do this, so I hit the App Store. Indeed, there was. Buzzers.com has all sorts of buzzer-type paraphernalia, including an app for both the computer and portable devices. Even better, the app was free. Sounded good. Problem was twofold, though. 1. All computers had to be on the same network (a common requirement, and one that we at least don’t have; my computer is on a different network from the students’); 2. the structure of the app seemed too restrictive, i.e. it seemed that you could have two teams of five each, while I wanted probably 8 or 9 teams of 2-3 each. Back to the drawing board.
What I really wanted was just a button on the students’ screen that they could click on that would then somehow record the order in which that button was clicked. I knew that GoogleForms timestamped all entries, so I wondered if that would work. And for the most part it did. It’s not the most elegant solution, I’ll admit; I wish there were a bit more customization available (I wanted that button but had to settle for a text box), but overall it mostly worked, and the students seemed to enjoy it.
The process is pretty basic:
- one field: student name
- the process: students type their name in the form but don’t hit submit
- the question is read
- the submit button becomes the buzzer
- the form on my computer autopopulates as students buzz in
- (interestingly enough, there were a number of ties time-wise on the form, but I went with the top name; I wonder what puts a name at the top; does Google time it beyond hundredths of a second but only shows hundredths? or does it somehow randomize the ties?)
The one adjustment I would make, and this is only for those of you whose school use Google for email, etc., is that I would require students to use their Wayland emails and leave checked (which for most of my forms I uncheck) that box that says require users to be part of the Wayland domain (however it is phrased). I could then have the Form autorecord the username of each student, which would prevent some impersonation that began to take place as the game went on.
Overall, though, the GoogleForm proved a viable buzzer. I’ve included below both the form itself and the results of one or two questions.
September 26, 2012
With the advent of the 1:1, at least a couple of my students have been taking advantage of Word’s Notebook view. It’s a nice looking format with some features that seem to make it very useful. I’ve not used it myself, but from what I’ve seen my students do you can collapse and expand bullets (to save space by seeing less or see more), create diagrams / shapes, and demarcate sections (similar, it seems, to sections in Excel). I’ve included an image here of both the blank page and a page that one of my students used to outline her paper (reproduced here with her permission; thanks, SB-S).
September 24, 2012
I’ve written a good amount about Twitter here. Here (thanks, Steven Anderson / @web20classroom) is a good post for educators starting with Twitter, as it takes the perspective of one fairly familiar with Twitter but also one that understands teachers’ concerns going into using it. For instance, I’m finding myself at the point in my Twitter use where it’s difficult (really, impossible) to keep up with all of the tweets I receive.
September 21, 2012
I’d been toying with GoogleForms for a while last year, but didn’t have a lot of success. The link always seemed wrong or the privacy settings weren’t quite right, and I got away from them. But this year, for a number of reasons, the most prominent of which is the 1:1, I decided to return to give them a try and, to be honest, I’m glad I did.
GoogleForms is a quick, efficient way to collect information from students without having to go around to each of them or take time out of class to record it. Here are the ways I’m using them this year (with screenshots):
- Book Numbers. I teach three English classes, two of which have 8 or so books, so keeping track of those book numbers through the course of the year proved challenging. Now with a simple GoogleForm not only do I have a self-populating spreadsheet with all of my book numbers but the students complete it on their own rather than me taking class time to do it; it’s linked in their CMS. (One note: I had originally created the form with a field for each book, but then realized that students wouldn’t be able to return to their original form as they received books throughout the year, so in the end, rather than having a spreadsheet with [student name] and then [book name] for each book, I’ll have 8 [student name] rows with a title and a book #. Not ideal, but still better than the old way.)
- Contact Information. As a soccer coach, I’d spend part of the first practice’s stretching session passing a clipboard around and having the team fill out their contact information. I would then type it up and pass it around again to make sure I had read their handwriting correctly. Now, I have a GoogleForm linked to our page on the school’s CMS, and they took care of it on their own. I’m also using a Google form to collect sizes and customization for the t-shirts we’re ordering.
- Standardized Testing Sign-ups. I’m the Testing Coordinator at school, and this is my first year running PSATs, for which students register themselves with the school (as opposed to SATs for which students register directly with College Board). I’d had some experience with this as AP coordinator and it isn’t efficient (and that’s with the majority of AP takers set by virtue of taking an AP course). I was hoping for a more efficient way to sign students up. GoogleForms did it. Students now go to our testing website (http://www.whstesting.com) and follow the link to a GoogleForm. So far, I have over 160 sign-ups, all organized in a spreadsheet with me doing little other than checking it, answering some questions, and setting the form up. Much more efficient.
I’ve not quite reached the point of using GoogleForms for class; I aspire to that. But to see some nice examples of that, check out this post here.
September 20, 2012
Saw this link on Twitter (thanks, @kylepace) to a concise and clear explanation of a new iOS 6 feature that will benefit educators and parents by preventing iOS device users from leaving an app. Thank you, Apple.