FXFE

Horace

Three myths of enterprise wiki deployment

By Kathleen Lau | Feb 2, 2009
A Denmark-based analyst with research firm J. Boye said she's encountered an organization that, after implementing an enterprise-wide employee wiki, realized it didn't exactly have the right culture to bring it to life.
Discussions prior to the site launch debated whether employees should contribute anonymously or through profiles, and whether those profiles should include user photos, recounted Dorthe Jespersen. Ultimately, employees were allowed to contribute through profiles with pictures, she said, "but [the organization] had a conservative culture so no one actually wanted to make visible what they were working on right now."
Jespersen said the employees' concerns varied anywhere from harbouring concerns around writing about work that perhaps wouldn't be considered "real" work, or about work that they weren't supposed to be doing at the time, or even having fears of making spelling errors.
"Even small things, as how you decide to set up the design... that can actually have an effect on adoption," she said.
With the growing popularity of enterprise 2.0, many organizations are increasingly willing to grant employees a common platform upon which to collaborate and contribute and share ideas. Wikis are often touted as such a platform that is easily launched and to which employees will flock to contribute ideas, but Jespersen said they can prove difficult to get off the ground if not done properly.
One issue is the hype surrounding wikis or the blind faith with which they are approached, said Jespersen. "People often look to Wikipedia as a free form where everyone is contributing, and why could we not do the same with our organization?," she said, having observed wikis entering the scene to compensate for an intranet that has fallen to the wayside. But, she said, technology alone won't resolve that issue.
Jespersen lists three myths surrounding wiki implementation that might make some organizations rethink the expectations they've built around their platform:
Myth One: Wikis will motivate employees to contribute content.
It won't happen automatically that employees will freely contribute. Jespersen describes the "Empty wiki syndrome," or when a wiki is deployed without a clear purpose or is too general in its focus, resulting in a site with almost no activity.
It helps, said Jespersen, to appoint someone to manage the wiki, ensure there is structure like guidelines and a basic information architecture, and that it is launched with content already posted because "it's very hard to just react to this empty space for the user."
And, as Jespersen described, a conservative corporate culture that is not based in collaboration to begin with, will have to ensure its expectations are realistic when launching a wiki. If employees are expected to use the platform to critique each others work -- as they would normally do through e-mail chains and back-and-forths -- it can be a hurdle to openly critique content, she said.
Highly-successful wikis are often driven by IT-savvy employees, noted Jespersen, given the familiarity with technology and previous experience with wikis. But in general, those tasked with driving the project will be determined by the scope of the wiki, which could be either enterprise-wide or group level. The former, she said, will require a person like an intranet manager, whereas the latter can be managed by a member of each group.
Myth Two: Employees know how to contribute.
The concept of a wiki may be simple, but contributing content is not necessarily logical for casual users. Jespersen said some organizations prefer to refer to existing written policies around content creation that say, for instance, employees are responsible for the content they produce. But policies can be tricky considering the goal is to strike a balance between governance and structure and flexibility, said Jespersen, "but it's difficult not to fall into either extreme."
Some wiki-specific policies can include guidelines around creating pages that are easy to read by having a table of contents if the page is long, or having a naming system for links to ensure consistency.
Myth Three: Wikis will always provide the information employees need.
Although searchability is often a selling point of wikis, Jespersen said the reality is wikis are difficult to search through, unlike a content management system. Given there is little structure built into wikis, "it is difficult to structure this information to make it findable the next day even."
Content on a wiki can grow faster than the organization can keep up, she said, therefore the wiki managers must perform regular searches and quality checks of the content.
Overall, Jespersen suggested starting with a pilot so that the true purpose and scope of the wiki can be first ascertained before an enterprise-wide launch.

Horace

Xampp on WinXP - Open Garden

have just installed and got working Deki-Hayes on WinXp for a second time. I wrote down what I did this time so I wrote a tutorial that I think works well.

I recommend downloading the formatted Word doc from
http://wiki.opengarden.org/User:Abarras

