Thing 16 - ScreenToaster

Since I couldn't get the embed thing to work, here's the URL for my ScreenToast: http://www.screentoaster.com/watch/stUEpWQEdIRFtZSFVZX1JaVldd

I had a lot of trouble getting the audio to work, but after some superhuman rescue attempts by Deb Friedman, I was ready to go for my 5th attempt at recording the same no-script how-to video. (So if I made mistakes or repeated myself, blame the repeated efforts.) By and large, however, I like this THING a lot! Now that I've successfully completed it, I can imagine making many more instructional videos to post to our website for new staff, for mini-lessons (how to do a mail merge, for example), how to set up your library account so that you can track your circulation, how to use SWAN to find a book -- and then how to get the library to order it for you -- and so on , and so on, and so on.

For classroom teachers, this could be a great teaching tool -- but for students, what wonderful practice in oral expression. Good for learning how to deliver information verbally (a Speech component of the English curriculum?), and also good for information technology skills -- how to "do" technology language and literacy. If they can teach it, they will know it themselves. I would limit the length of a video presentation - to teach how to be concise, and also so that the "teachers" don't lose their audience. So pre-planning (storyboarding, practicing, etc.) are important.

All in all, a good thing!

Thing 15 - Voicethread

Well, even though I'm commenting in my blog about Thing 15 in order, I actually made my Voicethread comments a couple of weeks ago, when Alicia posted this task. It IS cool. I experimented with commenting by drawing, typing, and "phoning in" my comments. It was fun to see what others did. It would be interesting to see whether this would actually be a good teaching (or learning) tool. Though it seems neat and collaborative, it seems there would be quicker ways to get fellow-learners to pool their knowledge. I liked the possibility for delivering a lesson online (as the art teacher did in the demo we watched), but a video might work just as well. It seems that Voicethread, just like Animoto, would be most effective if the content were minimized. Short and sweet and get to the point. Otherwise, even WITH the visuals and the audio, it seems to drag on too long without really GOING anywhere.

A tour of the library for new students might be nice -- to point out where they could go for different types of materials. We could add comments on how to find and use our catalog, where to find the biographies, where our "Book of the Day" and new books are displayed, and so on.

Seems to leave out the ELL students, unless you used a native language for the voiceover while typing the English -- or something like that. (too bad both modes of comments won't "play" at the same time!)

I will be fascinated to see if any teachers find a way to use this at RB -- please let me know if you do!

Thing 14: Wiki

Well, Alicia D., I think that (from looking at Welker's econ wiki) a wiki might offer more formatting opportunities than Google Docs. I think both equally invite collaborative content creation. I liked all the different ways that Mr. Welker set up his wiki -- he had obviously been AT it for a long time! and experimented with a variety of uses for his class. As you might recall, I thought that Weebly was somewhat limited in its layout options. It seems that wetpaint allows a lot of widgets, sharing among different sites such as FaceBook, Twitter, etc., and it INVITES viewers to participate in a way that a weebly website wouldn't. All in all, I think they are all more useful for teachers than our current Curriculum Page option, where the librarian usually sets up the page and posts it to the web. A wiki allows teachers to do their own updates regularly. And for organizing a course with student postings, chapter summaries and links to helpful resources, polling options, and so on, this wiki tool seems really helpful. I am going to set one up for our preparation for the School Board presentation. That way you, Susie, and I can all throw things into the mix and not lose ideas or actual paper in my mess of an office. -- Doreen F.

Thing 4: Google Docs / Calendar

We have already experimented with using Google Calendar in the library - for our shared calendars (trying to keep track of where everyone is supposed to be every day and every period is sometimes a challenge!). Unfortunately, we can't seem to get Noelle or Karen to the point where they can view the calendar, so Alicia and I have to update it and then print it out -- somewhat defeating the purpose.

The Tech Committee had toyed with the idea of using Gmail to replace our school's email - leading to shared documents and other "cloud computing" applications. BUT - - - this would lead to other restrictions, such as a diminished address book (dependent on users to maintain the link to the whole school, etc.), possible leakage to non-RB people for in-house announcements, etc.. We concluded that further study is warranted . . .

But Google Docs has definite possibilities in terms of shared editing of documents -- whether it be for tech planning, lesson planning, display ideas, committee activities, or whatever. I love the idea of not keeping track of which version I'm looking at, of not remembering what pile on my desk I put that thing I needed to do, etc. etc. It will be both fun and interesting to explore the use of this new tool in my professional life.