This 2.0 tool is my favorite example to use when trying to talk about which 2.0 tools are useful to use and when. I have seen wikis used often in cases where there is no real need to take advantage of the most useful feature - the ability for multiple users to edit. In these cases, I wonder why a wiki was used - and I surmise it was only because the person or group wanted to appear current with the technology.
For example, the Dallas Library policies and procedures wiki linked to here - how many authors had access to editing this? Too many and its a mess, too few and why bother with a wiki at all?
The compliment here is that they are so easy people seem to create them regularly. The criticism is that we seem to latch onto them because they seem (or sound?) cool, not because they are the best tool.
When they are used in a situation where the best features contribute to the success of the project, they can be tremendous tools. The SJCPL subject guide wiki makes sense to me.
The best library application that I can think of would be a wiki for a reference desk. Organized well, this could include web links for subject areas similar to what SJCPL is doing, as well as the ability to update with current information, locally peculiar questions that get asked, difficult questions that might arise again, etc.
Made available for editing by all the librarians assigned to the desk, ideally it would create a kind of group knowledge base built directly from experience at the desk.