Installing Deki-Hayes 1.8.1c on WindowsXP Pro using Xampp.
By: Andrew Barras
abadger AT bellsouth.net

Much of this guide is similar to PeteE’s guide located at http://wiki.opengarden.org/User:Pete...llation_(Hayes)

The only main differences are this one uses Xampp which greatly simplifies things. Also I have not had any luck installing Aspell yet so this guide leaves it out.

Part 1: Installations
Downloads required:

1. Xampp 1.6.3a win32 Basic Package
2. Deki_Wiki_1.8.1c_Hayes_source
3. ImageMagick-6.3.5-5-Q16-windows-dll
4. Dot Net 2.0 Framework

Disable IIS to free the required ports: (if not installed then skip this)

1. Go to All Programs->Administrative Tools->Internet Information Services (IIS) Manager.
2. If necessary, expand the Web server that you want, and then expand Web Sites.
3. Right-click the Web site that you want to change. (Default)
4. Click Properties.
5. Click the Web Site tab.
6. Change the TCP Port Number in the TCP Port edit box and change it to something other than 80. (20001 should be good)
7. Click OK to save the changes.

8. Go to All Programs->Administrative Tools->Services
9. Find IIS Admin.
10. Right click to bring up Properties.
11. Change Startup type to Disabled.
12. Press the Stop button if it is not grayed out.
13. Close those windows.

Installing the Dot Net 2.0 Framework

1. Double-click the installable file "dotnetfx.exe"

2. Follow the prompts.

Installing Deki-Hayes

1. Unzip the downloaded file. (Deki_Wiki_1.8.1c_Hayes_source)

2. Copy it to where you want your Wiki directory to be. Remember this location. (Ex. C:\deki-hayes)

3. Copy file mono.posix.dll
a. from C:\YOUR_INSTALL_LOCATION\src\redist
b. to c:\YOUR_INSTALL_LOCATION\web\bin

Installing Xampp

1. Run the installer
a. Check Install Apache as Service
b. Check Install MySQL as service

2. Press Install. If WinXP comes up with a security alert, roll your eyes, then press Unblock.

3. The installer will test all the ports for you.

a. If it says success then run the Xampp control panel when it asks you to.
b. If it says you have a problem, run xampp-portcheck.exe in the Xampp directory. See what is blocking the ports and turn off that stuff. (usually it is IIS)

4. When the Xampp control panel comes up it should say Apache Running and MySql Running. If either of these are not shown as running then you probably have a port conflict.

5. Keep the control panel open as we will want to restart Apache a few times.

6. Test if everything is working at this point by loading http://localhost/index.php in a browser. You should see a Xampp splash screen. Xampp, Php, MySQL, and Apache are installed and configured.

Install ImageMagick.

1. Use all the defaults to install it.

Copy Curl dlls

1. In order for Curl to work, you need to
a. Copy C:\xampp\php\libeay32.dll and C:\xampp\php\ssleay32.dll
b. to C:\windows\system32\

Part 2: Configuration

Note: There are several files of the same name in the Xampp directory (such as multiple php.ini files) so read carefully and open the right one.

Configure PHP and Curl

1. Open C:\xampp\apache\bin\php.ini

2. Set short_open_tag = On

3. Remove the semicolon from in front of extension=php_curl.dll

4. Save and exit.

Configure Apache.

1. Open C:\xampp\apache\conf\httpd.conf

2. Enable the following Modules by removing the # at the front of the line.
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so

The Virtual Host stuff needs to be added in a specific location or it will mess up.

1. Find this text: mod_mime_magic module

2. Immediately above that there is a line called . Right after that line add the following:

DocumentRoot "c:/deki-hayes/web"
ServerName deki-hayes

RewriteEngine On
RewriteCond %{REQUEST_URI} ^/$
RewriteRule ^/$ /index.php?title= [L,NE]

