Three myths of enterprise wiki deployment

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.

How to: Disable all the external data connections included in a workbook in Excel 2007.

How to: Disable all the external data connections included in a workbook in Excel 2007.

How to: Disable all the external data connections included in a workbook in Excel 2007.

Solution Open the Microsoft Excel workbook. Click the 'Microsoft Office' button. Click the 'Excel Options' button. In the left pane, click 'Trust Center'. In the 'Microsoft Office Excel Trust Center' section, click the 'Trust Center Settings' button. In the left pane, click 'External Content'. In the 'Security settings for Data Connections' section, select the 'Disable all Data Connections' check box. Click 'OK'. Click 'OK'.

Details

Microsoft Excel 2007 is configured to protect worksheet elements from external threat such as viruses. If the worksheet is not protected properly, the malicious content can corrupt or damage the worksheet data. To protect the worksheet against external threats, you must disable all the external data connections included in a workbook.

To disable all the external data connections included in a workbook:

1) Open the Microsoft Excel workbook.
2) Click the 'Microsoft Office' button.
3) Click the 'Excel Options' button. (The 'Excel Options' dialog box appears.)
Screen: 'Excel Options' dialog box
4) In the left pane, click 'Trust Center'. (The 'Trust Center' screen appears.)
Screen: 'Trust Center' screen
5) In the 'Microsoft Office Excel Trust Center' section, click the 'Trust Center Settings' button. (The 'Trust Center' dialog box appears.)
Screen: 'Trust Center' dialog box
6) In the left pane, click 'External Content'. (The 'External Content' screen appears.)
Screen: 'External Content' screen
7) In the 'Security settings for Data Connections' section, select the 'Disable all Data Connections' check box.
8) Click 'OK'.
9) Click 'OK'.

Knowledge-Paks Online and Knowledge-Paks On Site Copyright (c) 2008 by RightAnswers, Inc. Subject to the terms set forth in the end-user license agreement. All rights reserved.

Details

restore ms sql 2008 db to ms sql 2005

How To Convert Database of SQL Server 2008 to SQL Server 2005?

Requirements

If you are trying to restore database backup of SQL Server 2008 to SQL Server 2005, you are bound to fail. Database backup of SQL Server 2008 is not compatible backward, you cannot restore it to SQL Server 2005. The following is a solution to convert databases of SQL Server 2008 to 2005

Step by Step Guide

1) Start convert wizard

Open SQL Server Management Studio2008. in 'Object Explorer', right click the database that you want to convert. Select 'Tasks' > 'Generate Scripts...'.

2) Next

Click 'Next'.

3) Select database and objects

Select the database that you want to convert, and check on 'Scripts all objects in the selected databases'

4) Convert Options

Set options:

'Script for Server Version' = 'SQL Server 2005' 'Script Data' = 'True' 'Scirpt Database Create' = 'True'     

5) Output Option

Select option 'Script to file', 'Single file' and 'Unicode text'.

6) 'Finish'

View summary and click 'Finish'.

7) Result

Now you got a complete database creation script with data. It can be executed on target database server.

8) Amend Script

Open the generated script in SQL Server Management Studio 2005. Find the following section and amend the path to proper data folder

    CREATE DATABASE [StockTraderDB] ON  PRIMARY  ( NAME = N'StockTraderDB',  FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\StockTraderDB.mdf ,  SIZE = 4352KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )  LOG ON  ( NAME = N'StockTraderDB_log',  FILENAME = N'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\StockTraderDB_log.LDF',  SIZE = 6272KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) 

9) Execute the Script

When finished, You should get converted database of SQL Server 2005

sidewiki test

test

in reference to: Activity - Fuji Xerox Far East Ltd. (view on Google Sidewiki)

How do I...Troubleshoot problems running updateWiki.sh from behind a proxy server? - Open Garden

How do I...Troubleshoot problems running updateWiki.sh from behind a proxy server? - Open Garden

How do I...Troubleshoot problems running updateWiki.sh from behind a proxy server?

• We have highlighted your search term http_proxy for you. If you'd like to remove the search term, reload this page.

Table of contents

No headers

updateWiki.sh uses the svn up command to get the latest dekiwiki bits. If your wiki is behind a proxy server it may fail. SVN allows you to set your proxy server like this:

nano /root/.subversion/servers

Then set these values in the [global] section

http-proxy-host = defaultproxy.whatever.com
http-proxy-port = 7000
http-proxy-username = defaultusername
http-proxy-password = defaultpassword

NOTE: This may not work if you're using a Microsoft ISA proxy server.

For more informaiton about configuring SVN options see this page:

http://svnbook.red-bean.com/en/1.4/s....confarea.opts

Unofficial ISS Linux Web Pages - Proxy Settings

Unofficial ISS Linux Web Pages - Proxy Settings: "Environment Variables

Some software, mostly command line based software, get their proxy settings from a group of enviroment variables.

http_proxy='http://wwwcache.ncl.ac.uk:8080'
https_proxy='http://wwwcache.ncl.ac.uk:8080'
ftp_proxy='http://wwwcache.ncl.ac.uk:8080'

export http_proxy https_proxy ftp_proxy

You can setup these variables automatically for all users by adding them to the file /etc/profile or the proxyenv files in /etc/profile.d/ depending on your distribution."

Upgrading Deki Wiki From 1.9.0 (Itasca) to 8.05 (Jay Cooke) VM Only - MindTouch Deki Wiki

Upgrading Deki Wiki From 1.9.0 (Itasca) to 8.05 (Jay Cooke) VM Only - MindTouch Deki Wiki

Upgrading Deki Wiki From 1.9.0 (Itasca) to 8.05 (Jay Cooke) VM Only

This guide assumes you are upgrading the MindTouch Deki Wiki VMWare-Certified Virtual Appliance from v.1.9.0 to v.8.05. If you are upgrading from an earlier version, please visit http://wiki.opengarden.org/Deki_Wiki/Installation_and_Upgrade to find your appropriate guide.

While the upgrade script does not affect the MySQL database and settings files, it is recommended in case a full reinstall is needed.

Back Up Attachments

Type the following commands to create the backup directory and back up your attachments:

# mkdir ~/deki_backup
# cd /var/www/dekiwiki/
# tar cvzpf ~/deki_backup/attachments.tar.gz /var/www/dekiwiki/attachments

Back Up Settings Files

Enter the following commands to back up the files that Deki Wiki uses to determine settings:

# cp /var/www/dekiwiki/LocalSettings.php ~/deki_backup
# cp /etc/dekiwiki/mindtouch.deki.startup.xml ~/deki_backup
# cp /etc/dekiwiki/mindtouch.host.conf ~/deki_backup

Backup your MySQL Database

Use the following line to back up the MySQL database:

# mysqldump -u -p wikidb > ~/deki_backup/wikidb.sql

If you did not change the default username and password, then it would be root and password for and , respectively.

Upgrade the Wiki

Type the following command to upgrade DekiWiki to the newest version:

updateWiki.sh

After that script has completed, go to the IP of your wiki and click on Tools, and then About to confirm you are at the latest version.

Rebuild the Index

In the wiki, click on Tools, then Control Panel, and then Site Settings.Click Rebuild Index to re-index the wiki.