A few years ago, I created a wiki called "Newton Free Library Teen Advisory Group", in conjunction with the creation of our new Teen Advisory Board. I thought it would be a great way for board members and librarians to collaborate on various YA projects -- a way to stay organized as we planned and executed ideas and programs. It was strictly to be used as an intranet, a private wiki. I used the wiki software Wetpaint (drawback of this software is the ads), which I found very easy to learn; here is the link:
http://newtonfreelibraryteens.wetpaint.com/
Generally, I feel I did a good job in my creation of the "scaffolding" for the wiki; I tried to think of every area in which we might like our TAB to collaborate, and I set up a page for it. I also posted our monthly meeting agendas and minutes on this wiki. Comments were enabled, and all TAB members were invited to be Writers. This wiki was a good idea in theory, but a failure in practice. Our TAB did not participate in contributing to the wiki unless constantly prompted (and even then, not much was added!). This collaborative, structured website was simply a place these teens were not inclined to go -- unlike Facebook, to name the most obvious social networking site they
do populate. And without the teens input, the wiki essentially was DOA.
I mentioned in my previous post two places where wikis can be used successfully: a workplace intranet, and as a current, collaborative website for conference-goers. Here is a slideshare presentation about Escondido Public Library's Wiki/Intranet (difficult to find a "live example" of such a wiki, as they are designed to be proprietary!):
Here is an example of a Conference wiki: Computers in Libraries 2010 took place in April; here is the
link to the wiki they set up. While I don't think this particular wiki was used as extensively as it might have been, you can see that it was "seeded" with pages for Announcements, Community (who are the presenters, bloggers, sharing rides, etc.), info about the conference's geographic area, tracking the conference on Twitter and blogs, actual blogposts about it, and so on.
On another important aspect of wiki creation, I found the following on a
blogpost from an Australian pharmaceutical company, JCintra, about
"content ownership", because after all, the content on the wiki
is its key asset:
"For many Intranet owners, the model for content ownership is a key point of focus. With JCintra, our philosophy (successfully so far) has been:
- If someone isn't willing to maintain a piece of content, it can't be that important to the business.
- We happily show people how to do things with the site, but we don't do it for them.
- Occasionally we highlight sections of the site on the home page, which is a great way to drive the defacto owners to clean it up a little.
- We encourage people to have high expectations for content on the Intranet. If something is missing, please report it to the appropriate area of the business, or better still, add it for them.
- The answer to verbal queries for many departments has become, "it's on JCintra". This reminds people to search first and ask later.
- In the end, the quality of content in an area is a reflection on the defacto department owner, not the Intranet itself."
And finally, an example of a good, working wiki is
Nancy Pearl's "Book Lust", billed as "a community for book lovers". There is lots there for a librarian to love!