Wikis in the Library

Wikis are one of my favorite Web 2.0 tools because they are so accessible and collaborative.  In the 90’s, if you wanted to make a page of information on the web, it involved HTML knowledge and some FTP knowledge, as well. Pages could not easily be updated and if a page moved or was changed, it would often mean broken links and dead-ends. Thankfully, with the invention of the wiki, individuals can create informative pages without any HTML knowledge. On top of that, they can easily create, edit, and change pages by anyone with access – not just the webmaster.

The biggest benefit for libraries to use wikis, as mentioned above, is that they allow individuals to create an informative page without having to know anything about web-design. Of course, knowing web-design certainly doesn’t hurt, but it is no longer necessary as it once was. This opens the doors to many people being able to share their information who might not have been able to before because of their lack of HTML knowledge. Wikis also allow anyone with access to edit, so one wiki can be maintained by several people (or by anyone). Since libraries are generally collaborative anyway, this is perfect for them!

There are many different ways libraries could use wikis. I could see a county having its own wiki with a page for each different public library within that county. One or two librarians from each different library could be responsible for maintaining their specific branch page and could use it to post timely information about their library – such as branch hours, events, and new features or additions. Libraries could also use wikis as a main page for all of their library information. For instance, a special library could use a wiki to explain all the databases it subscribes to, resources it provides, and staff members.

There is a really interesting wiki built by librarians for librarians called Library Success. It has links to all the various projects – including wikis – that librarians are using.  In the old days – as mentioned above – many websites existed like this that had a list of links about a particular topic. If someone wanted a link added or changed, they would have to contact the webmaster directly and wait for them to change it. If a link was broken or changed locations, only the webmaster could update the site. Thankfully, with this wiki, those one-person pages are a thing of the past. Anyone can edit or change the wiki as they like, which allows for the most up-to-date resource possible.

Wikis, however, are not without their drawbacks. For one, wikis can be too collaborative. Take the wiki mentioned above that anyone can edit. If someone wanted to, they could erase or deface the information on the pages. Thankfully, most wikis have the technology to revert to previous versions to help reverse blatant vandalism. However, this takes time and effort to maintain. The bigger the wiki is, and the more people that have access to edit it, the more of a problem this “over collaboration” becomes.

Another problem with wikis is that they take time and resources to set up and maintain. A wiki has to be hosted somewhere and the files, pages, and multiple versions take up space. There are websites – such as pbwiki – that allow anyone to set up a wiki without having a webpage. However, the wiki still needs to be maintained by someone or a group of people, which can be more effort than it first appears.

Overall, I think wikis are a great addition to libraries and the web in general. I like how it allows knowledgeable people to share information and collaborate with one another.