From ZooidWiki

Contents 1 Using Wikis in organizations 1.1 What is a wiki 1.2 Where do they come from? 1.3 Visualizations 1.4 Problems solved 1.5 Quotes about wikis 1.6 Compared to other applications 1.7 How do they work 1.8 Creating a page 1.8.1 Hands on 1.9 Issues 1.10 Types of Wikis 1.11 Sample wikis 1.12 Mediawiki 1.13 Semantic wikis 1.13.1 Hands on 1.13.2 Tasks easy to hard 1.14 Problems solved 1.15 Using Semantic Mediawiki practically in organizations 1.16 Developing uses 1.17 Applications for organizations 1.17.1 Encouraging wiki use in organizations 1.17.1.1 Key concepts 1.17.1.2 Challenges

[edit] Using Wikis in organizations

[edit] What is a wiki

Hawaiian for "quick."

Classically - A wiki (pronounced /ˈwɪki/ WIK-ee) is a website that allows the easy creation and editing of any number of interlinked web pages via a web browser using a simplified markup language. (Wikipedia).

The simplified markup focuses on the simplest ways to create meaningful formatting and navigation. While the markup is designed so anyone can start with basic editing, it's still a major stumbling block to newcomers.

Usually wikis have a simple access model - the site is completely open for editing, some pages or locked, or the entire site is only available for writing and/or reading to a restricted group.

Culturally wikis try to emphasize the same level of access for everyone, though practically some levels of administration are required.

Wiki features are starting to merge with web-based content management systems to support features such as fine grained editing and access permissions and rich editors.

[edit] Where do they come from?

• Hypertext 1950s - 70s - Microfiche, http://en.wikipedia.org/wiki/Douglas_Engelbart (Computer mouse, Hypertext, Groupware, Interactive Computing)
• Hypertext 1990s - the web

• Culture - view source - http://www.whitehouse.gov/ (well designed) links to other media
• Transparency, open source & reusable data (web browsers & servers)
• Mass involvement
• Computer culture, facebook &c - http://www.facebook.com/video/video.php?v=37403547074&ref=nf

• Wiki like systems predate wikipedia hgttg, everything

[edit] Visualizations

• Vandalfighter / Beren
• Touchgraph

• http://www.akamai.com/html/technology/visualizing_akamai.html
• http://labs.digg.com/stack/
• http://labs.digg.com/swarm/

[edit] Problems solved

• Reference
• Codeveloped documentation - definitions
• Personal or workgroup notes/database
• Knowledge management (using categories)
• Share organized info without blasting everyone
• Message of openness - creative commons

[edit] Quotes about wikis

Stefan comments:

• a wiki is like play-doh or paper and you can make anything out of it. With a few formatting conventions i've seen wikis used for documentation, task and TODO lists, planning and timelines, bug tracking, tracking physical resources (where is this piece of equipment and has it been paid for yet) and customer relations

• it's faster and easier and safer than emailing around a bunch of word documents with "track changes" turned on

Helen comments:

• What makes me a Wiki enthusiast after tonight, however, is that I've now seen how wikis enable the management & generation of knowledge, and the planning & generation of work. Specifically, I think it's incredible that with wikis (or at least this particular wiki software), you are expected to generate the title (reference) for a link BEFORE you generate the content for the link. So if I'm tackling a multidimensional beast, even just a complicated grant, I can start with the main text, and put in links to appendix documents without having those documents in existence yet. In other words, it's a conceptual approach -- I LIKE!!

[edit] Compared to other applications

• More generalizable, less rigid
• Not really for communications (but see Blikis)
• With semantic wikis, they will become more like applications

[edit] How do they work

• Rows and columns, relational databases vs hypertext and wikis
• Easy editing, on the spot
  • Simple syntax, typically no rich text editor
• Typically write-able by anyone
• Full history is always there, can revert
• Use discussion tab for comments and questions

[edit] Creating a page

• From main – a few links per page
• Keep each major topic on its own page, or move to one when its time
• When editing other's work, be considerate of what they were trying to say

[edit] Hands on

• Create an account
• Create your user page with a heading and a link
• Fill in the link

[edit] Issues

• Not everyone has access to a computer / is comfortable using a wiki
  • Summaries
  • Currently don't compare to more specialized apps
  • Different workflows for different people -storyteller, coder
• Making information available
  • NPOV, substantiated
  • Culture is changing to be more critical, expect more
• Different wikis are better at different tasks
• Flagged revisions - editor culture
• Sometimes experimental, community involvement doesn't work

