You know what a wiki is “ A type of Web site that allows users to easily add and edit content and is especially suited for collaborative writing.” Source: Wikipedia http://en.wikipedia.org/wiki/Wiki
German 311 (Just by the way . .) Part Two . . Blogging in character Part Three . . Video the drama, and put it on YouTube.com Wikis are Not blogs which are Not Forums But there are blikis !! http://en.wikipedia.org/wiki/Bliki
Five key concepts . . Wikis RSS Aggregators Blogs Social Software Tagging
Case Three: TT701 2006 Part One . . Context: needed a quick overview of Adult learning theory. An entire document (20 pages) was loaded into a wiki and opened for comment USE: Sharing ideas and commentary
Implementation #1: Purpose One of the most fundamental things about making a wiki successful is having a purpose for using it . Although the wiki us very different from many other technologies, one great similarity it shares is that it needs to be used in response to specific “pain points” where knowledge construction and collaboration are not efficient. Once you know where it’s needed, the best way to start is to get everyone together who will be using a wiki and have a conversation to mutually agree on how it will be used, and establish it as part of the existing social structure of your group, team, or project. Provide some basic structure http://www.ikiw.org/category/wiki-uses/
Implementation #2: Agendas Once your group starts using the wiki, be firm about making sure people don’t drift back to earlier means of collaboration . For example, if you used to send out meeting agendas by email , and now you put them on the wiki and email a link to the appropriate page, you may get someone who protests and asks for the agenda by email. They may argue that it’s more work to get an email and have to link to a wiki page, instead of just having the agenda right in the email.
Implementation #3: Persist If this happens, I’d suggest responding that although it seems like an inconvenience now, it’s really only a temporary inconvenience that paves the way for several improvements . First is a reduction in email when people are using to going to the wiki and an email with a link to the meeting agenda wiki page is no longer necessary. The second is a further reduction in email when people need to edit the agenda and can do so directly on the wiki instead of emailing the person who sent the agenda. The third improvement is that now information is stored in a more archival, accessible, and secure format than email: if you were to lose your laptop or it’s stolen, email is lost along with it and this can compromise the security of sensitive information. However, if you’re using a wiki, that information is stored on a secure server and won’t be lost or compromised as easily. The fourth improvement is that once you start using the wiki for meeting agendas, it lays the foundation for further wiki use, like managing the tasks and projects that arise from the agenda. It’s this organic use that makes the wiki quickly become an indispensable tool for information and collaboration.
Implementation #4: Shared documents (eg Policies!!) Documentation, policies and procedures – kept centralised on a wiki – more efficient than constantly printing and distributing addenda to policies and rules, and vastly more efficient than reprinting and distributing entire documents when enough changes have to be made. So the lesson here is that in addition to being a great collaboration tool, wikis can also be incredibly useful for keeping information constantly up to date and immediately accessible. In addition to the efficiency of this, think of the cost savings and environmental benefit!
They want to contribute! They don’t want to be passive receivers of information. Why some people like wikis
Wiki technology enables collaborative knowledge gathering and “peer review.” Allows community-moderated, content, updated in real time.