Put MediaWiki to Work for You

NewsForge (Also owned by VA) is running a short writeup on how to put MediaWiki to work for your organization. The writeup includes several addition tools that could be helpful in rounding out the overall package. From the article: " Imagine how useful it would be to have an online knowledge base that can easily be updated created by key people within your organization. That's the promise of a wiki -- a Web application that 'allows users to easily add, remove, or otherwise edit all content, very quickly and easily,' as Wikipedia, perhaps the best-known wiki, puts it. Why not bring the benefits of a wiki to your organization?"

Comments

worked for me

[bcrowell]

It worked for me. I teach physics at a community college, and our physics stockroom has hundreds of pieces of equipment that we need to keep a catalog of. The solution we tried before was that the lab technician kept the catalog in an MS Excel spreadsheet. The problem with that was that if someone other than the lab tech wanted to add something to the catalog, or document the fact that they'd moved it, there was no easy way to do it. Also, the only way to get access to the latest version of the catalog was to ask the tech for the latest (paper or electronic) copy. None of this worked very well, for example, in night classes when she wasn't there. I converted the catalog to a wiki, and I think it's worked fairly well. Nobody in the department was familiar with the concept, so they needed a little hand-holding. But even people who aren't comfortable with editing a wiki can at least understand that there's this web address they need to go to in order to find a piece of equipment.

Company wikis

[allenw]

Most of the experiences I've had with wikis inside our corporate environment have been mixed. A lof of folks (techie or otherwise) treat it more like a generic CMS rather than a hyperactive hyperlinking system. When they create a page, they make the assumption that it is their private page... so we end with page names like "Status". A lot of time is spent cleaning these up or the wiki becomes full of potholes.

Sure, user education would help here, but there is only so much one can do... especially in a company of 30,000+ users.

While wikis certainly lower the bar for producing web content, there really needs to be some sort of way to prevent users from doing things that they don't particularly realize are (overall) harmful. Or at least much better training tools.

Wikis are evil

[PietjeJantje]

I like wikepedia, but I don't like wikis. Your "knowledge base" is your web site or documentation section. If you add a wiki, I have two places to search for information, do I have to look in the docs, or in the chaotic wiki, where you won't be able to find it anyay? Wikis seem an excuse for laziness, just throw the information somewhere instead of making a structured, well designed web site or documentation section.

Mixed results with our intranet wiki

[ewg]

Our management wanted an "intranet" a few years back but had zero budget. My answer was JSPWiki on a Linux box.

The wiki has succeeded in a couple of notable areas. The photo directory page is critical for learning new faces on a rapidly growing staff. Another page has completely replaced sticky-notes that were formerly used to coordinate certain tasks among staff and interns. The IT department has a lot of miscellaneous documentation pages. A few other pages serve the function of an electronic bulletin board for staff scattered across two buildings.

Management was very concerned at first that staff would abuse the wiki, either by wasting time posting trivia or by outright vandalism. Neither fear has materialized.

The biggest failure of the wiki is the number of abandoned pages. They don't do any harm, but about a third of pages are derelict, with old information that the author obviously lost interest in maintaining. Having a wiki editor might solve that problem, but in practice it doesn't rise to the level.