Comments on: Five Key Differences between Wikipedia & Enterprise Wikis

By: Sean Radford

Sean Radford — Fri, 20 Nov 2009 09:36:57 +0000

As per point 1 I agree that Enterprise WIKIs are usually deployed based on project or department basis. However, I would like to stress that the Enterprise should make this information available to the whole organisation (given the correct access rights) as part of its ECM strategy – removing the continuation of information silos.

By: uberVU - social comments

uberVU - social comments — Thu, 19 Nov 2009 15:25:43 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by rob_giggey: article describing the difference between intranet and internet wikis http://is.gd/1seAv...

By: Kristi Kuhn

Kristi Kuhn — Wed, 11 Nov 2009 20:05:38 +0000

Enterprise wikis seem to be just for the company and workers, not the readers; while Internet wikis allow the readers to have more of an input into the content. Personally, I think the Enterprise wikis need a lot of security because it has work-related content and is important to the worker as well as the company. Internet wikis are wonderful because comments and information can be shared easily. The Wikitravel is a wonderful tool that I have discovered and love reading the different travel guides.

By: 【シルベ】　企業向けウィキ（Wiki）とソーシャルメディアのエキスパート » Blog Archive » Future Changes:Grow your wiki

Mon, 29 Jun 2009 05:34:14 +0000

[...] ここでは、主にエンタープライズ向けのウィキの調査、考察を行っており、中でもFive Key Differences between Wikipedia & Enterprise Wikisの調査は、エンタープライズ用ウィキを考察する際の資料としてよく引用されます。この他も、必要な機能の考察やカンファレンスの情報など、硬派で中身のある記事が充実しています。 [...]

By: Altre risorse sui wiki interni | Intranet Management

Altre risorse sui wiki interni | Intranet Management — Fri, 26 Jun 2009 15:43:01 +0000

[...] 5 fondamentali differenze tra Wikipedia e i wiki interni [...]

By: Two Major Trends in Wiki Software for Business Use

Two Major Trends in Wiki Software for Business Use — Tue, 14 Apr 2009 18:00:39 +0000

[...] 5 Differences between Wikipedia & Enterprise Wikis [...]

By: Words on a page » Wikis aren’t just for techies - they’re for writers, too

Mon, 13 Apr 2009 10:02:17 +0000

[...] Those words (or words to that effect) were spoken by wiki consultant Stewart Mader. And he’s right. Stewart was talking about wikis within a company, but what he said can definitely apply to a wiki that you have installed on your Web site. You can read more this here and here. [...]

By: Sanjiva Nath

Sanjiva Nath — Thu, 02 Apr 2009 01:06:08 +0000

There are some additional characteristics that make a particular wiki more pertinent to the needs of an enterprise:
1. Ability to integrate information from external data sources as well as to expose information to external tools and applications
2. Provision of templates (and forms) for consistent and easy data entry (without requiring every user to be familiar with the wiki markup)
3. Automated or easy cross-linking between wiki content
4. Reusability of content (without copying and pasting or manually linking it everywhere)
5. Easy and precise access to information
6. Integration with MS Office
7. Support for WebDAV

zAgile offers Wikidsmart for Confluence that extends it to provide 1-5 above. Recent releases of Confluence also have support for 6 and 7, as well as the items you mentioned above.

The open source product is available for download as well as hosted for an easy test drive. http://www.zAgile.com

By: Fünf Unterschiede zwischen Wikipedia und Unternehmens-Wikis

Fünf Unterschiede zwischen Wikipedia und Unternehmens-Wikis — Wed, 26 Nov 2008 16:41:39 +0000

[...] Artikel wurde im Original am 5. August 2008 unter dem Titel „5 Differences between Wikipedia & Enterprise Wikis“ von Stewart Mader veröffentlicht und von der //SEIBERT/MEDIA GmbH aus Wiesbaden ins Deutsche [...]

By: Stewart Mader

Stewart Mader — Fri, 08 Aug 2008 22:49:07 +0000

@MB Your latest points are right on target! Whenever I work with an organization on their internal wiki use, I advise them:

* To require names be associated with edits, because everyone should be able to take credit or be held accountable for their contributions.

* To make sure the structure of the wiki, i.e. the various spaces reflect the existing structure of the organization. As you say, people inside the organization should be able to rely on the idea that content in the “intranet network” space was authored by that team.

* The wiki should be a Magnet for information, so that people get used to the idea that it’s both the go-to place to find what they need, and the place to add new information others will need.

Stewart