[edit] Types of Wikis

• Personal wiki (tiddly, bliki)
• Workgroup/intranet/project – third party and self hosted - http://www.semanticweb.com/article.php/3787986
• Public, unique topic focused
• Public, general topic
• Wikipedia

[edit] Sample wikis

• http://hlwiki.slais.ubc.ca - Health librarians
• http://www.wikihow.com/Main-Page
• http://www.dkosopedia.com/wiki/Main_Page
• http://www.wikipedia.org
• http://policywiki.theglobeandmail.com/tiki-index.php?page=Child+Nutrition+Briefing+Note
• http://www.childrenarewelcome.co.uk
• http://techpresident.com/blog-entry/wisdom-feds-internal-wikifying-obamas-open-government-directive use in government

[edit] Mediawiki

• Same software as used by Mediawiki, probably millions of other sites
• Well tested
• Well established bot programming interface
• Hundreds of useful extensions
• Not meant to be a CMS

[edit] Semantic wikis

• computers are stupid – parsing
• inference - http://smwxbig.zooid.org/wiki/Community, associate terrorism with whitehouse.gov!? , http://smwxbig.zooid.org/wiki/Community

• Properties – ad hoc and non
• Categories
• Queries and views

http://www.mediawiki.org/wiki/Extension:Semantic_Forms#Sites_that_use_Semantic_Forms

• Templates & Forms
• Facets
• http://semanticweb.org/wiki/User:Markus_Kr%C3%B6tzsch/Map_example
• http://semanticweb.org/wiki/User:Markus_Kr%C3%B6tzsch/Browse_tools
• http://www.discoursedb.org
• Extensions
• Different meanings for a word – hing:book, person:author - individual, person, personne
• Relating data sources - http://www.wandora.org/wandora/wiki/index.php?title=Main_Page

[edit] Hands on

• Put yourself in the Person category
• Add your birth date
• Add your postal code
• Add your favourite colour
• Views

[edit] Tasks easy to hard

• Use a todo annotation, view it in a query.
• Add the same interests as other people on user page, view on a graph
• Create a class with form and template using the Special page.
• Use a semantic internal object.

[edit] Problems solved

• Databases with finely and arbitrarily defined data, with forms and querying
• self contained applications like mapping, task tracking, diagramming with fine grained data integration between "apps"
• Connecting with other systems using semantic web standards

[edit] Using Semantic Mediawiki practically in organizations

• Start slow - use it for particular projects
  • Good as general web site
    • Restrict access unless the project is about open access
  • internal documentation, public development
• Make sure there are helpers and champions ready to 'garden' quickly, or use an extension like Flagged Revisions
• Use forms to make common tasks easier
• Always update documentation on the wiki rather than repeating
• Can always use other SMW sites as examples since their code is completely open, even locked pages

[edit] Developing uses

• Interface to mail, IM, twitter, etc - send a page update, todo or queries
• Interface to other systems using PHP, bots, XML, RDF

[edit] Applications for organizations

• Neighborhood knowledge - http://www.placeography.org/index.php/Bridge_Trail_Walking_Tour - add arbitrary knowledge
• Workgroup practices
• Codifying co-developed knowledge, getting people up to speed
• Analysis, references
• Link to other groups

[edit] Encouraging wiki use in organizations

• Introduce progressively, encouraging the idea of progressive learning
  • start with why wikis, wikipedia, the culture of wikis
  • good uses
    • sketch out idea with links
    • page management
  • show a few good sites - wikipedia
  • create account
  • edit home page, add headings, lists, a link
  • demonstration of formatting/layout, common.css
  • emphasize looking at markup examples
  • introduce idea of semantic, distinct content, resuse
  • few good sites - placeography, discoursedb
  • simple example of semantic use - birthday, show on timeline
  • simple example of a class - todo
  • facet search, narrowing down, copy and paste

• Find out what their real problems are
• find champions
• break wikis into sites "owned" by different people/communities
• Ease of hosting
• Don't pretend wiki can do everything, don't oversell
• Alternative to uploading document - good summary, link to original

[edit] Key concepts

• play-doh - for wikis
• structured
• wikipedia - well known
• built on mediawiki, millions of sites, thousands of extensions
• emphasize control - no database management, open source, users can create data or can lock it down, import and export data
• good opportunity to introduce and encourage adoption of creative commons

[edit] Challenges

• Working with conservative top level management
  • "this is already happening" - examples
• gaining critical mass