You want I should talk about Wikis?

Well, then. I will. I had to do a fairly extensive amount of research on wikis when we (the Computer Services department) were getting ready to create our own. From the back end, wikis are written in a few of the popular programming languages of the day. PHP, PERL, Ruby on Rails, etc. In many cases, they use a database back-end, such as MySQL, to keep track of their information. In essence, wikis are created to be shared repositories of information. They can be very helpful to keep facts, details, and processes clear. For many businesses, information retention can be a problem. Say Jill is your head of some technical aspect of the business. She leaves for a better job, and all you have to go on in regards to training the next person is a big file folder of hastily-written notes, most of which only tell half the story. The business has to, in many cases, re-invent the position and figure out a whole new set of processes.

Not with a wiki, they don't! If Jill writes down, in detail, the processes required to do her job, the next person can just sit down and read her articles. Sure, there will always be parts that don't make it in, but for the most part, the new person will "get it" at the end of the day. When processes change, the new person in the position can simply update the articles with the new info.

I think it'll be great for the library when we are able to field a wiki for the staff. It'll allow us to retain and codify so much more information. Besides, with the ability to search by keyword, we'll be able to find info much faster than wading through big binders. I hope that we are able to embed the Employee's Handbook and the Policies and Procedures manual into the wiki. I see that as a reason to create one, even outside of all the other benefits.

By the way, the CS wiki has helped a great deal. When we have a procedure that's outlined in the wiki (and remember to look), we don't have to wait for other staffers to come in before we dig into a project. It used to be, "Well, so and so knows, but he won't be back until Thursday." In general, if we keep up our documentation, that doesn't happen as much now. We use MediaWiki, the same engine that powers Wikipedia. It's pretty friendly, and has vast powers we have hardly touched yet.

That's the superfluous info for now.