Thursday, March 20, 2008

Blog vs wiki

Blogs are solitary endeavours. You got something to say. Here's your forum. Someone might even read it. Good for digesting material for your clientele, keeping them up to date on whatever it is you think you've cornered the market on, good for announcements. I don't see this as hugely important in our library. We have firewall issues. I can only access my blog for this class through a VPN. So far, I'm finding the blogging thing very addictive, but I have a lot of regular work to do, so reading a bunch of blogs and then blogging myself just isn't going to happen, until my director tells me to do it, of course. Which she may do. She's been reading my blog. She's going to read this. Oh, dear, this is so public.

Wikis are communal. We all have something to say, and we can all edit for the good of the group. Good for groups for managing things like schedules, appointments, documents, lists; I haven't even begun to imagine all the possibilities. I think we could actually use a wiki in our library for vacation days, meetings, announcements, working on documents (we do nothing without everyone proofing!), putting up articles, videos, but I'm not sure we have any uses for them at the moment with our patrons. And again, that firewall issue. I created my wiki for my boarding barn. I may flesh it out and present it to a couple of folks at the barn to see what they think - right now they might just say, eh! we're used to looking at three different marker boards, two calendars, and trying to keep up with phone calls. I think it would take a strong directive from the owner/trainer to keep such a wiki up and running. And the boards would have to come down...

No comments: