Author Archive

Useful API for Firefox

posted: 8.28.06 by Nick Carbone

Why am I posting about a Firefox API on a teaching tips blog? Because it’s so useful for teaching, even though it’s not a teaching tool per se. The API is called Flashblocker–you can get it here:

It blocks Flash movies from playing automatically when you land on a page. For a lot of my browsing, and often when I’m showing sites in workshops or classrooms, the Flash movies are ads, and they do some pretty annoying things. Like move when I’m trying to read. I find movement to the side text that I’m trying to read distracting (you can tell I’m not 18, or 25, or 35 for that matter). But it’s also distracting sometimes when showing a page in a class or workshop. For example, consider this snippet of an image from the NY Times Online:

As you can see, the ad, with just an acccidental mouseover, expands to cover the text. That’s extremely annoying. If you’re in rush to get rid of the mouseover, it doesn’t take much (well it doesn’t take me much, me who is sometimes a mouse klutz) to click the space and then open the ad sponsor’s WWW site (in this case Evian, makers of over-priced water).

However, with Flashblocker, the same bit of page looks like this:

Flashblocker replaces the dancing flash ad with the f-icon you see the image. To see the ad–or any other Flash element on a page–all you have to do is click the icon and the spot is filled with the flash movie that was intended.

There are times, of course, when you might want to see the ads, or another Flash element. What’s nice about the API, is that it gives you a choice, and a little bit more control over your teaching and/or presentation space. And clear choices and meaningful controls, when you can have them, are friends to teachers.

And Lord knows, teachers can use friendly technology.

Comments Off on Useful API for Firefox
Categories: Teaching with Technology
Read All Nick Carbone

Student Advises: Don't Cite Wikipedia

posted: 8.19.06 by Nick Carbone

Soumya Srinagesh, a student intern at C|Net News, advises her peers not to rely on Wikipedia as a primary source.

This advice comes to the same end conclusion as that given by Wikipedia co-founder Jim Wales’s own advice not to use Wikipedia–or any encyclopedia–as a sole or primary source.

The usual back and forth in this debate is that Wikipedia can be edited by anyone, and that you might use an entry before it’s been vetted and re-edited by other Wikipedians for accuracy (or something closer to it). That’s the tack Srinagesh takes, and it’s legitimate enough. But Wales makes a larger point about the role encyclopedias should have in research. They’re meant to be starting places, not end places. If you take Wales’s point to heart, then the argument over Wikipedia’s accuracy is less important (though it still matters). Diligent students should in fact use it as a start and then seek out richer sources on the subjects they’re writing about. And they should reconcile any discrepancies they find in their further research. Was Wikipedia accurate, or is the other source accurate when facts are not in agreement? How will they know? What does the difference mean? What does a third source say? If they determine Wikipedia is wrong, should they go back and edit Wikipedia?

The process of leaving Wikipedia instead of ending there opens up a new view of the research process and the social negotiations that go on to determine what is fact and what isn’t.

But what’s really intriguing about Srinagesh’s piece is not the part about Wiki’s communal editing practices, but these two observations:

1. “Unlike search engines, Wikipedia searches do not bombard you with thousands of sites that have little or no relation to the subject you are researching.”
2. “Unlike traditional textbooks, Wikipedia articles do not require a trip to the library, but are available from the comfort of your home or dorm.”

On the first: Wikipedia as a search engine substitute, a guide entry into a topic instead of relying on search engines makes a lot of sense. I never thought of Wikipedia as a search engine before, but of course it is. It’s entries are a communal version of what tries to do. So guiding students to start at Wikipedia in much the same way they might start research with Google or Yahoo might be a good way to lead them to a wiser use of Wikipedia.

On the second: There’s a lot of comfort to be found in a library. Heck, on college campuses these days kids even wear pajamas to the library, how much more comfortable can you get? But the real comfort is having the library’s collection at hand. When researching, students will often come across sources that are only in the library. So why not go to the library and use a computer there and call up Wikipedia to get started if that’s what works, but then use its content to cull keyword ideas and subject search terms that can be used in the library’s online card catalog or databased journals collections?

The purpose of good textbooks is to guide students into their libraries, not to make it easier for them to avoid them. Besides, today’s libraries are more and more hives of communal learning, with technology centers, places for students to get coffee and to talk, collaborative workstations and group study rooms, and most important and useful of all, people you can talk to if you’re stuck: reference librarians. Who wouldn’t want to go to a library to do research? It beats sitting alone in your home or dorm. Grab some friends and go to the library, find a big table, spread out your stuff, and have both the whole Internet and the whole collection in the library at your disposal. Why have so little –a lone computer with an Internet connection by yourself in your dorm– when you can have so much to help you do research?

Comments Off on Student Advises: Don't Cite Wikipedia
Categories: Citing Sources, Finding Sources, Research, Working with Sources
Read All Nick Carbone