Thing 15: Wikis

In exploring a few library wikis, the thing I found most interesting was the degree to which different libraries allow their customers to edit the wikis. The St. Joseph County Public Library, for instance, seems to allow only library staff to edit the wiki. [full disclosure: the library I used as a child] Customers can call or email suggestions, but really it seems to be the SJCPL's reference site.

The Library of Stevens Co. (WA), on the other hand, looks to have an open wiki policy. Thier intent seems to be to have a community resource hosted (and perhaps monitored) by the public library, but with content provided by their customers.

SJCPL's approach has its benefits: I imagine any staff member could add or update the site, which would make the staff more invested in the library's web site. With more strict oversight, the possibility of malicious or even just careless activity is reduced too. But this restricted way of wikiing flies in the face of the idea of a wiki as I understand it. If the idea is to democratize the information on a website, I would think the LSC wiki is the way to go. Yes, there is a lack of control. But simply looking at the two sites makes the benifits of the wiki way apparent.

The LSC site is robust, with great reading lists and local information. I imagine that both library employees and customers enjoy being involved in a project together. The community is invested in the success of the library in a new way. The library's catalog is linked to book mentions, so it's easy to move from something useful on the wiki to something useful at the library. Wikis are social internet at its best.