11 August 2010


Until recently my experience of wikis was limited to the use of Wikipedia (only ever as a consumer rather than as a contributor). Then a few weeks ago (after exchanged comments on Cam23 blogs), I became involved in the Cambridge TeachMeet. The TeachMeet Wiki has been a useful site for giving out information  - and receiving information from interested parties - at a time that suits those interested, without having to wait for replies from e-mails etc. It also means less duplication of effort - as the contributors put their details directly onto the site - complete with live links to their blogs. I have heard of the Library Routes Wiki before, but had not considered contributing - perhaps after Cam23 is completed would be a good time to give it a go (My career to-date will make it more of a scenic tour rather than a motorway journey... but watch this space!!)

I like the thought of using a wiki in the workplace; it would be very useful to have one at work to form a readily accessible repository in which to put all the procedures information. The one thing that has made me hesitate however is the issue of security. I would not wish to go down the public route chosen by Antioch University:- "This Wiki is public on the Web. Never put personal or security-sensitive information here ... All sensitive information resides in the library in private places."  - as this seems to negate the advantages of having all the information in one place. However it concerns me that even having a wiki that is nominally private, but hosted by a third party, in itself could be considered a security risk.

In conclusion I love the idea of wikis but I would want to look at them in much greater depth before using one for anything I was worried about others reading.

No comments:

Post a Comment