RewriteCond %{REQUEST_URI} !/(@api|editor|skins|config)/
RewriteCond %{REQUEST_URI} !/(redirect|texvc|index|Version).php
RewriteCond %{REQUEST_URI} !/error/(40(1|3|4)|500).html
RewriteCond %{REQUEST_URI} !/favicon.ico
RewriteCond %{REQUEST_URI} !/robots.txt
RewriteCond %{REQUEST_URI} !/dummy.php
RewriteCond %{REQUEST_URI} !/phpinfo.php
RewriteCond %{QUERY_STRING} ^$ [OR] %{REQUEST_URI} ^/Special:Search
RewriteRule ^/(.*)$ /index.php?title=$1 [L,QSA,NE]

ProxyPass /@api http://localhost:8081 retry=1
ProxyPassReverse /@api http://localhost:8081
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1

AllowEncodedSlashes On

3. Change the DocumentRoot above to show the path to where you are putting Deki-hayes.

4. Change the ServerName above to show the name of your Wiki server.

5. Find .

6. Add Allow from all right after Deny from all.

Restart Apache

1. Using the Xampp control panel, restart Apache. (wait a few seconds between stopping and starting it)

2. If you typed everything right, you should get Apache to say Running again. If it doesn't come back up, you missed a step or did something wrong. Try running the apache_start.bat file in the Xampp directory. It will give you more information about where it is failing.

Part 3: Running Deki-Hayes install

1. In a web browser type http://localhost/

2. The Deki install page now comes up. It should give errors about ImageMagick Identify and about Aspell but otherwise says you are OK to install.

3. Fill out the info about your wiki.

a. For Superuser password, there is none right now so leave it blank.

b. Make sure ImageMagick is set up correctly. (Identify is blank. Fill it in as below)

i. ImageMagick convert: C:\Program Files\ImageMagick-6.3.5-Q16\convert.exe

ii. ImageMagick identify: C:\Program Files\ImageMagick-6.3.5-Q16\identify.exe

4. Press Install Deki Wiki

