Monday, November 8, 2010

Wiki Wiki Wiki

Looking at some of the Wiki pages for this weeks training, showed the differences that wiki's can be used for and how complex (or simple) they can be.   This can be seen in both the design or content of the site.  The Montana History Wiki and Antioch University's Staff Training and Support Wiki  are quite simple in design but that does not mean the information available are.  They are both used for different reasons with quite detailed information but they don't need to be complex (fancy) in design. 

I found the clear link to be a writer on the site for Games and Public Libraries Wiki  and NSW State Library Readers' Advisory Services wiki  informative in stating not just anyone can change the information on the Wiki, so there is a feeling that you can trust what is put on the site.  The other sites that I looked at didn't seem to be as clearly stated as who could change content but did have a log in button on the page.

Before this week, I have had a bit of experience with wiki's, not just including Wikipedia.  A friend of mine created a Wiki site that was part of and followed a Superheroes (no relation to the TV show but the Champions system) Rolyplaying campaign. We put information about what was happened in each session and a bit of history about our characters on the site. With this wiki, only the players could change things on the site but everyone could see it.  This helped with following what had happened and gave us the ability to develop our characters and the world we were in but allowed out friends to see what was happening. This was just a fun campaign but the wiki help make it more fun.

Wiki's can easily be used by the libraries both externally and internally, but should have clear who can edit and comment on the pages.  If it is aimed to the public, a good idea that was on the Montana History Wiki site, was that if you would like to comment, you  can email to a email account and the comment may be then added.  This would be a good way to stop spamming of the site but still allow comments.  For protection of the site, I think that should be locked to staff only.

5 comments:

  1. I hear what you say, but i am still a bit funny about using wikis in a library situation.

    ReplyDelete
  2. I havn't got to wikis yet this time around, so found your post very enlightening. I do admit to being a bit of a fan of wikopedia and think wikis could be quite useful in a working context - hey I might just suggest it to a bunch of young people I work with and watch the shock!

    ReplyDelete
  3. I also think that perhaps a library wiki for the public might not be used that much but I guess you don't know until you actually have one or see if another public library has had many posts put on theirs.

    ReplyDelete
  4. I like your observation that wikis can make a project more fun.

    ReplyDelete