5. Do the last commands at the end of the resulting install page. (you don't have to do them from the command line on Windows. Wink )

Note: the last step is to run the command mindtouch.host.bat, which opens a cmd window. DO NOT CLOSE THIS WINDOW. Leave it open. Minimize it if you want. This batch file starts the actual Deki server (which is written in .NET). You may be accustomed to closing command windows after running batch files - your instinct to do so will cause endless frustration, so don't do it. There are methods to running this batch file as a Windows service, one of which is covered here.

6. You should now be able to type http://localhost/index.php and get your Wiki up!

The way the captcha code is written it won't work on WinXp so we have to diable it. If not, we won't be able to create users!

I removed the captcha checking from my installation by changing the following:

In file includes\SpecialUserlogin.php

1. change line 336 from if (captcha::check()) to if (true) (line 352 in v1.8.2)

2. comment out ( put // at the front of the line) lines 522, 523, 524 and 587-594

(v1.8.2: lines 532-534, 596-604)

3. Save the file.

Horace

ThoughtFarmer - Beyond wikis: Knowledge sharing for the new enterprise

ThoughtFarmer combines structure and social networking with easy wiki authoring, helping companies share knowledge and strengthen community.

ThoughtFarmer's structured wiki approach is a 'best of both worlds' solution: the flexibility of a wiki, without the chaos. Even the least technical people in the organisation find it easy to use.

Miko Coffey, Head of Digital Media, NESTA

Working with ThoughtFarmer, we quickly built a clinical reference portal that physicians found easy to use and is easy to maintain.

Dr. Morgan Price, Medical Informatics Consultant
to Vancouver Coastal Health Primary Care IT Strategy

Horace

XWiki - Main - WebHome

come to XWiki

The XWiki project offers both a generic platform for developing collaborative applications using the wiki paradigm and products developed on top of it. All XWiki software is developed in Java and under the LGPL open source license.

Horace

MediaWiki - MediaWiki

MediaWiki is a free software wiki package originally written for Wikipedia. It is now used by several other projects of the non-profit Wikimedia Foundation and by many other wikis, including this website, the home of MediaWiki.

Use the links below to explore the basic site contents. You'll find some content translated into other languages, but the primary reference language for the whole site is English.

For general questions dealing with the software see the recommended possibilities of communication and maybe our support desk. If you have a suggestion dealing with this wiki, please visit the Forum.

About this site | About MediaWiki | Download | Help & Support

Horace

WikiMatrix / Integrated Wiki/Forum - Compare them all:

SMF (Simple Machines Forum) Authorization Modules for Dokuwiki:
http://www.web-threads.com/downloads/dokuwiki-smf.php

SMF/DokuWiki Integration: creates a topic for each article when the user clicks on the discuss button
http://wiki.splitbrain.org/wiki:tips:in … _smf?s=smf

PunBB Authentication for DokuWiki:
http://wiki.splitbrain.org/wiki:auth:punbb

How to integrate DokuWiki with vBulletin 3.5.X authentication
http://wiki.splitbrain.org/wiki:tips:in … etin_3.5.x

IPBWiki connects MediaWiki with Invision Power Board software: http://www.ipbwiki.com/IpbWiki_Features

List of sites running IPBWiki:
http://www.ipbwiki.com/Sites_Running_IpbWiki

What it takes to do an install:
http://www.ipbwiki.com/IpbWiki:IpbWiki_Installation

Example of the kind of threaded discussion you can have for each article:
http://www.ipbwiki.com/forums/index.php?showtopic=1140

IpbWiki Free Version:
http://www.ipbwiki.com/forums/index.php … showcat=13

PHPBB integration for Mediawiki:
http://www.phpbb.com/community/viewtopi … p;t=578123

VBulletin extension for MediaWiki:
http://www.mediawiki.org/wiki/Extension … ntegration

NuWiki (VBulletin with a wiki) and vbWiki (a VBuuletin/MediaWiki extension) Comparison
http://www.nuhit.com/nuwiki/comparison.html

SMF_Authentication: Authenticates users from Simple Machines Forum and automatic logs them in and out on MediaWiki. http://www.mediawiki.org/wiki/Extension … entication

Last edited by Ross (2007-10-31 13:37:21)

Horace

Confluence - Enterprise Wiki Software

Confluence – the enterprise wiki

Confluence is an enterprise wiki that makes it easy for your team to collaborate and share knowledge. Confluence - The Enterprise Wiki

Adding, sharing and finding content has never been easier.

These benefits come with all the additional features needed to make it a part of your business:

Enterprise security
Simple installation and management
Attractive, user-friendly WYSIWYG interface
Powerful tools for structuring and searching your wiki
Professional features such as PDF export and automated refactoring
An open API for extension and integration
Atlassian's Legendary Service
and much more...

Horace

Deki Wiki - MindTouch

Deki Wiki Overview

unlimited users
unlimited pages
no restrictions

$495

Basic

limited support

$2,495

Silver

standard support

$4,995

Gold

premium support

MindTouch Deki Wiki is a free open source wiki and application platform for communities and enterprises. Deki Wiki is an easy to use and sophisticated wiki for authoring, aggregating, organizing, and sharing content. Deki Wiki is also a platform for creating collaborative applications, or adding wiki capabilities to existing applications.

Why Deki Wiki?

Deki Wiki is an award winning and easy to use way to create, organize, aggregate, mashup and share information of almost any type. You will not find an easier to use and more affordable way to build a community, collaborate in a team, or simply share things like office documents, emails, videos, images, and more. In fact, Deki Wiki is free why not ';return false;" class="external" rel="external nofollow" target="blank" href="http://sourceforge.net/project/showfiles.php?group_id=173074&package_id=198184&release_id=534709" title="http://sourceforge.net/project/showfiles.php?group_id=173074&package_id=198184&release_id=534709">download it right now?It installs in minutes. Don't take MindTouch's word, let some recent testimonials inform your opinion of MindTouch Deki Wiki.

Warning: skip this paragraph if you're not geeky. Deki Wiki isn't just a really easy to use application. It's also a platform. Similar to CMS web frameworks like Drupal, Mambo, Joomla and DotNetNuke, Deki Wiki delivers a remarkably extensible platform, but it's a wiki in nature; therefore making it community-centric and significantly easier for end-users to participate. Also, it has a complete application programming interface (API) for programmers. We've actually built the entire application on our API. This means everything Deki Wiki can do can be accessed via the API. Moreover, with our innovative web-services extension model you can extend Deki Wiki in any programming language. If you're a programmer, you should investigate the MindTouch supported developer community at OpenGarden.org. Also, the Deki Wiki developer page provides a wealth of information.

Great Interface and WYSIWYG Editing

Just take a look at Deki Wiki (you actually are right now, this site is powered by Deki Wiki). What you'll find is that Deki Wiki is intuitive and easy to use. In fact, it's actually fun to use!! Edit a page. You'll immediately notice that Deki Wiki has a WYSIWYG, or rich text, editor similar to a light-weight word processor. There is no arcane or non-standard markup language. You can copy/paste from office documents or other web pages. Linking is as easy as selecting the text and navigating to the page or attachment you wish to link. You need not memorize the path or learn a new language. You'll find Deki Wiki to be very familiar.

Pages and Files

Creating pages and attaching files is just a click away. Users of Deki Wiki can attach documents and images to individual pages. Images are presented in an attractive image gallery. At a glance you one can see who edited pages or attached files, when it was done, and read a description of the action that is automatically generated or manually provided..

Nothing is ever lost in Deki Wiki. Every edit is tracked and versioned. Users can compare versions of pages. Similarly, file attachments are versioned. When a user links to a file the link will always point to the most recent version of the attached file. Likewise, if a user renames a page all links to this page will be properly maintained.

Permissions

Deki Wiki has one of the most advanced permission systems available. Deki Wiki administrators can make wikis public or private, anonymous or not. There is user groups support. Users can permission entire hierarchies to create private or non-editable workspaces or permission single pages. Deki Wiki has built in support for LDAP, Active Directory, Drupal, Wordpress, and Joomla.

Finding and Organizing Content

Deki Wiki provides many ways to organize content. Hierarchies allow users to define a taxonomy of pages. This is a very natural way to organize things. Everyone understands a family tree.

Deki Wiki also allows tagging. Tag folksonomies are wonderfully useful when using systems with multiple users. With Deki Wiki a user can use key word tags, date and time tags, and define tag categories.

As users add content to Deki Wiki the time the content is added is tracked. There are many ways to browse content chronologically. We call these chronologies. Users can follow recent changes chronologically throughout an entire wiki site, on a per page basis, or based on individual users' contributions. This makes it very easy to discover content and track what's going on in the wiki. Date and time tags also provide another way of organizing and finding information chronologically.

If users are especially interested in some pages they can create a watchlist of pages. With a watchlist it's easy to track topics of interest or pet projects.

Another of the many ways Deki Wiki is unique is that it comes with an enterprise strength search engine named Lucene. Lucene is developed by the Apache Foundation. Lucene is a powerful search engine that is employed by many high performance enterprise-class search tools. Deki Wiki uses Lucene to index all pages and most common file types. Finding what you're looking for in pages, files or tags is just a search away with Deki Wiki.

Subscribe! Deki Wiki generates RSS feeds in a number of ways. Users may subscribe to the entire wiki site, individual users' contributions, their watchlist, or the watchlists' of other users.

Find out more about Deki Wiki's features or learn more about it's benefits.

Horace

tikiwiki.org -- Home of TikiWiki CMS/Groupware : HomePage

Welcome to Tiki

TikiWiki (Tiki) is your Groupware/CMS (Content Management System) solution. Tiki has the features you need:

Wikis (like Mediawiki)
Forums (like phpBB)
Blogs (like WordPress)
Articles (like Digg)
Image Gallery (like Flickr)
Map Server (like Google Maps)
Link Directory (like DMOZ)
Multilingual (like Babel Fish)
Bug tracker (like Bugzilla)
Free (LGPL)

And much more...

all unified (like no one else)

Whatever you are looking for, chances are Tiki has it. Your search for the most feature-complete CMS is over.

Read the Top 10 Reasons to use Tiki, then get started with Tiki today.